[asterisk-bugs] [JIRA] (ASTERISK-30453) On external transfer Contact header rewriten with external_signaling_address

[Rafal Ramocki (JIRA)]

Rafal Ramocki created ASTERISK-30453:
----------------------------------------

             Summary: On external transfer Contact header rewriten with external_signaling_address
                 Key: ASTERISK-30453
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30453
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: pjproject/pjsip
    Affects Versions: 18.16.0
         Environment: Oracle Linux 8
            Reporter: Rafal Ramocki


When PJSIP option external_signaling_address is set because node is behind NAT when Transfer() application is executed to redirect call incomming on SIP Trunk back to the same trunk Contact: header of 302 responce is rewriten with external_signaling_address.  Transfer() is executed in following way:

Transfer(PJSIP/sip:XXXXXXXXX at sip.example.com);

And this results in following responce:

SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 87.204.129.4:5060;rport=5060;received=87.204.129.4;branch=z9hG4bK5fpi6q209g1s0s873tq0.1
Call-ID: SD6bg3a01-d831b6e708921fa733c1a098525082f7-ag3jn70
From: <sip:XXXXXXXXX at xxx.com;user=phone>;tag=SD6bg3a01-1699263443-1678104169287-
To: "xxxxxxxxx xxxxxxxxx" <sip:xxxxxxxxx at xxx.com.pl;line=xzlstoa>;tag=542f525d-dda1-446a-9641-3675c9e0a70e
CSeq: 459720100 INVITE
Server: Asterisk PBX 18.16.0
Contact: <sip:XXXXXXXXX at 1.2.3.4>
Reason: Q.850;cause=0
Supported: histinfo
Content-Length:  0

Where 1.2.3.4 from Contact: header is the same as external_signaling_address. When external_signaling_address is not set in pjsip.conf, 1.2.3.4 is the domain that the same as one in parameter of Transfer applicaation.

In my opinion expected behaviour is to not rewrite Contact: headers with external_signaling_address at transfer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)