[asterisk-bugs] [JIRA] (ASTERISK-28621) Enforce T.38 error correction mode at 200 ok received
Friendly Automation (JIRA)
noreply at issues.asterisk.org
Mon Dec 2 06:47:32 CST 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=248916#comment-248916 ]
Friendly Automation commented on ASTERISK-28621:
------------------------------------------------
Change 13290 merged by Joshua Colp:
res_pjsip_t38: T.38 error correction mode selection at 200 ok received
[https://gerrit.asterisk.org/c/asterisk/+/13290|https://gerrit.asterisk.org/c/asterisk/+/13290]
> Enforce T.38 error correction mode at 200 ok received
> -------------------------------------------------------
>
> Key: ASTERISK-28621
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28621
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip_t38
> Affects Versions: 13.20.0
> Reporter: Salah Ahmed
> Assignee: Salah Ahmed
> Severity: Minor
>
> Hello,
> Recently we have found, if asterisk offer T38 SDP with none error correction scheme and the endpoint respond with redundancy EC scheme, asterisk switch to that mode. As we configure the endpoint as none EC mode I think we should not switch to any other mode except none. We have made a simple change to determine the EC mode at 200 OK received using following logic.
> 1. If asterisk offer none, and anything except none in answer will be ignored.
> 2. If asterisk offer fec, answer with fec, redundancy and none will be accepted.
> 3. If asterisk offer redundancy, answer with redundancy and none will be accepted.
> Could anyone please verify the logic and the codes?
> Thank You,
> Salah
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list