Directing Voip Calls To Specific Ports

[SteveZ]

I am running what is a pretty low volume inbound-only application, but I had to buy 4 ports because of the licensing requirement for VG7 Enterprise. I am using the Dialogic HMP drivers for H323 connectivity with Cisco Call Manager (thanks for helping me resolve those issues in an earlier thread). I notice that inbound calls round-robin through the 4 VG/HMP ports. Is there any way that I can configure an inbound H323 connection to direct to one specific port/.VGS script so that I can assign other numbers to the remaining ports and use them with different .VGS files?

[SupportTeam]

Maybe we can use DNIS routing on VoiceGuide level to have VoiceGuide to jump to the script corresponding to that DNIS.

 

This approach would allow you to support an unlimited number on different applications, with the applications type just determined based on the number dialed by caller.

 

Can you please post VocieGuide traces (ktTel and vgEngine) capturing the system startup and an incoming call so that we can see if the DNIS information is provided by this CallManager.

 

Any Port Routing on the HMP level would need the DNIS information as well, (how else would you tell the calls apart?) but HMP does not have any DNIS routing options.

[SteveZ]

I have attached the logs, but I can see in them that the DNIS is being set. It is being set to the extension number defined by Call Manager (5511) as opposed to the complete outside phone number. I also notice that the CallerID variable is being set to the IP address of the Call Manager instead of the actual Caller ID. I thought I had seen it being set correctly early on in my testing, back before calls were not being completed. Its not really that important for my application, I just thought I'd mention it.

0324_0952_vgEngine.zip

[SupportTeam]

As the CallManager supplies the destination extension number as DNIS then maybe you can have multiple extensions point to the VoiceGuide system and then VoiceGuide can start different scripts depending on which extension is called.

 

How the CallerID and DNIS values are presented would need to be set on the Call Manager. Right now CallManager sends them in this format:

 

CallerID: TA:10.140.80.11:1720

DNIS: TEL:5511,5511

 

So if for example you can have extension 5512 pointing to VoiceGuide system as well then to switch based on DNIS you can use the a starting script with one Evaluate Expression module in it. The expression being evaluated would be:

 

$RV_DNIS

 

and the paths in that module would be something like these:

 

on {TEL:5511,5511} goto [myfirstscript.vgs|]

on {TEL:5512,5512} goto [mysecondscript.vgs|]

[SteveZ]

Thanks, this looks like it will do what I want. I will try it out.