Hi Guys,
We have two network interfaces. One public and one private. We had enabled mhomed and works great BUT if we do a netstat -naup | grep 5060 we see that some sockets keeps opened also when the call is finished. The source port in netstat it's not 5060 so I suppose that kamailio use another one for something else.
Is this the right behavior? How long does this sockets remain opened? Are we missing something in our cfg?
6 2017-01-25 15:52:04.986651 172.16.213.38 172.16.200.159 SIP/SDP 146 Request: INVITE sip:xxx@172.16.200.159:5060 34 2017-01-25 15:52:19.636895 172.16.213.38 172.16.200.159 SIP 716 Request: ACK sip:xxx@172.16.200.159:5060 | 37 2017-01-25 15:54:38.947831 172.16.208.111 172.16.213.38 SIP 736 Request: BYE sip:127.0.0.8:5060;line=sr-987jhlk* | 40 2017-01-25 15:54:38.950899 172.16.213.38 172.16.200.159 SIP 660 Request: BYE sip:172.16.208.111:5060 |
[root@dwrfsd01 kamailio]# netstat -naup | grep 5060 udp 0 0 172.16.213.38:*56086* http://172.16.213.38:56086 172.16.200.159:5060 ESTABLISHED 17015/kamailio udp 0 0 172.16.213.38:5060 0.0.0.0:* 17006/kamailio udp 0 0 172.16.213.38:*41971* http://172.16.213.38:41971 172.16.200.159:5060 ESTABLISHED 17051/kamailio udp 0 0 172.16.213.38:*54651* http://172.16.213.38:54651 172.16.200.159:5060 ESTABLISHED 17008/kamailio
Thanks in advance!
Diego.
Hi list,
Any help on this?
Cheers.
Diego.
2017-01-25 16:29 GMT-03:00 Diego Nadares dnadares@gmail.com:
Hi Guys,
We have two network interfaces. One public and one private. We had enabled mhomed and works great BUT if we do a netstat -naup | grep 5060 we see that some sockets keeps opened also when the call is finished. The source port in netstat it's not 5060 so I suppose that kamailio use another one for something else.
Is this the right behavior? How long does this sockets remain opened? Are we missing something in our cfg?
6 2017-01-25 15:52:04.986651 172.16.213.38 172.16.200.159 SIP/SDP 146 Request: INVITE sip:xxx@172.16.200.159:5060 34 2017-01-25 15:52:19.636895 172.16.213.38 172.16.200.159 SIP 716 Request: ACK sip:xxx@172.16.200.159:5060 | 37 2017-01-25 15:54:38.947831 172.16.208.111 172.16.213.38 SIP 736 Request: BYE sip:127.0.0.8:5060;line=sr-987jhlk* | 40 2017-01-25 15:54:38.950899 172.16.213.38 172.16.200.159 SIP 660 Request: BYE sip:172.16.208.111:5060 |
[root@dwrfsd01 kamailio]# netstat -naup | grep 5060 udp 0 0 172.16.213.38:*56086* http://172.16.213.38:56086 172.16.200.159:5060 ESTABLISHED 17015/kamailio udp 0 0 172.16.213.38:5060 0.0.0.0:* 17006/kamailio udp 0 0 172.16.213.38:*41971* http://172.16.213.38:41971 172.16.200.159:5060 ESTABLISHED 17051/kamailio udp 0 0 172.16.213.38:*54651* http://172.16.213.38:54651 172.16.200.159:5060 ESTABLISHED 17008/kamailio
Thanks in advance!
Diego.
Hello,
I am not sure what ESTABLISHED is meant by netstat for UDP sockets, because there is no connection defined for UDP (datagram socket is kind of shoot and forget) -- maybe it track that there was some traffic and remembers that for a while. Perhaps reading the manual of netstat will help to understand better.
Cheers, Daniel
On 26/01/2017 22:03, Diego Nadares wrote:
Hi list,
Any help on this?
Cheers.
Diego.
2017-01-25 16:29 GMT-03:00 Diego Nadares <dnadares@gmail.com mailto:dnadares@gmail.com>:
Hi Guys, We have two network interfaces. One public and one private. We had enabled mhomed and works great BUT if we do a netstat -naup | grep 5060 we see that some sockets keeps opened also when the call is finished. The source port in netstat it's not 5060 so I suppose that kamailio use another one for something else. Is this the right behavior? How long does this sockets remain opened? Are we missing something in our cfg? 62017-01-25 15:52:04.986651172.16.213.38172.16.200.159SIP/SDP146Request: INVITE sip:xxx@172.16.200.159:5060 <http://sip:xxx@172.16.200.159:5060> 342017-01-25 15:52:19.636895172.16.213.38172.16.200.159SIP716Request: ACK sip:xxx@172.16.200.159:5060 <http://sip:xxx@172.16.200.159:5060> | 372017-01-25 15:54:38.947831172.16.208.111172.16.213.38SIP736Request: BYE sip:127.0.0.8:5060;line=sr-987jhlk* | 402017-01-25 15:54:38.950899172.16.213.38172.16.200.159SIP660Request: BYE sip:172.16.208.111:5060 <http://172.16.208.111:5060> | [root@dwrfsd01 kamailio]# netstat -naup | grep 5060 udp 0 0 172.16.213.38:*56086* <http://172.16.213.38:56086>** 172.16.200.159:5060 <http://172.16.200.159:5060> ESTABLISHED 17015/kamailio udp 0 0 172.16.213.38:5060 <http://172.16.213.38:5060> 0.0.0.0:* 17006/kamailio udp 0 0 172.16.213.38:*41971* <http://172.16.213.38:41971>* * 172.16.200.159:5060 <http://172.16.200.159:5060> ESTABLISHED 17051/kamailio udp 0 0 172.16.213.38:*54651* <http://172.16.213.38:54651> 172.16.200.159:5060 <http://172.16.200.159:5060> ESTABLISHED 17008/kamailio Thanks in advance! Diego.
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
Hi Daniel,
Thanks for your answer. My question was more related to why kamailio opens those extra sockets also when it's not sending any data. Is that the normal behavior?
You are right, i will read netstat's manual for how long and why keeps those sockets opened.
Thanks again!
Diego
El vie, 27 de ene. de 2017 a las 05:14, Daniel-Constantin Mierla < miconda@gmail.com> escribió:
Hello,
I am not sure what ESTABLISHED is meant by netstat for UDP sockets, because there is no connection defined for UDP (datagram socket is kind of shoot and forget) -- maybe it track that there was some traffic and remembers that for a while. Perhaps reading the manual of netstat will help to understand better.
Cheers, Daniel
On 26/01/2017 22:03, Diego Nadares wrote:
Hi list,
Any help on this?
Cheers.
Diego.
2017-01-25 16:29 GMT-03:00 Diego Nadares dnadares@gmail.com:
Hi Guys,
We have two network interfaces. One public and one private. We had enabled mhomed and works great BUT if we do a netstat -naup | grep 5060 we see that some sockets keeps opened also when the call is finished. The source port in netstat it's not 5060 so I suppose that kamailio use another one for something else.
Is this the right behavior? How long does this sockets remain opened? Are we missing something in our cfg?
6 2017-01-25 15:52:04.986651 172.16.213.38 172.16.200.159 SIP/SDP 146 Request: INVITE sip:xxx@172.16.200.159:5060 34 2017-01-25 15:52:19.636895 172.16.213.38 172.16.200.159 SIP 716 Request: ACK sip:xxx@172.16.200.159:5060 | 37 2017-01-25 15:54:38.947831 172.16.208.111 172.16.213.38 SIP 736 Request: BYE sip:127.0.0.8:5060;line=sr-987jhlk* | 40 2017-01-25 15:54:38.950899 172.16.213.38 172.16.200.159 SIP 660 Request: BYE sip:172.16.208.111:5060 |
[root@dwrfsd01 kamailio]# netstat -naup | grep 5060 udp 0 0 172.16.213.38:*56086* http://172.16.213.38:56086 172.16.200.159:5060 ESTABLISHED 17015/kamailio udp 0 0 172.16.213.38:5060 0.0.0.0:* 17006/kamailio udp 0 0 172.16.213.38:*41971* http://172.16.213.38:41971 172.16.200.159:5060 ESTABLISHED 17051/kamailio udp 0 0 172.16.213.38:*54651* http://172.16.213.38:54651 172.16.200.159:5060 ESTABLISHED 17008/kamailio
Thanks in advance!
Diego.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
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