[asterisk-bugs] [JIRA] (ASTERISK-22026) Peers in realtime not register after "sip reload" using callbackextension

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-22026:
------------------------------------

    Assignee: Michael L. Young  (was: wushumasters)
      Status: Triage  (was: Waiting for Feedback)
    
> Peers in realtime not register after "sip reload" using callbackextension
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-22026
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22026
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_realtime
>    Affects Versions: 11.4.0
>         Environment: Debian Wheezy 64 bits
>            Reporter: wushumasters
>            Assignee: Michael L. Young
>            Severity: Critical
>         Attachments: sip.conf
>
>
> When i use peers in realtime with option callbackextension after "sip reload" the peer change to "unregister" and stay.
> If i restart asterisk or unload/load chan_sip works again
> {noformat}
> debian*CLI> sip show registry 
> Host                                    dnsmgr Username       Refresh State                Reg.Time                 
> xxxxxxxxxxxx:5060                        Y      xxxx              160 Registered           Sat, 06 Jul 2013 10:31:41
> 1 SIP registration.
> debian*CLI> sip reload
>  Reloading SIP
>   == Parsing '/etc/asterisk/sip.conf': Found
> debian*CLI> sip show registry
> Host                                    dnsmgr Username       Refresh State                Reg.Time                 
> xxxxxxxxxxxx:5060                        N      xxxxx              120 Unregistered                                  
> {noformat}                   
> Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira