@Marbled wrote:
Hi!
Did they all code their G722 support from scratch or could they be using the same library (or something similar in concept to it, maybe even in hardware) to implement G722?
That might explain why all of them are failing while others are fine...
If G722 was a new protocol I would suggest this is an error in interpretation of something in the protocol by many manufacturer but as it is relatively old it's kind of weird they supposedly all got the same thing wrong...
So it's either all of these manufacturer getting something wrong, all of them using the same library (or something similar) or hardware or Asterisk having a problem with how they implemented G722....
edit: I found the following comment on Wikipedia interesting: "Consequently correct implementations represent the value 8,000 where required but encode and decode audio at 16 kHz." ( https://en.wikipedia.org/wiki/G.722#RTP_encapsulation ). What happens if they get that wrong?
Have a nice day!
Nick