I'm setting up a Cube for my customer and i'm running into problems with incoming calls. Outgoing calls are working fine, my SIP trunks get registered but when I try to make an incoming call it just won't work.
When I do a debug ccsip message I can see that I receive a sip invite with my SIP username instead of the called number:
And in my debug voip dialpeer it's showing allso my username as called number:
*Oct 8 08:17:54.923: //-1/62C7FFCD8054/DPM/dpAssociateIncomingPeerCore: Calling Number=0562xxxxx, Called Number=90908358PXXX, Voice-Interface=0x0, Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE, Peer Info Type=DIALPEER_INFO_SPEECH
Is there a way that I can tell my cube that he doesn't have to look at the Invite sip:Username but to the TO: in my sip message? I have tried several methods for dial-peer destination-pattern, incoming called number etc. i've tried to configure the dial peer with asserted id pai, but none works.
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...