invalid extension 4

[kwing112000]

i know i have seen this before. i tried the google search a few times but could not locate what i wanted.

On VM pro I have a menu that has say 2?? then it transfers to $KEY and sends it into the IPO. WHat can you do if you do not have a valid ext. Like 265 has no ext or user. Right now you dial 265 and it would hang up on you. Is there a way to make it transfer to the operator ot play a message that it was invalid and start the AA again.

THanks in advance.

 

[ronromano]

$

 

[ronromano]

Sorry, should have read you post better. I have to think about it. Usually I try to avoid thst although sometimes its tough.

 

[ronromano]

Might try assisted transfer.

 

[jml2665]

ronromano is correct, the $ is supposed to define where invalid inputs route to, but where do you stick the it? does it work only in the module you have it in?
or does having it in the initial module (where Avaya documentation puts it in all their examples) allow it to work further out into the trees?
or do you need it in each branch of the tree where invalid inputs can occur?

 

[kwing112000]

I am thinking that i may have to do something on the IPO side. What seems to happen is the VM transfers the call to the IPO and the IPO diconnects it. The $ sign doesnt work because it sees it as part of the 2?? so it sends it to the IPO. I think the assisted tranfer may work i will have to try it. If I make a short code on the ipo like 2xx with VM Collect and "Invalid" mabe it will go back to the VM and i can announce the youve dialed an invalid ext please try again.

 

[ProviderReborn]

Kwing your correct I believe. Because you have matched in the VM with 2?? its then back to the system.
I dont see why your shortcode should not work, and then just point it back into the main menu after you have stated they have made an invalid entry.
Let me check a config or two as I have done this before.

 

[kwing112000]

The Provider

That would be great. i have not tried it yet i was just thinking about it this way. It sounds like it should work.

 

[aarenot]

Call list action should restrict transfer to members of a HG. Create a HG with all the members you want them to be able to transfer to.

Also, in VMPRO,
Menu A option 2 to new menu B

Menu B Options 0?,1?,2?,3?,4?,5? to blind transfer ($KEY)
$ to go to INVALID

It is late so I am probably in need of a little tweaking for this to work, but you get the idea. Same for the suggestion below.

Also another option,
Menu 2?? to Test Condition(compare)$KEY<265 Lead that to transfer $KEY, False lead to "INVALID" Menu, or whatever.

 

[kwing112000]

THanks Aarenot i will give that a try. I will let you know how it works.

 

[balmy57]

My recommendation is to use the Compare function in the Conditions Editor of VM Pro as in the example below:

Valid Extns. are 201 to 299. Invalid Extns. are 265 and 273.

1. Create a new condition called "Test Extns" for example.
2. Add a Compare function where Value A is "$KEY" Is "Greater than or equal to" and Value B is "201".
3. Add another Compare function where Value a is "$KEY" Is "Less than or equal to" and Value B is "299".
4. Add a third Compare function where Value A is "$KEY" Is "Not equal to" and Value B is "265".
5. Repeat Step 4 for 273.
6. After Menu option 2?? use Test Condition for "Test Extns"
where Valid leads to {Assisted}/Transfer and Invalid leads to Module Return, for example.

Good luck.

 

[aarenot]

balmy,
I assumed the valid users were consecutive, but yours works great if they did not set up their users with consecutive numbers as well. Only issue is 200 would not fall into your parameters, change the first value to 200, not 201 should fix it.

 

[intrigrant]

You all think too difficult!
If the VM dials a number then IPO will first look if it is a directory number, if it is not a directory number then it will check the shortcodes.
So, create a shortcode like this:
SC = 2XX, TN = "InvalidNumber" Action = VoiceMailCollect

The module in VM Pro has only a announcement like "You have dialled a unknown number, please try again" and then a jump to the menu.
The annoncement must be at least 3 seconds long otherwise VM Pro thinks it is a call-loop from VM to VM!

 

[kwing112000]

Intrigrant,
That is what i ended up doing but i had to get more specific with the code because with the newer manager it creates alot of errors. i had 4 digit extensions like 23xx so i made a few codes like 231x and 232x and it worked.

 

[kwing112000]

i forgot. Thanks everyone who helped with this.