you left too fast.<br><br>1) I told you if you put <> around the sip uri it will work.<br>2) I told you I added a patch in tree to add one for you if it's not supplied so update to trunk.<br><br><br><div class="gmail_quote">
On Thu, Oct 1, 2009 at 9:27 AM, Shelby Ramsey <span dir="ltr"><<a href="mailto:sicfslist@gmail.com">sicfslist@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello:<br><br>I asked this on IRC yesterday and I think I confused everyone involved. So I apologize in advance here for reposting the question and if I wasted anyone's time.<br><br>So here is the issue I'm having. I'm trying to use FS as a redirect server (specifically to serve up LNP queries via 302 redirects). But I'm having an issue where based on the string in the dialplan FS will respond with a 500 internal error message instead of a 300 redirect. <br>
<br>The call flow should be this:<br> -- remote party sends an Invite to my FS instance<br> -- FS should respond with a 302<br><br>The following works as expected (FS will send a 302 when it receives an Invite):<br><br>
<action application="redirect" data="sip:${destination_number}@${network_addr};rn=${rn};npdi=yes"/><br><br>However if I do this (which is the way the response should look) FS will respond with a 500 internal server error:<br>
<br><action application="redirect" data="sip:${destination_number};rn=${rn};npdi=yes@${network_addr}"/><br><br>So the issue is the placement of the user params .... if they are before the @ FS will send a 500 internal server error ... if they are after the @ FS will send a 302. Unfortunately placing the user params after the @ doesn't quite conform to the way other devices expect to receive the 302 for this application.<br>
<br>Any help would be greatly appreciated.<br><font color="#888888"><br>Shelby<br></font><br>PS ... hats off to the author of mod_memcache ... that is extremely useful!<br><br><br>
<br>_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>