[SR-Users] presence not work proper with subs_db_mode = 2

Aatif Shaikh aatif.shaikh at ecosmob.com
Fri Dec 4 09:41:44 CET 2020


Hello, all have a problem with Kamailio presence, I have configured my
kamailio.cfg to handle dialog presence and facing issue in case of
subs_db_mode = 2 in case of mode 2 facing the following presence issue.

   1. after hangup presence is still up
   2. sometimes stuck in a ringing state
   3. sometimes presence not came..etc

but in the case of subs_db_mode = 3 (DB ONLY) mode presence working fine
not facing any issue with this mode.

I noticed that sometimes Kamailio will throw the following message during
PUBLISH processing and it will not generate appropriate NOTIFY I also
verify inactive watcher subscription is there for that user and also a
proper entry in the dialog table.

MSG during PUBLISH processesing and it will not generate appropriate NOTIFY

Oct 30 07:42:10 NC-HOSTED-1 /usr/local/sbin/kamailio[2409]: DEBUG: presence
[notify.c:1444]: publ_notify(): Could not find subs_dialog

kamailio.cfg param

modparam("pua", "db_url", DBURL_KAMAILIO)
modparam("pua", "db_mode", 2)
modparam("pua", "update_period", 100)
modparam("pua", "dlginfo_increase_version", 1)
modparam("pua", "default_expires", 3600)
modparam("pua", "fetch_rows", 1000)
modparam("pua", "outbound_proxy", SERVER_IP)

modparam("dialog", "db_url", DBURL_KAMAILIO )
modparam("dialog", "db_mode", 1)
modparam("dialog", "db_update_period", 260)
modparam("dialog", "db_fetch_rows", 500)

modparam("pua_dialoginfo", "include_callid", 1)
modparam("pua_dialoginfo", "send_publish_flag", 8)
modparam("pua_dialoginfo", "caller_confirmed", 0)
modparam("pua_dialoginfo", "include_tags", 1)
modparam("pua_dialoginfo", "use_pubruri_avps", 1)
modparam("pua_dialoginfo", "include_localremote", 1)
modparam("pua_dialoginfo", "override_lifetime", 300)
modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)")
modparam("pua_dialoginfo", "pubruri_caller_dlg_var", "pubruri_caller")
modparam("pua_dialoginfo", "pubruri_callee_dlg_var", "pubruri_callee")
modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)")

modparam("presence_dialoginfo", "force_single_dialog", 1)
modparam("presence", "db_table_lock_type", 0)
modparam("presence", "db_url", DBURL_KAMAILIO)
modparam("presence", "db_update_period", 5)
modparam("presence", "send_fast_notify", 1)
modparam("presence", "clean_period", 100)
modparam("presence", "subs_db_mode", 2)
//modparam("presence", "subs_db_mode", 3)
modparam("presence", "timeout_rm_subs", 1) //new/
//modparam("presence", "notifier_processes", 2) //new//
modparam("presence", "notifier_poll_rate", 20) //new//
modparam("presence", "waitn_time",1)
modparam("presence", "fetch_rows", 1000)
modparam("presence", "presentity_table", "presentity")
modparam("presence", "active_watchers_table", "active_watchers")
modparam("presence", "watchers_table", "watchers")
modparam("presence", "max_expires", 3600)

modparam("presence_xml", "db_url", DBURL_KAMAILIO)
modparam("presence_xml", "force_active", 1)

logic for presence

request_route {

    if(is_method("PUBLISH") || is_method("SUBSCRIBE")) {
            route(HANDLE_PRESENCE);
    }

}

route[HANDLE_PRESENCE] {

    if (! t_newtran())
    {
            sl_reply_error();
            exit;
    }

    if(is_method("PUBLISH"))
    {
           handle_publish();
           t_release();
    } else if( is_method("SUBSCRIBE")) {
           handle_subscribe();
       t_release();
    }
    exit;

}

route[RELAY] {

    if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) {
            $avp(t_ext) = $tU ;
            $avp(domain) = $fd ;
            $avp(et) = $_s(sip:$avp(t_ext)@$avp(domain)) ;
            $avp(s:puburis_callee) = $avp(et);
            setflag(8);
            dlg_manage();
    }

}
I already report this issue in Kamailio git
https://github.com/kamailio/kamailio/issues/2540


-- 
-- 

Regards,

*Aatif Shaikh *| Software Developer

+91 9033976268Hangout: aatif.shaikh at ecosmob.comSkype :
aatif.shaikh at ecosmob.com
*Ecosmob Technologies Pvt. Ltd. *
https://www.ecosmob.com
VoIP | Web | Mobile | IoT | Big Data
<https://twitter.com/ecosmob>  <https://www.facebook.com/Ecosmob>
<https://plus.google.com/+Ecosmob>
<https://www.linkedin.com/company/ecosmob>
<https://in.pinterest.com/ecosmob/>

This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
Ecosmob Technologies is not responsible for errors or omissions in this
message and denies any responsibility for any damage arising from the use
of e-mail. Any opinion and other statement contained in this message and
any attachment are solely those of the author and do not necessarily
represent those of the company.

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20201204/a98d2fa9/attachment.htm>


More information about the sr-users mailing list