[asterisk-bugs] [JIRA] (ASTERISK-24673) outgoing sip registers cannot be removed or modified without doing restart (or doing module unload chan_sip.so)

[Torbjörn Abrahamsson (JIRA)]

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

Torbjörn Abrahamsson commented on ASTERISK-24673:
-------------------------------------------------

FYI, I work together with Stefan Engström, and compiled the logs in his absence. We are surprised that you could not reproduce, as this have happened on every Asterisk 13 installation we tried. All installed in different ways, from source or RPMs. This is the most streamlined install though. Seems like a regression, as it works great in our 12.6.0 servers. In the logs we use 10.10.10.10 as domain for the register, which do not respond. But the result is the same if using a real, working, sip-account to register to. 

Thanks for your efforts.

> outgoing sip registers cannot be removed or modified without doing restart (or doing module unload chan_sip.so)
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24673
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24673
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 13.0.0, 13.1.0
>         Environment: fedora 20, x86_64
>            Reporter: Stefan Engström
>            Assignee: Stefan Engström
>         Attachments: console-register-problems.txt, debug-register-problems, procedure-register-problems.txt
>
>
> Let sip.conf contain a register line such as:
> register => test97:foo at boo.se/266
> asterisk -rx "sip show registry" now outputs a single registry entry:
> Host                                    dnsmgr Username       Refresh State                Reg.Time
> boo.se:5060                             N      test97             105 Registered           Thu, 08 Jan 2015 15:39:03
> Comment out the above register-line (;register => test97:foo at boo.se/266)
> Issue asterisk -rx "sip reload" 
> ==>the registration is still alive! that is, asterisk -rx "sip show registry"  still has an entry.
> When I had asterisk version 12.6.0 installed, commenting out the line and issuing that 'sip reload' would destroy the sip registration as expected. ( asterisk -rx "sip show registry" would output 0 SIP registrations). However, it doesn't for version 13.0.0 or for version 13.1.0... 
> Modifying an existing line 'register=>...' line in sip.conf (and not removing it) produces similar bad behaviour as well as this creates multiple active registrations (old+new). 
> Having to restart the asterisk process (or unload+reload chan_sip.so) every time I want to change the callbackextension(266 above) for a sip-registry is not very fun.



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