read vs. write codec channel variables clarification needed for CDR purposes
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
Those variables should be set, and apply in all those situations. The read codec is the format the channel needs to read in, in the case of conference, that application requires raw audio, the write codec is the codec that it needs to write out of the channel. This shouldn’t make a difference if its an inbound or outbound call, its all from the perspective of the individual channel.
On Nov 10, 2017, at 1:25 AM, Andrew Keil <andrew.keil@visytel.com> wrote:
To FreeSWITCH Users,
I am just looking for confirmation of the following:
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)?
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)?
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://confluence.freeswitch.org <http://confluence.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org <http://www.freeswitch.org/>
participants (2)
-
Andrew Keil
-
Michael Jerris