CUCM 6.1.5 and CUCM 9.1 Call Recording CODEC Issue
I have a call recording issue where if the CODEC agreed between an MGCP gateway and the IP phone is G711 call recording fails as it looks for an MTP (there are subs running XCODE in the MRGs for the devices in this scenario). The traces seem to suggest that there is mismatch between the agreed DTMF.
When the call between the phone and the gateway is G729 then call recording works fine and doesn't request MT resource.
SIP traces show that the recorder (Verint Impact 360) responds with a SIP OK which contains options for PCMA, PCMU, and G729.
Call manager traces show that as soon as the INVITE is sent to the call recorder from the CUCM the request for MTP resource begins (i.e. before any media options are presented and even before the 100 TRYING is sent back)
The region setting between the phone and the gateways, in the failure scenario, is set to G711 and link loss type is low loss. On CUCM 9.1 Ive set a CODEC preference list which I have tried g711 as the preference and then also G729.
The region setting between the phone and the gateway regions towards the region the call recording SIP trunk is in allows max. G711.
The question is, why when the call is set up using G729 there is no requirement for an MTP on the call recorded leg whereas when the call is setup with G711 then the CUCM looks for MTP?
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...