Using 'SetTransferLabel' command with H323 CVP deployment
We have a CVP 4.1comprehensive deployment using H323.
We have coresident Ingress/VXML gateways, a gatekeeper and a CallManager cluster.
In order to reduce the transfers between Ingress and VXML gateways we are planning to use the 'SetTransferLabel' command to make calls treated in the same VXML gateway as the originating Ingress gateway.
Is there any configuration that we should do in addition to the 'SetTransferLabel' command in CVP VBAdmin?
Is there any special requirements that we need to do?
Re: Using 'SetTransferLabel' command with H323 CVP deployment
Yes there is. If the transfer label is (say) 8111111111 then when a CVP warm transfer is called, you may have the system trying to send this label back to the originator when the originator is CUCM. In order to prevent this you should add your subscribers to the list of "setExcludeIPs" (I can't recall the exact VBAdmin setting, but it's something like that. You will find it).
This is important with H.323 but not needed with SIP.
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...