3rd party SIP phone <--> Internet <--> SIP Proxy <--> LAN <--> CUCM
The SIP proxy basically terminates everything (REGISTER, INVITE, etc), including the RTP stream.
I can register the 3rd party SIP phone to CUCM and in CUCM and i can see SIP Proxy IP Address as the registered address of the phone.
Calls from the 3rd party SIP phone to internal Cisco or internal 3rd party SIP phone and vice versa work like charm.
The only (fatal) problem is i can only register 1 3rd party SIP phone to CUCM via this SIP proxy.
Since this SIP Proxy always use its internal IP Address and port 5060 (TCP) as its source of registration, CUCM sees multiple registrations for multiple extensions (users) come from a single IP and port, and rejects the second registration request.
It seems that CUCM binds a digest user to an IP address and port, therefore cannot accept multiple registrations from a single IP and port.
Can anyone clarify this? Or is there any way around this?
I'm using CUCM 8.6.2 and CUCM 9.X (both do not work).
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...