02-10-2010 07:59 AM - edited 03-21-2019 02:09 AM
I have found that in configuring the UC500s, if I make a change to the Internet connection (even the SA500s on the WAN side of the UC500s), that it breaks the connection to the SIP trunk (which is not a surprise). Is the UC500 set to retry the SIP registration, and if so, how often?
In my typical deployment scenario, the Uc500 will likely be up and running prior to our Internet connection being established. I would like to be able to have the Uc520 keep trying to register (frequently) until registration occurs. If a break occurs, to attempt to reregister frequently. Is there a way to do this in CLI?
Thanks,
Seth
Solved! Go to Solution.
02-10-2010 12:27 PM
I think thats the place....do a ? and see what it offers, but again, this is the timeout we suggest for registration. I am not sure the S.P. has its own value. In fact, look at the 200 OK and llok what they say..... Hmmmmm.... 300. SO our periodic refresh works for this..... I think you dont have to change anything....
Steve
02-10-2010 01:32 PM
Seth - there is a slight twist to this - there is a REGISTER refresh timer (that Steve references) which is negotiated between UC500 and the SIP registrar as well. So even if you configure this on the UC500 to a lower value, it may not be honored by the SIP registrar and this may not help. Would talk to your SIP provider on this.
Another note, if the WAN is down & above registration refresh timer has expired, the UC500 retries the SIP REGISTER 6 times as default, at intervals of
0.5 sec, then 1 sec, 2 sec, 4sec, 4sec, 4sec. But if all of REGISTER fails, UC500 seems to wait for about 2 minutes and then retries again.
This last 2 minute timer is not configurable.
To restart registration instantly the best option (today via CLI, something we are looking to add to CCA):
sip-ua
no registrar
registrar ipv4:x.x.x.x
02-10-2010 12:07 PM
in the CCA Monitor Window, there is a SIP Trunk Status.
The top left window shows the registration status and countdown to the next registration for all DIDs
Looks like every 236 seconds we reregister.
CLI = 'sh sip reg status'
UC540#sh sip reg status
Line peer expires(sec) registered P-Associated-URI
============ ============= ============ =========== ================
6783979422 20056 206 yes
6783979423 20055 96 yes
6783979426 20016 3 yes
UC540#sh sip reg status
Line peer expires(sec) registered P-Associated-URI
============ ============= ============ =========== ================
6783979422 20056 205 yes
6783979423 20055 95 yes
6783979426 20016 2 yes
UC540#sh sip reg status
Line peer expires(sec) registered P-Associated-URI
============ ============= ============ =========== ================
6783979422 20056 204 yes
6783979423 20055 94 yes
6783979426 20016 1 yes
UC540#sh sip reg status
004222: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:sipconnect-fca.atl0.cbeyond.net:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.75.104:5060;branch=z9hG4bK79951379
From: <>>6783979426@sipconnect-fca.atl0.cbeyond.net>;tag=81C26EE8-4A9
To: <>>6783979426@sipconnect-fca.atl0.cbeyond.net>
Date: Wed, 10 Feb 2010 20:05:32 GMT
Call-ID: 55642996-1E911DF-8002F1E3-A7435E5E
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1265832332
CSeq: 10195 REGISTER
Contact: <6783979426>
Expires: 3600
Supported: path
Content-Length: 06783979426>
004223: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.75.104:5060;branch=z9hG4bK79951379
From: <>>6783979426@sipconnect-fca.atl0.cbeyond.net>;tag=81C26EE8-4A9
To: <>>6783979426@sipconnect-fca.atl0.cbeyond.net>;tag=aprq33sidp2-i1um2t000o96d
Call-ID: 55642996-1E911DF-8002F1E3-A7435E5E
Timestamp: 1265832332
CSeq: 10195 REGISTER
Contact: <6783979426>;expires=3006783979426>
Line peer expires(sec) registered P-Associated-URI
============ ============= ============ =========== ================
6783979422 20056 199 yes
6783979423 20055 89 yes
6783979426 20016 235 yes
UC540#
But notice the bold above?
in CLI I see this (which you can carefully adjust)
sip-ua
registrar dns:sipconnect-fca.atl0.cbeyond.net expires 3600
But I am not sure 'we' determine the expiration?
Nonetheless, we send them every 236 seconds.
02-10-2010 12:16 PM
Thanks Steve,
To adjust those values, would I issue these commands:
config t
sip-ua
registrar dns:sipconnect-fca.atl0.cbeyond.net expires 3600 (change this value to whatever value I would like)
or is it adjusted elsewhere?
That is very helpful.
Seth
02-10-2010 12:27 PM
I think thats the place....do a ? and see what it offers, but again, this is the timeout we suggest for registration. I am not sure the S.P. has its own value. In fact, look at the 200 OK and llok what they say..... Hmmmmm.... 300. SO our periodic refresh works for this..... I think you dont have to change anything....
Steve
02-10-2010 01:32 PM
Seth - there is a slight twist to this - there is a REGISTER refresh timer (that Steve references) which is negotiated between UC500 and the SIP registrar as well. So even if you configure this on the UC500 to a lower value, it may not be honored by the SIP registrar and this may not help. Would talk to your SIP provider on this.
Another note, if the WAN is down & above registration refresh timer has expired, the UC500 retries the SIP REGISTER 6 times as default, at intervals of
0.5 sec, then 1 sec, 2 sec, 4sec, 4sec, 4sec. But if all of REGISTER fails, UC500 seems to wait for about 2 minutes and then retries again.
This last 2 minute timer is not configurable.
To restart registration instantly the best option (today via CLI, something we are looking to add to CCA):
sip-ua
no registrar
registrar ipv4:x.x.x.x
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: