On Fri, Jul 10, 2009 at 8:42 PM, Alex Balashov<[email protected]> wrote: > Victor Pascual Avila wrote: >> >> On Fri, Jul 10, 2009 at 8:12 PM, Alex Balashov<[email protected]> >> wrote: >>> >>> Yes, you can. >>> >>> Just beware that you will _have_ to use something like 302s. If you >>> send the INVITE request back to the switch, it will be considered a >>> call loop. >> >> Unless you added ;npdi or ;rn parameters to the RURI > > I am not sure how adding those parameters would circumvent the fundamental > problem. > > Softswitch --> call leg 1 --> proxy --> still call leg 1 --> softswitch
The idea was not creating a loop but an spiral instead. In such scenario, one could be using the following routing options (I don't really know whether they are all implementable using opensips or not): - Direct routing: get invite, npdb dip, route the invite based on the result (npdi, rn). - Redirect routing: get invite, npdb dip, send back 302 (npdi, rn) - Route updated invite back (spiral): get invite, npdb dip, send back the updated invite (npdi, rn). Cheers, -- Victor Pascual Ávila _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
