we have a mixed environment of combo IOS ingress/vxml GWs and some that are separated. It is a smaller deployment. Wanting a standard routing mechanism, what is the best way to route with CVP/ICM comprehensive model in an H.323 environment
- by customer (associating lables to customers)
- by using sigdigits/settransferlabel (routing with tech prefix in the GK)
we have not been successful using muliple customers under the customer instance. Just won't throw back the right label.
Using the sigdigits method, we have issues trying to use redundant VXML GWs (primary and secondary). We can get the label back to the GK and route to the primary VXML GW, but if that primary VXML GW is down, how do you get the call to the secondary VXML GW? We dont want to load balance the VXML GWs, b/c they are spearated between two data centers with a high speed pipe between them....so they are registered with different tech prefixes..
You want to share ICM/CVP with multiple customers? The standard way is NAM with multiple CICM's and CVP is on NAM, each customer has own DN's and scripts, the queue label can be the same, when ICM script triggers this label, CVP sends calls to VXML gateway by this label together with external script name and media file names, so VXML gateway can still play different prompts upon script's instruction.
For the question on how GK sends to secondary VXML, zone prefix with priority.
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...