Like I said, it just worked for me. Fs parsed the new contact (with maddr) and re-sent the invite to the new contact. I'm on "vacation" so I won't be able to look at this but I will in the next couple of weeks if you're still having problems. -- Kristian Kielhofner http://blog.krisk.org ------------------------------ *From*: freeswitch-users-bounces@lists.freeswitch.org < freeswitch-users-bounces@lists.freeswitch.org> *To*: 'FreeSWITCH Users Help' <freeswitch-users@lists.freeswitch.org> *Sent*: Wed Aug 11 19:02:46 2010 *Subject*: Re: [Freeswitch-users] FS processing 302 I’d like Freeswitch to send a new Invite to the server IP listed in the maddr address in the 302 contact. Checking out the wiki to see what variable options are possible, ------------------------------ *From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Steven Ayre *Sent:* Wednesday, August 11, 2010 4:39 PM *To:* FreeSWITCH Users Help *Subject:* Re: [Freeswitch-users] FS processing 302 AFAIK 302 reenters the dialplan. If the destination number is unchanged, it will execute the same commands after the redirect as it did before the redirect, which would likely cause it to continously bridge, redirect, bridge, redirect.... That could explain what you're experiencing. How do you want to handle the 302? It's advisable to be careful what to do with a 302 which is why it reenters the dialplan. You can try dialing a $0.01 route but have it redirect you to a $1.00 route leaving you sending the call out on a route costing you $1.00 but charging your customer $0.01, or if you do bill them correctly leaving them with a bill of $1.00 when they expected only $0.01. It's possible to handle a 302 manually by sending them to a dialplan context specifically for it, which keeps the redirect logic away from your main dialplan. See http://wiki.freeswitch.org/wiki/Dialplan_Handling_Incoming_Redirect -Steve