[OpenSIPS-Devel] [opensips] Opensips 1.8.3, wrong IP and Port combination while sending the response. (#737)
suryaveerc
notifications at github.com
Fri Dec 25 06:33:23 CET 2015
I am trying to run OpenSips presence server on kubernetes but it's not working The reason for it is what I found is the wrong IP - Port combination choosen by OpensSips to send the response 200
Below is the tcpdump
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
04:34:30117024 IP (tos 0x0, ttl 63, id 10208, offset 0, flags [DF], proto UDP (17), length 999)
**1024424040351 > 102447115060**: SIP, length: 971
PUBLISH sip:service-1 at opensipstestorg SIP/20
Via: SIP/20/UDP **19216814410:32569**;branch=z9hG4bK-6324-1-0
Max-Forwards: 20
From: <sip:service-1 at opensipstestorg>;tag=1
To: <sip:service-1 at opensipstestorg>
Call-ID: 1-6324 at 19216814410
CSeq: 1 PUBLISH
Expires: 3600
Event: presence
Content-Length: 607
User-Agent: Sipp v11-TLS, version 20061124
<Removed presence xml>
04:34:30118455 IP (tos 0x10, ttl 64, id 28000, offset 0, flags [DF], proto UDP (17), length 417)
**102447115060 > 1024424032569**: SIP, length: 389
SIP/20 200 OK
Via: SIP/20/UDP **19216814410:32569**;received=10244240;branch=z9hG4bK-6324-1-0
From: <sip:service-1 at opensipstestorg>;tag=1
To: <sip:service-1 at opensipstestorg>;tag=6c8cd3bc7eb4fe86b153056f4d236d23-ba2c
Call-ID: 1-6324 at 19216814410
CSeq: 1 PUBLISH
Expires: 3600
SIP-ETag: a14509226693820
Server: OpenSIPS (184-notls (x86_64/linux))
Content-Length: 0
As you can see in the dump the IP address where the reply is being sent is the one from which it received the request ie **10244240** while the port is **32569**, which is the actual client port instead it should have been **40351**
Please correct me if I made some wrong observation
Thanks,
Suryaveer
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/737
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20151224/2b41e178/attachment.htm>
More information about the Devel
mailing list