06-26-2013 06:00 AM - edited 03-16-2019 06:05 PM
Hi,
I was carrying out some testing yesterday with our provider.
We have 2 routes out to their 2 sip data centres.
They took the primary route down so we could test that the backup route
to the secondary data centre worked ok in case of DR.
It worked - the call went through ok - but only after about 30 seconds of
trying the primary route.
Apparently there is a command to reduce the timer so that after only X seconds
the call will re-route to the backup route.
Does anyone know what that command is?
Regards
Dominic
Solved! Go to Solution.
06-26-2013 03:07 PM
good stuff guys. +5 each
Deji my friend I hope you are doing well.
Terry
06-26-2013 06:39 AM
You can tweak the number of retry and trying timer. Off the top of my head I think its 6 retries by default and timer doubling with each try.
Sip-ua
Retry invite 2
Timers trying x
Tweak above settings to get desired time.
Terry
Sent from Cisco Technical Support iPhone App
06-26-2013 06:57 AM
Thanks Terry - I'll have a dig around.
Regards
Dominic
06-26-2013 07:08 AM
Not a problem mate. Please rate the useful posts and if you have no other queries please mark the thread as answered.
Terry
Sent from Cisco Technical Support iPhone App
06-26-2013 11:45 AM
You may also want to consider SIP OPTIONS PING as a keepalive mechanism to busy-out the dial-peer when the connection is lost. Without this, the timer must expire for each call.
dial-peer voice tag voip
voice-class sip options-keepalive
Please remember to rate helpful responses and identify helpful or correct answers.
06-26-2013 01:45 PM
+5 to Terry..Always good to see on the forum...guess you have been busy
+5 to Jonathan..Love your posts
Dominic,
Default SIP settings won't allow dial-peer failover to take place. The default number of SIP INVITE retries is 6 while the initial TRYING timer is 500 msec. In you case when the call arrive:
Initial SIP invite request
1st invite retry (delay to retry: ~500ms) 150ms
2nd invite retry (delay to retry: ~1sec) 300ms
3rd invite retry (delay to retry: ~2sec)
4th invite retry (delay to retry: ~4sec)
5th invite retry (delay to retry: ~8sec)
6th invite retry (delay to retry: ~16sec)
Failover time to second UAS (delay to failover: ~32)
Note: Time delay increases using the formula (2xOld Time)
The total time to failover is 63.5 seconds
If you change your config to something like this
sip-ua
retry invite 2
timers trying 150
Failover will happen after 2 retries with a retry time of 150ms instead of the default 500ms
For more information please refer to this doc
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
06-26-2013 03:07 PM
good stuff guys. +5 each
Deji my friend I hope you are doing well.
Terry
06-27-2013 06:44 AM
Terry - thanks that has been a great help.
Regards
Dominic
06-27-2013 04:12 PM
Dominic not a problem, glad that helped.
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide