Voicemail Pro call continuation

[CFSmitten]

I'm working on building a AA module and was hoping someone could help me out.

Here's the situation. We have multiple remote sites that are set up on a Fiber ELAN and all phones are managed by IP Office from our corporate office (hub and spoke network). Normally when someone calls a local site phone number, it just routes to a hunt group and anyone at that site can take the call. But now the executives want all incoming calls to those sites to go through a call menu. I was hoping that I could just build 1 AA Module with some kind of variable that would allow calls to continue on to that local hunt group. That way I wouldn't have to build a module for each individual site.

1. Billing ---------------> Transfer to Corporate Billing​

2. Sales ---------------> $VAR (Local Site Hunt Group)​

3. Training ---------------> $VAR (Local Site Hunt Group)​

Is this even possible? Any help or insight would be appreciated.

 

[Okkie26]

Just enter the local huntgroup phone number as destination.

Same as you do now in the ICR..

 

[CFSmitten]

I could do that, but that means I'd have to create a module for each site, right? I was trying to avoid that, if possible.

 

[Okkie26]

I understand.

You could try to enter the destinations in the ICR tag field (ie. 120 121)

Then route the call to one VM pro startpoint. Enter a menu here with 3 options.

After option 2, you need to enter a basic action the copy the left 3 digits of $TAG to variable ($SAV). Then transfer the call to $SAV and make sure to enter a new TAG here

After option 3, you need to enter a basic action the copy the right 3 digits of $TAG to variable ($SAV). Then transfer the call to $SAV and make sure to enter a new TAG here

 

[derfloh]

You could also use the called number ($DDI) to route the calls. Strip the last three or four digits and copy them to $CP0. Then routing by variable.

Nevertheless maintenance will be easier with one module per site.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[budbyrd]

It is pretty simple to cut and paste modules, change a few destinations, and not jump through a bunch hoops.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[CFSmitten]

Thank you all for the insight. I'm trying out the variable option. If it gets to be to much to, I'll just go with a module for each

 

[TouchToneTommy]

If you keep things clean, it is pretty easy to use the ICR Tag as a variable to do the routing.

I did a system for 30 Sites
Each Site has cookie cutter setup of 4 Users and 4 Groups

Site 1's Users are 201, 202, 203, 204, Groups are 200, 207, 208, 209
Site 2's Users are 211, 212, 213, 214, Groups are 210, 217, 218, 219
and so on

Incoming Call Route has site name in Tag field

When call arrives at AA, branch to a submenu that uses Variable Routing to match the Tag and set $CP0 to the first Group extension number. It also sets $CP1 to $CP0+8; $CP2 to $CP0+9, and $CP3 to $CP0+7

The call returns from the submnenu with the $CP values set, checks the time conditions, and if Open plays "OPEN$CP0.wav". If the callers selects the option to speak with a team member, it transfers to $CP1

If the system is in Night Service, it plays "CLOSED$CP0.wav", and if the caller selects the option to leave a general message, it plays a generic general mailbox greeting and records into Mailbox $CP2 (which lights up on all the phones)

There is also a Holiday or Temp Closure override, which plays "HOLIDAY$CP0.wav" with the same options as Night mode

4 modules to do everything