Hello, I have a couple of FreeSWITCH boxes functioning as SBCs on our network. We need them to: - Route Calls - Function as B2BUAs for call logging - Hide topology from the endpoints They do not need to: - Intercept/play audio - Manipulate the SDP - Transcode - Process anything other than SIP So these machines have been running with Proxy Media enabled in the dialplan. Is the the proper/recommended way of configuring for our environment/needs? Is the minimal gain of resources by not processing the RTP worth it? Thanks, Max
If your intention is to *strictly* hide topology proxy media will rewrite the IP address in the SDP but that's about it. Technically that counts as "topology hiding". Other SDP parameters, however, will pass through and leak various bits of information about the endpoints behind the SBC: - Codec support - Payload types - Other "random" various SDP parameters Most real SBCs will rewrite the entire SDP (as FS does by default). Another thing to consider - the vast majority of FS users do not use proxy media (and most that do use it incorrectly). This leaves you open to the possibility that you'll experience strange edge case bugs using a media mode different from the majority of the rest of the FS user base. On Wed, Mar 9, 2011 at 10:52 AM, Max Clark <max.clark@gmail.com> wrote:
Hello,
I have a couple of FreeSWITCH boxes functioning as SBCs on our network. We need them to:
- Route Calls - Function as B2BUAs for call logging - Hide topology from the endpoints
They do not need to:
- Intercept/play audio - Manipulate the SDP - Transcode - Process anything other than SIP
So these machines have been running with Proxy Media enabled in the dialplan. Is the the proper/recommended way of configuring for our environment/needs? Is the minimal gain of resources by not processing the RTP worth it?
Thanks, Max
-- Kristian Kielhofner
Yes, you probably don't need "media proxy", just the "default" to hide the remote IP. See: http://wiki.freeswitch.org/wiki/Proxy_Media <http://wiki.freeswitch.org/wiki/Proxy_Media>-Avi On Wed, Mar 9, 2011 at 7:02 PM, Kristian Kielhofner <kris@kriskinc.com>wrote:
If your intention is to *strictly* hide topology proxy media will rewrite the IP address in the SDP but that's about it. Technically that counts as "topology hiding". Other SDP parameters, however, will pass through and leak various bits of information about the endpoints behind the SBC:
- Codec support - Payload types - Other "random" various SDP parameters
Most real SBCs will rewrite the entire SDP (as FS does by default).
Another thing to consider - the vast majority of FS users do not use proxy media (and most that do use it incorrectly). This leaves you open to the possibility that you'll experience strange edge case bugs using a media mode different from the majority of the rest of the FS user base.
On Wed, Mar 9, 2011 at 10:52 AM, Max Clark <max.clark@gmail.com> wrote:
Hello,
I have a couple of FreeSWITCH boxes functioning as SBCs on our network. We need them to:
- Route Calls - Function as B2BUAs for call logging - Hide topology from the endpoints
They do not need to:
- Intercept/play audio - Manipulate the SDP - Transcode - Process anything other than SIP
So these machines have been running with Proxy Media enabled in the dialplan. Is the the proper/recommended way of configuring for our environment/needs? Is the minimal gain of resources by not processing the RTP worth it?
Thanks, Max
-- Kristian Kielhofner
_______________________________________________ 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
Avi Marcus-2 wrote:
Yes, you probably don't need "media proxy", just the "default" to hide the remote IP. See: http://wiki.freeswitch.org/wiki/Proxy_Media I took a look at the above link in the section on http://wiki.freeswitch.org/wiki/Proxy_Media#How_to_enable_it How to enable it which states to set proxy_media=true before the bridge. When I take a look at the conf/dialplan/public/00_inbound_did.xml file, there is no bridge except transfer as the application. So, will proxy media work on transfer?
----- FreeSWITCH hosted on a Seagate DockStar with OpenWRT. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/To-Proxy-Media-or-Not-tp615419... Sent from the freeswitch-users mailing list archive at Nabble.com.
The transfer application doesn't do a bridge and doesn't create any other legs, it just moves the call processing to another point in the dialplan. Think of it as a GoTo (albeit one that can change the destination_number). As such proxy_media doesn't apply. That set, once channel variables are set the variable remains set, even after a transfer. So you can set proxy_media=true, transfer to another extension, bridge in that extension and proxy media will be enabled for that bridge because proxy_media is still true after the transfer. -Steve On 9 March 2011 17:48, mazilo <Nabble@slickdeals.endjunk.com> wrote:
Avi Marcus-2 wrote:
Yes, you probably don't need "media proxy", just the "default" to hide the remote IP. See: http://wiki.freeswitch.org/wiki/Proxy_Media I took a look at the above link in the section on http://wiki.freeswitch.org/wiki/Proxy_Media#How_to_enable_it How to enable it which states to set proxy_media=true before the bridge. When I take a look at the conf/dialplan/public/00_inbound_did.xml file, there is no bridge except transfer as the application. So, will proxy media work on transfer?
----- FreeSWITCH hosted on a Seagate DockStar with OpenWRT. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/To-Proxy-Media-or-Not-tp615419... Sent from the freeswitch-users mailing list archive at Nabble.com.
_______________________________________________ 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
Advantages of Proxy Media: 1) Support codecs not natively supported by FreeSWITCH 2) Lower CPU resources on FreeSWITCH So for 1) I'm really only concerned with t38/fax over g711. With our current configuration faxing (although unsupported) is working just fine. What should I expect if I revert to media mode? 2) If I disable transcoding, what kind of difference in resource utilization should I expect? Nominal (less than 10%), Moderate (11-30%), or more? Thanks, Max On Wed, Mar 9, 2011 at 9:02 AM, Kristian Kielhofner <kris@kriskinc.com> wrote:
If your intention is to *strictly* hide topology proxy media will rewrite the IP address in the SDP but that's about it. Technically that counts as "topology hiding". Other SDP parameters, however, will pass through and leak various bits of information about the endpoints behind the SBC:
- Codec support - Payload types - Other "random" various SDP parameters
Most real SBCs will rewrite the entire SDP (as FS does by default).
Another thing to consider - the vast majority of FS users do not use proxy media (and most that do use it incorrectly). This leaves you open to the possibility that you'll experience strange edge case bugs using a media mode different from the majority of the rest of the FS user base.
On Wed, Mar 9, 2011 at 10:52 AM, Max Clark <max.clark@gmail.com> wrote:
Hello,
I have a couple of FreeSWITCH boxes functioning as SBCs on our network. We need them to:
- Route Calls - Function as B2BUAs for call logging - Hide topology from the endpoints
They do not need to:
- Intercept/play audio - Manipulate the SDP - Transcode - Process anything other than SIP
So these machines have been running with Proxy Media enabled in the dialplan. Is the the proper/recommended way of configuring for our environment/needs? Is the minimal gain of resources by not processing the RTP worth it?
Thanks, Max
-- Kristian Kielhofner
"Nominal (less than 10%), Moderate (11-30%), or more?" I think it's far less than even that 10%. -Steve On 9 March 2011 17:13, Max Clark <max.clark@gmail.com> wrote:
Advantages of Proxy Media:
1) Support codecs not natively supported by FreeSWITCH 2) Lower CPU resources on FreeSWITCH
So for 1) I'm really only concerned with t38/fax over g711. With our current configuration faxing (although unsupported) is working just fine. What should I expect if I revert to media mode?
2) If I disable transcoding, what kind of difference in resource utilization should I expect? Nominal (less than 10%), Moderate (11-30%), or more?
Thanks, Max
On Wed, Mar 9, 2011 at 9:02 AM, Kristian Kielhofner <kris@kriskinc.com> wrote:
If your intention is to *strictly* hide topology proxy media will rewrite the IP address in the SDP but that's about it. Technically that counts as "topology hiding". Other SDP parameters, however, will pass through and leak various bits of information about the endpoints behind the SBC:
- Codec support - Payload types - Other "random" various SDP parameters
Most real SBCs will rewrite the entire SDP (as FS does by default).
Another thing to consider - the vast majority of FS users do not use proxy media (and most that do use it incorrectly). This leaves you open to the possibility that you'll experience strange edge case bugs using a media mode different from the majority of the rest of the FS user base.
On Wed, Mar 9, 2011 at 10:52 AM, Max Clark <max.clark@gmail.com> wrote:
Hello,
I have a couple of FreeSWITCH boxes functioning as SBCs on our network. We need them to:
- Route Calls - Function as B2BUAs for call logging - Hide topology from the endpoints
They do not need to:
- Intercept/play audio - Manipulate the SDP - Transcode - Process anything other than SIP
So these machines have been running with Proxy Media enabled in the dialplan. Is the the proper/recommended way of configuring for our environment/needs? Is the minimal gain of resources by not processing the RTP worth it?
Thanks, Max
-- Kristian Kielhofner
_______________________________________________ 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
Fax over g711 (if it's going to work at all) should not be affected by proxy media or default media handling as long as you allow PCMU/PCMA when using the default media handling. However, T38 and fax over 711 are completely different. Using T38 through FreeSWITCH with the default media handling will require some extra configuration (nothing drastic). No one said anything about transcoding... Proxy media mode does not have the ability to transcode at all as FreeSWITCH is completely unaware what codec you are using (internally it actually reports "proxy" as the codec). Just because you're using default media mode DOES NOT mean you will be transcoding. Using some Sofia params and late-negotiation dialplan logic you can have an incredible amount of control over what codecs your end points are using. As long as they agree on at least one codec and codec parameters you are the one who decides which codecs take precedence and whether or not you'll be transcoding. On Wed, Mar 9, 2011 at 12:13 PM, Max Clark <max.clark@gmail.com> wrote:
Advantages of Proxy Media:
1) Support codecs not natively supported by FreeSWITCH 2) Lower CPU resources on FreeSWITCH
So for 1) I'm really only concerned with t38/fax over g711. With our current configuration faxing (although unsupported) is working just fine. What should I expect if I revert to media mode?
2) If I disable transcoding, what kind of difference in resource utilization should I expect? Nominal (less than 10%), Moderate (11-30%), or more?
Thanks, Max
-- Kristian Kielhofner
So this is an interesting side effect of removing proxy_media=true from the dialplan: 2011-03-09 19:17:31.055236 [ERR] mod_g729.c:145 This codec is only usable in passthrough mode! 2011-03-09 19:17:31.055236 [ERR] switch_core_io.c:897 Codec G.729 decoder error! Am I reading this correctly that FreeSWITCH attempted to transcode a G.729 audio stream? On Wed, Mar 9, 2011 at 11:07 AM, Kristian Kielhofner <kris@kriskinc.com> wrote:
Fax over g711 (if it's going to work at all) should not be affected by proxy media or default media handling as long as you allow PCMU/PCMA when using the default media handling. However, T38 and fax over 711 are completely different. Using T38 through FreeSWITCH with the default media handling will require some extra configuration (nothing drastic).
No one said anything about transcoding... Proxy media mode does not have the ability to transcode at all as FreeSWITCH is completely unaware what codec you are using (internally it actually reports "proxy" as the codec).
Just because you're using default media mode DOES NOT mean you will be transcoding. Using some Sofia params and late-negotiation dialplan logic you can have an incredible amount of control over what codecs your end points are using. As long as they agree on at least one codec and codec parameters you are the one who decides which codecs take precedence and whether or not you'll be transcoding.
On Wed, Mar 9, 2011 at 12:13 PM, Max Clark <max.clark@gmail.com> wrote:
Advantages of Proxy Media:
1) Support codecs not natively supported by FreeSWITCH 2) Lower CPU resources on FreeSWITCH
So for 1) I'm really only concerned with t38/fax over g711. With our current configuration faxing (although unsupported) is working just fine. What should I expect if I revert to media mode?
2) If I disable transcoding, what kind of difference in resource utilization should I expect? Nominal (less than 10%), Moderate (11-30%), or more?
Thanks, Max
-- Kristian Kielhofner
It appears so. What are your codec settings on the profile(s)? Do you have late negotiation enabled? If so, what does your dialplan look like? What are the SDP offers of each of your endpoints? On Wed, Mar 9, 2011 at 2:21 PM, Max Clark <max.clark@gmail.com> wrote:
So this is an interesting side effect of removing proxy_media=true from the dialplan:
2011-03-09 19:17:31.055236 [ERR] mod_g729.c:145 This codec is only usable in passthrough mode! 2011-03-09 19:17:31.055236 [ERR] switch_core_io.c:897 Codec G.729 decoder error!
Am I reading this correctly that FreeSWITCH attempted to transcode a G.729 audio stream?
-- Kristian Kielhofner
Yes. You said you have PCMU and G729 enabled? Is that both inbound and outbound? If so, it means that either your caller negotiated PCMU with FS, then FS offers PCMU+G729 to the callee and they pick G729, or visa versa. That's because FS will offer all the enabled codecs on the bleg. That leaves the choice up to the callee on what they use and it might not be the same as the aleg. That's only a problem with passthrough codecs such as G729, or if you want to avoid transcoding because of CPU. The way around it is to set either disable-transcoding or late-negotiation parameters on the SIP profile. disable-transcoding will only offer on the bleg the codec which has already been negotiated for the aleg. late-negotiation approaches it from the other end - it doesn't pick an aleg codec straight away but instead offers all the choices to the bleg and then uses for the aleg what the bleg selected. -Steve On 9 March 2011 19:21, Max Clark <max.clark@gmail.com> wrote:
So this is an interesting side effect of removing proxy_media=true from the dialplan:
2011-03-09 19:17:31.055236 [ERR] mod_g729.c:145 This codec is only usable in passthrough mode! 2011-03-09 19:17:31.055236 [ERR] switch_core_io.c:897 Codec G.729 decoder error!
Am I reading this correctly that FreeSWITCH attempted to transcode a G.729 audio stream?
On Wed, Mar 9, 2011 at 11:07 AM, Kristian Kielhofner <kris@kriskinc.com> wrote:
Fax over g711 (if it's going to work at all) should not be affected by proxy media or default media handling as long as you allow PCMU/PCMA when using the default media handling. However, T38 and fax over 711 are completely different. Using T38 through FreeSWITCH with the default media handling will require some extra configuration (nothing drastic).
No one said anything about transcoding... Proxy media mode does not have the ability to transcode at all as FreeSWITCH is completely unaware what codec you are using (internally it actually reports "proxy" as the codec).
Just because you're using default media mode DOES NOT mean you will be transcoding. Using some Sofia params and late-negotiation dialplan logic you can have an incredible amount of control over what codecs your end points are using. As long as they agree on at least one codec and codec parameters you are the one who decides which codecs take precedence and whether or not you'll be transcoding.
On Wed, Mar 9, 2011 at 12:13 PM, Max Clark <max.clark@gmail.com> wrote:
Advantages of Proxy Media:
1) Support codecs not natively supported by FreeSWITCH 2) Lower CPU resources on FreeSWITCH
So for 1) I'm really only concerned with t38/fax over g711. With our current configuration faxing (although unsupported) is working just fine. What should I expect if I revert to media mode?
2) If I disable transcoding, what kind of difference in resource utilization should I expect? Nominal (less than 10%), Moderate (11-30%), or more?
Thanks, Max
-- Kristian Kielhofner
_______________________________________________ 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 (5)
-
Avi Marcus
-
Kristian Kielhofner
-
Max Clark
-
mazilo
-
Steven Ayre