Two bridged FreeSWITCH servers - both in bypass_media mode - possible?
Hi, I am trying to make 2 freeswitches (bridged) to work both in bypass media mode - currently with no luck. Would appreciate your advice. Let say I have 2 FreeSWITCH servers - one acts as PROXY (in bypass_media_after_bridge mode) and second processes media. I make a call from one sip client to another via these 2 servers (let's say G711 is used everywhere). SIP CLIENT1 -> FS1 (proxy) -> FS2 (media) -> SIP CLIENT2 Proxy server (FS1) sends a re-INVITE and excludes itself from the media path after the call was answered (I am using bypass_media_after_bridge). So, the media goes like this: SIP CLIENT1 <-> FS2 <-> SIP CLIENT2 Now, I want to try to exclude the media server (FS2) as well (just experimenting, but if both clients use same codec, I suppose this can be legitimately done?). I put bypass_media_after_bridge=true on the media server (I did it in few places in Lua script). *But as per sip trace, it does not sends any reinvite after the call was answered.* *Only FS1 sends reINVITE.* So, looks like I cannot remove FS2 from media path like this. Do you think it is not possible to acheive this kind of configuration so both servers will work in bypass media? Thank you, Vitalie
On Jun 9, 2010, at 9:36 AM, Vitalii Colosov wrote:
Hi,
I am trying to make 2 freeswitches (bridged) to work both in bypass media mode - currently with no luck. Would appreciate your advice.
Let say I have 2 FreeSWITCH servers - one acts as PROXY (in bypass_media_after_bridge mode) and second processes media.
In bypass mode or not, FreeSWITCH is never a proxy, it is always a B2BUA. Processing media or not is your only choice in regards to this.
I make a call from one sip client to another via these 2 servers (let's say G711 is used everywhere). SIP CLIENT1 -> FS1 (proxy) -> FS2 (media) -> SIP CLIENT2
Proxy server (FS1) sends a re-INVITE and excludes itself from the media path after the call was answered (I am using bypass_media_after_bridge).
So, the media goes like this: SIP CLIENT1 <-> FS2 <-> SIP CLIENT2
Now, I want to try to exclude the media server (FS2) as well (just experimenting, but if both clients use same codec, I suppose this can be legitimately done?). I put bypass_media_after_bridge=true on the media server (I did it in few places in Lua script).
But as per sip trace, it does not sends any reinvite after the call was answered. Only FS1 sends reINVITE.
There is something wrong in your script?
So, looks like I cannot remove FS2 from media path like this.
Do you think it is not possible to acheive this kind of configuration so both servers will work in bypass media?
There is nothing different here than the first box as far as your explanation goes. This should work fine, and as you showed with FS1, it does. Mike
Hi Michael, Thanks for important note. Why can't we name FreeSWITCH in Bypass Media mode as PROXY? Which thing it is missing? Regarding the script, I don't think it is incorrect. Most probably the FreeSWITCH is not able to handle such crazy scenario. Because the first reinvite occurs right after the call was answered. So when the second reinvite should happen? Right after the first re-invite? Without any delay? Or maybe it tries to execute both reinvites after the call was answered, and selects the first one? Vitalie 2010/6/14 Michael Jerris <mike@jerris.com>
On Jun 9, 2010, at 9:36 AM, Vitalii Colosov wrote:
Hi,
I am trying to make 2 freeswitches (bridged) to work both in bypass media mode - currently with no luck. Would appreciate your advice.
Let say I have 2 FreeSWITCH servers - one acts as PROXY (in bypass_media_after_bridge mode) and second processes media.
In bypass mode or not, FreeSWITCH is never a proxy, it is always a B2BUA. Processing media or not is your only choice in regards to this.
I make a call from one sip client to another via these 2 servers (let's say G711 is used everywhere). SIP CLIENT1 -> FS1 (proxy) -> FS2 (media) -> SIP CLIENT2
Proxy server (FS1) sends a re-INVITE and excludes itself from the media path after the call was answered (I am using bypass_media_after_bridge).
So, the media goes like this: SIP CLIENT1 <-> FS2 <-> SIP CLIENT2
Now, I want to try to exclude the media server (FS2) as well (just experimenting, but if both clients use same codec, I suppose this can be legitimately done?). I put bypass_media_after_bridge=true on the media server (I did it in few places in Lua script).
*But as per sip trace, it does not sends any reinvite after the call was answered.* *Only FS1 sends reINVITE.*
There is something wrong in your script?
So, looks like I cannot remove FS2 from media path like this.
Do you think it is not possible to acheive this kind of configuration so both servers will work in bypass media?
There is nothing different here than the first box as far as your explanation goes. This should work fine, and as you showed with FS1, it does.
Mike
_______________________________________________ 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
On Jun 14, 2010, at 9:05 AM, Vitalii Colosov wrote:
Hi Michael,
Thanks for important note. Why can't we name FreeSWITCH in Bypass Media mode as PROXY? Which thing it is missing?
Because when you proxy the media it goes thru your FreeSWITCH instance and when you're in bypass you don't have the media it goes direct P2P /b
Hi Brian, I did not find the mandatory requirement for the proxy server to proxy also media: http://www.ietf.org/rfc/rfc3261.txt Proxy, Proxy Server: An intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity "closer" to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it. So I am still not convinced that I cannot name FreeSWITCH in Bypass Media mode as a PROXY :-) Because it does all the things described: 1.intermediary entity 2.plays the role of routing 3.its job is to ensure that a request is sent to another entity "closer" to the targeted user Please pay attention that nothing is written about media here. Vitalie 2010/6/14 Brian West <brian@freeswitch.org>
On Jun 14, 2010, at 9:05 AM, Vitalii Colosov wrote:
Hi Michael,
Thanks for important note. Why can't we name FreeSWITCH in Bypass Media mode as PROXY? Which thing it is missing?
Because when you proxy the media it goes thru your FreeSWITCH instance and when you're in bypass you don't have the media it goes direct P2P
/b
_______________________________________________ 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 clearly overlooking that we aren't a proxy server. We are a b2bua. /b On Jun 14, 2010, at 10:06 AM, Vitalii Colosov wrote:
Hi Brian,
I did not find the mandatory requirement for the proxy server to proxy also media:
http://www.ietf.org/rfc/rfc3261.txt
Proxy, Proxy Server: An intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity "closer" to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it.
So I am still not convinced that I cannot name FreeSWITCH in Bypass Media mode as a PROXY :-) Because it does all the things described:
1.intermediary entity 2.plays the role of routing 3.its job is to ensure that a request is sent to another entity "closer" to the targeted user
Please pay attention that nothing is written about media here.
Vitalie
You still can't call this a proxy because its just passing the SDP's across so the media goes P2P. /b On Jun 14, 2010, at 10:06 AM, Vitalii Colosov wrote:
So I am still not convinced that I cannot name FreeSWITCH in Bypass Media mode as a PROXY :-) Because it does all the things described:
Vitali, You can call anything whatever you want. However, the purpose of any language is to effectively communicate meaning to others. Calling FreeSWITCH a "SIP Proxy" in SIP circles (with SIP people) will only confuse them and make you seem ignorant. When discussing SIP signaling a "proxy" looks very distinct. They basically slap on a Record-Route/Route/Via header and forward the message. FreeSWITCH builds a completely new and separate call leg with rewritten headers for each call leaving the system. This makes it a B2BUA. On Mon, Jun 14, 2010 at 11:06 AM, Vitalii Colosov <vetali100@gmail.com> wrote:
Hi Brian, I did not find the mandatory requirement for the proxy server to proxy also media: http://www.ietf.org/rfc/rfc3261.txt Proxy, Proxy Server: An intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity "closer" to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it. So I am still not convinced that I cannot name FreeSWITCH in Bypass Media mode as a PROXY :-) Because it does all the things described: 1.intermediary entity 2.plays the role of routing 3.its job is to ensure that a request is sent to another entity "closer" to the targeted user Please pay attention that nothing is written about media here. Vitalie
-- Kristian Kielhofner http://www.astlinux.org http://blog.krisk.org http://www.star2star.com http://www.submityoursip.com http://www.voalte.com
Thank you! Can I name the FreeSWITCH as a powerful B2BUA that contains all SIP Proxy functionality? Vitalie 2010/6/14 Kristian Kielhofner <kris@kriskinc.com>
Vitali,
You can call anything whatever you want. However, the purpose of any language is to effectively communicate meaning to others. Calling FreeSWITCH a "SIP Proxy" in SIP circles (with SIP people) will only confuse them and make you seem ignorant.
When discussing SIP signaling a "proxy" looks very distinct. They basically slap on a Record-Route/Route/Via header and forward the message. FreeSWITCH builds a completely new and separate call leg with rewritten headers for each call leaving the system. This makes it a B2BUA.
On Mon, Jun 14, 2010 at 11:06 AM, Vitalii Colosov <vetali100@gmail.com> wrote:
Hi Brian, I did not find the mandatory requirement for the proxy server to proxy also media: http://www.ietf.org/rfc/rfc3261.txt Proxy, Proxy Server: An intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity "closer" to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it. So I am still not convinced that I cannot name FreeSWITCH in Bypass Media mode as a PROXY :-) Because it does all the things described: 1.intermediary entity 2.plays the role of routing 3.its job is to ensure that a request is sent to another entity "closer" to the targeted user Please pay attention that nothing is written about media here. Vitalie
-- Kristian Kielhofner http://www.astlinux.org http://blog.krisk.org http://www.star2star.com http://www.submityoursip.com http://www.voalte.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
Try bypass_media=true instead. This sets the call in bypass right off the bat with no need for reinvites. On Jun 14, 2010 10:45 AM, "Vitalii Colosov" <vetali100@gmail.com> wrote: Thank you! Can I name the FreeSWITCH as a powerful B2BUA that contains all SIP Proxy functionality? Vitalie 2010/6/14 Kristian Kielhofner <kris@kriskinc.com>
Vitali,
You can call anything whatever you want. However, the purpose of any language i...
_______________________________________________ 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
No, it's a B2BUA, with an embedded RTP Proxy. FS can't be a SIP Proxy. 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 14/06/2010 à 17:39, Vitalii Colosov a écrit :
Thank you!
Can I name the FreeSWITCH as a powerful B2BUA that contains all SIP Proxy functionality?
Vitalie
2010/6/14 Kristian Kielhofner <kris@kriskinc.com> Vitali,
You can call anything whatever you want. However, the purpose of any language is to effectively communicate meaning to others. Calling FreeSWITCH a "SIP Proxy" in SIP circles (with SIP people) will only confuse them and make you seem ignorant.
When discussing SIP signaling a "proxy" looks very distinct. They basically slap on a Record-Route/Route/Via header and forward the message. FreeSWITCH builds a completely new and separate call leg with rewritten headers for each call leaving the system. This makes it a B2BUA.
On Mon, Jun 14, 2010 at 11:06 AM, Vitalii Colosov <vetali100@gmail.com> wrote:
Hi Brian, I did not find the mandatory requirement for the proxy server to proxy also media: http://www.ietf.org/rfc/rfc3261.txt Proxy, Proxy Server: An intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity "closer" to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it. So I am still not convinced that I cannot name FreeSWITCH in Bypass Media mode as a PROXY :-) Because it does all the things described: 1.intermediary entity 2.plays the role of routing 3.its job is to ensure that a request is sent to another entity "closer" to the targeted user Please pay attention that nothing is written about media here. Vitalie
-- Kristian Kielhofner http://www.astlinux.org http://blog.krisk.org http://www.star2star.com http://www.submityoursip.com http://www.voalte.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
_______________________________________________ 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
On Mon, Jun 14, 2010 at 10:24 AM, David Ponzone <david.ponzone@gmail.com>wrote:
No, it's a B2BUA, with an embedded RTP Proxy. FS can't be a SIP Proxy.
David, Well said. People hear the word "proxy" and it's easy to make assumption about exactly *what* is being proxied. So, for posterity's sake: FreeSWITCH is not, and CANNOT, be a SIP proxy. Period. No discussion, no debate. -MC
participants (7)
-
Anthony Minessale
-
Brian West
-
David Ponzone
-
Kristian Kielhofner
-
Michael Collins
-
Michael Jerris
-
Vitalii Colosov