Summary: | ASTERISK-13093: Calls are not beeing disconnected | ||
Reporter: | Marcin Kowalczyk (kowalma) | Labels: | |
Date Opened: | 2008-11-19 14:43:41.000-0600 | Date Closed: | 2009-01-28 19:58:13.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) agent-ibm.JPG ( 1) ibm-gateway.JPG | |
Description: | Hi, I have very strange problem, that some calls remain in my asterisk box. I use sesion timer so call should be dropped after expire time but it stays. My main (I call it Asterisk-IBM) asterisk is 1.6.0.1 stable. Agents also use same asterisk version. Each agent has installed asterisk on his PC. On Asterisk-IBM I can see hanging calls ie: asterisk-IBM*CLI> core show channel SIP/1127-afccc138 -- General --LI> Name: SIP/1127-afccc138 Type: SIP UniqueID: 1227122591.258108 Caller ID: 1127 Caller ID Name: agent--name DNID Digits: 0107040300050850522 Language: en State: Ring (4) Rings: 0 NativeFormats: 0x8 (alaw) WriteFormat: 0x8 (alaw) ReadFormat: 0x8 (alaw) WriteTranscode: No ReadTranscode: No 1st File Descriptor: 757 Frames in: 2753 Frames out: 1424 Time to Hangup: 0 Elapsed Time: 1h3m31s Direct Bridge: <none> Indirect Bridge: <none> -- PBX -- Context: ccig Extension: 01070403000508505223 Priority: 40 Call Group: 0 Pickup Group: 0 Application: Dial Data: Local/1010505223@mg Blocking in: ast_waitfor_nandfds Variables: GOSUB_RETVAL= gw=1010 typ=110 NoUseLCR=1 ProjektOK=1 BiuroOK=1 numer=505223 konsultant=000508 team=03 projektPOD=04 projektGL=07 projekt=0704 biuro=01 SPYGROUP=1127:000508 full=01070403000508505223 SIPCALLID=416663194bb91e142aab98333dadf0d4@192.168.1.127 SIPDOMAIN=sip.local SIPURI=sip:1127@192.168.1.127 CDR Variables: level 1: godzina=20 level 1: licznik=1 level 1: clid="agent.name" <1127> level 1: src=1127 level 1: dst=01070403000508505223 level 1: dcontext=ccig level 1: channel=SIP/1127-afccc138 level 1: dstchannel=Local/1010505223@mg-e1d6;1 level 1: lastapp=Dial level 1: lastdata=Local/1010505223@mg level 1: start=2008-11-19 20:23:11 level 1: duration=3811 level 1: billsec=0 level 1: disposition=NO ANSWER level 1: amaflags=DOCUMENTATION level 1: uniqueid=1227122591.258108 when I login to agetnt's asterisk there is no call CC1127*CLI> core show channels Channel Location State Application(Data) 0 active channels 0 active calls 584 calls processed CC1127*CLI> In Agent's CDR I can see that call had status "no answer" CC1127:/var/log/asterisk/cdr-custom# grep 01070403000508505223 * "","","konsultant","default","Dial","SIP/1127/01070403000508505223","2008-11-19 20:22:56","","2008-11-19 20:22:57","1","0","NO ANSWER","DOCUMENTATION","","","1227122576.1055","","","","","","Local/konsultant@default-28d9;1" CC1127:/var/log/asterisk/cdr-custom# For today my Asterisk processed "133053 calls processed" and: 172 active channels, 86 active calls hangs in system. On my "master" Asterisk I have following setup for Session-Timer: rtptimeout = 600 session-timers=accept session-expires=120 session-minse=90 session-refresher=uas rtptimeout=600 on client: rtptimeout = 600 session-timers=accept session-expires=120 session-minse=90 session-refresher=uac | ||
Comments: | By: Mark Michelson (mmichelson) 2008-11-21 14:46:51.000-0600 murf: Do you think this might be a case of the stale BYE/CANCEL problem that you fixed earlier in 1.4? By: Marcin Kowalczyk (kowalma) 2008-11-21 15:55:49.000-0600 I've just checked tcpdump and you are right - bye is missing. But I think session timer should handle this? I've attached screenshot from whireshark showing SIP between agent and IBM box, and IBM box and asterisk acting as media gateway. I've just checked, that this media-gateway asterisk is running 1.4.19-rc4, so I will upgrade it tomorrow to 1.6.0.1 stable. By: Mark Michelson (mmichelson) 2008-11-21 16:01:25.000-0600 kowalma: It may be worth trying, especially since 1.4 does not contain session timer support. The problem I was asking murf about was a different one, though, and so I figured he would know if your situation matched one which he fixed recently. He would know what to ask for in order to identify the problem. It is also possible that this is a problem which we have not seen before. By: Marcin Kowalczyk (kowalma) 2008-11-21 16:49:33.000-0600 ok - Asterisk media-gateway upgraded to 1.6.0.1. Let's see if it solves problem. By: Leif Madsen (lmadsen) 2008-11-24 08:31:11.000-0600 Waiting on feedback to determine if this is an issue when running on 1.6. By: Marcin Kowalczyk (kowalma) 2008-11-24 08:43:32.000-0600 for now it looks that upgade to 1.6 on MG solved problem, but let's wait unill end of work-day (5 more hours) By: Marcin Kowalczyk (kowalma) 2008-11-24 14:52:18.000-0600 I've just found hanged connection on DAHDI channel asterisk-IBM*CLI> core show channel DAHDI/27-1 -- General --LI> Name: DAHDI/27-1 Type: DAHDI UniqueID: 1227531626.98227 Caller ID: 1030338 Caller ID Name: (N/A) DNID Digits: (N/A) Language: en State: Ringing (5) Rings: 0 NativeFormats: 0x48 (alaw|slin) WriteFormat: 0x8 (alaw) ReadFormat: 0x8 (alaw) WriteTranscode: No ReadTranscode: No 1st File Descriptor: 47 Frames in: 2580 Frames out: 510 Time to Hangup: 0 Elapsed Time: 7h49m3s Direct Bridge: <none> Indirect Bridge: <none> -- PBX -- Context: do-centrali Extension: 1030338 Priority: 1 Call Group: 0 Pickup Group: 0 Application: AppDial Data: (Outgoing Line) Blocking in: (Not Blocking) Variables: DIALEDPEERNUMBER=R0/3385 TRANSFERCAPABILITY=SPEECH CDR Variables:> level 1: dst=s level 1: dcontext=do-centrali level 1: channel=DAHDI/27-1 level 1: start=2008-11-24 14:00:26 level 1: duration=28142 level 1: billsec=0 level 1: disposition=NO ANSWER level 1: amaflags=DOCUMENTATION level 1: uniqueid=1227531626.98227 By: Leif Madsen (lmadsen) 2008-12-22 11:19:47.000-0600 Changed back to acknowledged as reporter has provided some more information. By: Mark Michelson (mmichelson) 2008-12-22 11:24:33.000-0600 A hung DAHDI channel...I wonder if this is the same issue as ASTERISK-13201? By: Leif Madsen (lmadsen) 2008-12-22 11:50:12.000-0600 It is possible.. I'm going to make these issues related right now so we can verify that. Thanks! By: Leif Madsen (lmadsen) 2009-01-20 14:07:58.000-0600 The fix to 14057 has been applied, and putnopvut was thinking this may be the same issue. Can you verify that this fixes your issue and report back? Thanks! By: Marcin Kowalczyk (kowalma) 2009-01-20 14:34:32.000-0600 I will apply patch to box durring next maintenance window - should be durring weekend. By: Leif Madsen (lmadsen) 2009-01-28 15:32:44.000-0600 Guess I'll ping this issue as well :) By: Marcin Kowalczyk (kowalma) 2009-01-28 15:54:06.000-0600 I've upgraded dahdi to following package: dahdi-linux-complete-2.1.0.3+2.1.0.2.tar.gz and * to 1.6.0.3 on media gateway's and seems that problem is gone. By: Leif Madsen (lmadsen) 2009-01-28 19:58:12.000-0600 Fixed with most recent DAHDI per the reporter. Please re-open this issue should this not actually be the case. |