[asterisk-bugs] [JIRA] (ASTERISK-28884) x-ast-orig-host not filtered out from request URI and To header
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Thu May 28 07:29:28 CDT 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-28884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-28884:
-------------------------------------
Target Release Version/s: 17.5.0
> x-ast-orig-host not filtered out from request URI and To header
> ---------------------------------------------------------------
>
> Key: ASTERISK-28884
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28884
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip_nat
> Affects Versions: 16.9.0, 16.10.0
> Reporter: nappsoft
> Assignee: Unassigned
> Severity: Minor
> Labels: patch
> Target Release: 13.34.0, 16.11.0, 17.5.0
>
> Attachments: ast_message_filter.diff, patch2.diff, patch3.diff
>
>
> In the Changelog to Change-Id Idc263ad2d2d7bd8faa047e5804d96a5fe1cd282e one can read concerning x-ast- URI parameters: "Asterisk will never send a request with those headers in it". But while res_pjsip_nat filters out the x-ast-* URI parameters from the contact header, they stay in the request URI and the to-Header.
> This makes the INVITE request larger than necessary and because of that we were facing issues in some scenarios with PPPoE connections (MTU 1492) and routers that do not support UDP fragmentation.
> I was able to work around the issue with the attached patch. However you might prefer to add the removal of the URI parameters to res_pjsip_nat or you might think that it's necessary to not remove the parameters at all for whatever reason.
> So please let me know whether you'd like the patch to be submitted via gerrit or not.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list