But bear in mind that the client might not follow the 302. FreeSWITCH for example either terminates the call on 302 or returns to the dialplan so you can validate the new destination, so that you don't (as an example) have someone redirecting you to a premium rate number without the caller's knowledge.


On 11 January 2016 at 13:59, Michael Jerris <mike@jerris.com> wrote:
redirect using full sip uri should do a 302


On Monday, January 11, 2016, ik <idokan@gmail.com> wrote:
Hello,

I have an incoming call that on some occurrences, instead of answering it, I need to "move" the call to a different Freeswitch server.

I have tried to use deflect, and redirect, however the call with deflect just hangup immediately, and with redirect, it arrive to timeout and then hangup.
I'ved noticed at the wiki page (confluence) that the call must be answered with deflect.

Only when I use bridge, the other Freeswitch see's the SIP request and handle the call properly, but as a statful request.


How can I make the original Freeswitch out of the routing or at least make it stateless redirect (302) instead of stateful one?

Thanks,
Ido

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.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