[asterisk-bugs] [JIRA] (ASTERISK-25036) Asterisk still send an INVITE request after a call was canceled(realtime, rtcachefriends is enabled)

Joshua Colp (JIRA) noreply at issues.asterisk.org
Thu Apr 30 06:15:33 CDT 2015


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

Joshua Colp commented on ASTERISK-25036:
----------------------------------------

Thanks for the report and debug. However we also need protocol specific debug captured at the time of the issue. Please include the following:

* Asterisk log files generated using the instructions on the Asterisk wiki [1], with the appropriate protocol debug options enabled, e.g. 'pjsip set logger on' if the issue involves the chan_pjsip channel driver.
* Configuration information for the relevant channel driver, e.g. pjsip.conf.
* A wireshark compatible packet capture, captured at the same time as the Asterisk log output.

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> Asterisk still send an INVITE request after a call was canceled(realtime, rtcachefriends is enabled)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25036
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25036
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.0.0, 13.1.0, 13.2.0
>         Environment: Debian wheezy x64
>            Reporter: Mikhail Fast
>            Severity: Minor
>
> Asterisk 13.2
> Realtime, rtcachefriends=yes
> Steps to reproduce a bug:
> 0) Asterisk has a public IP, cliens A and B connect over  NAT.
> 1) Regiser user A 
> 2) Register user B
> 3) Unexpectedly disconnect client B (you may kill a proocess or simply disconnect a network cable)
> 4) Make a call from A to B(B exists in realtime cache, but really it is offline!)
> 5) Cancel a call 
> 6) Register with a client B again
> On secondary register you get a call into your sip-client B. In the console you may see, that asterisk still send an INVITE,  although a call already was canceled. 



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



More information about the asterisk-bugs mailing list