01-07-2016 11:05 AM - edited 03-17-2019 05:26 AM
Have a Call Manager Express and my SIP proxy provider is seeing failed registration attempts being from internal (non-DID) extensions. What could be the cause and fix for this. I assume it's not normal. My SIP proxy provider has said these failed attempts have blocked / firewall-ed off registration attempts from my IP.
In the below logs from the SIP proxy provider 1005 is an internal number with no DID associated. How can I prevent these from occurring?
Registration from '<sip:1005@did.voip.les.net>' failed for '76.97.XXX.XX:50251' - No matching peer found
Jan 7 12:05:47 sbproxy1 asterisk[27050]: NOTICE[27072]: chan_sip.c:26360 in handle_request_register: Registration from '<sip:1001@did.voip.les.net>' failed for '76.97.XXX.XX:50251' - No matching peer found
Jan 7 12:05:47 sbproxy1 asterisk[27050]: NOTICE[27072]: chan_sip.c:26360 in handle_request_register:
Thanks
Solved! Go to Solution.
01-08-2016 03:11 AM
Hi,
Please check the following discussions;
https://supportforums.cisco.com/discussion/9930651/avoid-pots-dial-peer-sip-register
https://supportforums.cisco.com/discussion/11337566/pots-dial-peer-trying-register-sip-registrar
- Vivek
01-08-2016 03:11 AM
Hi,
Please check the following discussions;
https://supportforums.cisco.com/discussion/9930651/avoid-pots-dial-peer-sip-register
https://supportforums.cisco.com/discussion/11337566/pots-dial-peer-trying-register-sip-registrar
- Vivek
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