Using 'SetTransferLabel' command with H323 CVP deployment

Unanswered Question


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?

Thanks in advance.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)

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.




This Discussion