[sr-dev] RLS Notify sent to wrong transport

[Daniel-Constantin Mierla]

Hello,

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.

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)?

Having the parameters for presence, rls and pua modules might be helpful
to spot what is wrong.

Cheers,
Daniel

On 03/08/15 12:28, M S wrote:
> Any ideas anyone?
>
> I have updated the Kamailio to v4.3.1 Rev.4717b5, still the same issue.
>
> Thank you.
>
>
>
> On Fri, Jul 31, 2015 at 7:36 PM, M S <shaheryarkh at gmail.com
> <mailto:shaheryarkh at gmail.com>> wrote:
>
>     Hi,
>
>     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,
>
>     --
>     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)
>     --
>
>     (X.X.X.X is server IP and Y.Y.Y.Y is end user IP).
>
>     Not sure if it is configuration issue or some bug, so posting it
>     to both mailing list.
>
>     Please help.
>
>     Thank you.
>
>
>
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20150803/3b228886/attachment.html>