[asterisk-bugs] [JIRA] (ASTERISK-17883) SIP CANCEL is broken when phone is not registered to asterisk (sip friend and/or sip user)

[Carlos Ramos (JIRA)]

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

Carlos Ramos commented on ASTERISK-17883:
-----------------------------------------

Hi I would like to confirm this bug as well. Asterisk 11.13.1 and Samsung Galaxy S5 with Android 5.0. If pedantic=no it hangs up correctly. If pedantic=yes y does not hang up. Is there any missing information to resolve this ?

> SIP CANCEL is broken when phone is not registered to asterisk (sip friend and/or sip user)
> ------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-17883
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17883
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.4, 13.3.2
>            Reporter: Artem Makhutov
>            Severity: Minor
>         Attachments: sip.log
>
>
> I have discovered a bug while playing with asterisk and with the embedded sip client of an android mobile phone.
> Canceling a call is broken when the mobile phone is not registered to asterisk.
> When calling from the android phone and the other party picks up the phone everything works just fine. But when the other party does not pick up the phone and I hangup the call on the mobile then the other phone will never stop ringing.
> This problem does not occur when the mobile phone is registered to asterisk.
> Here is the relevant configuration of sip.conf:
> [2005]
> type=friend
> defaultuser=2005
> transport=udp
> fromuser=2005
> context=internal
> host=dynamic
> fromdomain=xxxxxxx
> secret=xxxxxxx
> qualify=yes
> nat=yes
> directmedia=no
> disallow=all
> allow=speex
> allow=alaw
> allow=ulaw
> allow=gsm
> allow=g729
> allow=h264



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