Different codecs for different devices?
This may be a far out question but here goes: Our fax machines that are connected to ATA's need to be g.711 on both Call Leg A and Call Leg B (in either direction). However, our phones need to be g.711 on the internal side that faces our PBX. On the side facing our SIP provider, the calls should be transcoded to g.729. Inbound the calls to phones (not ATA's) need to be g.729 on the inbound call leg and g.711 on the outbound call leg. I realize we can set inbound / outbound codec preferences in single or multiple profiles and we can set the "absolute_codec_string" value for the outbound call leg. However, I've yet to determine how to set the inbound call leg's codec differently depending on the device. Is this possible? Thanks, Ken Fulmer
Just in case others are interested, this is possible with the following parameters: SIP Profile: <param name="inbound-late-negotiation" value="true"/> Dial-Plan: <action application="set" data="inherit_codec=true"/> The codec negotiated in Call Leg B, is forced onto Call Leg A. This is possible due to the "inbound late negotiation" parameter in the sip profile. Hope this helps someone else. Ken From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Ken Fulmer Sent: Tuesday, May 04, 2010 8:29 AM To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] Different codecs for different devices? This may be a far out question but here goes: Our fax machines that are connected to ATA's need to be g.711 on both Call Leg A and Call Leg B (in either direction). However, our phones need to be g.711 on the internal side that faces our PBX. On the side facing our SIP provider, the calls should be transcoded to g.729. Inbound the calls to phones (not ATA's) need to be g.729 on the inbound call leg and g.711 on the outbound call leg. I realize we can set inbound / outbound codec preferences in single or multiple profiles and we can set the "absolute_codec_string" value for the outbound call leg. However, I've yet to determine how to set the inbound call leg's codec differently depending on the device. Is this possible? Thanks, Ken Fulmer
you can regex the SDP for something specific and use that to set the absolute_codec_string in a standalone extension that comes first in the stack and has continue=true on it On Tue, May 4, 2010 at 11:32 AM, Ken Fulmer < kenfulmer@icstechnologysolutions.com> wrote:
Just in case others are interested, this is possible with the following parameters:
SIP Profile:
<param name="inbound-late-negotiation" value="true"/>
Dial-Plan:
<action application="set" data="inherit_codec=true"/>
The codec negotiated in Call Leg B, is forced onto Call Leg A. This is possible due to the “inbound late negotiation” parameter in the sip profile.
Hope this helps someone else.
Ken
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Ken Fulmer *Sent:* Tuesday, May 04, 2010 8:29 AM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* [Freeswitch-users] Different codecs for different devices?
This may be a far out question but here goes:
Our fax machines that are connected to ATA’s need to be g.711 on both Call Leg A and Call Leg B (in either direction).
However, our phones need to be g.711 on the internal side that faces our PBX. On the side facing our SIP provider, the calls should be transcoded to g.729. Inbound the calls to phones (not ATA’s) need to be g.729 on the inbound call leg and g.711 on the outbound call leg.
I realize we can set inbound / outbound codec preferences in single or multiple profiles and we can set the “absolute_codec_string” value for the outbound call leg.
However, I’ve yet to determine how to set the inbound call leg’s codec differently depending on the device. Is this possible?
Thanks,
Ken Fulmer
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
I think you can also use another variable on the A leg SDP to make it easier on the regex. ep_codec_string. This will contain the parsed version of the A leg SDP and that's what I use most of the times for these tricks. Also, can you document that? :-) Regards, João Mesquita On Tue, May 4, 2010 at 1:52 PM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
you can regex the SDP for something specific and use that to set the absolute_codec_string in a standalone extension that comes first in the stack and has continue=true on it
On Tue, May 4, 2010 at 11:32 AM, Ken Fulmer < kenfulmer@icstechnologysolutions.com> wrote:
Just in case others are interested, this is possible with the following parameters:
SIP Profile:
<param name="inbound-late-negotiation" value="true"/>
Dial-Plan:
<action application="set" data="inherit_codec=true"/>
The codec negotiated in Call Leg B, is forced onto Call Leg A. This is possible due to the “inbound late negotiation” parameter in the sip profile.
Hope this helps someone else.
Ken
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Ken Fulmer *Sent:* Tuesday, May 04, 2010 8:29 AM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* [Freeswitch-users] Different codecs for different devices?
This may be a far out question but here goes:
Our fax machines that are connected to ATA’s need to be g.711 on both Call Leg A and Call Leg B (in either direction).
However, our phones need to be g.711 on the internal side that faces our PBX. On the side facing our SIP provider, the calls should be transcoded to g.729. Inbound the calls to phones (not ATA’s) need to be g.729 on the inbound call leg and g.711 on the outbound call leg.
I realize we can set inbound / outbound codec preferences in single or multiple profiles and we can set the “absolute_codec_string” value for the outbound call leg.
However, I’ve yet to determine how to set the inbound call leg’s codec differently depending on the device. Is this possible?
Thanks,
Ken Fulmer
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Guys, I added this variable to the wiki: http://wiki.freeswitch.org/wiki/Channel_Variables#variable_xxxx David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 04/05/2010 à 23:50, João Mesquita a écrit :
I think you can also use another variable on the A leg SDP to make it easier on the regex. ep_codec_string.
This will contain the parsed version of the A leg SDP and that's what I use most of the times for these tricks. Also, can you document that? :-)
Regards, João Mesquita
On Tue, May 4, 2010 at 1:52 PM, Anthony Minessale <anthony.minessale@gmail.com
wrote: you can regex the SDP for something specific and use that to set the absolute_codec_string in a standalone extension that comes first in the stack and has continue=true on it
On Tue, May 4, 2010 at 11:32 AM, Ken Fulmer <kenfulmer@icstechnologysolutions.com
wrote: Just in case others are interested, this is possible with the following parameters:
SIP Profile:
<param name="inbound-late-negotiation" value="true"/>
Dial-Plan:
<action application="set" data="inherit_codec=true"/>
The codec negotiated in Call Leg B, is forced onto Call Leg A. This is possible due to the “inbound late negotiation” parameter in the sip profile.
Hope this helps someone else.
Ken
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org ] On Behalf Of Ken Fulmer Sent: Tuesday, May 04, 2010 8:29 AM
To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] Different codecs for different devices?
This may be a far out question but here goes:
Our fax machines that are connected to ATA’s need to be g.711 on both Call Leg A and Call Leg B (in either direction).
However, our phones need to be g.711 on the internal side that faces our PBX. On the side facing our SIP provider, the calls should be transcoded to g.729. Inbound the calls to phones (not ATA’s) need to be g.729 on the inbound call leg and g.711 on the outbound call leg.
I realize we can set inbound / outbound codec preferences in single or multiple profiles and we can set the “absolute_codec_string” value for the outbound call leg.
However, I’ve yet to determine how to set the inbound call leg’s codec differently depending on the device. Is this possible?
Thanks,
Ken Fulmer
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
You are the man. Thank you for documenting those. I have a few on my list that I never seem to find the freaking time to actually do them. Regards, JM On Wed, May 5, 2010 at 11:12 AM, David Ponzone <david.ponzone@gmail.com>wrote:
Guys,
I added this variable to the wiki:
http://wiki.freeswitch.org/wiki/Channel_Variables#variable_xxxx
David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34
Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com
*Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. **IPeva** décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur.* * *
Le 04/05/2010 à 23:50, João Mesquita a écrit :
I think you can also use another variable on the A leg SDP to make it easier on the regex. ep_codec_string.
This will contain the parsed version of the A leg SDP and that's what I use most of the times for these tricks. Also, can you document that? :-)
Regards, João Mesquita
On Tue, May 4, 2010 at 1:52 PM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
you can regex the SDP for something specific and use that to set the absolute_codec_string in a standalone extension that comes first in the stack and has continue=true on it
On Tue, May 4, 2010 at 11:32 AM, Ken Fulmer < kenfulmer@icstechnologysolutions.com> wrote:
Just in case others are interested, this is possible with the following parameters:
SIP Profile:
<param name="inbound-late-negotiation" value="true"/>
Dial-Plan:
<action application="set" data="inherit_codec=true"/>
The codec negotiated in Call Leg B, is forced onto Call Leg A. This is possible due to the “inbound late negotiation” parameter in the sip profile.
Hope this helps someone else.
Ken
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Ken Fulmer *Sent:* Tuesday, May 04, 2010 8:29 AM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* [Freeswitch-users] Different codecs for different devices?
This may be a far out question but here goes:
Our fax machines that are connected to ATA’s need to be g.711 on both Call Leg A and Call Leg B (in either direction).
However, our phones need to be g.711 on the internal side that faces our PBX. On the side facing our SIP provider, the calls should be transcoded to g.729. Inbound the calls to phones (not ATA’s) need to be g.729 on the inbound call leg and g.711 on the outbound call leg.
I realize we can set inbound / outbound codec preferences in single or multiple profiles and we can set the “absolute_codec_string” value for the outbound call leg.
However, I’ve yet to determine how to set the inbound call leg’s codec differently depending on the device. Is this possible?
Thanks,
Ken Fulmer
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (4)
-
Anthony Minessale
-
David Ponzone
-
João Mesquita
-
Ken Fulmer