Vector / Range of Extensions

[JDTurk]

I created an auto attendant so that calls to a certain group of about 50 of our virtual extensions would go directly into their modular messaging accounts. Is there a way to limit the extensions accepted (i.e. extensions 2000-2050 only)? The current vector for this is listed here:

CALL VECTOR

Number: 45 Name: WFL Teachers
Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n
Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? n
Prompting? y LAI? y G3V4 Adv Route? y CINFO? y BSR? y Holidays? y
Variables? y 3.0 Enhanced? y
01 wait-time 2 secs hearing silence
02 collect 4 digits after announcement 1150 for none (Please enter 4-digit extension . . .)
03 route-to digits with coverage y
04 collect 4 digits after announcement 1151 for none (That extension is not valid . . .)
05 route-to digits with coverage y
06 goto step 4 if unconditionally
07
08
09
10
11
12


S8730 Processors (Redundncy/Mirror Img)
Aura 5.2 (Communication Manager)
Modular Messaging 5.2

 

[4merAvaya]

Use a Vector Routing Table (vrt) to screen the extensions.

The vector would look like this:

01 collect 4 digits after announcement 2050 for none
02 goto step 12 if digits in table 1
..
..
12 queue to Skill 99 (messaging).

In the VRT enter the extensions that you want.

Kevin

 

[Stinney]

The VRT is a good solution. But if you don't have any extensions less than 2000 you could add a line like:

goto step 12 if digits <= 2050

You'll need to set up a variable for the collect digits as line 12 should be:

messaging skill [messaging skill #] for extension [variable]

So your collect step needs to change from "for none" to for [variable]

If you've never set up variables, you need to set the variable type as collect, the scope as local, the length to 4 and the start to 1.




- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[JDTurk]

Thanks guys. Excellent ideas.

S8730 Processors (Redundncy/Mirror Img)
Aura 5.2 (Communication Manager)
Modular Messaging 5.2