<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 06/07/10 10:34, Jonas Kellens wrote:
<blockquote cite="mid:4C32F891.5090501@telenet.be" type="cite">
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<font face="Helvetica, Arial, sans-serif">Hello list,<br>
<br>
what is the use of realtime SIP peers when you always need to reload
the sip configuration as if you were just putting your SIP peers in
sip.conf ??<br>
<br>
My SIP peers are now defined in a mysql-DB and when I add a mailbox in
the field 'mailbox', the change is not active untill a do a "sip
reload" or a "module reload chan_sip.so".<br>
<br>
Doing a "sip reload" or </font><font
face="Helvetica, Arial, sans-serif">a "module reload chan_sip.so"
makes that all the SIP peers need to re-register again to Asterisk so
that they are 'available' again.<br>
<br>
So what is "realtime" about the ARA ??<br>
<br>
<br>
Kind regards,<br>
<br>
Jonas.<br>
</font>
</blockquote>
If you are using RealTime and make any changes to a peer entry in your
DB you need to prune the peer from the realtime cache using <br>
<br>
sip prune realtime <peer name><br>
<br>
The peer will need to re register but only that one and it will pick up
the updated settings from the DB<br>
<br>
Ish<br>
<div class="moz-signature">-- <br>
<title></title>
<span
style="font-family: Arial,Helvetica,sans-serif; color: rgb(0, 0, 0);">Ishfaq
Malik<br>
Software Developer<br>
PackNet Ltd<br>
<br>
Office: 0161 660 3062<br>
</span>
</div>
</body>
</html>