Can anyone explain the default behavior of CUBE in regards to caller ID in a SIP-to-SIP environment?
This is our setup: CUCM 7.x <----sip---> CUBE <----sip-----> Paetec SIP service
The recommended configuration from Cisco for Paetec is to use "no remote-party-id" in the sip-ua configuration. However, I should still be able to get named caller id in the FROM header. I see names being passed to us from Paetec, but CUBE strips the names in the TO and FROM headers of the INVITE message.
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...
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 discusses the bas...