There are setting (system parameters) in UCM for advertise g729. These need to be disabled. <br clear="all">Best Regards,<br><br>Mike Lydick<br><br>
<br><br><div class="gmail_quote">On Wed, Jan 14, 2009 at 11:25 PM, Peter Slow <span dir="ltr"><<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Aman,<br>
you are correct regarding it being a resource/codec<br>
negotiation/dsp related issue with that cause code. Depending on your<br>
region configuration, you almost certainly needed transcoders in the<br>
MRGL assigned to the _gateway_ taking the inbound calls.<br>
<br>
The transcoder must always be physically co-located with the device<br>
doing the higher-bandwidth codec. in a case where regions dictate that<br>
g.729 is required between the CTI ports and the gateway, _both_<br>
devices might need transcoders, assuming that the CTI ports are only<br>
capable of g.711.<br>
<br>
If you have CCM traces (with h.245 message tracing enabled) from a<br>
failing scenario i'd be happy to read them for you.<br>
<br>
-Peter<br>
<div><div></div><div class="Wj3C7c"><br>
On Wed, Jan 14, 2009 at 10:50 PM, James Buchanan <<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>> wrote:<br>
> Hello,<br>
><br>
><br>
><br>
> Does your inbound CSS have access to the partition where the ports reside?<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
><br>
><br>
> James<br>
><br>
><br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Aman Chugh<br>
> Sent: Wednesday, January 14, 2009 9:47 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: [cisco-voip] UCCX with H.323 gateway<br>
><br>
><br>
><br>
><br>
><br>
> I have an issue where I am looking for ideas on what to do next. I have<br>
> inbound calls coming in to an H.323 gateway and going to UCCX . Calls do not<br>
> work , it rings twice and then disconnects. I have forced the codec on the<br>
> dial-peer to use g.711 using voice class codec , I have checked and<br>
> unchecked MTP on the H.323 gateway, ISDN disconnect cause code is resource<br>
> unavailable which indicates codec or media resource issue but I have an MRGL<br>
> with hardware transcoders assigned to CTI port group on IPCCX. As a<br>
> workaround I switched the dial-peer to SIP and now calls work. I am clueless<br>
> at this time.<br>
><br>
><br>
><br>
><br>
><br>
> PS - Cant use MGCP because I also want to use the gateway with CVP.<br>
><br>
><br>
><br>
> TIA<br>
><br>
><br>
><br>
> Aman<br>
><br>
> No virus found in this incoming message.<br>
> Checked by AVG - <a href="http://www.avg.com" target="_blank">http://www.avg.com</a><br>
> Version: 8.0.176 / Virus Database: 270.10.6/1891 - Release Date: 1/14/2009<br>
> 6:59 AM<br>
><br>
</div></div>> _______________________________________________<br>
> cisco-voip mailing list<br>
<div class="Ih2E3d">> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
</div>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<div class="Ih2E3d"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
</div><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br>