[Spce-user] Transcode Audio Codec and preferred vocoder list

Raúl Alexis Betancor Santana rabs at dimension-virtual.com
Wed Sep 9 01:57:22 EDT 2015

Thats because SCPE doesn't touch the RTP at all ... it only proxy it if needed, but don't do any transcoding. 

If you whant transcoding or more advanced RTP tricks ... you should play with the SEMS part of SPCE. 

> De: "Matthias Hohl" <matthias.hohl at telematica.at>
> Para: "Spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
> Enviados: Miércoles, 9 de Septiembre 2015 2:24:29
> Asunto: [Spce-user] Transcode Audio Codec and preferred vocoder list

> Hello,

> i want to force HD Audio (like G.722) on my SPCE for calls on subscriber site,
> so I told some test subscribers to force G.722 on clientsite.
> That works well, but I regonized, that if a peering just support G.711, the
> subscriber can't phone outside or can recieve a call.

> I get: NAT-Reply - S=488 - Not acceptable here

> So it seams that the SPCE don't transcode the audio to the right codec.

> 1.) Is there an option that the SPCE Transcode the G.711 Audio to G.722 Audio
> and vica verse?
> 2.) If the subscriber and the peerings support booth Codecs, which codec will be
> taken? Is there a internal preferred Vocoder list with a ranking, which vocoder
> is preferred over another?

> Thanks for you help.

> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150909/416c8bc2/attachment-0001.html>

More information about the Spce-user mailing list