I have interconnected 2 Alcatel OXE PBXs with Yeastar TE100 gateways. Analogue and digital extensions from the two systems can call each other using the E1 link but the attendant sets can call other remote extensions. I am getting trunk unavailable error.
Can someone assist
E1 trunk unavailable on OXE Attendant sets
Re: E1 trunk unavailable on OXE Attendant sets
hi
traces please !
traces please !
Re: E1 trunk unavailable on OXE Attendant sets
Entity, public network COS (attendant sets and usual) - the same?
You have problem with outgoing site (COS etc) or with incoming (DID routing etc)?
You have problem with outgoing site (COS etc) or with incoming (DID routing etc)?
Re: E1 trunk unavailable on OXE Attendant sets
haroun wrote: ↑29 Oct 2024 10:15 hi
traces please !
[(101)xa001001> 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 ...
(348642:000001) MTRACER host (10.237.7.2, xa001001), version: R11.0.1-k1.520-29-e-za-c7s2
(348642:000001) MTRACER num: 004, time: 2024/10/30 12:03:09, loss: 0%
______________________________________________________________________________
| (348754:000002) 1044: Send_IO1 (link-nbr=11, sapi=0, tei=0) :
| long: 44 desti: 0 source: 15 cryst: 0 cpl: 11 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 08 ca
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 85 -> T2 : B channel 5 exclusive
| IE:[6c] CALLING_NUMBER (l=2) -> 00 81 Num :
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 4004
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|______________________________________________________________________________
______________________________________________________________________________
| (348755:000003) Concatenated-Physical-Event :
| long: 23 desti: 0 source: 0 cryst: 0 cpl: 11 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 88 ca
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 85 -> T2 : B channel 5 exclusive
|______________________________________________________________________________
______________________________________________________________________________
| (348755:000004) 1044: Send_IO1 (link-nbr=11, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 0 cpl: 11 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : 08 ca
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
______________________________________________________________________________
| (348756:000005) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 0 cpl: 11 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 88 ca
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
______________________________________________________________________________
| (348756:000006) 1044: Send_IO1 (link-nbr=11, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 0 cpl: 11 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : 08 ca
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
]
Re: E1 trunk unavailable on OXE Attendant sets
Is that trace for the call with issues ? because nothing is wrong except for the calling number IE:[6c] CALLING_NUMBER (l=2) -> 00 81 Num : and the
disconnect is sent from the calling oxe after it receives Call processing whichi is not be a big deal .
message sent : DISCONNECT [45] Call ref : 08 ca
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
CAN YOU attribute a normal Directory number for that attandent ? and test again
I guess this the thopology
OXE1-----E1----Yeastar TE100------E1------OXE2
disconnect is sent from the calling oxe after it receives Call processing whichi is not be a big deal .
message sent : DISCONNECT [45] Call ref : 08 ca
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
CAN YOU attribute a normal Directory number for that attandent ? and test again
I guess this the thopology
OXE1-----E1----Yeastar TE100------E1------OXE2
Re: E1 trunk unavailable on OXE Attendant sets
haroun wrote: ↑31 Oct 2024 09:04 Is that trace for the call with issues ? because nothing is wrong except for the calling number IE:[6c] CALLING_NUMBER (l=2) -> 00 81 Num : and the
disconnect is sent from the calling oxe after it receives Call processing whichi is not be a big deal .
message sent : DISCONNECT [45] Call ref : 08 ca
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
CAN YOU attribute a normal Directory number for that attandent ? and test again
I guess this the thopology
OXE1-----E1----Yeastar TE100------E1------OXE2
[I have created attendant as1001 and Individual Att. call as 8201 but it is failing to pick the trunk group. Any other extensions can call each other.
(102)xa000000> t3
____________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
| IE:[28] DISPLAY (l=4) `8201`
| IE:[6c] CALLING_NUMBER (l=6) -> 21 81 Num : 8201
| IE:[70] CALLED_NUMBER (l=5) -> 81 Num : 4004
| [a1] Sending complete
|______________________________________________________________________________
(101)xa001001> t3
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 98 -> T2 : B channel 24 exclusive
| IE:[6c] CALLING_NUMBER (l=6) -> 00 81 Num : 8201
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 4004
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|___________________________________________________________
Re: E1 trunk unavailable on OXE Attendant sets
the above traces are incomplete please paste the whole trace
2how did the attd seize the trunkgp? prefix ? how did you call the remote oxe extension network number , routing number , abbreviated n°, prefix etc ?
2how did the attd seize the trunkgp? prefix ? how did you call the remote oxe extension network number , routing number , abbreviated n°, prefix etc ?
Re: E1 trunk unavailable on OXE Attendant sets
haroun wrote: ↑03 Nov 2024 01:07 the above traces are incomplete please paste the whole trace
2how did the attd seize the trunkgp? prefix ? how did you call the remote oxe extension network number , routing number , abbreviated n°, prefix etc ?
[I have resolved the issue by creating a trunk group seize prefix. The attendant dials the prefix followed by extension number and it's going through.]