[asterisk-users] CAPI didn't get a frame | avoiding initial deadlock | multiple instances of Asterisk
Marco Mouta
marco.mouta at gmail.com
Mon Dec 10 05:46:57 CST 2007
Hi guys,
First of all, I know that this server must be upgraded asap, I'm just
wondering if anyone of you has already faced this problem and , if so, would
the upgrade solve my problems...
CAPI version 0.6
Asterisk 1.2.5
AGI scripts are being used
Main problems:
-Dropped Calls
- ps aux | grep asterisk shows that asterisk (that is started with
safe_asterisk) is generating multiple instances of asterisk by it's self.
This may be caused by AGI scripts http://bugs.digium.com/view.php?id=8086?
Extracted from /var/log/asterisk/full :
Dec 6 10:11:07 DEBUG[5858] channel.c: Didn't get a frame from channel:
CAPI/ISDN1/141-721
Dec 6 10:11:07 DEBUG[5858] channel.c: Bridge stops bridging channels
CAPI/ISDN1/141-721 and SIP/741411-57bf
Dec 6 10:11:07 DEBUG[5858] chan_sip.c: update_call_counter(741411) -
decrement call limit counter
Dec 6 10:11:07 VERBOSE[5858] logger.c: == Spawn extension (from-trunk,
141, 111) exited non-zero on 'CAPI/ISDN1/141-721'
Dec 6 10:11:07 VERBOSE[5858] logger.c: -- Executing
NoOp("CAPI/ISDN1/141-721", "from-trunk - h - 112 - 112") in new stack
Dec 6 10:11:07 VERBOSE[5858] logger.c: -- Executing
AGI("CAPI/ISDN1/141-721", "set_callerid.agi") in new stack
Dec 6 10:11:08 DEBUG[5858] res_agi.c: CAPI/ISDN1/141-721 hungup
Dec 6 10:11:08 VERBOSE[5858] logger.c: == Spawn extension (from-trunk, h,
2) exited non-zero on 'CAPI/ISDN1/141-721'
Dec 6 10:11:08 DEBUG[2692] channel.c: Avoiding initial deadlock for
'CAPI/ISDN1/141-721'
Dec 6 10:11:08 DEBUG[2692] channel.c: Avoiding initial deadlock for
'CAPI/ISDN1/141-721'
Dec 6 10:13:02 DEBUG[5878] channel.c: Didn't get a frame from channel:
SIP/741411-f7c1
Dec 6 10:13:02 DEBUG[5878] channel.c: Bridge stops bridging channels
CAPI/ISDN1/141-722 and SIP/741411-f7c1
Dec 6 10:14:15 DEBUG[5902] channel.c: Didn't get a frame from channel:
CAPI/ISDN1/141-723
Dec 6 10:14:15 DEBUG[5902] channel.c: Bridge stops bridging channels
CAPI/ISDN1/141-723 and SIP/741411-4d0f
Dec 6 10:14:34 DEBUG[2692] channel.c: Avoiding initial deadlock for
'CAPI/ISDN1/141-725'
Dec 6 10:14:34 DEBUG[2692] channel.c: Avoiding initial deadlock for
'CAPI/ISDN1/141-725'
Dec 6 10:14:54 VERBOSE[5941] logger.c: -- SIP/741411-26c2 answered
CAPI/ISDN1/141-726
Dec 6 10:15:15 DEBUG[5941] channel.c: Didn't get a frame from channel:
SIP/741411-26c2
Dec 6 10:15:15 DEBUG[5941] channel.c: Bridge stops bridging channels
CAPI/ISDN1/141-726 and SIP/741411-26c2
Dec 6 10:45:29 DEBUG[6235] channel.c: Didn't get a frame from channel:
SIP/741411-9981
Dec 6 10:45:29 DEBUG[6235] channel.c: Bridge stops bridging channels
CAPI/ISDN1/132-72d and SIP/741411-9981
I definitely must go through CAPI 1.0 and asterisk 1.2.25, but would be
interesting to learn from this problem before upgrading, that's why I'm
posting on the list.
Could it be possible that the multiple instances of Asterisk that are
started due to the bug ( http://bugs.digium.com/view.php?id=8086, solved in
asterisk 1.2.13) are causing all the troubles, making this multiple
instances try to access same asterisk channel (leading us to Avoiding
deadlock messages) ?
I mean applying the patch might solve the problems instead off all system
upgrade?
Best regards,
Marco Mouta
--
Esta mensagem (incluindo quaisquer anexos) pode conter informação
confidencial para uso exclusivo do destinatário. Se não for o destinatário
pretendido, não deverá usar, distribuir ou copiar este e-mail. Se recebeu
esta mensagem por engano, por favor informe o emissor e elimine-a
imediatamente. Obrigado.
This e-mail message is intended only for individual(s) to whom it is
addressed and may contain information that is privileged, confidential,
proprietary, or otherwise exempt from disclosure under applicable law. If
you believe you have received this message in error, please advise the
sender by return e-mail and delete it from your mailbox. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20071210/5977bba3/attachment.htm
More information about the asterisk-users
mailing list