Alcatel Unleashed

Hello Guys ,

The case is the following ,

ISDN (TO)-->OXO<---SIPTRUNK-->OXO-->ONMITOUCH CALL CENTER (ACD)

When an incoming call is landed to acd from isdn and the caller hungs up, the release of the call comes after 30 sec.

The traces from OCS is the following :
ISDN3_00004 26/10 17:27:05 RX d_channel: 26 (S:00 T:127) payload: (44) 08 01 01 05 A1 04 03 80 90 A3 18 01 89 6C 0C 00 81 36 39 35 31 30 30 34 35 30 35 70 0B C1 32 33 31 30 35 34 33 39 31 30 7D 02 91 81
0x05 SETUP Ref: O,1
ie 0xA1 Sending complete
ie 0x04 Bearer capability: 80 90 A3
Coding: CCITT standardized
Information transfer capability: Speech
Transfer mode: Circuit mode
Transfer rate: 64 Kbit/s
User info layer 1: G.711 A-law
ie 0x18 Channel identification: 89
Interface identifier: Implicit
Interface type: Basic
Indicated channel: Exclusive
D-channel identified: Yes
Information channel selection: B1 channel
ie 0x6C Calling party number: 00 81 36 39 35 31 30 30 34 35 30 35
Number type: Unknown
Numbering plan: Unknown
Presentation: presentation allowed
Screening: user-provided, verified and passed
Number: 695XXXXXX -------------------------------------------------------------------->(callers number)
[/size] ie 0x70 Called party number: C1 32 33 31 30 35 34 33 39 31 30
Number type: Subscriber number
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 231xxxxxxx----------------------------------------------------------------------->(called number)
ie 0x7D High layer compatibility: 91 81
ISDN3_00005 26/10 17:27:05 TX d_channel: 26 (S:00 T:000) payload: (7) 08 01 81 02 18 01 89
0x02 CALL_PROCEEDING Ref: D,1
ie 0x18 Channel identification: 89
Interface identifier: Implicit
Interface type: Basic
Indicated channel: Exclusive
D-channel identified: Yes
Information channel selection: B1 channel
ISDN3_00006 26/10 17:27:05 TX d_channel: 26 (S:00 T:000) payload: (8) 08 01 81 03 1E 02 85 81
0x03 PROGRESS Ref: D,1
ie 0x1E Progress indicator: 85 81
Coding: CCITT standardized
Location: Private network serving the remote user
Progress: Call is not end-to-end ISDN: more info may be available in-band -----------------------------------------(SIP trunk)
ISDN3_00007 26/10 17:27:05 TX d_channel: 26 (S:00 T:000) payload: (42) 08 01 81 01 1C 20 91 A1 12 02 01 6F 02 01 12 30 0A 0A 01 00 0A 01 02 A0 02 80 00 A1 09 02 01 70 02 01 13 01 01 FF 1E 02 85 82
0x01 ALERTING Ref: D,1
ie 0x1C Facility: 91 A1 12 02 01 6F 02 01 12 30 0A 0A 01 00 0A 01 02 A0 02 80 00 A1 09 02 01 70 02 01 13 01 01 FF
ie 0x1E Progress indicator: 85 82
Coding: CCITT standardized
Location: Private network serving the remote user
Progress: Destination address is non-ISDN
ISDN3_00008 26/10 17:27:06 TX d_channel: 26 (S:00 T:000) payload: (8) 08 01 81 07 1E 02 85 81
0x07 CONNECT Ref: D,1
ie 0x1E Progress indicator: 85 81
Coding: CCITT standardized
Location: Private network serving the remote user
Progress: Call is not end-to-end ISDN: more info may be available in-band-------------------------------(ACD)
ISDN3_00009 26/10 17:27:06 RX d_channel: 26 (S:00 T:000) payload: (4) 08 01 01 0F
0x0F CONNECT_ACK Ref: O,1
ISDN3_00012 26/10 17:27:30 RX d_channel: 26 (S:00 T:000) payload: (12) 08 01 01 45 08 02 80 90 1E 02 82 88
0x45 DISCONNECT Ref: O,1--------------------------------------------------------------------------------------------------------------CALLER HUNG UP
ie 0x08 Cause: 80 90
Coding: CCITT standardized
Location: User
Class: Normal event
Value: Normal release
ie 0x1E Progress indicator: 82 88
Coding: CCITT standardized
Location: Public network serving the local user
Progress: In-band information or appropriate pattern now available

Waiting 30 SECONDS

ISDN3_00015 26/10 17:28:00 RX d_channel: 26 (S:00 T:000) payload: (8) 08 01 01 4D 08 02 80 90
0x4D RELEASE Ref: O,1
ie 0x08 Cause: 80 90
Coding: CCITT standardized
Location: User
Class: Normal event
Value: Normal release
ISDN3_00016 26/10 17:28:00 TX d_channel: 26 (S:00 T:000) payload: (4) 08 01 81 5A
0x5A RELEASE_COMP Ref: D,1
SAN_00017 at line 18060 "dljex.c"
on 26.10 at 17:28:00 (7075467)
info : FFFF FFF9 FFFF FFFF 0000 0002 0000 010F

COMPLETE.


when it is in conversation If the call is terminated by the acd agent is done immediately , but if the opposite happens ,caller hungs up the release comes after 30 secs and the acd agent must hung up manually if he wants to terminate the call earlier .The problem occurs also when the call is landed to welcome message of the acd and the caller hungs up before the call is arived to the agent the call is ringing (again 30 sec). If he answer the call is hearing disconnect tone for 30 sec

Codecs ,rtp, isdn protocols triple checked...

Any idea why this is happening ?

Tried so many things but no luck .

Thanks !!

Hi

I don't have many ISDN trunks because this is not common here, usually E1 R2. But if you call to ISDN trunk landing to an extension of the same OXO as ISDN and the caller releases the call, what does it happen?
It may be a stupid question, but you don't mention anything about this.

Best regards.

hello enio .

on the same oxo works fine . no problems.

tomorrow I will sent the sip traces to check there also. calls btwn the 2 oxos are working perfect. I don't think is the sip trunking is the problem .


Sent from my iPhone using Tapatalk

It is. Check the forum for this issue. We have discussed it a lot.
30 seconds is a symptom of SIP signalling path issues.

Enviado de meu E6633 usando Tapatalk

Hello Cav ,

I have searched the forum but I cannot find a similar case .
Maybe the terms I am searching is deferent from the ones you referring to .
I have posted also the wireshark traces.

The thing I see the disconnect message doenst passthrough from the sip trunk .
Rtp port is open until I get ICMP message unreachable and then the call disconnects .

Any hint to check to make this message appear?

Thanks!

Hi Konstantinos.E

Do you have the .pcap file to share? What is the OXO IP address where ISDN is connected?

Best regards.

Hello Enio,

Down load the txt file and rename it to pcap . then you can open it!

isdn--192.168.1.246---sip--192.168.1.230---acd

Thanks

Hi Konstantinos.E

Fur sure, I downloaded the file but my brain could not understand what you wrote in the name.

Well, I saw the trace and on my undertanding, OXO 192.168.1.246 should send BYE to the other side when ISDN caller releases the call, but it does not do it. It does 30 seconds later, as you said the call releases after 30 seconds, although I can see the BYE.
I have a lot of OXO with this scenario, but with PCM R2. I have never seen this situation here.

On my understand, OXO 192.168.1.246 receives disconnection from ISDN, as you said on the same OXO works fine, but it does not send it through SIP trunk.
From traces I can understand your OXO 192.168.1.246 is R7.10 and OXO 192.168.1.230 is R10.1. Is it correct? If yes, I would run a test, if possible, upgrading OXO 192.168.1.246 at least to tha same release as OXO 192.168.1.230. R7.10 is too old and a lot of SIP improvements have been done, and this might cause the situation you are facing.

I would open a SR with Alcatel-Lucent to check it out, although somebody may have another opinion about the traces that can help you, but if your OXO is running on R7.10, there is no technical support anymore.

Best regards.

I will do the test and I will let you know!

SIP 30 seconds

tip: DNS resolution