I have vcs ver 7.x with h323 endpoints registered. I also have cucm ver 8.6 with jabber registered to it. I am trying to setup an integration between VCS end CUCM. I have configured everything..Setup cucm as a neighbour, setup transforms and search rules. I can succesfully call from Jabber to codecs, but when I try to call from Codec (c60) to Jabber I get internal server error...... I enabled diagnostic loggin and here is what I see...
After the endpoing sent a ARQ, VCS does a seacrh and sends a RIP then sends the ff:
Try the call as a SIP call from the C60 to the CUCM registered Jabber client. Curious to know if that will work.
Also, see the attached VCS topology diagram named VCS_ZONES.jpg I am a visual learner and must have a topology diagram to understand the many platforms that I support. Additionally, this documentation makes clients VERY happy as they have a reference they can always refer to.
Newly created Zones and Subzones have, by default, two links. One link to the DefaultSZ and one link to the TraversalSZ. The names of these links are in the format "Zone00XTo"New Zone Name" where X is a number determined by how many zones and subzones have been previously created.
I just created a zone named "New_Test_Zone" and it's two newly created links, coincidentally, were Zone007ToDefaultSZand Zone007ToTraversalSZ. This means that I had previously created 6 zones. You can see those 6 zones in my topology diagram.
I recommend renaming your default link names so that you can readily identify them. You can then easily sort by the "Name" column header in the VCS Configuration >> Bandwidth >> Links page. See the attached file VCS_Zones_1.jpg.
For example - I just made a SIP to SIP call from an VCS registered MX300 located in the NY1 Subzone to my CUCM registered Jabber client located in the CUCM Zone. To find it's path - locate the call details by clicking the "Local call serial number" hyperlink that can be found in numerous ways:
From Status >> Calls >> History - find the call and click the hyperlinked "View" in the far right of the screen:
While looking at my attached VCS_ZONES.jpg topology diagram - read the following explanation:
NY1 - this is subzone where the MX300 lives based on my Subzone membership rules that are based on source IP subnet of the codec
SubZone_NY1_To_DefaultSZ_Link - this is one of the 2 links that were created, by default, when I created my NY1 Subzone
DefaultSubZone - this is simply the name of the Default Subzone
Zone_CUCM_To_DefaultSZ_Link - this is one of the 2 links that were created, by default, when I created my CUCM Zone
CUCM - this is Zone where my Jabber lives
So with my topology diagram and renaming suggestion - you should be able to easily build a topology diagram for your environment - make a test call and visually understand why the call took the following path:
CUCM US -> Zone004ToTraversalSZ -> TraversalSubZone -> SubZone004ToTraversalSZ -> uk
CUCM US - this is the zone where you jabber client lives
Zone004ToTraversalSZ - this is the default link that represents the link from your CUCM US zone to the Traversal Subzone
TraversalSubZone - this is simply the name of the TraveralSubZone in all it's glory
SubZone004ToTraversalSZ - this is default link that represents the link from the TraveralSubZone to your SubZone004
uk - this is the Subzone where you C60 lives
I would rename your links as follows:
Zone004ToTraversalSZ ---- to ---- Zone_CUCM_US_TO_TraversalSZ
SubZone004ToTraversalSZ ---- to ----- SubZone_UK_TO_TraversalSZ
Good luck and thank you SO much for your amazing help on this forum. My little contribution PALES to the number of people you have help. It is greatly appreciated!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...