I want to evaluate the VOIP module and need to know how you need to configure a CISCO router to support this.
I can't use the automatic configuration wizard because the routers are managed by our telecom provider.
Would it also be possible to measure between 2 IP phones, i now that it simulates a VOIP call between 2 "border" gateways but it would be nice to monitor between 3 end-stations ( IP phones ).
Can't be done unfortuanately. The phones are very light weight devices.
Andy
If you have switches that run a newer IOS revision (12.2 or greater), you can configure the IP SLA's on those devices.
I know that it can be configured when you have the correct IOS, but which commands do i need to set or is IP SLA responder the only necessray command ? )
Did you ever find a answer to your question? Please let me know. Thanks
Guys, if you add your devices into VOIP monitor sites list, but in the call paths section, click "Manual" a little help icon will appear at the top of the page, click this, it will drop down (in the manual configuration section) and show you the commands you need to put in.
For Ref they are
Apply the below steps to configure each device that needs to be configured for VoIP monitoring. The <OperationNumber> should be a number that uniquely defines a destination for a given source site. Steps to configure UDP Jitter operations:1.Router> enable2.Router# configure terminal3.Router(config)# ip sla monitor <OperationNumber>4.Router(config-sla)# type jitter dest-ipaddr <DestinationIPAddress> dest-port 17000 codec G711ULAW advantage-factor 05.Router(config-sla-jitter)# tos 1846.Router(config-sla-jitter)# exit7.Router(config)# ip sla monitor schedule <OperationNumber> life forever start-time now8.Router(config)# exit
Thanks
Matt
And I assume the <OperationNumber> must be unique per router/switch and assuming fully meshed a
<DestinationIPAddress>must be entered for each destination i.e.
1.Router> enable2.Router# configure terminal3.Router(config)# ip sla monitor <OperationNumber>
4.1.Router(config-sla)# type jitter dest-ipaddr <DestinationIPAddress#1> dest-port 17000 codec G711ULAW advantage-factor 0
4.2.Router(config-sla)# type jitter dest-ipaddr <DestinationIPAddress#2> dest-port 17000 codec G711ULAW advantage-factor 0
4.3.Router(config-sla)# type jitter dest-ipaddr <DestinationIPAddress#3> dest-port 17000 codec G711ULAW advantage-factor 0
4.4.Router(config-sla)# type jitter dest-ipaddr <DestinationIPAddress#4> dest-port 17000 codec G711ULAW advantage-factor 0
5.Router(config-sla-jitter)# tos 1846.Router(config-sla-jitter)# exit7.Router(config)# ip sla monitor schedule <OperationNumber> life forever start-time now8.Router(config)# exit
correct?
JB
On my understanding of it, you would configure a seperate IP SLA monitor for each device, with a seperate operation number, then in voip monitor settings you set the call path operation number with the number you have just configured. So you would be typing
#ip sla monitor (1)
#type jitter dest-ipaddr (your first responder) dest port 1700 codec g711ulaw
#tos 182
#ip sla monitor sched (1) life forever start-time now
#ip sla monitor (2)
#ip sla monitor sched (2) life forever start-time now
So on and so forth
Please someone correct me if I am wrong
Just for a quick update JB, my above post is correct, you set up a new operation number for each call path you are creating, in both directions. The way I have ours configured is if we have a site range, I will use that number and add 01,02,03 etc to the end. IE, site 10.0.10.0 will be 1001,1002,1003 operation numbers, site 10.0.11.0 will be 1101, 1102,1103 etc.
Hope this makes sense.
If the VoIP add on uses just the jitter option within IPSLA, can the destination be any host that responds to ICMP or does this need to be another IOS device with IPSLA rtr responder enabled?
Cheers
Steve
The target needs to be an IOS device.
Ok, but does this need to have IPSLA RTR enabled?
Sorry - I should have included - it does require an IP SLA responder on the target.