[asterisk-bugs] [Asterisk 0013488]: mISDN rejects incoming calls
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Sep 19 09:47:06 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13488
======================================================================
Reported By: Christian_Pinedo
Assigned To: crich
======================================================================
Project: Asterisk
Issue ID: 13488
Category: Channels/chan_misdn
Reproducibility: random
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.4.21.2
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-09-16 08:15 CDT
Last Modified: 2008-09-19 09:47 CDT
======================================================================
Summary: mISDN rejects incoming calls
Description:
Asterisk seems to work well but sometimes per day calls from pstn are
rejected and outgoing calls cann't be done also. This is the output of a
rejected incoming call:
Tue Sep 16 09:58:11 2008: P[ 1] channel with stid:0 for one second still
in use!
Tue Sep 16 09:58:11 2008: P[ 1] set_channel: bc->channel:0 channel:1
Tue Sep 16 09:58:11 2008: P[ 1] I IND :NEW_CHANNEL oad:943336600
dad:943445807 pid:23 state:none
Tue Sep 16 09:58:11 2008: P[ 1] --> channel:1 mode:TE cause:16 ocause:16
rad: cad:
Tue Sep 16 09:58:11 2008: P[ 1] --> info_dad: onumplan:0 dnumplan:2
rnumplan: cpnnumplan:0
Tue Sep 16 09:58:11 2008: P[ 1] --> caps:Speech pi:0 keypad:
sending_complete:1
Tue Sep 16 09:58:11 2008: P[ 1] Chan not existing at the moment
bc->l3id:20012 bc:0x81e0374 event:NEW_CHANNEL port:1 channel:1
Tue Sep 16 09:58:11 2008: P[ 1] NO USERUESRINFO
Tue Sep 16 09:58:11 2008: P[ 1] !! NO FREE CHAN IN STACK
Tue Sep 16 09:58:11 2008: P[ 1] Requested Channel Already in Use
releasing this call with cause 34!!!!
Tue Sep 16 09:58:11 2008: P[ 1] I SEND:RELEASE_COMPLETE oad:943336600
dad:943445807 pid:23
Tue Sep 16 09:58:11 2008: P[ 1] --> channel:0 mode:TE cause:16 ocause:34
rad: cad:
Tue Sep 16 09:58:11 2008: P[ 1] --> info_dad: onumplan:0 dnumplan:2
rnumplan: cpnnumplan:0
Tue Sep 16 09:58:11 2008: P[ 1] --> caps:Speech pi:0 keypad:
sending_complete:1
Tue Sep 16 09:58:11 2008: P[ 1] $$$ CLEANUP CALLED pid:23
Tue Sep 16 09:58:11 2008: P[ 1] couldn't handle event
Tue Sep 16 09:58:11 2008: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Tue Sep 16 09:58:11 2008: P[ 1] I IND :RELEASE_COMPLETE oad: dad: pid:23
state:none
Tue Sep 16 09:58:11 2008: P[ 1] --> channel:0 mode:TE cause:16 ocause:34
rad: cad:
Tue Sep 16 09:58:11 2008: P[ 1] --> info_dad: onumplan:0 dnumplan:0
rnumplan:0 cpnnumplan:0
Tue Sep 16 09:58:11 2008: P[ 1] --> caps:Speech pi:0 keypad:
sending_complete:0
Tue Sep 16 09:58:11 2008: P[ 1] --> no Ch, so we've already released.
Tue Sep 16 09:58:11 2008: P[ 0] Cannot hangup chan, no ch
Tue Sep 16 09:58:11 2008: P[ 1] release_chan: Ch not found!
Tue Sep 16 09:58:11 2008: P[ 1] $$$ CLEANUP CALLED pid:23
Tue Sep 16 09:58:11 2008: P[ 1] $$$ CLEANUP CALLED pid:23
It seems that mISDN has the Port 1 (first BRI) in a bad state and network
tries to send a new incoming mail through this port. I have to exec "misdn
restart port 1" to solve this situation. The rest of BRI links are free and
network tries to send the calls always through port 1 because it thinks
that is free. mISDN thinks that this port is already used and so all call
are rejected.
Software versions:
Debian GNU/Linux 4.0
Kernel 2.6.18
Asterisk 1.4.21.2
Zaptel 1.4.11
mISDN and mISDNuser 1.1.7.2
======================================================================
----------------------------------------------------------------------
(0092701) Christian_Pinedo (reporter) - 2008-09-19 09:47
http://bugs.digium.com/view.php?id=13488#c92701
----------------------------------------------------------------------
Ok. I'll try it.
The Cause = 44 frames comes from Port 1. Today I have switch off the cable
of the Port 1 and we have until now no errors. If it continues well the
error could be related with the port 1 (line, cord, card, ...)
There is something that I don't understand. If Asterisk thinks that
channel 2 of port 1 is unavailable but Network thinks it's available, it's
clear that Network will try to use that port and Asterisk will refuse. But
if I have defined a mISDN group and if I call through the group and
Asterisk knows that the channel is unavailable, why do Asterisk/misdn try
to use it? Could be similar to unavailability due to L2 being down that
it's necessary to use misdn_check_l1l2 application?
Issue History
Date Modified Username Field Change
======================================================================
2008-09-19 09:47 Christian_PinedoNote Added: 0092701
======================================================================
More information about the asterisk-bugs
mailing list