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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What could I be missing (ARS Problem) 3

Status
Not open for further replies.

sjforcum

Technical User
Jul 15, 2002
859
US
Hello all,

I'm having trouble getting calls from my switch to the outgoing CO Trunk group. I know the telephone number is correct because when I use the TAC vs. the ARS fAC I am able to complete the call without issue.

When trying to use the ARS FAC (7) plus the number, I get "please dial the number 1, plus the area code when dialing long distance". The troubling thing is I did dial the one, so I'm assuming the system is chopping it off somewhere. The route pattern is clean (as shown below)...so where else should I look that could alter the dial string?

One other note...

The entry for 1860 uses route pattern 65. This route pattern inserts a 1. For some numbers, it works (even though I dial a one as a part of the dial string). I tried using route 65 for this dialsting in question, but when I did that, I heard a short pause, then a disconnect from the switch.

TIA,
Steve
_________________________________________________________

FIG 1 List route for the dialstring in question

Partitioned Group Number: 2

Dialed Total Route Call Node
String Min Max Pat Type Number

1860828 11 11 64 fnpa

__________________________________________________________

Fig 2 the ARS ANA entry for the route 1860828 on partition 2

Partitioned Group Number: 2 Percent Full: 55

Dialed Total Rte Call Nd ANI Dialed Total Rte Call Nd ANI
String Mn Mx Pat Type Num Rq String Mn Mx Pat Type Num Rq
1860828 11 11 64 fnpa n n
1863 11 11 20 fnpa n n
1864 11 11 20 fnpa n n
1865 11 11 n/a fnpa n n
1866 11 11 n/a fnpa n n
1868 11 11 20 fnpa n n
1870 11 11 20 fnpa n n
1876 11 11 20 fnpa n n
1877 11 11 20 fnpa n n
1888 11 11 20 fnpa n n
1889 11 11 20 fnpa n n
190 11 11 20 fnpa n n
1900 11 11 den fnpa n n
1900555 11 11 den fnpa n n
1901 11 11 20 fnpa n n
____________________________________________________________
Fig 3 Route 64

Switch name: Tolland - Network -64attern Number:

Grp. FRL NPA Pfx Hop Toll No. Del Inserted
No. Mrk Lmt List Digits Digits
1: 10 7 860
2:
3:
4:
5:
6:
 
Try putting a "1" in the prefix mark and don't insert any digits
 
I added a 1 for the prefix mark and received the same "please dial the numerial one when placing a long distance call".

Any ideas where (other than the route pattern) the switch could be chopping off the first digit of this dial string?
 
There ar 5 option to us in this field. 0-4 options 2and 3 are for toll routes. If 1 didn't work then try 0 or 4 and make sure the FRL is lower then the FRL of the COR your calling from. Wisdom is Knowledge
that is Shared

Thanks All Phoneman2
 
If you are using dedicated long distance trunking, try leaving the NPA blank and using prefix mark 1, if you are using AT&T you may need to use prefix mark 0.

If you are doing long-distance over the trunks you use for local calls, try to put the PBX's area code in the NPA field and use prefix mark 1.

Hope that helps

 
I used 0, 1 & 4 in the prefix mark field...and all calls had the same result.

The trunk group used is for local and long distance calling. The local area code is already a part of the NPA field. When I put any of the above entries into the Prefix mark field, I had the same result...the switch seemingly stripping out the one.
 
Check your COR on the set you are using and make sure it is pointing to "time of day chart" 2 or ARS partition group 2 and not defaulted to ARS partition group 1.

Netcon1
 
Hi NetCon,

The COR these stations are using is 10. I am not using Time of Day routing (that I am aware of...is it even available in V6?). I've included the screen cap of the COR page. All stations with this COR should be using ARS partition table 2.

TIA,
Steve

___________________________________________________________

DISP COR 10

Switch name: Tolland - Network - CLASS OF RESTRICTION

COR Number: 10
COR Description:

FRL: 7 APLT? y
Can Be Service Observed? n Calling Party Restriction: none
Can Be A Service Observer? n Called Party Restriction: none
Partitioned Group Number: 2 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: all Facility Access Trunk Test? n
Restricted Call List? n Can Change Coverage? n

Access to MCT? y Fully Restricted Service? n
Category For MFC ANI: 7 Hear VDN of Origin Annc.? n
Send ANI for MFE? n
MF ANI Prefix: Automatic Charge Display? n
Hear System Music on Hold? y PASTE (Display PBX Data on Phone)? n
Can Be Picked Up By Directed Call Pickup? n
Can Use Directed Call Pickup? n


CLASS OF RESTRICTION


CALLING PERMISSION (Enter "y" to grant permission to call specified COR)

0? y 12? y 24? y 36? y 48? y 60? n 72? y 84? y
1? y 13? y 25? y 37? y 49? y 61? y 73? y 85? y
2? y 14? y 26? y 38? y 50? y 62? n 74? y 86? y
3? y 15? y 27? y 39? y 51? n 63? n 75? y 87? y
4? y 16? y 28? y 40? y 52? y 64? y 76? y 88? y
5? y 17? y 29? y 41? y 53? n 65? y 77? y 89? y
6? y 18? y 30? y 42? y 54? n 66? y 78? y 90? y
7? y 19? y 31? y 43? y 55? n 67? y 79? y 91? y
8? y 20? y 32? y 44? y 56? n 68? y 80? y 92? y
9? y 21? y 33? y 45? y 57? n 69? y 81? y 93? y
10? y 22? y 34? y 46? y 58? n 70? y 82? y 94? y
11? y 23? y 35? y 47? y 59? n 71? y 83? y 95? y





CLASS OF RESTRICTION


SERVICE OBSERVING PERMISSIONS
(Enter "y" to grant permission to service observe the specified COR)
0? y 12? y 24? y 36? y 48? y 60? n 72? y 84? y
1? y 13? y 25? y 37? y 49? y 61? y 73? y 85? y
2? y 14? y 26? y 38? y 50? y 62? n 74? y 86? y
3? y 15? y 27? y 39? y 51? n 63? n 75? y 87? y
4? y 16? y 28? y 40? y 52? y 64? y 76? y 88? y
5? y 17? y 29? y 41? y 53? n 65? y 77? y 89? y
6? y 18? y 30? y 42? y 54? n 66? y 78? y 90? y
7? y 19? y 31? y 43? y 55? n 67? y 79? y 91? y
8? y 20? y 32? y 44? y 56? n 68? y 80? y 92? y
9? y 21? y 33? y 45? y 57? n 69? y 81? y 93? y
10? y 22? y 34? y 46? y 58? n 70? y 82? y 94? y
11? y 23? y 35? y 47? y 59? n 71? y 83? y 95? y
 
Time of Day chart is what they renamed Partitioned Group Number in the COR on the newer systems.

Is the area code you are using, your local area code or is it outside your area like the 1863.

What is above the 1860.. in the ars ana table?

What is trunk group 10?

Some FYI stuff that may help...


DDD Calls with Prefix Digit 1 Required — The Pfx Mrk (Prefix Mark)
field (on the Route Pattern form) is administered as follows for each of the
6 possible routing choices on the form:
The digit 1 may or may not be required at the public network office to
which the call is routing. (If 1 is dialed on 7-digit calls at a stand-alone
system (non-ETN), the 1 is outpulsed by the system.) In the other cases,
the 1 outpulsing requirements are indicated in the system. Since any given
call may have a choice of routes, some of which may require a 1 and some
of which may not, this indication is associated with each route. Five choices are available and are identified in translations by a Prefix Mark.
Digit 1 outpulsing only applies to calls administered as “fnpa” or “hnpa" in
the ARS Digit Analysis table. The values and meanings of the Prefix Marks
are as follows:
— Prefix Mark 0 — Suppress a user-dialed Prefix digit 1 for 10-digit
FNPA calls, but leave a user-dialed Prefix digit 1 for the following
types of calls:
n 10-digit calls that are not administered as FNPA or HNPA
types in the ARS Routing Table.
n 7-digit HNPA calls
— Prefix Mark 1 — Send a 1 on 10-digit calls, but not on 7-digit calls.
— Prefix Mark 2 — Send a 1 on all toll calls (for example, all 10-digit
calls and 7-digit toll calls).
— Prefix Mark 3 — Send a 1 on all toll calls and keep or insert the NPA
to ensure that all toll calls are 10-digit calls. Note that a user-dialed
Prefix digit 1 for a 7-digit call makes it a toll call and, hence, NPA is
also inserted in this case.
— Prefix Mark 4 — Always suppress a user-dialed Prefix digit 1.
Which of the five possible treatments of the 1 prefix digit should be
administered on a given route is based on the characteristics of the
distant office. Prefix Mark 0 prevents the system from sending a 1 prefix
digit for 10-digit FNPA calls. However, the system leaves a user-dialed
prefix digit 1 for 7-digit HNPA calls and 10-digit calls that are not
administered as FNPA or HNPA types in the ARS Routing Table. In some
areas, all toll calls must be dialed as 1+10 digits. Check with your local
network provider.
Prefix Mark 1 causes the system to send a 1 prefix on all 10-digit FNPA
calls.
With Prefix Marks 2 and 3, the decision is based on whether the call is a
toll call. Toll Lists are provided in the system to furnish this information. A
Toll List simply indicates if the office code associated with the call
constitutes a toll call from the interconnecting office (not from the local
system). Up to 32 Toll Lists are provided. The applicable list number, if
any, for the call is assigned in the Routing Pattern.
Prefix Marks are only applicable on 7- or 10-digit DDD public network
calls. Requirements for outpulsing a 1 are specified via Prefix Marks and
go into effect when the call accesses is outpulsed. Digit 1 outpulsing only
applies to calls administered as “fnpa" or “hnpa” in the ARS Digit Analysis
table.
DDD Calls with Prefix Digit 1 Not Required — The first digit of a
long-distance call following the ARS access code may or may not be a 1
(dialing the 1 prefix before a 10-digit call is optional). In systems where the
1 prefix is dialed (even though not required), the prefix is ignored if no
match is found with the “1” included. The default ARS translations include
entries starting with “1.”

Netcon1
 
Hi SJ - Is it possible to tell me the number you want to dial out.
 
try coping route pattern 20 and just change the FRL it looks like rt pattern 20 is the one your using for everything else?

also look at ars digit conversion, make sure some funny stuff is not going on in there.

RTMCKEE
 
NRV, RTMCKEE,

Thanks for the help. Using the info Netcon provided above, I was able to correct the problem (although I think it's going to lead to me redoing the whole ARS table). I changed from fnpa to natl and the call completed without issue using a clean (no digit insertions or deletions) routing path.

Thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top