Page 1 of 2

Problem with ISDN Incoming Call

Posted: 18 Dec 2007 21:18
by jupiter919
Dear all,

I facing some ISDN Line in one of the customer site,basically cstomer had no problem with outgoing call but there are no incoming received.When I made the T3 traces it show some invalid information from the local carrier.The following traces file as:

mtracer started ...
(125958:000001) MTRACER host (192.168.92.220, C4mlk), version: R7.1-f5.401-17-d-my-c80s1
(125958:000001) MTRACER num: 013, time: 2007/11/16 16:30:35, loss: 0%
______________________________________________________________________________
| (126013:000002) Physical-Event :
| long: 50 desti: 0 source: 0 cryst: 1 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 41 00
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 81 -> T2 : B channel 1 preferred
| IE:[6c] CALLING_NUMBER (l=12) -> 01 83 Num : 0136308879
| IE:[70] CALLED_NUMBER (l=5) -> c1 Num : 8500
|______________________________________________________________________________

______________________________________________________________________________
| (126013:000003) 1149: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 1 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : c1 00
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (126013:000004) 1149: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 1 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : ALERT (01) Call ref : c1 00
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

______________________________________________________________________________
| (126015:000005) Physical-Event :
| long: 27 desti: 0 source: 0 cryst: 1 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : STATUS [7d] Call ref : 41 00
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=4) 02 80 e4 1e -> [e4] INVALID INFORMATION ELEMENT CONTENTS
| IE:[14] CALL_STATE (l=1) 07
|______________________________________________________________________________

______________________________________________________________________________
| (126015:000006) 1149: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 1 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : c1 00
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 e4 -> [e4] INVALID INFORMATION ELEMENT CONTENTS
|______________________________________________________________________________

______________________________________________________________________________
| (126015:000007) Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 1 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 41 00
|______________________________________________________________________________


Hopefully somebody got experience problem before.Thank you.

Re: Problem with ISDN Incoming Call

Posted: 18 Dec 2007 22:26
by cavagnaro
Maybe you can try configuring the OXE to avoid wrong messages from your provider.

mgr/system/
Ignore ISDN Fault In Mandatory EI + YES

Re: Problem with ISDN Incoming Call

Posted: 18 Dec 2007 22:31
by frank
You should try to change the carrier protocol , reset the T1 , and try again.
Did you try ALL carrier protocols, with ALL multiframe type ?

You have 3 in each, so you should try the 9 solutions.

Re: Problem with ISDN Incoming Call

Posted: 19 Dec 2007 02:26
by alex
| IE:[08] CAUSE (l=4) 02 80 e4 1e -> [e4] INVALID INFORMATION ELEMENT CONTENTS
It says that element 1e is not expected together with ALERT.

Above yo see that 1e is
IE:[1e] PROGRESS_ID (l=2) 81 88
Just do not send PROGRESS. You can disable it in local parameters for TG.

Re: Problem with ISDN Incoming Call

Posted: 19 Dec 2007 05:38
by tot3nkopf
Check the B channel choice in TG parameters.

See what happens.

Re: Problem with ISDN Incoming Call

Posted: 19 Dec 2007 05:42
by vad
In System manage "ignore" in items "Reaction Receiving Message State ".

Re: Problem with ISDN Incoming Call

Posted: 19 Dec 2007 09:59
by jupiter919
Dear All,

I had check with this parameter in the system, it Works!! I had ignore everything been send by the provider and finally it Ok now.

That's good if somebody can recomended some ISDN book for it? May be i need to understand the T3 trace info.

Thank you for the help.

Re: Problem with ISDN Incoming Call

Posted: 10 Aug 2011 04:35
by thkim81
Dear All

I wonder about system option.

When I change this system -> Ignore ISDN Fault In Mandatory EI flase -> true, Do i reboot call server ?

and another system option is same ?

Re: Problem with ISDN Incoming Call

Posted: 10 Oct 2019 04:01
by yevhen
Dear All
In our company, we faced a similar situation with incoming calls. Our's ISP taken advice to change the attribute of sending parameters that sent STATUS messages and turn off it. We managed it, but the issue still is. There is an interesting situation because of the different operator mobile network is working on incoming calls.

Below the log incoming call the operator A which doesn't work good:

Traces Analyser activated

mtracer started ...
(767102:000001:16023) MTRACER host (192.164.181.70, xa000000), version: R12.2-m3.402-22-c-ru-c8
(767102:000001:16023) MTRACER num: 010, time: 2019/10/10 09:22:32, loss: 0%
______________________________________________________________________________
| (767145:000002:03609) Concatenated-Physical-Event :
| long: 57 desti: 0 source: 0 cryst: 0 cpl: 9 us: 0 term: 1 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 00 2f
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 81 -> T2 : B channel 1 preferred
| IE:[1e] PROGRESS_ID (l=2) 00 81
| IE:[6c] CALLING_NUMBER (l=12) -> 01 83 Num : 067xxxxxx
| IE:[70] CALLED_NUMBER (l=8) -> c1 Num : 49xxxxx
|______________________________________________________________________________

______________________________________________________________________________
| (767145:000003:03489) 3489: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 26 desti: 0 source: 15 cryst: 0 cpl: 9 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : STATUS [7d] Call ref : 80 2f
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 1e -> [e4] INVALID INFORMATION ELEMENT CONTENTS
| IE:[14] CALL_STATE (l=1) 06
|______________________________________________________________________________

______________________________________________________________________________
| (767145:000004:03489) 3489: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 0 cpl: 9 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : 80 2f
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (767145:000005:03489) 3489: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 0 cpl: 9 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : ALERT (01) Call ref : 80 2f
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________


And different operator B is working well on incoming calls:
(And this call doesn't send the message about STATUS)


Traces Analyser activated

mtracer started ...
(761663:000001:15944) MTRACER host (192.164.181.70, xa000000), version: R12.2-m3.402-22-c-ru-c8
(761663:000001:15944) MTRACER num: 009, time: 2019/10/10 09:13:29, loss: 0%
______________________________________________________________________________
| (761837:000002:03609) Concatenated-Physical-Event :
| long: 53 desti: 0 source: 0 cryst: 0 cpl: 9 us: 0 term: 1 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 00 2c
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 81 -> T2 : B channel 1 preferred
| IE:[6c] CALLING_NUMBER (l=12) -> 01 81 Num : 050xxxxxxx
| IE:[70] CALLED_NUMBER (l=8) -> c1 Num : 49xxxxx
|______________________________________________________________________________

______________________________________________________________________________
| (761837:000003:03489) 3489: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 0 cpl: 9 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : 80 2c
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 81 -> T2 : B channel 1 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (761837:000004:03489) 3489: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 0 cpl: 9 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : ALERT (01) Call ref : 80 2c
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

______________________________________________________________________________
| (761874:000005:03609) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 0 cpl: 9 us: 0 term: 1 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 00 2c
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 80 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (761874:000006:03489) 3489: Send_IO1 (link-nbr=9, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 0 cpl: 9 us: 8 term: 1 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 80 2c
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (761875:000007:03609) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 0 cpl: 9 us: 0 term: 1 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 00 2c
|______________________________________________________________________________


May be somebody knows about this issue somethings!

Re: Problem with ISDN Incoming Call

Posted: 10 Oct 2019 13:35
by tot3nkopf
Maybe System/ Other System Param/ System Parameters/ Specific EI status for GSM?