On 13/01/15 00:28, Mikko Lehto wrote:
Juha Heinanen j...@tutpro.com:
in case of tcp (and tls) the source port is always a random one.
only the destination port can be predetermined.
OK, thanks. I'll go with that then.
Actually I can see non-random port with TLS...
...but that's with Homer
Makes sense, I can live with this.
Thanks for clarfication.
--
Mikko Lehto
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Juha Heinanen j...@tutpro.com:
in case of tcp (and tls) the source port is always a random one.
only the destination port can be predetermined.
OK, thanks. I'll go with that then.
Actually I can see non-random port with TLS...
...but that's with Homer + sip_trace() captured traffic.
I'll
Mikko Lehto writes:
Here is the trouble:
when I observe outgoing TLS traffic with tcpdump, I can see that local
source port is not following what I set with force_send_socket(). I tried to
place force_send_socket() in request_route, branch_route, and
tm:local-request, but it is always some
Some additional information:
OS is Linux Debian Wheezy 7.6 on amd64
pua_subscribe is launched like this:
kamcmd mi pua_subscribe sip:+35812345789@A.B.C.D:5041 sip:myproxy.fqdn.invalid
presence 3600
--
Mikko
___
SIP Express Router (SER) and Kamailio
Hi
I am having strange behavior on local port assignment when
proxying out locally generated request. Kamailio is 4.2.1 from git.
I use MI pua_subscribe to create subscription to be handled by
external presence server.
In event_route[tm:local-request] I set $du to point back to proxy itself.