[asterisk-bugs] [JIRA] Created: (ASTERISK-20486) MeetMe Unable to write frame to channel after SIP channel hangs up.
Michael Cargile (JIRA)
noreply at issues.asterisk.org
Fri Sep 28 14:47:27 CDT 2012
MeetMe Unable to write frame to channel after SIP channel hangs up.
-------------------------------------------------------------------
Key: ASTERISK-20486
URL: https://issues.asterisk.org/jira/browse/ASTERISK-20486
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Applications/app_meetme, Channels/chan_sip/General
Affects Versions: 1.8.16.0
Environment: I have two asterisk boxes. One is running asterisk 1.4.43. It is acting like a test carrier. The other box is running 1.8.16.0 and is placing calls to the test carrier and routing them to MeetMe conferences.
Reporter: Michael Cargile
Basically it looks like in some instances MeetMe is still trying to pass frames to a channel that should have hung up. If you look the caller id name which we use as a Unique ID matches the caller id name in the BYE event before this error. It looks like it is generating about 50 errors per second for one of these calls. I am not sure if this is a SIP issue, or a MeetMe issue. I think this might be related to this issue:
https://issues.asterisk.org/jira/browse/ASTERISK-19594
but that one has already been closed.
Output from AGI script called before getting into the MeetMe conference to show the channel as well as the calleridname (which we use to keep track of the call):
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi|AGI Environment Dump:
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- accountcode =
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- arg_1 = NORMAL-----LB
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- callerid = 8633939330
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- calleridname = V9281514180000238212
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- callingani2 = 0
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- callingpres = 0
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- callingtns = 0
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- callington = 0
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- channel = SIP/testcarrier-00017f4b
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- context = default
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- dnid = unknown
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- enhanced = 0.0
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- extension = 8368
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- language = en
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- priority = 3
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- rdnis = unknown
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- request = agi-VDAD_ALL_outbound.agi
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- threadid = -1268466832
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- type = SIP
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- uniqueid = 1348859661.314636
2012-09-28 15:14:33|agi-VDAD_ALL_outbound.agi| -- version = 1.8.16.0
Asterisk CLI output with SIP debugging enabled:
[Sep 28 15:14:35] -- Executing [8600058 at default:1] MeetMe("SIP/testcarrier-00017f4b", "8600058,F") in new stack
[Sep 28 15:14:35] == Parsing '/etc/asterisk/meetme.conf': [Sep 28 15:14:35] == Found
[Sep 28 15:14:35] == Parsing '/etc/asterisk/meetme-vicidial.conf': [Sep 28 15:14:35] == Found
[Sep 28 15:14:35] -- Created MeetMe conference 1022 for conference '8600058'
[Sep 28 15:14:35] -- <SIP/testcarrier-00017f4b> Playing 'conf-onlyperson.gsm' (language 'en')
...
[Sep 28 15:14:38]
<--- Transmitting (NAT) to 192.168.198.14:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.198.14:5060;branch=z9hG4bK099f4e9c;received=192.168.198.14;rport=5060
From: <sip:9999024387 at 192.168.198.14>;tag=as657a2bf3
To: "V9281514180000238212" <sip:8633939330 at 192.168.198.15>;tag=as4bc64123
Call-ID: 05a3c6f264fb72905243ca216bb0eba2 at 192.168.198.15:5060
CSeq: 102 BYE
Server: Asterisk PBX 1.8.16.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
...
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:39] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
...
[Sep 28 15:14:45] WARNING[3688]: app_meetme.c:3678 conf_run: Unable to write frame to channel SIP/testcarrier-00017f4b
[Sep 28 15:14:45] WARNING[8004]: chan_sip.c:3918 __sip_autodestruct: Autodestruct on dialog '05a3c6f264fb72905243ca216bb0eba2 at 192.168.198.15:5060' with owner in place (Method: BYE). Rescheduling destruc
tion for 10000 ms
[Sep 28 15:14:45] -- Hungup 'DAHDI/pseudo-753634465'
[Sep 28 15:14:45] == Spawn extension (default, 8600058, 1) exited non-zero on 'SIP/testcarrier-00017f4b'
[Sep 28 15:14:45] -- Executing [h at default:1] AGI("SIP/testcarrier-00017f4b", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----111---------------") in new stack
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list