I think what you're looking for is to have one Kamailio server be able to write presence information into a database, and have
other kamailio servers detect those change and send NOTIFY messages, and I don't think that this will work in that manner based on the documentation:
-
The call-info subscriber information is stored in memory and is periodically written to the database. Call state information is stored in memory. A future release may periodically write call state to the database, as well. The database
is purely for restoring subscriptions after a restart of the application server. Subscriber information is also flushed to the database when the service is stopped.
There are probably other ways of getting what you want here, like maintaining subscriber information in memory on each individual host (you don't want to send NOTIFY from each server to a single UA for every event, right?), and replicating call state information
via DMQ to trigger the notifications. But that's just a quick guess.
Regards,
Kaufman
|
Kaufman
Senior Voice Engineer
E: bkaufman@bcmone.com
|
|
SIP.US Client Support: 800.566.9810
| SIPTRUNK Client Support: 800.250.6510 | Flowroute Client Support: 855.356.9768
|
|
|
|
|
|
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thanks! Work!
Now, is there a way to get the module to work on a kamailio cluster? I don't see anything in the documentation...
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions --
sr-users@lists.kamailio.org
To unsubscribe send an email to
sr-users-leave@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
__________________________________________________________
