<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Aaron,</p>
<p><br>
</p>
<p>== Jabber ==<br>
</p>
<p><br>
</p>
<p>You mention, "intermittent jabber problems .... high number of SIP register events ... call is not successful".
<br>
</p>
<p><br>
</p>
<p>Where are you seeing this<i>, </i>I'm guessing here but, <i>ccsip messages</i> in the gateway debugs? When the Jabber client is attempting to make a call, I'm assuming your Jabber client is registered to CCM on the inside of the network and users are trying
to dial out for an audio call? Based on your description, it sounds like the Jabber client is presenting a video codec to a PSTN carrier on the other end of your PRI and the carrier is dropping the call like its hot (as PSTN carriers will).</p>
<p><br>
</p>
<p>If the above is what you're facing here; under the T1 voice port (voice-port x/x/x:23) set the bearer capabilities to speech (<i>bearer-cap speech</i>). You also mention that the gateway is configured as H.323; on the H.323 gateway device configuration page,
ensure that "<i><span>Retry Video Call As Audio</span></i>" is checked. Next, verify the regional relationship between the Jabber clients and the H.323 gateway is not allowing a session bit rate for video calls (or immersive). Lastly, ensure all CCM egress
paths for the Jabber client egress through the H.323 gateway and not any SIP trunks pointed at the gateway.</p>
<p><br>
</p>
<p>== Gateway ==</p>
<p><br>
</p>
<p>I'm a little confused here. In the second sentence you state the gateway is configured as H.323 however in the last sentence you state that you would have expected an MGCP / H.323 integration with CUCM Vs. a SIP integration; which leads me to believe there
is no H.323 integration currently?</p>
<p><br>
</p>
<p>Does the gateway peer with SIP service at all, or is it simply just a PRI/T1? If in-fact the gateway only has a PRI/T1 I would integrate that as an H.323 gateway into CUCM (with all the appropriate dial peers and bindings on the gateway) and verify that
all your CCM egress goes to the H.323 gateway and not the CCM SIP trunk pointed at the gateway.</p>
<p><br>
</p>
<p>Thanks,</p>
<p><br>
</p>
<p>-Ryan<br>
</p>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Aaron Banks <amichaelbanks@hotmail.com><br>
<b>Sent:</b> Monday, October 31, 2016 7:30 PM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Unusual configuration</font>
<div> </div>
</div>
<div>
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>I am supporting a customer with 2901 GW (PRI) and CUCM 11.0(2). The setup: SIP trunk from CUCM to the 2901 GW, GW is configured as H323 with a full 23 channel PRI. I have never seen this kind of set up before. Anyone on the list ever do (or see) this
setup before? Did you encounter any issues? I see intermittent jabber problems where a high number of SIP register events occur and the call is not successful. I would have thought the gateway would have been configured as either MGCP or H323 in CUCM.</p>
<p><br>
</p>
<p>Aaron<br>
</p>
</div>
</div>
</div>
</div>
</body>
</html>