[cisco-voip] Unity External Transcoding

Pritchard, Jon Jon_Pritchard at adp.com
Tue Mar 28 10:49:12 EST 2006


I'm attempting to enable Unity external transcoding for g729 connections to offload CPU and improve voice quality.  I have a PVDM2 based DSPFarm with 80 transcoder sessions.  I have successfully disabled native transcoding on Unity and have verified external transcoding is in play when calling Unity internally (VM or AA) from a Region set for g729 relative to the Region Unity is in.   However, when external calls are routed to Unity from the g729 regions I get disconnected with what "sounds" like a codec mismatch.  

I compared the CCM traces (detailed/debug) of the successful internal calls vs. the failed external calls.  The successful calls showed the MediaResourceManager negotiating the transcoder connection and minimal MediaTerminatePointControl activity.  The unsuccessful calls didn't show a specific error but does show trying to push a G711ulaw payload during the MediaTerminationPointControl phase and no interaction with the MediaResourceManager to set up transcoding.

The gateways involved are 1760 H323 on 12.3(8)T4 and have both G711 and G729 codecs enabled via codec class in the dial-peers, pref 1 G711 and pref 2. G729.

The really weird part is the external connections have been and still are successful when Unity is running native transcoding with the rest of the configuration is the same.

Is it possible I'm missing something relative to MTP requirements?  MTP resource is currently limited CallManagers and is within scope of the MRGL for all devices, VM ports and gateways included.
 
Any insight you might have would be appreciated.

Thx,
Jon Pritchard
 



This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.



More information about the cisco-voip mailing list