Brian,

Thanks for the info.  I guess I'll go read section 19.1 of RFC3261 again.  I do think the above has a valid host portion (I don't think the port is required).

I'm not so sure that putting params in the user portion of the uri is valid (from the RFC it states sip:user:password@host:port;uri-parameters?headers).

The issue is that in the real world this is done all the time .... SIP is fantastic :)

Shelby


On Thu, Oct 1, 2009 at 9:42 AM, Brian West <brian@freeswitch.org> wrote:

On Oct 1, 2009, at 9:27 AM, Shelby Ramsey wrote:

<action application="redirect" data="sip:${destination_number};rn=${rn};npdi=yes@${network_addr}"/>

This will produce an INVALID sip uri... You can not feed this to sofia it'll get PISSED. 

Its missing the host portion.


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.

Any help would be greatly appreciated.

Shelby

PS ... hats off to the author of mod_memcache ... that is extremely useful!


_______________________________________________
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