Asterisk Does Not Re-register As A Sip Client After A “sip Reload” If “sip.conf” Or “users.conf” Is Changed

Home » Asterisk Users » Asterisk Does Not Re-register As A Sip Client After A “sip Reload” If “sip.conf” Or “users.conf” Is Changed
Asterisk Users 4 Comments

Hi all,

I have a confusing problem with “sip reload”. I have an outgoing registration in my SIP.conf in the form of “register=>”
, and generally when ever I do a sip reload , Asterisk sends out a new registration and re-registers. But if I change anything in sip.conf or users.conf , the re-registration does not work anymore after a sip reload (even if I don’t change the files and just re-save them). in this case after a sip reload when I issue “sip show registry” I see 0
registrations and not even a pending reg. I need to add /delete users and extensions on a frequently basis and don’t want to lose my registrations to outside or my active calls , and I suppose a “sip reload” after changing the configs is the only way . I am really confused why it is not working. I am sure that asterisk is re-reading the new config files –new users are added– but registration is not triggered again. I am not sure if it is a misconfiguration on my side or some kind of bug in asterisk but any help on this issue would be really appreciated.

* I tried including an external config file in sip.conf or users.conf but in this case even without changing anything, after a sip reload , I lost my registration.
* I tried mysql real time module but since I am working with some websocket clients I have some issues to forward calls from udp clients to websocket ones.
*I am working with trunk asterisk 11 (r 373330 ) and I tried it with the latest trunk and same results .

Regards Hadi Ams

4 thoughts on - Asterisk Does Not Re-register As A Sip Client After A “sip Reload” If “sip.conf” Or “users.conf” Is Changed