Hi Surya,
Actually none of the functions update_subs_db (used in fallback2db mode)
and update_db_subs (used by timer), when comes to updating, are not
pushing the socket and the local contact fields.
Those 2 columns are also not loaded by get_database_info() when
get_stored_info() (in fallback2db mode) is looking up for existing
subscriptions.
I guess the code assumes that those elements do preserve across the same
subscription.
In your case, subscriptions to same user may land on different presence
servers right ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 26.08.2015 17:23, surya wrote:
Hi,
Thanks for the reply.
I was checking the code but I don't see update to socket_info and
local_contact colums while there's a subscription within dialog. The flow I
understood is:
Receive SUBS:
Check etag and set init_req
if init_req==0
get_stored_info
update_subscription
update_subs_db
The update_subs_db method is not updating those two columns.
Those are being updated by update_db_subs method which is being called from
timer_db_update method.
Sorry, If I missed something. I am using version 1.8.3
Thanks,
Surya
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Use-of-socket-info-and-local-contact-columns-in-the-active-watcher-table-tp7598639p7598684.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
