ISDN Disconnect not working

[wallacezammit]

Hi,

I have an oxe release 9 which has a pra E1 connected to it.

There is a situation when the disconnect is not working :

If I dial an external number of a mobile and hang up immediately, the disconnect doesn't work, the mobile still rings and when is answered a void sound is heard since there would be no one on the other end.

If I dial the same number but wait till it rings and then hang up, the disconnect works and mobile stops ringing. Even if I am in conversation and hang up the disconnect works.

I did some tracing together with the carrier provider and during the situation where the disconnect doesn't work the carrier told me that they are not receiving the disconnect message. But with my t3 trace on the oxe I could see the disconnect message followed by the normal call clearing message.

Do you know what could be the problem?

The t3 trace is performed on the pra card?

Thanks and Regards
Wallace

[haroun]

Can u put the t3 trace for that issue
disconnect is send or not ? ack received ?

[wallacezammit]

Hi,

the t3 trace shows that the disconnect is being sent but no ack is received as you can see from the t3 trace below

But the carrier provider is saying that they are not receiving any disconnect message from us.

So I don't know if the pabx is really sending the disconnect message or not.

t3 trace of a call to a mobile and hanging up right after the number was dialed :

______________________________________________________________________________
| (978931:000004) 1061: Send_IO1 (link-nbr=0, sapi=0, tei=0) :
| long: 49 desti: 0 source: 15 cryst: 0 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 44 8a
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 8e -> T2 : B channel 14 exclusive
| IE:[6c] CALLING_NUMBER (l=10) -> 01 81 Num : 25992502
| IE:[70] CALLED_NUMBER (l=3) -> 81 Num : 99
| IE:[7d] HLC (l=2) 91 81
|______________________________________________________________________________
______________________________________________________________________________
| (978932:000006) 1061: Send_IO1 (link-nbr=0, sapi=0, tei=0) :
| long: 27 desti: 0 source: 15 cryst: 0 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : INFORMATION [7b] Call ref : 44 8a
|______________________________________________________________________________
|
| IE:[70] CALLED_NUMBER (l=7) -> 81 Num : 499988
|______________________________________________________________________________
______________________________________________________________________________
| (978940:000008) 1061: Send_IO1 (link-nbr=0, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 0 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : 44 8a
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

[cavagnaro]

Well as you can see pbx does, they "say", any proof?

[murraya]

be careful with t3.
it is known that the trace is on the coupler and not on the actual circuit. it is possible that the t3 shows messages that don't actually get sent to line so it would be good to get trace from provider and open e-sr with both traces attached.

[haroun]

oh with /wout ovellaping dialling mode?
something wrong here lotof messages sent but no answer, at list after setup & information " message received :call proc no? you are not so much fast that opposite system don't have time to send call process.
disconnet is not taken in consideration so release is absent .
timer issue may be ?

[wallacezammit]

it is with overlapping dialing mode.

which timer issue can it be?