ARS ROUTING PROBLEM FOR SOME NPAS 2

[SYQUEST]

I volunteered to help out with a problem on a Definity G3 system. I have never worked on one of these before. I forgot to note the software version. It seems to have a problem dropping the digit 1 when out pulsing the digits to the CO on ten digit calls with NPAs in the 90x thru 91x series, except NPA 916 works! I was able to verify this much by monitoring four of the analog trunks in the group after locating them and using my "BerryBox" trunk testset to decode the Touch-Tone digits to see why the calls would not complete. The customer keeps getting non-completion recordings from the CO.

The inhouse person that normally works on the G3 in away in the national guard and the other IT person only knows limited station adds, moves, and changes. Nothing else... But he did log me into the switch and I was able to fumble my way around and find the ARS analysis list, the Route Patterns list, and another item that showed the trunk groups which I printed out. But w/o documentation this is very confusing trying to figure out the relationship between these items and the trunk groups etc. on how a call is processed in Definity ARS! I went to the Avaya site and found some FAQS about routing patterns and adding new area codes/office codes but that did not help. Everything seems to be there except for the description or rules for out pulsing digits to the trunks.

I don't know how long this has been going on. When I asked the customer, they said only about 2 months. They are in NPA 909 and evidently didn't place calls to many NPAs in the 9xx range until two months ago when they tried calling a client in Alaska, NPA 907, and kept getting a recording requesting a 1 or 0 is required to complete the call.
It looks like there are two trunk groups used for outgoing calls both are listed on the route patterns list, but I could not figure out what some of the headings mean or indicate.

Any help would be much appreciated or point me to some Definity docs that cover the trunks and ARS. I tried browsing some of the stuff on Avaya's site but got lost looking for anything on ARS.

Thanks in advance!

....JIM....

 

[1a22ip]

I think you are looking for prefix mark. According to the books:

0 * Suppress a user-dialed prefix digit 1 for 10-digit FNPA calls.
* Leave a user-dialed prefix digit 1 for 7-digit HNPA calls.
* Leave a prefix digit 1 on 10-digit calls that are not FNPA or HNPA
calls.
Do not use Prefix Mark 0 in those areas where all long-distance calls
must be dialed as 1+10 digits. Check with your local network provider.
1 * Send a 1 on 10-digit calls, but not on 7-digit calls.
Use Prefix Mark 1 for HNPA calls that require a 1 to indicate
long-distance calls.
2 * Send a 1 on all 10-digit and 7-digit long-distance calls.
Prefix Mark 2 refers to a Toll Table to define long distance codes.
3 * Send a 1 on all long-distance calls and keep or insert the NPA (area
code) so that all long distance calls are 10-digit calls. The NPA is
inserted when a user dials a Prefix digit 1 plus 7-digits.
Prefix Mark 3 refers to a Toll Table to define long distance codes.
4 * Always suppress a user-dialed Prefix digit 1.
Use Prefix Mark 4, for example, when ISDN calls route to a switch
that rejects calls with a prefix digit 1.
blank For tie trunks, leave this field blank.

Thats my story and I'm sticking with it

ED

1a2 to ip I seen it all

 

[Bobg1]

DO a Disp ars ana 9xx and look to see what route pattern is being used. Then look at the route pattern, Disp ro xx
and see if the prefix mark is wrong, which Ed has explained.

 

[Definity]

You can see the preffered route pattern by "li ars rout XXX XXX XXXX" this will give you the route choosen to send the call out via ARS. You can add digit "1" in the route patterns to add 1 by default.

Hope this would help..

 

[mdeeves]

If the client is in 909 and they are calling 907 wouldn't they dial 1-907-xxx-xxxx?

you should be looking at the ARS ANA for 190X not 90X.


let me know if this helps.

 

[SYQUEST]

Hi 1a22ip,

Thanks for your input. You hit the nail on the head! When I finally figured out where the 'prefix mark' is hidden all those fields in the trunk group definitions were blank - nothing! Evidently the switch was using random data - garbage - when processing outgoing calls. I put in prefix mark 1 for the correct dialplan. It now works great. (Read very happy customer!) I also cleaned up the ars list, which was missing some strings and had ones that did not apply.

Also, what is the story behind NOT displaying the 'prefix mark' field when you list the trunk groups?

BTW, what Definity document or practice covers ARS, so I know where to look next time? This is very different from the Legend switch ARS...

....JIM....

 

[1a22ip]

SYQUEST
The prefix mark is contained in the route due to different groups to different carriers wil require different prefix's. The book I referenced is on a CD that was delevered with my switch. I loaded the entire CD on to my Harddrive. The docs are PDF and has a very good search tool.

I use it often
Thanks
ED

1a2 to ip I seen it all