Jonas Kellens
2010-Apr-17 09:25 UTC
[asterisk-users] Realtime changes not reflected realtime
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Helvetica, Arial, sans-serif">Hello list,<br> <br> Using Asterisk 1.4.25.1<br> Using realtime sip_buddies<br> <br> I notice that when changing the sip_buddie name (field 'name' and 'username') or secret, this is not implemented until a sip reload.<br> <br> When changing the secret, the old secret is still the one to use until a sip reload.<br> When changing the name, the old name is still the one to use for registrations until a sip reload.<br> <br> <font color="#3333ff">asterisk*CLI> sip show peers<br> testcorp3/testcorp3 192.168.1.100 D N 5061 OK (28 ms) Cached RT</font> <br> <br> -- now I change the secret in sip_buddies --<br> -- I restart my IP-phone --<br> <br> <font color="#3333ff">asterisk*CLI> <br> [Apr 17 11:19:45] NOTICE[24072]: chan_sip.c:16612 sip_poke_noanswer: Peer 'testcorp3' is now UNREACHABLE! Last qualify: 28<br> [Apr 17 11:19:55] NOTICE[24072]: chan_sip.c:12985 handle_response_peerpoke: Peer 'testcorp3' is now Reachable. (24ms / 2000ms)<br> asterisk*CLI> </font><br> <br> -- IP-phone is still able to register with the old password --<br> -- I do a sip reload --<br> <br> <font color="#3333ff">asterisk*CLI> sip reload<br> [Apr 17 11:22:00] Reloading SIP<br> [Apr 17 11:22:00] == Parsing '/etc/asterisk/sip.conf': [Apr 17 11:22:00] Found<br> [Apr 17 11:22:00] == Parsing '/etc/asterisk/users.conf': [Apr 17 11:22:00] Found<br> [Apr 17 11:22:00] == Parsing '/etc/asterisk/sip_notify.conf': [Apr 17 11:22:00] Found</font><br> <br> </font></font><font size="-1"><font face="Helvetica, Arial, sans-serif">-- I restart my IP-phone --<br> <br> <font color="#3333ff">asterisk*CLI> <br> [Apr 17 11:22:58] NOTICE[24072]: chan_sip.c:12985 handle_response_peerpoke: Peer 'testcorp3' is now Lagged. (2025ms / 2000ms)<br> [Apr 17 11:23:05] NOTICE[24072]: chan_sip.c:12985 handle_response_peerpoke: Peer 'testcorp3' is now Reachable. (31ms / 2000ms)<br> [Apr 17 11:23:05] NOTICE[24072]: chan_sip.c:15889 handle_request_register: Registration from '<a class="moz-txt-link-rfc2396E" href="sip:testcorp3@192.168.1.150"><sip:testcorp3@192.168.1.150></a>' failed for '192.168.1.100' - Wrong password<br> [Apr 17 11:23:08] NOTICE[24072]: chan_sip.c:12985 handle_response_peerpoke: Peer 'testcorp3' is now Reachable. (30ms / 2000ms)<br> asterisk*CLI> </font><br> <br> -- Now the new secret is in place !! --<br> </font></font><font size="-1"><font face="Helvetica, Arial, sans-serif"><br> <br> This is my realtime setting in sip.conf :<br> <br> <br> ;----------------------------------------- REALTIME SUPPORT ------------------------<br> ; For additional information on ARA, the Asterisk Realtime Architecture,<br> ; please read realtime.txt and extconfig.txt in the /doc directory of the<br> ; source code.<br> ;<br> rtcachefriends=yes <br> ;rtsavesysname=yes<br> ;rtupdate=yes<br> ;rtautoclear=yes<br> ;ignoreregexpire=yes<br> <br> <br> <br> Kind regards,<br> <br> Jonas.<br> </font></font> </body> </html>
Steve Howes
2010-Apr-17 10:13 UTC
[asterisk-users] Realtime changes not reflected realtime
On 17 Apr 2010, at 10:25, Jonas Kellens wrote:> When changing the secret, the old secret is still the one to use until a sip reload. > When changing the name, the old name is still the one to use for registrations until a sip reload.So it's being cached? Does 'sip prune realtime all' clear it too?> rtcachefriends=yesBy that? S