Re: [Freeswitch-users] Bypass-media and REFER method
We don't support the series of 100,180,200 in the notifies that is typically a pure sip pbx feature. We are a b2b and protocol agnostic softswitch. When you do refer to a sofia leg you are talking to that leg independantly. We do not track the progress of what the channel does once you transfer it, instead we send the channel back to the dialplan and accept the refer. This operation if sucessful will generate 202. The resume media on hold and bypass after att xfer sofia options or bypass_media_after_bridge var may be what you need if you want no media on fs. We have to make some sacrifices on sip madness to gain some general flexibility and call volume. =/ On Feb 14, 2010 3:39 AM, "Victor Maruani" <vmaruani@interwise.com> wrote: Hi, I would say it fails in 2 points: First in the fact that a "NOTIFY 200 OK" (line 1070) is sent right after FS gets the REFER. Then in the REINVITE (line 1094) sent to A (10.10.5.19) just after this NOTIFY, This REINVITE contains the SDP of the FS (10.10.5.92) causing the A side to send media to FS. There will be no REINVITE with SDP of C (10.10.5.48) But as you say, just afterwards, the REFER action is actually done and C is invited by FS with the SDP of A. Conclusion : 1) B is notified of success just after it sent the REFER and is disconnected. B may be notified of every step of the connection to C (100 trying… 200 OK) when these actually happen. What if C is down? Can't FS notify a failure? (didn't test that.) 2) 'A' gets to send media to FS Because of a REINVITE which disconnect him from B (we are in bypass media mode) . during the process of REFER, A should be still connected to B from a media perspective. The REINVITE is not done at the right time with the right params. Here, a pseudo bridge (on way voice) is established when C gets the INVITE and is sending media to A. A can hear C but C can't hear A after the REFER. If C was down, A would be "lost" in FS… I believe the correct behavior would be: B sends REFER. FS INVITE C C replies 100, 180… 200 and FS notifies B in accordance. Once C has sent 200 OK with its SDP. B is disconnected and A is updated (REINVITE) with C's SDP. Please share your thoughts, I still don't know if it's a bug or if I configured something wrong although I don't think so. Hasn't anyone done that before? Thank you. *From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Anthony Minessale *Sent:* Friday, February 12, 2010 1:02 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Bypass-media and REFER me... Where do you think it's failing? that log shows it get refer, go back to dp, invite to 3341 and... _______________________________________________ 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
Hi, I understand your point and the reason I want to bypass media has a lot to do with load/call volume. I don't mind the notify series being implemented or not, the notify OK is enough if it succeeded indeed. I think the issue here is the order of action. Instead of making a long speech and lose my point allow me to put it like this: What I see today is: a- REFER is received b- FS immediately sends 202 accepted ----- ok c- FS sends NOTIFY OK to B ---- wrong (not true yet) d- FS sends reINVITE to A ------ wrong (why not after FS gets C's sdp) e- B is disconnected ------- wrong (same as above , and if C is down I lose the caller) f- FS INVITE C ------ ok Without getting in sip madness, I would change the order to a,b, F , c,d,e This way only do I have the sofia leg talking to the B-leg independently during the REFER in my view. What do you think? In the meantime I'll try playing with the config but so far I don't have it work. Thanks, Regards, Victor. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Sunday, February 14, 2010 4:54 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Bypass-media and REFER method We don't support the series of 100,180,200 in the notifies that is typically a pure sip pbx feature. We are a b2b and protocol agnostic softswitch. When you do refer to a sofia leg you are talking to that leg independantly. We do not track the progress of what the channel does once you transfer it, instead we send the channel back to the dialplan and accept the refer. This operation if sucessful will generate 202. The resume media on hold and bypass after att xfer sofia options or bypass_media_after_bridge var may be what you need if you want no media on fs. We have to make some sacrifices on sip madness to gain some general flexibility and call volume. =/ On Feb 14, 2010 3:39 AM, "Victor Maruani" <vmaruani@interwise.com> wrote: Hi, I would say it fails in 2 points: First in the fact that a "NOTIFY 200 OK" (line 1070) is sent right after FS gets the REFER. Then in the REINVITE (line 1094) sent to A (10.10.5.19) just after this NOTIFY, This REINVITE contains the SDP of the FS (10.10.5.92) causing the A side to send media to FS. There will be no REINVITE with SDP of C (10.10.5.48) But as you say, just afterwards, the REFER action is actually done and C is invited by FS with the SDP of A. Conclusion : 1) B is notified of success just after it sent the REFER and is disconnected. B may be notified of every step of the connection to C (100 trying... 200 OK) when these actually happen. What if C is down? Can't FS notify a failure? (didn't test that.) 2) 'A' gets to send media to FS Because of a REINVITE which disconnect him from B (we are in bypass media mode) . during the process of REFER, A should be still connected to B from a media perspective. The REINVITE is not done at the right time with the right params. Here, a pseudo bridge (on way voice) is established when C gets the INVITE and is sending media to A. A can hear C but C can't hear A after the REFER. If C was down, A would be "lost" in FS... I believe the correct behavior would be: B sends REFER. FS INVITE C C replies 100, 180... 200 and FS notifies B in accordance. Once C has sent 200 OK with its SDP. B is disconnected and A is updated (REINVITE) with C's SDP. Please share your thoughts, I still don't know if it's a bug or if I configured something wrong although I don't think so. Hasn't anyone done that before? Thank you. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Friday, February 12, 2010 1:02 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Bypass-media and REFER me... Where do you think it's failing? that log shows it get refer, go back to dp, invite to 3341 and... _______________________________________________ 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 (2)
-
Anthony Minessale
-
Victor Maruani