[Freeswitch-users] Re- read_codec/read_rate vs. write_codec/write_rate channel variables

[Andrew Keil]

Anyone have any comments?

From: FreeSWITCH-users [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Andrew Keil
Sent: Friday, 3 November 2017 12:11 PM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: [Freeswitch-users] Re- read_codec/read_rate vs. write_codec/write_rate channel variables


This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>

Feedback<http://aka.ms/SafetyTipsFeedback>

To FreeSWITCH Users,

I am just looking for confirmation of the following:


  1.  If I receive an inbound call to FreeSWITCH (the codec is negotiated and the call is answered by FreeSWITCH) and there is NO call bridging done, then am I correct that only the read_codec & read_rate channel variables apply (for CDR purposes)?


  1.  If I make an outbound call from FreeSWITCH (using originate api command) and once again there is NO call bridging done, then am I correct that only the write_codec & write_rate channel variables apply (for CDR purposes)?


  1.  When using mod_conference (for conferencing two inbound calls together or one inbound and one outbound (using originate api command) together) does this affect the read_codec & read_rate and write_codec & write_rate channel variables in any way?

The reason I ask this is I noticed the following on an outbound call made (using the originate api command) recently and wanted to better understand what the read_codec & read_rate are used for when NO call bridging is done:

read_codec: L16
read_rate: 8000
write_codec: PCMA
write_rate: 8000

I appreciate the clarification.

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20171107/0614c7f2/attachment-0001.html>