Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ARS Table Digit Strings

Status
Not open for further replies.

telecomadmin12

Technical User
Apr 27, 2012
408
DE
I am confused about a denial event when dialing any 1800 toll free number, which has to do with the digit strings entered in the ARS.
denial event 1751: No AAR/ARS route pat/pref D1=0x6141 D2=0xc1c0019

ARS table:
Dialed Total Route Call Node
String Min Max Pattern Type
1800 11 11 5 fnpa

I don't get denied if the digit string in the ARS looks like this: 1800xxxx. I do get denied if the digit string is 1800.
Why would that be?
For other area codes a 4 digit entry is sufficient (e.g. 1212), but for 1800 (and maybe other digit strings, I don't know), I have to add at least four xxxx to the digit string.
Can you explain?
Thanks.
 
change to hnpa on the route pattern

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1
 
also can you post the route pattern for the 1800 entry, I just noticed ours is set the same as yours so the route pattern is where the problem lies

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1
 
Thank you.
Below is the route pattern for the 1800 entry. My call won't even go to that route pattern, only if the entry is 1800xxxx. I changed the entry in the ARS to hnpa, but no success. Also leaving at fnpa and changing the route pattern, e.g. removing the NPA entry doesn't help.

Pattern Number: 5 Pattern Name: Toll free 1800
SCCAN? n Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 3 0 845 1 n user
2: 4 0 845 1 n user
3: 2 0 845 1 n user
4: 1 0 845 1
 
So prefix is 1 right? what type of trunk are you going out on? do a list trace station and post results

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1
 
It is a CO trunk.
time data
14:59:19 tone-receiver 04B0005 cid 0x151e
14:59:19 active station 1577 cid 0x151e
14:59:24 dial 9180031593 route:ARS
14:59:24 denial event 1751: No AAR/ARS route pat/pref D1=0x6141 D2=0xc1c0019
14:59:24 dial 9180031593 route:ARS
14:59:24 denial station 1577 cid 0x151e
14:59:26 idle station 1577 cid 0x151e
 
are you using ars location tables? what type of pbx and release? your trace seems to be referencing another ars table, not hitting a route pattern as you stated, has this ever worked for 1800 calls?

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1
 
I got Avaya Definity, CM.3.0
Software Load: R013x.00.1.346.0
Memory Configuration: G3xV13
Offer Category: A
I am not familiar with location tables, so I wouldn't know what other ARS table my trace would be referencing. How do I find out?
This came to my attention when I started to use the AAR table as a simple temporary alternative to ARS, when my main trunk was out. Apart from denying some digit strings in the AAR, I only had two entries that I thought covered all calls. x for seven digit local calls and 1x for 11 digit calls.
Then I found out that 1800 numbers weren't working. I looked at the ARS table for comparison and I saw that for toll free numbers (1800, 1555, 1866, etc.) there were unusual entries in the digit string field, i.e. 1800xxxx, 1555xxxx, 1877xxxx, etc. When setting the digit string to 1800xxx e.g., with only three x following the 1800 instead of four, the call would be denied.
I didn't understand why that was happening.
 
These commands also work with location number

list ars analysis
list ars digit
list toll
list ars route-chosen 180031593

Are you only dialing 9 digits?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
any update on this yet?

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1
 
I don't have any news about this but there is one strange thing that I have noticed.
I get different results when doing a list ars route-chosen command, depending on the entry in the digit string field in the ARS.

When my digit string in the ARS is entered as 1800xxxx (with 4 x) I get the following page when I do a list ars route-chosen 18003159.... I dial a 1+10 digit toll free number.

Dialed Total Route Call Node
String Min Max Pattern Type Number Location
18003159 11 11 p16 fnpa all

When my digit string in the ARS is entered as 1800xxx (or with fewer x or just 1800) I get the following page when I do a list ars route-chosen 18003159....
Note that there is a "deny" in route pattern field. Why is that?

Dialed Total Route Call Node
String Min Max Pattern Type Number Location

18003159 11 11 deny fnpa all
 
ok now I understand you are using partition route tables enter the same info on 1800 that you have for 1800xxxx and this should resolve the issue, 1800 calls are denied on your pbx

ACSS-SME,ACSS Avaya Aura Session Manager and System Manager,ACSS Avaya Scopia Solution,ACSS Avaya one-X UC Soft Clients,ACSS Avaya Session Border Controller, ACSS Avaya Aura Messaging,
ACSS Avaya Aura Call Center Elite, ACSS Avaya Aura CM and CM Messaging,ACIS Avaya Aura CM and CM Messaging, ACIS SME, ACIS Avaya CM 5.2.1
 
Thank you for help.
I am not denying 1800 calls in my PBX. They go to a route pattern (number 5).
Route
Index PGN 1 PGN 2 PGN 3 PGN 4 PGN 5 PGN 6 PGN 7 PGN 8
----- ----- ----- ----- ----- ----- ----- ----- -----
16 5 5
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top