[OpenSIPS-Users] siptrace picks incorrect source socket

[Jeff Pyle]

Hello,

I recently enabled siptrace on an OpenSIPS 2.2.2 system acting as a
registrar and a proxy.  It has one IPv4 address with several ports for UDP,
TCP and TLS.  In a case where the INVITE is relayed from TLS to UDP, the
replies to the UAC are incorrectly being reported as coming from the UDP
socket.

In the below scenario the UAC is at 64.65.66.67, and its ephemeral TCP
client port for this call is 61235.  The OpenSIPS proxy is at
131.132.133.134 listening on UDP 5060 and TLS 5061.  Also on
131.132.133.134 there is a Freeswitch media server listening on UDP 5080.
The UAC sends an INVITE to the proxy over TLS which routes it to the media
server over UDP.  The replies relayed to the UAC are reported as having
come from port 5060 over UDP when in reality they have come from port 5061
over TCP (TLS).

My config:

listen=udp:131.132.133.134:5060
listen=tls:131.132.133.134:5061
listen=hep_udp:127.0.0.1:9030

loadmodule "siptrace.so"
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_id", "[hep]uri=hep:127.0.0.1:9060
;transport=udp;")



Debugs:


INVITE in from UAC over TLS
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 22, host 64.65.66.67 , port 61235
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 22, host 131.132.133.134 , port 5061

INVITE out to media server over UDP
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5080

100 Trying in from media server over UDP
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24650]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5080
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24650]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060

180 Ringing in from media server over UDP
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5080
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060

180 Ringing out to UAC over TLS (even though it reports UDP)
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 22, host 64.65.66.67 , port 61235

200 OK in from media server over UDP
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5080
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060

200 OK out to UAC over TLS (even though it reports udp)
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060
Feb  3 21:20:22 testproxy /usr/sbin/opensips[24651]:
DBG:siptrace:pipport2su: proto 22, host 64.65.66.67 , port 61235

ACK in from UAC over TLS
Feb  3 21:20:23 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 22, host 64.65.66.67 , port 61235
Feb  3 21:20:23 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 22, host 131.132.133.134 , port 5061

ACK out to media server over UDP
Feb  3 21:20:23 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5060
Feb  3 21:20:23 testproxy /usr/sbin/opensips[24673]:
DBG:siptrace:pipport2su: proto 17, host 131.132.133.134 , port 5080


Everything routes properly, but it isn't reported by siptrace properly.  Is
this a bug or am I doing something wrong?



- Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170203/7a0cb7f1/attachment.html>