OneBox "Answer Mode" for secondary number 1

[fshields2]

We have the OneBox voicemail system connected to an MD110 (see specs below). Our organization's main # is processed by the Answer Mode function (time of day routing) to start call processors with different messages depending on after-hours, closure, or holiday conditions.

We would like to have inbound calls to another number (a DID) processed like the main number, but have different announcements and call processors.

The OneBox Answer Mode seems to only do its processing when it receives a call from a line or extension that does not have a subscriber mailbox. It then chooses which set of rules it uses based upon Line Groups. So one obvious solution to my problem is to peel off a few ports specifically for the processing of this new phone #, add them to their own Line Group, and use Answer Mode to process that Line Group. However, I don't want to segment my VM ports that way because it might leave me too few to process our main # and too few to process the new number.

I've toyed with the idea of using the call processor action: "Open Script". I was hoping that I could create a custom script that could route the call to other call processors based on time-of-day info I programmed into the script. However, I can find almost no information on how the "Open Script" action works. What is the script language and syntax? Where do I store the scripts? Etc. The only results my research has turned up is that this action might only be enabled if I have the Automated Agent option (IVR?). So I think this route is a dead end.

DOES ANYONE HAVE ANY SUGGESTIONS FOR ME?

Thanks,

Forrest C. Shields II

SPECS:
OneBox VMS 4.01 (ver. 7.2 build 270), 8 ports
Ericsson MD110 (BC12)

 

[doktor]

First of all thank you for choosing these great products: MD110 and OneBox!
I did solve your problem at a few customers.
The trics is to use empty GH-groups (i.e. with no members) in the MD110, and let these point by means af a diversion (CDINI) to the voice mail group (VMGEP; or VMPOP
So when you call the new number there should exist a callprocessor (or mailbox) that handles this specific number.
It is even possible to use timecontrolled callprocessors, where the extension number is entered in the call routing part of the administration module.
A "skeleton" of basic callprocessors have to be build up, and the "real" callprocessors serving your new number has to be build on top on the basic callprocessors.
So if calling e.g. ext. 4444, and this number is entered in the routing code table of the administrator module with e.g. a route code of 20 (added to the baisc callprocessor), then (in the specified time) the content of the basic callprocessor + 20 is "played" (press 1 for X, and press 2 for Y).
It takes many hours to get it to work , but hereafter it just works alright!
If you want to implement this, you need to get rid of all "old" callprocessors, as the time controlled ones cannot "live" together with non-timecontrolled callprocessors.


///doktor

 

[fshields2]

doktor,

I am far from proficient on the MD110. When you refered to the "routing code table of the administrator module" are you referring to the Least Cost Routing (LCxxx) commands on the MD110?

Here is an example of what I'd like to do. When someone dials x2380 (empty GH with a CDINI diversion to the voicemail group), I'd like to have OneBox activate call processor #1234 between 8am and 5pm M-F, and activate call processor #5678 before 8am M-F, after 5pm M-F, and on Sat & Sun.

Could you give me a hint as the the MD110 commands that I would need to accomplish this?

Thank you.

Forrest C. Shields II

 

[doktor]

You need to configure some GH-groups with no members pointing with a CDINI (call diversion) to the OneBox number.

///doktor

 

[fshields2]

docktor,

Unfortunately, you didn't answer my questions (but I really do appreciate your help on this). I have no problem making an empty hunt group with a diversion to VM. My main concern is how to route to different call processors at various times of day. From looking at ALEX I think you may be on the right track with "Least Cost Routing, Time of Day, LC" (if that is what you are talking about) but I've never had to mess with the LC commands and am looking for some guideance on this.

 

[doktor]

To solve your problem, the only thing to do in the MD110 is to make a number of GH-groups and have diversions to the VMGEP; group.
The rest of the installation has to be done in the OneBox.
Please refer to my first post.
This problem has nothing to do with LCR (Least Cost Routing)!

///doktor

 

[whosrdaddy]

fshields,

what doktor said is 100% correct.
besides, LCR functionality is for outgoing traffic, not for incoming traffic.

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[fshields2]

I finally understand! So I am going to summarize here for everyone's benefit. (doktor, if I'm wrong on any of this please correct me)

Step 1) On the MD110, create an empty hunt group (in my case, x2380) and then use CDINI to divert the hunt group to the VM group. When the empty hunt group is called, the MD110 will divert the call to the OneBox, but pass the empty hunt group's extension. This eliminates the need to use and actual digital or analog port on the PBX. I creates a premanently diverted "virtual" extension.

Step 2) On the OneBox server, open the Administration Program (Start --> Programs --> OneBox Desktop --> Administration). Then get into the System Configuration dialog (Configuration <menu> --> System... --> Call Routing <tab>).

Step 3) Add a new entry where the "Number" field equals the extension of your empy hunt group from step 1 (in my case, x2380). The "Service Type" field should be "Phantom Extension". The "Route Code" field should contain an integer number that will be added to the call processor's mailbox # for the currently active call processor in your "Answer Mode" tab. (see example below)

Step 4) Switch over to the "Answer Mode" tab and select the "Route Code" checkboxes for any Answer Mode rules that you want to route to a different call processor.

Example: Let's say that I have only two call processors in the Answer Mode tab, #0010 - "Business Hrs Menu" and #0020 - "After Hrs Menu" and their "Route Code" checkboxes are selected. I have also set up an entry in the Call Routing tab that looks like: Number:2380, Service Typehantom Extension, Route Code:200. Whenever x2380 is called it is diverted to OneBox which looks at the Answer Mode table and determines that the #0010 call processor should handle the call at this time of day. However, OneBox then notices that the "Route Code" checkbox is selected for that Answer Mode enrty. So it then looks in the Call Routing table and notices that there is a match between the extension the call was forwarded from (x2380) and an entry in the table. It sees that the route code should be 200. It then takes the call processor number #0010 and adds the route code 200 to it to yield #0210. THIS is the call processor that will actually be used to answer the call.

Step 5) Create your new call processors on the new number ranges. (for me, #0210 - Business Hrs Menu for x2380 & #0220 - After Hrs Menu for x2380)

I can see where this would get really complicated if the second set of call processors are to be activated at different times than the exisiting set.

Forrest C. Shields II

 

[doktor]

hallo Forrest C. Shields II.

Correct "V" to step 1 - 5.

I can add this - for the OneBox programming.

Go to the administarion module and create e.g. 10 callprocessors 1000-1009 to be used Monday to Friday (Weekdays).
Basic Callprocessors.
Callprocessor 1000 start time 08:00 A.M.
Callprocessor 1001 start time 10:00 A.M.
Callprocessor 1002 start time 12:00 A.M.
Callprocessor 1003 start time 02:00 P.M.
Callprocessor 1004 start time 04:00 P.M.
Callprocessor 1005 start time 06:00 P.M.

Secondly you initiate an empty GH group and make a CDINI to the VMGEP group.
If this number was e.g. 8888, then enter it in the routing code list in OneBox.
It is in the administrator program under Configuration -> System -> Call Routing. Enter 8888 as the number and the routing code could be 20.

Third:
Create a number of Callprocessors equal to the route code plus the basic callprocessors:
I.e. 1000 + 20 is 1020.

Functional callprocessors for group 8888:

Callprocessor 1020 start time 08:00 A.M.
Callprocessor 1021 start time 10:00 A.M.
Callprocessor 1022 start time 12:00 A.M.
Callprocessor 1023 start time 02:00 P.M.
Callprocessor 1024 start time 04:00 P.M.
Callprocessor 1025 start time 06:00 P.M.

Each of these Functional callprocessors could just have a TO (Time out) action to go to another Callprocessor, where all the choises exist for pressing 1, 2, 3 etc.
This should work alright.

My info is found here:

http://www.kandu.dk/spg97163.aspx

///doktor

 

[doktor]

To get this to work ALL callprocessors serving all group numbers and operator etc. should be made in the same way!
So non-time controlled and time controlled callprocessors cannot coexist.

///doktor

 

[doktor]

Just one important thing:

The Basic Callprocessors.
Callprocessor 1000 start time 08:00 A.M.
Callprocessor 1001 start time 10:00 A.M.
Callprocessor 1002 start time 12:00 A.M.
Callprocessor 1003 start time 02:00 P.M.
Callprocessor 1004 start time 04:00 P.M.
Callprocessor 1005 start time 06:00 P.M.

Should be initiated in the Answering Tab, where they should be enabled, the Line group, Schedule, Time and mailbox (that is the Callprocessor) should also be initiated.

This is only to be carried out for the basic callprocessors, as they control the functional callprocessors.

///doktor