Seems the cancel is coming from CUCM side and end the call. I would probably run a Trace SDI on the CUCM as well. Reason: Q.850 cause = 3 text = "no route to the destination.ĭo you have any hint for me where I can troubleshoot further? It's a question MCU or CUCM or VCS? Record-Route: / * / SIP transport = tls LR > If I spent a glance in the VCS, I see the appeal as active and connected.Īlso, I traced the call made by the VCS in debug mode. In the Cisco Jabber client I never receive video or audio of the MCU AA - it looks like the call's not connect. The MCU is registerd with / * / on the VCS - it's self attandant. In venture capital, there is a transformation for the 8099 dialed. In the CUCM, there is a Routepattern who translated the «Called Party Number» number = 8099 (this is the SIP Trunk for VCS). If I make a call my Client of Jabber Cisco SIP call has failed.
In our Videoinfrastructure, there is a little problem with cisco jabber client registry on the CUCM to our MCU.
CUCM (Cisco Jabber) - VCS - MCU (failed appeal of SIP - SIP)
0 kommentar(er)
