Need help on creating a callflow to check no match extension in VmPro

[msi12]

I am trying to create a callflow to check extension dialed thru auto attendant. Ex:2??? setup in Menu action
There is no example of how to use the new check digit replaced by "Test Variable" in VmPro 5.0.21.
This is my setup under "Test Variable" Specific:
Select the Varible to Match= $KEY
Select the parameter(s) to test the variable against= Extn

Result:
- Extension > Transfer action = $KEY
- No Match > Generic Menu [Prompt](Invalid Entry) > Menu [Prompt](Please Enter Extension Number)> Test Variable
- Timeout 5 sec > Transfer to a test extn 800

When I dial x2000 it just keeps timing out to x800. Not going to x2000.
When I dial a digit not in the menu option, it correctly gives me prompt "Invalid Entry" and plays Generic Menu prompt.

I thought Extn was to transfer caller if there was a match in the IP Office and would follow the No Match result. Maybe I'm missing something in the setup.

Any help or work around would be appreciated.

Thanks
Howard

 

[amriddle01]

Every time I go to watch a Vuvuzela concert someone starts playing football

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[CarGoSki]

Some guy made a Doom addon that has the vuvuzela as a weapon. Apparently it melts minds and explodes body parts.

http://www.youtube.com/watch?v=NXPPyjtw5WU

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.

 

[msi12]

@bas123

Ok. I'll will try that tomorrow.
I didn't know there was a routing variable action. I must have missed this.
Wow, IPO new releases is changing so fast that tech like us need to keep up.

Thanks bas123

 

[CarGoSki]

It would appear that TD is correct in suggesting coping $KEY to $CP0 with a generic action then testing against $CPO.

$KEY apparently doesn't work the way it should in this case without shifting stuff around.

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.

 

[amriddle01]

I think either way it's overcomplicated, all you need is a simple system shortcode (2xxx or similar)to catch the invalid entries and route them back to the relevant action/module...done

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[CarGoSki]

I suppose it depends on if you want your overcomplication on the frontend or backend. The vmpro build does not seem too over drawn.


Use system monitor unless of course you are a Tard then it IS the fault of the pbx.

 

[amriddle01]

It doesn't check for valid extension mumbers though, only that it's either 2xxx format or not, the shortcode will only match against invalid entries and so filter those better

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[CarGoSki]

Right so if you want to match the functionality of the vm build then the short code method would have to become more complex. Unless of couse you believe that a disconnection or misrouting for one who dials incorrectly is deserved.

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.

 

[amriddle01]

No, I was thinking hybrid effort, if the dialed number is not an extension it goes to the VM action the no match would, you get the same end result but without trying to figure out why VM Pro is acting all buggy again

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[CarGoSki]

Actin' all Gangsta Buggy

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.

 

[amriddle01]

Perhaps that could be the name of your next album

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[CarGoSki]

Other potential titles:

Still Gangsta after all these years.
A dozen buzzin' on my cousin
I be a VMPro Ho


Use system monitor unless of course you are a Tard then it IS the fault of the pbx.

 

[msi12]

@bas123
I did the callflow test you submitted.
The transfer worked, but the no match disconnected/drop the caller. It did not transfer unknown extn to no match x800. Ex: x2019 and any uncreated user in USER config. should goto VM module or a transfer action.
Will, this is a right step.
Thanks for your help.

@amriddle01
I did try using the 2xxx in sc to filter out unknown extn to Invalid Extn Entry module in vm. It worked.
I will incorporate this setup in the callflow.
Thanks for the tip.

@TaureanDragon
Otherwise:
If you want to do it without the '#', then use a menu action with a '2???' (any 4digit number starting with a 2) route, then copy contents from $KEY to $CP0 and use $CP0 in the 'Test Variable' and 'Transfer' action.

Does avaya have training manual shows how to setup this up? I'm new to this varialbe thing.

Thanks


Thanks to everyone for inputing their 2cents

 

[Bas1234]

Then try sending the "No Match" of each "Variable Routing" back to the begin of the menu(Please enter extn.).

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[msi12]

Ok guys, I decided to use 2??? for Menu action to Transfer action $KEY.
2xxx SC to filter out unknown user extn back to Invalid Extn Entry module.

This solution works out great.

@bas123
The No Match result did not do anything. So I just drop that solution. I will mess around with that later to find out how that work.

Any way, to all that gave me advises to this solution.
Thanks You
Tek-Tips is a great place to get help and offer advise.

 

[amriddle01]

(Takes a Bow).....why thankyou

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[CarGoSki]

All kisses and hugs but no stars.

Use system monitor unless of course you are a Tard then it IS the fault of the pbx.