[asterisk-bugs] [JIRA] (ASTERISK-30451) res_pjsip: Contact header set incorrectly for call redirect (302 Moved temp.) when external_* set
Karsten Wemheuer (JIRA)
noreply at issues.asterisk.org
Thu Apr 6 04:52:03 CDT 2023
[ https://issues.asterisk.org/jira/browse/ASTERISK-30451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261697#comment-261697 ]
Karsten Wemheuer commented on ASTERISK-30451:
---------------------------------------------
I have found a possible solution to the issue.
Unfortunately I have a problem with gerrit, so I attach the patch here.
The patch prevents NAT handling of the contact header when a 302 response message is sent.
As I understand the RFC, the Contact header is supposed to specify the new destination on a 302 response, so the destination is not local.
> res_pjsip: Contact header set incorrectly for call redirect (302 Moved temp.) when external_* set
> -------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-30451
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-30451
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip_nat
> Affects Versions: 18.16.0
> Environment: Debian 11 (Bullseye)
> Reporter: Karsten Wemheuer
> Attachments: pjsip.conf, trace-20230303-1.pcapng
>
>
> Hi,
> I may have found a bug that occurs with a "redirect" (application "transfer").
> The scenario concerns a call that comes from the provider to the Asterisk and is to be routed in the dialplan via transfer to an external destination. the dialplan uses
> Transfer(sip:+491708300432 at tel.t-online.de)
> The resulting 302 response contains the IP address of the router in the Contact header. However, the provider expects the domain there.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list