10-18-2023 12:34 PM - edited 10-18-2023 12:36 PM
Hello Guys,
I have configured SIP Line from Service Provide on the 4451 ISR Router. Link is not getting registered.
blr-vg-6a-01#show sip-ua register status
--------------------- Registrar-Index 1 ---------------------
Line peer expires(sec) reg survival P-Associ-URI
================================ ========= ============ === ======== ============
00918069697600 -1 27 no normal
When i checked the logs i can see Router sending Registration Messages but in response getting "Out of Retries"
Attaching Logs and Configuration. Can someone suggest what could be wrong here ?
Sent:
REGISTER sip:10.60.72.59:5061 SIP/2.0
Via: SIP/2.0/UDP 10.55.41.206:5060;branch=z9hG4bK1C112B
From: <sip:00918069697600@10.60.72.59>;tag=13DAE0-73A
To: <sip:00918069697600@10.60.72.59>
Date: Wed, 18 Oct 2023 11:18:03 GMT
Call-ID: 94C3976-6CDC11EE-8003CE2A-D29D3BB4
User-Agent: Cisco-SIPGateway/IOS-17.6.5
Max-Forwards: 70
Timestamp: 1697627883
CSeq: 11 REGISTER
Contact: <sip:00918069697600@10.55.41.206:5060>
Expires: 300
Supported: path
Content-Length: 0
002699: *Oct 18 11:18:03.908: //-1/xxxxxxxxxxxx/SIP/Info/info/1024/httpish_msg_free: Freed msg=0x7FA7A7693D10
002700: *Oct 18 11:18:07.906: //65/000000000000/SIP/Error/act_sent_register_wait_100:
act_sent_register_wait_100: Out of retries
002701: *Oct 18 11:18:07.906: //-1/xxxxxxxxxxxx/SIP/Info/info/262144/sipSPIDecrementOverloadCount: Count:Local 0 Global 0
002702: *Oct 18 11:18:07.906: //65/000000000000/SIP/Error/ccsip_api_register_result_ind:
Message Code Class 4xx Method Code 100 received for REGISTER
002703: *Oct 18 11:18:07.906: //-1/xxxxxxxxxxxx/SIP/Info/critical/262144/ccsipRegisterClearCallCountZeroTimer: Clearing call count zero timer
002704: *Oct 18 11:18:07.906: //-1/xxxxxxxxxxxx/SIP/Info/critical/4096/ccsipRegisterStopCallCountZeroTimer: Uninitialized timer
002705: *Oct 18 11:18:07.906: //-1/xxxxxxxxxxxx/SIP/Info/notify/262144/ccsip_register_reset_dns_cache: CCSIP_REGISTER:: registrar 0 DNS resolved addr reset
002706: *Oct 18 11:18:07.906: //-1/xxxxxxxxxxxx/SIP/Error/sipDestroyContainerContext:
Corrupted/Freed Container=0x0
10-18-2023 01:30 PM
It looks like you’re having connections to both Tata and Webex Calling. As both uses registration it would be recommended and maybe even required to use tenant configuration for both. Try with removing/moving the Tata registration configuration to a tenant from sip-ua.
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