<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Look at the trace when the SUBSCRIBE is handled, because the R-URI
in NOTIFY is the Contact from SUBSCRIBE.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 03/08/15 12:51, M S wrote:<br>
</div>
<blockquote
cite="mid:CAFZQphxVnvSNgSJgP=P_qFm84MggCBZPkauNsDxBAc_5vKxbKQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Yes in sip trace i do see notify being sent using udp
transport rather then tls.<br>
<br>
--<br>
U 2015/08/03 10:30:53.213962 X.X.X.X:5060 ->
Y.Y.Y.Y:57526<br>
NOTIFY <a class="moz-txt-link-freetext" href="sip:1234567890@Y.Y.Y.Y:57526">sip:1234567890@Y.Y.Y.Y:57526</a> SIP/2.0<br>
...<br>
--<br>
<br>
</div>
I also notice that R-URI domain part is destination user's IP,
instead of his/her domain, which i am afraid would be rejected
by destination user if it ever get there.<br>
<br>
</div>
<div>I am not using force send socket anywhere for presence. The
event_route[tm:local-request] just does some xlog. This xlog
appears AFTER the send socket warning in kamailio logs (so i
guess it is already too late to using force send socket
anyway).<br>
<br>
</div>
<div>Here are the presence modules params,<br>
<br>
--<br>
...<br>
# ----- presence params -----<br>
modparam("presence", "waitn_time", 10)<br>
modparam("presence", "subs_db_mode", 2)<br>
modparam("presence", "fetch_rows", 1024)<br>
modparam("presence", "clean_period", 30)<br>
modparam("presence", "db_update_period", 30)<br>
modparam("presence", "notifier_processes", 4)<br>
modparam("presence", "db_table_lock_type", 0)<br>
modparam("presence", "db_url", "WEBRTC_DBURL")<br>
<br>
modparam("presence", "timeout_rm_subs", 0)<br>
modparam("presence", "expires_offset", 10)<br>
modparam("presence", "local_log_level", 3)<br>
modparam("presence", "pres_htable_size", 12)<br>
modparam("presence", "subs_htable_size", 12)<br>
modparam("presence", "max_expires", WEBRTC_SIP_MAX_EXPIRE)<br>
<br>
<br>
# ----- presence_xml params -----<br>
modparam("presence_xml", "force_active", 1)<br>
modparam("presence_xml", "db_url", "WEBRTC_DBURL")<br>
modparam("presence_xml", "integrated_xcap_server", 1)<br>
<br>
<br>
# ----- xcap_server params -----<br>
modparam("xcap_server", "db_url", "WEBRTC_ALT_DBURL")<br>
modparam("xcap_server", "buf_size", 65536)<br>
<br>
<br>
# ----- pua params -----<br>
modparam("pua", "db_mode", 2)<br>
modparam("pua", "fetch_rows", 1024)<br>
modparam("pua", "update_period", 30)<br>
modparam("pua", "db_url", "WEBRTC_DBURL")<br>
<br>
modparam("pua", "hash_size", 12)<br>
modparam("pua", "check_remote_contact", 0)<br>
modparam("pua", "min_expires", WEBRTC_SIP_MIN_EXPIRE)<br>
modparam("pua", "default_expires", WEBRTC_SIP_DEFAULT_EXPIRE)<br>
<br>
</div>
<div>
<div><br>
# ----- rls params -----<br>
# only enable for distributed setup<br>
modparam("rls", "db_mode", 2)<br>
modparam("rls", "waitn_time", 10)<br>
modparam("rls", "fetch_rows", 1024)<br>
modparam("rls", "clean_period", 30)<br>
modparam("rls", "notifier_processes", 4)<br>
modparam("rls", "db_url", "WEBRTC_DBURL")<br>
<br>
modparam("rls", "hash_size", 12)<br>
modparam("rls", "to_presence_code", 10)<br>
modparam("rls", "integrated_xcap_server", 1)<br>
modparam("rls", "disable_remote_presence", 1)<br>
modparam("rls", "rls_event", "presence;winfo")<br>
modparam("rls", "max_expires", WEBRTC_SIP_MAX_EXPIRE)<br>
modparam("rls", "server_address",
<a class="moz-txt-link-rfc2396E" href="sip:rls@WEBRTC_SIP_IP:WEBRTC_SIP_PORT">"sip:rls@WEBRTC_SIP_IP:WEBRTC_SIP_PORT"</a>)<br>
...<br>
--<br>
<br>
</div>
<div>Thank you.<br>
<br>
</div>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Aug 3, 2015 at 12:33 PM,
Daniel-Constantin Mierla <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:miconda@gmail.com"
target="_blank">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hello,<br>
<br>
can you look at SIP trace and see what is the Contact
address of the subscription? You can use ngrep to sniff on
port 5060 (for tcp) on kamailio server.<br>
<br>
Also, are you using and routing enforcement for NOTIFY
(e.g., you have a chain of proxies or use
event_route[tm:local-request] with force send socket)?<br>
<br>
Having the parameters for presence, rls and pua modules
might be helpful to spot what is wrong.<br>
<br>
Cheers,<br>
Daniel
<div>
<div class="h5"><br>
<br>
<div>On 03/08/15 12:28, M S wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">
<div>Any ideas anyone?<br>
<br>
</div>
<div>I have updated the Kamailio to v4.3.1
Rev.4717b5, still the same issue.<br>
</div>
<div><br>
</div>
Thank you.<br>
<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jul 31, 2015 at
7:36 PM, M S <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:shaheryarkh@gmail.com"
target="_blank">shaheryarkh@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>Hi,<br>
<br>
</div>
I have a Kamailio v4.3.0 with SVN Rev.
c6aa95 running an RLS based presence
setup. Everything works fine when
end-user has UDP transport, however, if
user has TCP or TLS transport then i
aggregated NOTIFY sent by RLS gives send
error,<br>
<br>
--<br>
WARNING: <core> [forward.c:231]:
get_send_socket2(): protocol/port
mismatch (forced tls:X.X.X.X:5061, to
udp:Y.Y.Y.Y:12345) <br>
--<br>
<br>
</div>
(X.X.X.X is server IP and Y.Y.Y.Y is end
user IP).<br>
<br>
</div>
<div>Not sure if it is configuration issue
or some bug, so posting it to both mailing
list.<br>
<br>
</div>
<div>Please help.<br>
<br>
</div>
<div>Thank you.<br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
sr-dev mailing list
<a moz-do-not-send="true" href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a>
<a moz-do-not-send="true" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><span class="HOEnZb"><font color="#888888">
</font></span></pre>
<span class="HOEnZb"><font color="#888888"> </font></span></blockquote>
<span class="HOEnZb"><font color="#888888"> <br>
<pre cols="72">--
Daniel-Constantin Mierla
<a moz-do-not-send="true" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a moz-do-not-send="true" href="http://www.asipto.com" target="_blank">http://www.asipto.com</a></pre>
</font></span></div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a></pre>
</body>
</html>