[cisco-voip] How to use G711 when call placed via CM H323 gateway

[Ryan Ratliff]

I think it's time to look at the CCM traces for the same call to see  
why CUCM isn't allowing g.711.

-Ryan

On Jan 7, 2009, at 10:47 AM, Andy Yerofyeyev wrote:

Ryan , thanks for reply
Note the outbound TCS only has g.729 in it.  This indicates there is  
no codec configured on the inbound dial-peer.  Also of interest is  
that the inbound TCS also only has g.729 so this is probably why your  
g.711 call fails.

Here is it :
Jan  7 15:01:47.920: H245 MSC INCOMING PDU ::=
       capabilityTable
         {
           capabilityTableEntryNumber 1
           capability receiveAudioCapability : g729 : 6
         },

Do you perhaps have MTP required set on the gateway and are invoking  
a g.729 only MTP?

MTP Required flag is UNchecked. If I check it call is connected w/729  
and wont connect if incoming DP restricted w/codec g711ulaw. I have 2  
software MTP configured , which belongs to same Region/DP/Location.

Unless CCM is just matching your TCS I don't know of a device that  
only supports one particular g.729 codec.




-Ryan

On Jan 7, 2009, at 10:10 AM, Andy Yerofyeyev wrote:

Ryan, appreciate your reply.

H.245 info gathered from gateway itself. Full version of H.245 asn1  
here : http://pastebin.com/f1529472e

CM configured with Location A (unlimited bw) , Region A (codec G711  
inside Region) , Device Pool A (<-Region A) , Phones and newly  
created H323 gateway assigned to location A and DP A.
If I don't put any restriction on incoming dial-peer on h323 gateway  
(cisco ,2811 , 12.4 ios) call succeed with g729 codec, if I restrict  
codec to only 711ulaw by using codec class call failed.


On Wed, Jan 7, 2009 at 9:59 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
The codec selection on the gateway is defined by the codec-class or  
codec command applied to the outbound/inbound voip dial-peer.  On the  
CUCM server  the maximum bandwidth used for a voice call between two  
devices is set by the region configuration.  Because the region is  
simply a max value, if one party in a g.711 region only supports g. 
729 then assuming the other party also supports g.729 the call will  
be set up using that codec.

Is the H.245 TCS info you supplied below from the gateway or the CUCM?

-Ryan

On Jan 7, 2009, at 9:51 AM, Andy Yerofyeyev wrote:

Hello ,

I'll appreciate if you can help me understand how codecs is selected  
and how to restrict gateway to use only G711 when call placed via  
H323 gateway.
I created H323 gateway , assigned gateway to same device pool and  
location as all of my phones , but when I place call thru this  
gateway I can see only g729 codec in H245 capabilities .

debug h245 asn on gateway itself shows about incoming call (from CM)
       capabilityTable
       {

         {
           capabilityTableEntryNumber 6
           capability receiveAudioCapability : g729AnnexA : 2
         },
         {
           capabilityTableEntryNumber 5
           capability receiveAudioCapability : g729 : 2
         }
       }

       capabilityTable
       {

         {
           capabilityTableEntryNumber 1
           capability receiveAudioCapability : g729 : 6
         },
         {
           capabilityTableEntryNumber 44
           capability receiveAndTransmitUserInputCapability :  
hookflash : NULL
         },
         {
           capabilityTableEntryNumber 45
           capability receiveAndTransmitUserInputCapability :  
basicString : NULL
         },
         {
           capabilityTableEntryNumber 46
           capability receiveAndTransmitUserInputCapability : dtmf :  
NULL
         }
       }

If I use Non-gatekeeper controlled intracluster trunk situation  
pretty the same. Just FUI , location bandwidth is Unlimited and 711  
codec configured to use inside Region to which phones and gateway  
belongs to. If call placed from one 7960 to anoter they use 711 codec.

If I restrict to use only 711 codec on gateway itself (by using codec- 
class on incoming dial-peer) call failed.







-- 
Best Regards,

Andriy Yerofyeyev CCIE #21607
http://www.linkedin.com/in/ccie21607

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090107/3a539a9d/attachment.html>