Inconsistant results using the same digit maps in Line And AA .Is this a bug?

(1/2) > >>

larrybob:
I was experimenting with user defined digitmaps to have a digit map just for an area code:
I discovered that digit map programing does not work consistently ... this might be a bug.. or a rule I am missing I found the same  digit maps working or not working depending where it is used.
First I set up some userdefined digit maps:
I defined "areacode" as (<415>) in user defined digit maps Inconsistent

 I defined "us" calling map as (1[2-9][0-8]x xxxx|<1>(Mareacode)[2-9][0-8]x xxxx)|<1>[2-9][0-8]x xxxx)

Then under Line, I used for part of my digit map |<**1>(Mus)| This worked perfectly for 7 , 10 or 1+10 dialing from the phone.
___________________________________________________________________________
This same coding  DOES NOT WORK When applied in the Digit Map for the AA.! it will return an error when 7 numbers are entered.
HERE ONLY EXPANDING OUT THE USER DEFINED DIGIT MAP "areacode" as (<1415>[2-9][0-8]x xxxx)
and changing the "us" calling map as  (1[2-9][0-8]x xxxx|(Mareacode)|<1>[2-9][0-8]x xxxx) will work .

 If the coding is applied as shown in part a an invalid number response is returned when a 7 digit number is entered into the AA.

Larry

RonR:
Are PHONE Port -> PrimaryLine and Auto Attendant -> PrimaryLine both set to PSTN Line?

Are PHONE Port -> OutboundCallRoute and Auto Attendant -> OutboundCallRoute both set to Default?

larrybob:
Yes both set to PTSN Line
Yes Outbound callroute is default for phone and AA

here is programing
Userdefinded Digit map "areacode" : (<415>)
Userdefined Digit map "us" : (1[2-9][0-8]x xxxx|<1>(Mareacode)[2-9][0-8]x xxxx)|<1>[2-9][0-8]x xxxx)

Phone Digit map :  ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|<**1><011>(Mus)|**8{t=di}(Mli)|**9{t=od}(Mpp)|(Mpli))  THIS WORKS!! ( when dialing a 7 digit number)

AA Digit Map : ([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|<00:$1>|0|<**1><011>(Mus)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))  THIS DOES NOT WORK!!!

SEEMS DIGIT MAP PROGRAMING THAT WILL WORK IN THE PHONE DIGIT MAP WILL NOT WORK IN THE AA.

Solution: If arecode Digit map is expanded to :(<1415>[2-9][0-8]x xxxx)
and Us digit map is changed to :(1[2-9][0-8]x xxxx|(Mareacode)|<1>[2-9][0-8]x xxxx)
Will work in phone and AA.

However, what i am trying to do is have a clean digitmap with just the Areacode. so the solution I found is not optimal for me.

Again it seems that there is a Bug in the Programing of the AA which does not allow the same DigitMap programing As the Phone ...

Am I missing Something?


Larry

RonR:
Quote from: larrybob on April 14, 2012, 12:46:24 pm

Userdefined Digit map "us" : (1[2-9][0-8]x xxxx|<1>(Mareacode)[2-9][0-8]x xxxx)|<1>[2-9][0-8]x xxxx)


You have two problems:

A. You have a unmatched paren:

<1>(Mareacode)[2-9][0-8]x xxxx)

B. You have two rules trying to deal with 7-digit numbers, each in a different way:

<1>(Mareacode)[2-9][0-8]x xxxx

<1>[2-9][0-8]x xxxx

larrybob:
Ron ,
You are correct, but that is not the problem. I made your correction( It is  nice to have a second set of eye look at things sometimes) but I still do not get the same behavior form the  AA And Phone with the same digitmaps
I cut and pasted  the fields so what you see is what is in use:

digitmap "areacode":(<415>)
digitmap "us" :(1[2-9][0-8]x xxxx|<1>[2-9][0-8]x xxx xxxx|<1>(Mareacode)[2-9][0-8]x xxxx)

Digitmap Phone :
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|<**1><011>(Mus)|**8{t=di}(Mli)|**9{t=od}(Mpp)|(Mpli))

Digitmap AA  :
              ([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|<00:$1>|0|<**1><011>(Mus)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))


The outbound call routes are default.

I am scratching my head...if a 7 digit call goes through correctly with the phone it should also go through with the aa .. BUT IT DOES NOT... the call should either work or fail in both places, not only work with the phone.

Thanks Larry

Navigation

[0] Message Index

[#] Next page