[Home]

Summary:ASTERISK-26395: IAX2 doesn't support SILK
Reporter:Yury Tsaregorodtsev (aero.108)Labels:
Date Opened:2016-09-20 15:21:40Date Closed:2016-09-20 16:57:46
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_iax2
Versions:11.23.1 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hello,
IAX2 doesn't support SILK
*CLI> iax2 show peer PEER1


 * Name       : PEER1
 Description  :
 Secret       : <Not set>
 Context      : iq_in
 Parking lot  :
 Mailbox      :
 Dynamic      : No
 Callnum limit: 0
 Calltoken req: No
 Trunk        : No
 Encryption   : No
 Callerid     : "" <>
 Expire       : -1
 ACL          : No
 Addr->IP     : 88.8.1.1 Port 4569
 Defaddr->IP  : 0.0.0.0 Port 0
 Username     : me
 Codecs       : (nothing)
 Codec Order  : (silk24)

On Dial remote peer just get HANGUP message from origination asterisk.
Comments:By: Asterisk Team (asteriskteam) 2016-09-20 15:21:40.713-0500

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.

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].
By: Matt Jordan (mjordan) 2016-09-20 16:57:42.547-0500

You're correct, it doesn't support SILK.

That's even noted in the [IAX2 RFC, section 1.2|https://tools.ietf.org/html/rfc5456#section-1.2]:

{quote}
  While IAX is very effective, addressing many of today's
  communications needs, it does have a few limitations.  For instance,
  IAX uses a point-to-point codec negotiation mechanism that limits
  extensibility because every IAX node in a call path must support
  every used codec to some degree.  In addition, the codec definition
  is controlled by an internally defined 32-bit mask, so the codecs
  must be defined in the protocol, and the maximum number of
  simultaneous codecs is, therefore, limited.
{quote}

If you look at [Section 8.7|https://tools.ietf.org/html/rfc5456#section-8.7], you'll see what formats IAX supports. SILK isn't one of them.

At this time, there are no plans to update the RFC, nor are there any plans to add any media formats beyond what IAX supports today.

Closing out as "Won't Fix" (plus, technically, this is an improvement or feature request, and not a bug).