call release unspected

Post Reply
fery_s
Member
Posts: 72
Joined: 08 Nov 2014 06:38

call release unspected

Post by fery_s » 07 May 2017 04:05

hi dear alcatel man
i have pra e1 link and some of my incomming call is release during conversation.
in t3 trace i have this cause:
|______________________________________________________________________________
| (885298:030202) Concatenated-Physical-Event :
| long: 30 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 14 a9
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 82 93 -> [93] NO ANSWER FROM USER (USER ALERTED)
| IE:[1e] PROGRESS_ID (l=2) 82 88
| IE:[1e] PROGRESS_ID (l=2) 84 83
|______________________________________________________________________________

have you any idea what is the problem?

HUSSAINQCS
Member
Posts: 290
Joined: 21 Jan 2017 02:57

Re: call release unspected

Post by HUSSAINQCS » 07 May 2017 04:12

We need complete t3 trace calling no and caling no without that how ?

fery_s
Member
Posts: 72
Joined: 08 Nov 2014 06:38

Re: call release unspected

Post by fery_s » 07 May 2017 04:37

here is the complete t3:

______________________________________________________________________________
| (694457:021333) Concatenated-Physical-Event :
| long: 54 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 13 48
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=3) a9 83 97 -> T2 : B channel 23 exclusive
| IE:[1e] PROGRESS_ID (l=2) 84 83
| IE:[6c] CALLING_NUMBER (l=14) -> 00 83 Num : 6388569973
| IE:[70] CALLED_NUMBER (l=4) -> 81 Num : 84855466
|______________________________________________________________________________

______________________________________________________________________________
| (694457:021334) 1269: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 2 cpl: 7 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : 93 48
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 97 -> T2 : B channel 23 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (694457:021335) 1269: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 7 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : ALERT (01) Call ref : 93 48
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

______________________________________________________________________________
| (694457:021336) 1269: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 18 desti: 0 source: 15 cryst: 2 cpl: 7 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CONNECT (07) Call ref : 93 48
|______________________________________________________________________________

______________________________________________________________________________
| (694458:021337) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CONNECT ACK (0f) Call ref : 13 48
|______________________________________________________________________________

______________________________________________________________________________
| (695064:021351) Concatenated-Physical-Event :
| long: 30 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 13 48
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 82 93 -> [93] NO ANSWER FROM USER (USER ALERTED)
| IE:[1e] PROGRESS_ID (l=2) 82 88
| IE:[1e] PROGRESS_ID (l=2) 84 83
|______________________________________________________________________________

______________________________________________________________________________
| (695065:021352) 1269: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 7 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 93 48
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (695066:021353) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 13 48
|______________________________________________________________________________

HUSSAINQCS
Member
Posts: 290
Joined: 21 Jan 2017 02:57

Re: call release unspected

Post by HUSSAINQCS » 07 May 2017 06:29

In the below trace we are getting to know that OXE is receiving the disconnect message from the other end and this is not form the OXE side



| (695064:021351) Concatenated-Physical-Event :
| long: 30 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 13 48
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 82 93 -> [93] NO ANSWER FROM USER (USER ALERTED)
| IE:[1e] PROGRESS_ID (l=2) 82 88
| IE:[1e] PROGRESS_ID (l=2) 84 83
|______________________________________________________________________________

______________________________________________________________________________
| (695065:021352) 1269: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 7 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 93 48
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

fery_s
Member
Posts: 72
Joined: 08 Nov 2014 06:38

Re: call release unspected

Post by fery_s » 07 May 2017 11:09

HUSSAINQCS wrote:
07 May 2017 06:29
In the below trace we are getting to know that OXE is receiving the disconnect message from the other end and this is not form the OXE side



| (695064:021351) Concatenated-Physical-Event :
| long: 30 desti: 0 source: 0 cryst: 2 cpl: 7 us: 0 term: 0 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 13 48
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 82 93 -> [93] NO ANSWER FROM USER (USER ALERTED)
| IE:[1e] PROGRESS_ID (l=2) 82 88
| IE:[1e] PROGRESS_ID (l=2) 84 83
|______________________________________________________________________________

______________________________________________________________________________
| (695065:021352) 1269: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 7 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 93 48
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
thank you for your reply. as i know the NO ANSWER FROM USER (USER ALERTED) is the isdn code cause bye the remote connection but when i recive it from the public network provider is that mean the problem is in the oxe????

HUSSAINQCS
Member
Posts: 290
Joined: 21 Jan 2017 02:57

Re: call release unspected

Post by HUSSAINQCS » 07 May 2017 11:18

No its not from oxe

Post Reply

Return to “Traces”