[OpenSIPS-Devel] How port and IP are selected while sending the response. From SIP message or from packet header?

[surya]

Hi,

I just want to understand from where the IP and the PORT information is
picked when sending the response. By where I mean, is it from the SIP
message (contact header or VIA header) or from the UDP/IP packet.

Actually, I am trying to deploy Opensips Presence Server (1.8.3) on
Kubernetes and that is not working.

What I noticed is that when the 200 OK is sent by the opensips for the
PUBLISH request, the IP used is the VIP of the Kubernetes from which the
request is forwarded to opensips but the port used is from the SIP message.

Below is the tcpdump.

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes
04:34:30.117024 IP (tos 0x0, ttl 63, id 10208, offset 0, flags [DF], proto
UDP (17), length 999)
   * 10.244.24.0.40351 > 10.244.7.11.5060: SIP, length: 971*
        PUBLISH sip:service-1 at opensipstest.org SIP/2.0
        Via: SIP/2.0/UDP *192.168.144.10:32569*;branch=z9hG4bK-6324-1-0
        Max-Forwards: 20
        From: <sip:service-1 at opensipstest.org>;tag=1
        To: <sip:service-1 at opensipstest.org>
        Call-ID: 1-6324 at 192.168.144.10
        CSeq: 1 PUBLISH
        Expires: 3600
        Event: presence
        Content-Length:   607
        User-Agent: Sipp v1.1-TLS, version 20061124

        <?xml version="1.0"?>
        <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
xmlns:c="urn:ietf:params:xml:ns:pidf:cipid"
entity="ivaxer at tipmeet.com"><tuple xmlns="urn:ietf:params:xml:ns:pidf"
id="0x7fffd54b7860"><status
xmlns="urn:ietf:params:xml:ns:pidf"><basic>open</basic></status></tuple><tuple
xmlns="urn:ietf:params:xml:ns:pidf"
id="0x7fff6dad9400"><status><basic>open</basic></status></tuple><tuple
xmlns="urn:ietf:params:xml:ns:pidf"
id="0x7fff2b7a04c0"><status><basic>open</basic></status></tuple></presence>

04:34:30.118455 IP (tos 0x10, ttl 64, id 28000, offset 0, flags [DF], proto
UDP (17), length 417)
    *10.244.7.11.5060 > 10.244.24.0/.32569/: SIP, length: 389*
        SIP/2.0 200 OK
        Via: SIP/2.0/UDP
*/192.168.144.10:32569/*;received=10.244.24.0;branch=z9hG4bK-6324-1-0
        From: <sip:service-1 at opensipstest.org>;tag=1
        To:
<sip:service-1 at opensipstest.org>;tag=6c8cd3bc7eb4fe86b153056f4d236d23-ba2c
        Call-ID: 1-6324 at 192.168.144.10
        CSeq: 1 PUBLISH
        Expires: 3600
        SIP-ETag: a.1450922669.38.2.0
        Server: OpenSIPS (1.8.4-notls (x86_64/linux))
        Content-Length: 0
 
I am not expert in networks or opensips, but I hope what I observed is
correct. If this information is not complete I can provide more.

I'll ask a parallel question. Can I run OpenSips Presence Server in
Kubernetes?


Any suggestion and guidance is highly appreciated.

Thanks,
Surya



--
View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/How-port-and-IP-are-selected-while-sending-the-response-From-SIP-message-or-from-packet-header-tp7600340.html
Sent from the OpenSIPS - Devel mailing list archive at Nabble.com.