Hi-
We have had intermittent issues when moving to a new PRI(LEC) with cell phone calls.
Some cell phones require 7 digits or are local and some require 11.
The ars for "1319" was working fine for all "319 area code" outgoing calls - a few days ago.
We have not changed our config or rebooted our switches - have 2 people that have Admin access to system.
1.
We have setup an "ars analysis dialed string" on our S8300/G700's(LSP) for an area code that corresponds to our remote office(S8300/G700-LSP) in another state.
display ars analysis 1319 Page 1 of 2
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 3
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1319 11 11 100 fnpa n
1319398 11 11 26 fnpa n
1319530 11 11 100 fnpa n
1319739 11 11 26 hnpa n
1319866 11 11 26 hnpa n
1319936 11 11 100 fnpa n
display route-pattern 100 Page 1 of 3
Pattern Number: 100 Pattern Name: CDR 1319
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: 20 4 319 1319 n user
display trunk-group 20 Page 1 of 21
TRUNK GROUP
Group Number: 20 Group Type: isdn CDR Reports: y
Group Name: PRI COR: 73 TN: 1 TAC: 720
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
2.
All calls outgoing from the Remote office - that has the 319 area code - appears to be able to dial any "other" LD area codes - except for a handful of unknown cell numbers - to our knowledge at this point.
We could use some help figuring out why the above ARS for 1319 does "not" apply to all "Local" or "LD" outgoing calls with the 319 area code at this time?
Thanks for any help or clues.
-P
We have had intermittent issues when moving to a new PRI(LEC) with cell phone calls.
Some cell phones require 7 digits or are local and some require 11.
The ars for "1319" was working fine for all "319 area code" outgoing calls - a few days ago.
We have not changed our config or rebooted our switches - have 2 people that have Admin access to system.
1.
We have setup an "ars analysis dialed string" on our S8300/G700's(LSP) for an area code that corresponds to our remote office(S8300/G700-LSP) in another state.
display ars analysis 1319 Page 1 of 2
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 3
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1319 11 11 100 fnpa n
1319398 11 11 26 fnpa n
1319530 11 11 100 fnpa n
1319739 11 11 26 hnpa n
1319866 11 11 26 hnpa n
1319936 11 11 100 fnpa n
display route-pattern 100 Page 1 of 3
Pattern Number: 100 Pattern Name: CDR 1319
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: 20 4 319 1319 n user
display trunk-group 20 Page 1 of 21
TRUNK GROUP
Group Number: 20 Group Type: isdn CDR Reports: y
Group Name: PRI COR: 73 TN: 1 TAC: 720
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
2.
All calls outgoing from the Remote office - that has the 319 area code - appears to be able to dial any "other" LD area codes - except for a handful of unknown cell numbers - to our knowledge at this point.
We could use some help figuring out why the above ARS for 1319 does "not" apply to all "Local" or "LD" outgoing calls with the 319 area code at this time?
Thanks for any help or clues.
-P