Issue with ARS and Long distance

[jbower]

Okay, first let me apologize if this is the wrong category for this question.

Last week we received a message on the phones (4029, 4039, 4068)that said "Forbidden" Whenever someone would dial an international call. There is a recorded message that says "The number you have dialed is not authorized, please check with....." This is an PBX generated message.

1) everyone is authorized to dial international-so this is not the issue
2) all international calls go out across a specific PRI, it has better rates of course
3) I replaced the Adtran (CSU/DSU) for this PRI, I actually had a similar issue in the past and that was the culprit (not this time)
4) I reseated the DPT1 card- no difference
5) I replaced the DPT1 card since I had a spare- no difference
6) I called Level3 our service provider and they saw no issues on their end
7) tomorrow I am going to switch the suspect PRI with a good one to see if it follows the PRI or not

Any suggestions where to look next would be greatly appreciated or if you have ever ran into this issue yourself.

[tgn]

may be it is a connection cos issue...
do you have different connection cos for the users or do they have all the same connection cos?

regards...

[jbower]

All the same cos.

[cavagnaro]

a T3 what shows?

[jbower]

I haven't done a T3 trace. I will log it and see what it shows for more information.

[oldboy]

Are they part of a hunt group or CCD group??

[jbower]

No. They just stopped working after 7 years of being in service.

[jbower]

I believe it is a carrier issue. Here is the T3 trace if someone could verify my findings. The first call shows a long distance call forced over a different physical PRI then the one in question. The second trace shows same number going out the Long Distance PRI.

t3
--> Cleaning mtracer...
--> Positionning t3 filters...
+--------+-------+--------+--------+---------+---------+----------+------+
| filter | desti | src_id | cr_nbr | cpl_nbr | us_term | term_nbr | type |
+--------+-------+--------+--------+---------+---------+----------+------+
| 0 | ** | ** | * | ** | * | *** | 165 |
| 1 | ** | ** | * | ** | * | *** | 166 |
| 2 | ** | ** | * | ** | * | *** | 167 |
| 3 | | | | | | | |
| 4 | | | | | | | |
| 5 | | | | | | | |
| 6 | | | | | | | |
| 7 | | | | | | | |
+--------+-------+--------+--------+---------+---------+----------+------+
Traces Analyser activated

mtracer started ...
(842057:000001) MTRACER host (172.16.248.10, CPu_06), version: R10.1.1-j2.603-22-us-c7s2
(842057:000001) MTRACER num: 034, time: 2014/10/15 06:46:49, loss: 0%
______________________________________________________________________________
| (842629:000002) 1021: Send_IO1 (link-nbr=17, sapi=0, tei=0) :
| long: 86 desti: 0 source: 15 cryst: 2 cpl: 26 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 5e 00
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a2
| IE:[18] CHANNEL (l=3) a9 83 8a -> T2 : B channel 10 exclusive
| IE:[1c] FACILITY (l=25)
| [9f] Discriminator of supplementary service applications
| [8b] Interpretation APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=19):
| Invoke Ident. : 0001 (1)
| OP: 0000 (0)
| [80] Context specific (l=11) 42 6f 77 65 72 20 4a 65 72
| 72 79
| IE:[6c] CALLING_NUMBER (l=12) -> 21 81 Num : 7172451112
| IE:[70] CALLED_NUMBER (l=15) -> a1 Num : 01161292732730
|______________________________________________________________________________

______________________________________________________________________________
| (842630:000004) Concatenated-Physical-Event :
| long: 23 desti: 0 source: 0 cryst: 2 cpl: 26 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : de 00
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 8a -> T2 : B channel 10 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (842660:000005) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 2 cpl: 26 us: 0 term: 0 type a5
| tei: 0 >>>> message received : PROGRESS (03) Call ref : de 00
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 84 88
|______________________________________________________________________________

______________________________________________________________________________
| (842673:000006) 1021: Send_IO1 (link-nbr=17, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 26 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : 5e 00
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (842673:000007) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 2 cpl: 26 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : de 00
|______________________________________________________________________________

______________________________________________________________________________
| (842674:000008) 1021: Send_IO1 (link-nbr=17, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 26 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : 5e 00
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (842970:000009) 1021: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 86 desti: 0 source: 15 cryst: 4 cpl: 5 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 12 f0
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a2
| IE:[18] CHANNEL (l=3) a9 83 83 -> T2 : B channel 3 exclusive
| IE:[1c] FACILITY (l=25)
| [9f] Discriminator of supplementary service applications
| [8b] Interpretation APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=19):
| Invoke Ident. : 0001 (1)
| OP: 0000 (0)
| [80] Context specific (l=11) 42 6f 77 65 72 20 4a 65 72
| 72 79
| IE:[6c] CALLING_NUMBER (l=12) -> 21 81 Num : 7172451112
| IE:[70] CALLED_NUMBER (l=15) -> a1 Num : 01161292732730
|______________________________________________________________________________

______________________________________________________________________________
| (842972:000011) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 4 cpl: 5 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 92 f0
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 82 b2 -> [b2] REQUESTED FACILITY NOT SUBSCRIBED
|______________________________________________________________________________



(10)CPu_06> exit
logout

[vad]

Ask from provider:
1) may be some problem with CALLING NUMBER (provider not recognize calling set like authorized user)
2) may be some problem with payment

[jbower]

Verified not a payment issue.
I just spoke with Level3 our provider and they notice that one of the D channels on one of our PRI's was down. So since I have verified from our CSU into the PBX everything is working they are going to send a tech out to see if it is equipment on their end.