Voicemail & Inbound Routing...

[xtdirect]

Install Information:
Vicibox redux 32bit preload 3.1.15
VERSION: 2.6-372a
BUILD: 120713-2123

Scenario:
Set up an inbound campaign with a single ingroup and multiple (thousands) of DID's pointing to the single ingroup/campaign.

I have this scenario set up right now using one DID to test with. When the call comes in I pop a custom webform based upon the specific DID passed to the campaign. The agent then handles the call with customized answers from the webform based on the DID passed.... Here is the rub, I would like the agent to be able to transfer the call to a voicemail box that is specific to the incoming DID, not the campaign or the ingroup.

Issues:
- First... I am able to create and login to voicemail boxes created from the phone interface, but I am unable to log into mailboxes created using the Admin/Voicemail interface... I am making sure that the voicemail box ID is not a duplicate, but get no love... when I dial 8500 and enter the mailbox and password it says my login is invalid.....?? I can't imagine what I am doing wrong...

- Second... Once I can get the voicemail issue above worked out, how does one allow the agent to route the call to the voicemail that is specific to the DID within the framework of multiple DID's pointing to a single ingroup/campaign. For example I would like to set up a voicemail box that has the id of the DID so for DID 402-682-3093 a mailbox with an id of 4026823093 would be created, and the agent could transfer to that voicemail if desired.

IS this possible??? I would like to avoid setting up a DID/Ingroup/Campaign for each and every new inbound customer (Read as DID) as the multiple DID's pointing to a single ingroup/campaign works well from a management/agent/scripting point of view?

Thanks In advance for your wisdom in the matter!

[williamconley]

one method would be to use the agent api to send the call to VM from a script that would (obviously) have detected the did before doing so. another method would be to have the agent transfer to a specific dialplan or agi script that would "check" for the DID and route the call accordingly.

It may be necessary to store the DID as a variable at some point so it is available for any of these processes, or to create an ingroup for each ... but if you have thousands, LOL, that may not be desirable.

[xtdirect]

William,

I looked at the api documentation here:
http://www.vicidial.org/docs/AGENT_API.txt

And do not see a clear method to use to transfer the call to a specific voicemail box. Am I looking at the most up to date API documentation?

I can see that the "Transfer_Conference" command has a "LEAVE_VM - blind transfer customer to the campaign-defined voicemail message" method, but it would be specific to the campaign and not the DID of choice...

On an up note...
Figured out why the voicemail boxes created by clicking the "admin/Voicemail" route were not working. After I setup the box (only a day old) I Changed the IP address and ran the /usr/share/astguiclient/ADMIN_update_server_ip.pl script to update the IP as directed.

While debugging the Voicemail issue was poking around in the "admin/server settings" and found that the "sounds web server" and the "Active Voicemail Server" were still set to the Old IP address. Changed them to the new one rebooted and things are working now...

Is the "ADMIN_update_server_ip.pl" Suppose to change those two server settings settings?? (sounds web server & Active Voicemail Server)

Thanks for your help!

Thanks!

[williamconley]

the most up to date api documentation is available by downloading and installing vicidial's latest SVN. Vicibox.com is where you get it. You can install it on a Virtual machine if you like, and the /usr/src/astguiclient/trunk/docs/ folder will contain the latest documentation. "svn up" will keep it latest.

you would likely just transfer to an extension, and since the extension is unavailable, it would go straight to VM. Unless the extension were actually available, in which case it would ring.

Test