ARS problem

[sha111]

Hi,

I found the following entries in ARS digit analysis report,


ARS DIGIT ANALYSIS REPORT

Location: all

Dialed Total Route Call Node
String Min Max Pattern Type Number

905 10 10 p1 hnpa

1905 11 11 p1 fnpa

Please let me know if we can use both hnpa and fnpa for same area code. The problem we are facing is when users are trying to dial a specific number with area code 919...
getting error "your call did not go thru".

Shall i remove second entry (1905...) to resolve this issue?

Thanks.

 

[sha111]

one correction,

users are trying to dial a specific number with area code 905 and not 919...but getting error.

Thanks.

 

[4merAvaya]

Put a trace up (list trace station xxxx) and have the user dial the number. The trace should show you what the PBX is sending to the network.

Kevin

 

[sha111]

Thanks for reply....list trace station xxxx, which
station i should trace..the destination station(called number)?

 

[4merAvaya]

The one making the call.

 

[sha111]

Getting denial event 1178 when we do list trace station...

any clues?

Thanx.

 

[sha111]

Thanks...

here is list trace result,

LIST TRACE

time data

13:14:25 active station 2942792 cid 0x1ff5
13:14:25 G711MU ssff ps:20 rn:2/2 10.37.40.142:50736 10.37.5.171:50064
13:14:25 xoip: faxT modemT ttyff 10.37.5.171:50064 uid:0x886c
13:14:36 dial 9905472602 route:HNPA|ARS
13:14:36 term trunk-group 22 cid 0x1ff5
13:14:36 dial 99054726021 route:HNPA|ARS
13:14:36 route-pattern 1 preference 1 cid 0x1ff5
13:14:36 seize trunk-group 22 member 100 cid 0x1ff5
13:14:36 Setup digits 9054726021
13:14:36 Calling Number & Name 9052942792
13:14:36 G711MU ssff ps:20 rn:2/2 10.37.40.142:50736 10.37.5.170:51016
13:14:36 xoip: faxT modemT ttyff 10.37.5.170:51016 uid:0x886c
13:14:36 Proceed trunk-group 22 member 100 cid 0x1ff5
13:14:53 idle station 2942792 cid 0x1ff5

The user is getting error message,
"your call did not get through " 441T

what does 441T mean?

 

[Zen216]

my first thought is that 905 needs a "1" before it to successfully dial out... Can you successfulyl dial out to the same number if you dial 91905472602? If so try changing hnpa to fnpa, in your ARS analysis ,
by the looks of your posts above,, looks like they use the same route pattern,, so if you change to fnpa,, then the prefix mark should put the 1 in for you...

 

[koglass]

905 is an fnpa and not an hnpa. Change 905 and make it fnpa.

 

[sha111]

thanks again,

Today user was able to dial the number twice succesfully with same hnpa setting,but failed to get thru on the third attempt.

here is list trace tac,

list trace tac *91 Page 1

LIST TRACE

time data

15:30:54 dial 99054726021 route:HNPA|ARS
15:30:54 route-pattern 1 preference 1 cid 0x3991
15:30:54 seize trunk-group 22 member 7 cid 0x3991
15:30:54 Setup digits 9054726021
15:30:54 Calling Number & Name 9052942792
15:30:54 Proceed trunk-group 22 member 7 cid 0x3991
15:31:12 idle station 2942792 cid 0x3991

any clues?

 

[Zen216]

display your route pattern for the call...

 

[sha111]

Thanks for reply....

Pattern Number: 1 Pattern Name: Local
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: 22 1 200 0 n user
2: 21 1 200 0 n user
3: 31 1 200 0 n user
4: n user
5: n user
6: n user

BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 3 4 W Request Dgts Format
Subaddress
1: y y y y y n n bothept sdn none
2: y y y y y n n bothept sdn none
3: y y y y y n n bothept sdn none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none

 

[Zen216]

Just curious... but could the calls that made it ok happen to use preference 2 and 3,, and preference 1 (based on your trace) is the one failing? Maybe trunk group 22 needs the "1" but groups 21 and 31 don't?


this is the prefix mark table I pulled from a ars cd...

Prefix Call Type #of Digits Prefix
Mark Outpulsed Outpulsed
0 (1)+10D FNPA 10D None
(1)+10D HNPA 7D None
7D HNPA 7D None
1+7D HNPA 7D 1+

1 (1)+10D FNPA 10D 1+
(1)+10D HNPA 7D None
7D HNPA 7D None
1+7D HNPA 7D 1+

2 (1)+10D FNPA 10D 1+
(1)+10D HNPA 7D(Local) None
(1)+10D HNPA 7D(Toll) 1+
7D HNPA 7D(Local) None
7D HNPA 7D(Toll) 1+
1+7D HNPA 7D 1+

3 (1)+10D FNPA 10D 1+
(1)+10D HNPA 7D(Local) None
(1)+10D HNPA 10D(Toll) 1+
7D HNPA 7D(Local) None
7D HNPA 10D(Toll) 1+
1+7D HNPA 10D 1+

4 (1)+10D FNPA 10D none
(1)+10D HNPA 7D none
7D HNPA 7D none
1+7D HNPA 7D none



I am not really positive about the prefix mark and how it works,, but I was thinking maybe change it to a 2 for preference 1? I am sure the guru's here will correct me if I'm wrong

 

[sjforcum]

What type of trunks are being used for outbound calls?

If the T-1 Outgoing setting on the trunk group isn't set properly, it could cause an issue with the carrier not receiving all of the digits..

SJF

 

[1a22ip]

In my Old Phone Guy option If you complete calls on the same trunk group twice and the third fails with no changes on you end the problem is the Carrier. "your call did not get through " 441T

what does 441T mean? 441T is the announcement code from the carrier. Tell them this code and they should tell you what the problem is. Again all points to the carrier.

Just an old phone guy rant
ED

1a2 to ip I seen it all

 

[MERIDIAN11C]

display your partition table