[asterisk-bugs] [JIRA] (ASTERISK-26747) Ambiguity in PJSIP use_avpf and force_avp

[Joshua Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234843#comment-234843 ] 

Joshua Colp commented on ASTERISK-26747:
----------------------------------------

Provided that behavior is backwards compatible and tests are written to cover the new behavior, it could be.
As for documentation everything is documented in XML in the code which is exported onto the wiki[1]. The sample file isn't meant to serve as an exhaustive reference of options.

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Configuration_res_pjsip#Asterisk13Configuration_res_pjsip-endpoint_force_avp

> Ambiguity in PJSIP use_avpf and force_avp
> -----------------------------------------
>
>                 Key: ASTERISK-26747
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26747
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.13.1
>            Reporter: JoshE
>
> Placeholder issue and starting a discussion for some concerns about the way that use_avpf and force_avp (undocumented, though used in pjsip) are implemented in res_pjsip in Asterisk 13+.
> use_avpf right now forces the AVPF on all incoming invites. We would prefer the ability, as was closer to the behavior in chan_sip to allow it if present, but not require it.
> Similar to some issues with encryption, we have a need to "optimistically" accept avpf on incoming invites. Ideally, this would let us configure something like:
> use_avpf=yes
> force_avpf=no
> And allow an invite with RTP/AVP to pass through. Right now, this returns an invalid transport.
> Might be a question for @jcolp, but would a change to add this additional behavior - a knob for force_avpf - be acceptable?
> Secondarily, it may be beneficial to document the force_avp option, as it's currently undocumented in the .sample file.



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