After working with TAC as P2 and loosing about 4000 calls we moved to Hardware MTP which lowered the call capacity significantly but complete resolve the MTP bridging errors. TAC did find anything conclusive and has opened a new bug on the IOS version we were running. <div>
<br></div><div>Looking through the callmanager traces we found G711 calls with different Packetization sizes (20/30). I am thinking this was causing the MTP setup failures. </div><div><br></div><div>We asked TAC about this after the hardware MTP were installed and operating correctly. One TAC engineer said that the should fail even with Hardware MTP unless we do some transcoding? We were not seeing this. Some calls would coming as MTP and other as XCODE even though the Gateway is set for MTP resources only. </div>
<div><br></div><div>Is it possible that the MTP is transcoding for the packetization mismatch? <br><br><br>
<br><br><div class="gmail_quote">On Thu, Jun 3, 2010 at 12:56 PM, Mike Lydick <span dir="ltr"><<a href="mailto:mike.lydick@gmail.com">mike.lydick@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
We are using a 3845 for software MTP for UCM to IP-GW calls. We are getting 20-30 successful SCCP connections but we are seeing Open Logical Channel failures and reports of drop calls. We are seeing the following error from debug sccp all:<div>
<br></div><div><div>sym_xapp_calleg_bridge_failed bridge failed for sess_id 5095</div><div><br></div><div>Has anyone seen or resolved this error?</div><div><br></div><div><br></div><div><br clear="all">Best Regards,<br><br>
Mike Lydick<br><br><br>
</div></div>
</blockquote></div><br></div>