[asterisk-bugs] [JIRA] (ASTERISK-24277) answered call logged as unanswered

Filip Frank (JIRA) noreply at issues.asterisk.org
Thu Aug 28 07:45:29 CDT 2014


    [ https://issues.asterisk.org/jira/browse/ASTERISK-24277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222442#comment-222442 ] 

Filip Frank commented on ASTERISK-24277:
----------------------------------------

I think it is a bug in IAX module.

> answered call logged as unanswered
> ----------------------------------
>
>                 Key: ASTERISK-24277
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24277
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2, Channels/chan_sip/General
>    Affects Versions: 11.8.0, 11.11.0
>         Environment: RHEL6, x86_64, 4 core virtual machine (KVM)
>            Reporter: Nikola Ciprich
>
> we're experiencing strange issue, where outgoing answered calls are sometimes regarded as unanswered by asterisk - no ANSWER, BRIDGE_START, BRIDGE_STOP events are logged to CEL, as well as no mention about answer is logged to asterisk log, but the user spends minutes talking to remote party in answered call! (on the remote PBX, I can see call was really answered). Connection to remote PBX is via IAX2 trunk, remote asterisk is 1.8.x. We're are experiencing few such calls each day. Line quality is good, no packet loss, everything seems to be OK.
> here's example of such call (relevant log snippet:)
> Aug 26 08:53:40 comphatu asterisk[3812]: VERBOSE[14150][C-000074b7]: app_dial.c:1400 in wait_for_answer:     -- IAX2/vfn-7754 is ringing
> Aug 26 08:55:15 comphatu asterisk[3812]: VERBOSE[14150][C-000074b7]: chan_iax2.c:5423 in iax2_hangup:     -- Hungup 'IAX2/vfn-7754'
> according to the log, call started ringing on 8:53:40 and got hangup 2 minutes later, during that period, it was answered,but there is no mention about it in the logs, or CEL DB.
> I'll try switching provider trunk from IAX to SIP to see if that helps and report.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list