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 method Where do you think it's failing? that log shows it get refer, go back to dp, invite to 3341 and then the other end hangs up at some point. On Wed, Feb 10, 2010 at 11:01 AM, Victor Maruani <vmaruani@interwise.com> wrote: Hi, Logs are on pb 12099 I hope this helps. Reproduced with revision 16599. A-side (10.10.5.19) is an x-lite registered with extension 1002 B (.5.51) refers to C (.5.48) none are registered. Please refer to previous emails for details of dialplan and what I try to do... Let me know if you need more info Thanks! From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Wednesday, February 10, 2010 4:46 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Bypass-media and REFER method update to latest trunk and reproduce your problem with full debug enabled. sofia profile internal siptrace on console loglevel debug On Wed, Feb 10, 2010 at 4:44 AM, Victor Maruani <vmaruani@interwise.com> wrote: Hi, I can't have a blind transfer work properly if I use bypass-media=true. My first message may have been unclear, here I added excerpt from the dialplan: <!--- ext MyIVR --> <extension name="Extension MyIVR" continue="false"> <condition field="destination_number" expression="^337$"> <action application="set" data="bypass_media=true"/> <action application="bridge" data="sofia/internal/337@10.10.5.51"/> </condition> </extension> <!--- ext MyServ --> <extension name="Extension MyServ " continue="false"> <condition field="destination_number" expression="^3341$"> <action application="set" data="bypass_media=true"/> <action application="bridge" data="sofia/internal/3341@10.10.5.48"/> </condition> </extension> The connection to MyIVR works. Then it sends Refer-to (3341@...) which fails as I described it in the previous mail. I would like to know if the feature has been validated and if I'm missing something in the configuration. Any help would be very appreciated. Thanks! From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Victor Maruani Sent: Sunday, February 07, 2010 5:01 PM To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] Bypass-media and REFER method Hi, I'm trying to do a POC using FS, the goal is to have FS handle REFERs containing proprietary data. I want to have some logic on top of FS and also use the fail over mechanism. in short, I have something like this: (third party) A side --- FS ---- B side (IVR server) the IVR the sends a REFER to FS. I don't want A to deal with it. now say B refers to C, it would be considered as a "group" C1, C2 ... to which I want FS to failover. only when one has answered should A be updated (REINVITE) and B notified and disconnected. if all fails I would expect B to be notified of the failure and proceed as I wish without "losing" A. from what I've read FS should be OK for the job but I have a couple issues: 1 ) I have some issues getting FS handle a REFER while in bypass-media mode. (I tried with the release and some revisions including latest) first when I bridge A and B everything is fine and media is bypassed. When B sends REFER to C: - FS immediately NOTIFY B of success and send a reinvite to A with SDP containing its own media IP/port. - then it does INVITE C with A's SDP. - B gets disconnected. A is not updated with C's sdp. so at this point A sends RTP to FS and C sends RTP to A. ... I basically have one extension for B: (set bypass-media and bridge to B) and another extension to C which does the same actions. what do you think I do wrong? 2 ) how can I catch the REFER and set variables from it? (like ref-by or ref-to) in the dial plan I do catch the INVITE sent to C, but how to do it with the REFER itself? thanks for your help! Best Regards, Victor. _______________________________________________ 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 <mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com <mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <mailto:sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org <mailto: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 -- 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 <mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com <mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <mailto:sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org <mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900