Hello,

Got an issue and not sure what causes it.
Architecture of a presence on the system is "edge" Kamailio is sending
PUBLISH'es to "presence" Kamailio via "pua" and "pua_dialoginfo" modules
and proxying SUBSCRIBE's from endpoints.
"Presence" Kamailio basically just handle_subscribe()/handle_publish() with
the config

modparam("presence", "db_url", DBURL)
modparam("presence", "subs_db_mode", 3) # DB-Only scheme.
modparam("presence", "db_table_lock_type", 0)
modparam("presence", "notifier_processes", 0)
modparam("presence", "subs_htable_size", 15)
modparam("presence", "delete_same_subs", 1)
modparam("presence", "clean_period", 60)
modparam("presence", "sip_uri_match", 1)
modparam("presence", "pres_subs_mode", 0)
modparam("presence", "timeout_rm_subs", 0)
modparam("presence", "fetch_rows", 10000)
modparam("presence", "pres_htable_size", 15)
modparam("presence", "max_expires", 1800)
modparam("presence", "send_fast_notify", 1)
modparam("presence", "expires_offset", 10)

On "edge" Kamailio several devices can be hidden behind same AOR, so on
each branch of a call I'm getting PUBLISH with an "early" state, which is
passed to "presence" Kamailio with local/remote tags and target-uri in XML.
One of the devices are answering and hanging up, I'm getting PUBLISH with a
state of a dialog (without from/remote tags, but target-uri). Which is
completely fine.

Problem is appearing on a call end, when a new SUBSCRIBE is coming to AOR,
that was called with several devices behind. For whatever reason, "early"
state of a device, that was locally CANCEL'ed by "edge" Kamailio is still
there. As there were no "terminated" state generated by "edge" Kamailio for
this particular target-uri?

So, which Kamailio is need to be finetuned (and how?), one that is not
sending PUBLISH for locally generated CANCEL or the one, that is not
cleaning up dialog state completely?

Thanks in advance!
-- 
Best regards,
Ihor
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- 
[email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!

Reply via email to