Codec naming consistency

Status
Not open for further replies.

cobaltit

Platinum Partner
Advanced Certified
Joined
Mar 22, 2012
Messages
6,735
Reaction score
2,324
So under trunks codecs are primarily in all CAPS except for OPUS which is listed as opus. Then under extensions the 3CX Client uses the same references but Yealink for example uses PCMU where 3CX uses G.711 U-law. This might be because Yealink refers to the codec as PCMU. But then under PBX Settings for the Codec Priority you have PCMU again instead of G.711 U-law and then you have OPUS instead of opus. It would be nice if all the codes were referenced the same as far as spelling/capitalization.
upload_2018-8-30_23-54-48.png upload_2018-8-30_23-55-11.png
upload_2018-8-30_23-55-45.pngupload_2018-8-30_23-56-0.png
 

Attachments

  • upload_2018-8-30_23-55-34.png
    upload_2018-8-30_23-55-34.png
    13.1 KB · Views: 5
Yealinks definitely use PCMU and PCMA in their GUI.

upload_2018-8-31_8-9-27.png

I would agree with keeping things consistent however. You would be surprised how many 3CX users I speak to who don't know that G711 a/ulaw are the same as PCMU/PCMA.
 
You would be surprised how many 3CX users I speak to who don't know that G711 a/ulaw are the same as PCMU/PCMA.

It does not surprise me at all. This knowledge is mainly the domain of telecommunications engineers. I'm guessing that the folk at Yealink come from and IT background.
 
Hello @cobaltit

I can understand your point about keeping things consistent but the reason why codecs are different under phones settings is because the different naming used by different phone vendors. So when you add a phone the values are taken by the template and the config file is generated based on those values so the phone can understand the codecs. May i suggest a thread in the ideas section of forum so it can upvoted by other users and taken into consideration by the corresponding department.
 
  • Like
Reactions: craigreilly
@YiannisH_3CX Understood about it being different due to vendor differences although that is easily resolved by 3CX giving guidelines to the vendors when creating the templates for 3CX. Looking at the Yealink template for example it's a simple change:

<option value="0" payload="PCMU">PCMU</option>

becomes

<option value="0" payload="PCMU">G.711 U-law</option>

The trunk and codec priority sections are both 3CX generated as far as I can tell so there isn't internal consistency either.
 
  • Like
Reactions: craigreilly
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,893
Messages
589,598
Members
164,760
Latest member
SaschaA_