01-09-2020 12:33 PM - edited 01-09-2020 01:31 PM
we have CUBE which is directly connected to the internet and it is configured with SIP trunk. The SIP trunk was working fine till yesterday but all sudden SIP trunk got unregistered. When we check the logs and had troubleshooting session with TISP, we observed that CUBE is sending a register message and TISP responding back with 401. But on our side, we do not see the 401 messages in CUBE sip logs. When we turn on packet capture on the router interface, those packets show up in packet capture.
It looks like some process in CUBE is discarding 401 packets coming from TISP. As CUBE is not responding to 401 requests from TISP and not sharing credentials with TISP, the SIP trunk is not getting registered.
Kindly guide us on how to fix the issue.
Thanks in advance
01-09-2020 06:45 PM - edited 01-09-2020 06:46 PM
Hi,
As as add-on, I do see few software bugs related to similar issue. It may be worth to check if workaround in the software bug can resolve your issue.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCui97039
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtt43848
01-10-2020 06:33 AM
Here is my reply
01-10-2020 07:50 AM - edited 01-10-2020 07:52 AM
I think we found out the issue. We are hitting with bug CSCuy82008. When I remove the NAT configuration on WAN interface, the SIP trunk register. We are planning to move the NAT on another interface.
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: