[asterisk-users] Realtime SIP peers - reloading cached info

[Rob Hillis]

That's why I didn't see anything about the REALTIME function when I went 
looking - many of our production systems are still on later versions of 1.2.

Given that it wasn't made obsolete at the /beginning/ of the 1.4 cycle, 
I'm hoping Digium reconsider making it obsolete in 1.6 and schedule it 
for removal in 1.8.  Half a development cycle isn't a very long time for 
a warning that a function will be removed.

Atis Lezdins wrote:
> On 2/13/08, Rob Hillis <rob at hillis.dyndns.org> wrote:
>   
>>  -----BEGIN PGP SIGNED MESSAGE-----
>>  Hash: SHA1
>>
>>  If it is being removed in 1.6, I'm a little concerned since there's no
>> mention of this when you show the application, nor on voip-info.org.  What
>> application/function is it being replaced by?
>>     
>
> There's an obsolete warning in 1.4.18, but i somehow remember that
> it's obsolete already since some 1.4.11
>
> It's func_realtime as i said before. usage shouldn't be much
> different, you can replace with:
>
> Set(REALTIME(sip_buddies,name,100,my_field)=foo);
>
> Also, seems that func_realtime will soon support SQL INSERT's and DELETE's :)
>
> Regards,
> Atis
>
>
>   
>>  Atis Lezdins wrote:
>>  | On 2/13/08, Rob Hillis <rob at hillis.dyndns.org> wrote:
>>  |> -----BEGIN PGP SIGNED MESSAGE-----
>>  |> Hash: SHA1
>>  |>
>>  |> Atis Lezdins wrote:
>>  |> | By RealTimeUpdate do you mean func_realtime? It shouldn't care, as
>>  |> | cache is not implemented in realtime level, but higher (chan_sip).
>>  |> |
>>  |> | Are you sure you need "sip show XXX load". If you "sip prune" peer
>>  |> | data, it should be re-loaded on next access.
>>  |> |
>>  |> | What i was suggesting - to dig into chan_sip and create dialplan
>>  |> | application SipPrune(peer) that would prune the peer directly, by
>>  |> | using corresponding function - sip_prune_peer() in chan_sip.c - that
>>  |> | way you will gain some extra performance, as there's no manager/cli
>>  |> | overhead.
>>  |> |
>>  |> | However if you're uncomfortable with C, the app_system shouldn't cause
>>  |> | any troubles :)
>>  |>
>>  |> RealTimeUpdate is more likely to correspond to app_realtime rather than
>>  |> func_realtime.
>>  |
>>  | As to my knowledge - that is obsolete and being removed in 1.6,
>>  | func_realtime replaces it. That's why i wondered about name -  I just
>>  | never happened to use it :)
>>  |
>>  | Regards,
>>  | Atis
>>  |
>>  |
>>
>>  -----BEGIN PGP SIGNATURE-----
>>  Version: GnuPG v1.4.7 (GNU/Linux)
>>  Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
>>
>> iD8DBQFHsnaM6uKn5cBSgGQRAo/TAKDCruPrn2nm2XV/PYbfSuBKA0j5OwCfQ/Ox
>>  QE3SYEmZ01QHUT4ITwmLnT0=
>>  =SKEW
>>  -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>
>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>>     
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080213/a14aa20e/attachment.htm