[cisco-voip] MTP resources Codecs mismatch and DTMF relay

[Ryan Ratliff]

Why not just enable 2833 on the gateway?

mgcp dtmf-relay voip codec all mode nte-ca

mgcp package-capability fm-package

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/gateways.html#wp1044075


-Ryan

On Sep 26, 2012, at 11:24 AM, Jason Aarons (AM) wrote:

I believe his OOB (MGCP)  to 2833 (SIP handsets) is using the MTPs, but not 100% sure, but a CCM Trace would show MRM and Media invoking MTP based on the SDPs.   I know an end to end sip (handsets and sip trunks) with2833 doesn’t need MTPs. I would considering switching from MGCP to SIP Trunk myself.
 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Eric Pedersen
Sent: Wednesday, September 26, 2012 10:59 AM
To: abbas Wali; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] MTP resources Codecs mismatch and DTMF relay
 
 

I'm pretty sure you'll always need MTPs with RFC 2833 because DTMF is carried in the RTP stream. Can you use KPML on your SIP trunks to the IVRs?
 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of abbas Wali
Sent: 25 September 2012 11:55 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] MTP resources Codecs mismatch and DTMF relay
 
Recently we had a major VOIP fault which was escalated to TAC. Whom also spent some good time before realizing that we were running out of MTP resources at busy times.
 
What was happening that calls coming on phones and as soon as the receiver was lifted, the called party was hearing a fast busy.
Initially we had to restart the whole cluster and it used to settled down.
 
In the end we have to increase the MTP resources in the Service Parameters from 24 to 48 for each of the nodes, since then this fault has gone away.
 
Just going back into recent past –we believed that this issue started after we enabled MTP resource requirements for the SIP trunks, who at that time were struggling with the DTMF relays. So by enabling it for the SIP trunks we got into contentions for the rest of the network.
 
My question is (and I have overheard somewhere) that if your cluster is configured properly, you will never require the use of MTP resources (or may be in a very lesser amount). Also I feel like some mis configuration on the SIP trunks which has forced us to get help from the MTP resources  to support the DTMF relays.
 
Below are some of the points which emphasizes my points
 
 PCM type for our E1 cards are set to A-Law but when we make an VOIP to VOIP call internally it shows the codec as ULaw. (so to me it looks like that we are using MTP to convert from A to U for incoming PSTN calls)
 For the DTMF –the gateways are configured with  mgcp dtmf-relay voip codec all mode out-of-band while some of the SIP trunks are set to RFC 2833. I believe these are two different modes which again requires MTP for translation.
 
I believe if we make the codecs even by forcing the CUCM to use A Law internally as well and also use one single mode for the DTMF relays then we should not require to increase the MTP resources.
 
 
Just to add we are using CUCM 8.5. we have some 7k phones. we have MGCP gateways. And SIP trunks to 3rd party IVR’s and another neighbour CUCM 7.
Any help will be appreciated. 
 


-- 
@bbas..



itevomcid
The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.
 
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120926/117499e3/attachment.html>