-----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?
Atis Lezdins wrote:
| On 2/13/08, Rob Hillis <[EMAIL PROTECTED]> 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
