When we try to make external calls out of our system to the PSTN all etensions now reporting with "Congestion". The E1 service providers are saying there is no issue their side as incoming calls are fine. Here is the trace for the external calls
(1)CS1> 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 ...
(436370:000001:17154) MTRACER host (172.16.5.4, CS1), version: R100.0-n1.291-66-a-ke-c0s1
(436370:000001:17154) MTRACER num: 004, time: 2024/08/05 14:35:09, loss: 0%
______________________________________________________________________________
| (437571:000002:03484) 3484: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 49 desti: 0 source: 15 cryst: 3 cpl: 4 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 c7
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[6c] CALLING_NUMBER (l=6) -> 00 81 Num : 2215
| IE:[70] CALLED_NUMBER (l=11) -> 80 Num : 0789236060
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|______________________________________________________________________________
______________________________________________________________________________
| (437572:000003:03532) Concatenated-Physical-Event :
| long: 23 desti: 0 source: 0 cryst: 3 cpl: 4 us: 0 term: 1 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 80 c7
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 9e -> T2 : B channel 30 exclusive
|______________________________________________________________________________
______________________________________________________________________________
| (437595:000004:03532) Concatenated-Physical-Event :
| long: 26 desti: 0 source: 0 cryst: 3 cpl: 4 us: 0 term: 1 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 80 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=6) 82 a9 00 00 00 00 -> [a9] TEMPORARY FAILURE
|______________________________________________________________________________
______________________________________________________________________________
| (437595:000005:03484) 3484: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 4 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 00 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 08 -> [e4] INVALID INFORMATION ELEMENT CONTENTS
|______________________________________________________________________________
______________________________________________________________________________
| (437598:000006:03532) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 3 cpl: 4 us: 0 term: 1 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 80 c7
|______________________________________________________________________________
Not Able to make External Calls, message received "Congestion"
-
imukonyezi
- Member
- Posts: 19
- Joined: 09 Apr 2021 13:24
Re: Not Able to make External Calls, message received "Congestion"
Just wait a bit. It's just a temporary failure.imukonyezi wrote: ↑05 Aug 2024 07:49
______________________________________________________________________________
| (437595:000004:03532) Concatenated-Physical-Event :
| long: 26 desti: 0 source: 0 cryst: 3 cpl: 4 us: 0 term: 1 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 80 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=6) 82 a9 00 00 00 00 -> [a9] TEMPORARY FAILURE
|______________________________________________________________________________
Could be a problem on another service provider in network but in any case you receive DISCONNECT from your provider so you could create a ticket.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
- frank
- Alcatel Unleashed Certified Guru

- Posts: 3402
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: Not Able to make External Calls, message received "Congestion"
You also have
______________________________________________________________________________
| (437595:000004:03532) Concatenated-Physical-Event :
| long: 26 desti: 0 source: 0 cryst: 3 cpl: 4 us: 0 term: 1 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 80 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=6) 82 a9 00 00 00 00 -> [a9] TEMPORARY FAILURE
|______________________________________________________________________________
When you decode Information Element, your first octet (82) cause for issue is "No route to specified transit network".
This is coming from your carrier. Therefore it's on their end. You should tell them that the information element message you receive in your isdn trace mention that THEY are telling you there is no route to the transit network.
Your other message here
______________________________________________________________________________
| (437595:000005:03484) 3484: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 4 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 00 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 08 -> [e4] INVALID INFORMATION ELEMENT CONTENTS
|______________________________________________________________________________
means "Unallocated (unassigned) number.
They dont know how to route that. Probably on their end again.
______________________________________________________________________________
| (437595:000004:03532) Concatenated-Physical-Event :
| long: 26 desti: 0 source: 0 cryst: 3 cpl: 4 us: 0 term: 1 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 80 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=6) 82 a9 00 00 00 00 -> [a9] TEMPORARY FAILURE
|______________________________________________________________________________
When you decode Information Element, your first octet (82) cause for issue is "No route to specified transit network".
This is coming from your carrier. Therefore it's on their end. You should tell them that the information element message you receive in your isdn trace mention that THEY are telling you there is no route to the transit network.
Your other message here
______________________________________________________________________________
| (437595:000005:03484) 3484: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 4 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 00 c7
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 08 -> [e4] INVALID INFORMATION ELEMENT CONTENTS
|______________________________________________________________________________
means "Unallocated (unassigned) number.
They dont know how to route that. Probably on their end again.
Code Free Or Die
