Hi Geoff,

here's what i'm trying to achieve. I have an ipcc deployed in a company's HQ, and branches where ingress and vxml gateways are deployed on the same 2821 router. so the call hits the router at the branches and gets transfered to HQ for call routing and IVR processing (using a voip dial peer). I need a specific label to be returned based on a dialed number on ICM. to be able to send the vru leg to a specific vxml gateway. Hope this explains the scenario.

thanks in advance,

This is a classic "branch office" deployment, where the voice gateway at the branch is a combined ingress-vxml gateway.

We want the VRU leg to run on the same gateway as the incoming call.

If we have a number of gateways and put static routes in the SIP Proxy for the VRU transfer label (say 8111111111*) then the proxy will round robin the SIP INVITES across the set of gateways. Thus we cannot control which gateway the VRU leg will go to. Sometimes it will be correct, and run on the ingress gateway - and most of the time it will be incorrect and run on the wrong gateway, requiring an RTP stream between the ingress gateway and the VXML gateway.

This is elegantly solved by not having the VRU transfer label configured in the Proxy, but added to the "Send To Originator" area of the SIP section configuration of the CVP Call Servers. Add "8111111111>" to this section - the greater-than sign is a wild card that deals with the appended correlation ID. Also add the ringtone label 91919191 and the error label 92929292 to this section.

The Call Server will check the Send To Originator section first - before asking the Proxy. When the original INVITE comes from an IOS gateway, that information will be in the SDP section of the SIP request, and so it will be in the INVITE for the 8111111111xxx label. Under these conditions, the Call Server will send the INVITE back to the ingress gateway, catching your dial peer and starting the bootstrap service. When the call is sent to an agent, the ringback will also run on the originating gateway.

With this configuration, no matter how many gateways you have, the VRU leg will always run on the ingress gateway.

Why won't this be suitable?

Regards,

Geoff

Hi Geoff,

thanks for the explanation, apprerciate it much, i will use it in my future sip hub and spoke deployments. But the signaling used in this project is H323.

it would be nice if you can explain how can h323 handle the issue.

Regards,

Hi Geoff,

Sorry for not mentioning the signaling used before, your last past is very helpful.

I appreciate your help,

Cheers,