| Summary: | ASTERISK-30358: OPUS doesn't generate SDP according to codecs.conf | ||||
| Reporter: | Ruben Iniguez (rubenis) | Labels: | |||
| Date Opened: | 2022-12-16 10:15:47.000-0600 | Date Closed: | 2022-12-16 10:30:33.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_sip/CodecHandling Codecs/codec_opus | ||
| Versions: | 18.15.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | Opus configuration options in codecs.conf seem not to take effect.Example of this follows below:
For the config in codecs.conf: [myopus] type=opus max_playback_rate=8000 The SDP in 200 OK provided by Asterisk is: v=0 o=- 1035043469 4 IN IP4 10.10.10.121 s=Asterisk c=IN IP4 10.10.10.121 t=0 0 m=audio 23326 RTP/AVP 111 126 a=rtpmap:111 opus/48000/2 a=fmtp:111 useinbandfec=1 a=rtpmap:126 telephone-event/8000 a=fmtp:126 0-16 a=ptime:20 a=maxptime:20 a=sendrecv So it is missing maxplaybackrate parameter in SDP. I haven't made exhustive checkings but so far I found only bitrate parameter (maxaveragebitrate on SDP) is configurable. I found ASTERISK-26901 is related to this. However I opened a new case since that one seems unattended. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2022-12-16 10:15:54.310-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2022-12-16 10:21:34.093-0600 Opening a duplicate issue won't escalate things. Any updates will be posted on ASTERISK-26901. By: Ruben Iniguez (rubenis) 2022-12-16 10:29:36.501-0600 Can the other case be attended please, it's being opened for years... By: Asterisk Team (asteriskteam) 2022-12-16 10:29:36.849-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2022-12-16 10:30:33.887-0600 There is no time frame or guarantee on when things are resolved or looked into. Any updates will be posted on the linked issue. | ||||