Hey Ryan
===Jabber=== No ccsip messages at the gatway - ccapi inout. At least that was the debug file sent to me. Your assumption is correct - a jabber user is dialing from inside of the network to outside. Check on the bearer capabilities. That is set. ===Gateway=== The device is not configured in CUCM as an H323 gateway. It is a SIP trunk pointing to the 2901 gateway if that makes sense. This is where I said on the gateway itself it is configured as H323, not MGCP. There are no SIP trunks involved at all. The only transport is the 23 channel PRI. This is where I was confused with how this configuration should be working. If there are no carrier SIP trunks, why would there be a SIP trunk configured to an H323 gateway (i.e. H323 statements in the router config, no MGCP)? I think your list of questions confirmed to me that this device should have been configured as an H323 gateway in CUCM, not a SIP trunk pointing to a gateway. You are correct there is no H323 integration. Thanks for responding so quickly. At least I know my line of thinking isn't out of line. Aaron ________________________________ From: Ryan Huff <[email protected]> Sent: November 1, 2016 2:18 AM To: Aaron Banks; [email protected] Subject: Re: Unusual configuration Aaron, == Jabber == You mention, "intermittent jabber problems .... high number of SIP register events ... call is not successful". Where are you seeing this, I'm guessing here but, ccsip messages 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). 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 (bearer-cap speech). You also mention that the gateway is configured as H.323; on the H.323 gateway device configuration page, ensure that "Retry Video Call As Audio" 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. == Gateway == 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? 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. Thanks, -Ryan ________________________________ From: cisco-voip <[email protected]> on behalf of Aaron Banks <[email protected]> Sent: Monday, October 31, 2016 7:30 PM To: [email protected] Subject: [cisco-voip] Unusual configuration 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. Aaron
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
