[asterisk-bugs] [JIRA] (ASTERISK-24387) res_pjsip: rport sent from UAS MUST include the port that the UAC sent the request on
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Mon Nov 3 13:58:50 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-24387:
-----------------------------------
Target Release Version/s: 12.7.0
> res_pjsip: rport sent from UAS MUST include the port that the UAC sent the request on
> -------------------------------------------------------------------------------------
>
> Key: ASTERISK-24387
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24387
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip
> Affects Versions: 12.6.0, 13.0.0-beta2
> Reporter: Matt Jordan
> Target Release: 12.7.0, 13.0.0-beta3
>
> Attachments: ASTERISK-24387-log.txt
>
>
> When {{force_rport=Yes}} and a request is received without an rport, Asterisk will respond with an {{rport}} parameter in the top-most {{Via}} header without a specified port. Arguably, every response from the UAS should specify the port with the {{rport}} parameter:
> {quote}
> When a server compliant to this specification (which can be a proxy
> or UAS) receives a request, it examines the topmost Via header field
> value. If this Via header field value contains an "rport" parameter
> with no value, it MUST set the value of the parameter to the source
> port of the request.
> {quote}
> Now, since there *was* no {{rport}} in the request, this is a bit murky. On the other hand, we probably should always provide the port with the {{rport}}, as this is more specific (and a bit more clear) than simply responding with {{rport}} and nothing else.
> A sample rejected call flow by the client is attached to the issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list