‎Now, why would they do that, when they'd have to transcode every OPUS channel down to 3.1 KHz PCM? 

Meanwhile, G.711u is the "native", packetised correlate of what's already flowing down the TDM trunks.

--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Sent from my BlackBerry.
From: Colton Conor
Sent: Monday, March 14, 2016 10:01
To: James Milko
Subject: Re: [VoiceOps] G.729 A/B Experiences

Sure would be nice if a big carrier like bandwidth.com would natively support the OPUS codec! I think its going to take a big carrier like bandwidth.com or Level3 pushing the SBC/switch vendors to push OPUS. It would be the end all be all codec for voice.



On Mon, Mar 14, 2016 at 8:01 AM, James Milko <[email protected]> wrote:
Biased as all get out, but if your carrier doesn't support at least 729 and 711 find a new carrier.

JM

On Fri, Mar 11, 2016 at 10:02 PM, Calvin Ellison <[email protected]> wrote:
​Could you put their voice on wires (POTS/PRI/VoIP), and the rest of their data on fixed wireless?
This doesn't necessarily give you any more calls per Kbps, but at least keeps voice and data independent. Wires for dependability, radio waves for bandwidth at the cost of some latency & packet loss.

One consideration when using G.729 is how you're going to deliver it to a mostly non-G.729 world. Are your not-quite-broadband customers attached to some PBX that will handle it and send G.711 to your carriers? That's going to cost some CPU or dedicated transcoding hardware. Will your providers accept G.729 and transcode for you? Is there a cost for it? Or will your carriers blindly throw your G.729 at their LCR and hope something sticks?

_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops



_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops



_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to