I have a problem with a sip trunk connected to verizon. We used this trunk to make external calls.
We use a CUCM with a trunk connected to a CUBE and it is connected to the service provider.
We need to connect to a conference service. When we mark the conference telephony number, the system asks us for introduce a code, for example 11111#. We don't have problem with that, we introduce the code with the keyboard Cisco ip phone and the conference system recognize it correctly.
The problem is in the next step. The conference system asks us to say a name an press #. We do it and the conference system don't recognize the # in this step. The company which provides us the conference service told us they don't see # in their traces.
We have tried it with a Avaya system and work properly. The Avaya system uses a primary to connect to PSTN.
I have attached the putty log with the debug voip rtp session named-event and the CUBE configuration.
Sincerely I can't understand this debug. Anyone know where can I find information about this debug?
We use dtmf-relay rtp-nte into the dial-peer.
The dial-peer which mach the conference number is 202.
We have asked to the service provide whether they can check what is the problem. They told me this.
Please be informed that the problem is caused by the your equipment (CUCM). The call is dropped, from the customer side, after we try to switch to G.711 caused by DTMF tones. Please check with your vendor to solve this issue.
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...