[OpenSER-Users] About openser redirect - forward

Valerio Di Marino valeriodimarino at gmail.com
Sat Jun 21 00:33:25 CEST 2008


2008/6/21 Iñaki Baz Castillo ibc at aliax.net:


> Ok, but next time continue the thread in the maillist ;)
>


> I'm sorry !
>


>
>
> > 2008/6/20 Iñaki Baz Castillo ibc at aliax.net:
> > > AFAIK if a UAC is redirected it will not include the already used
> > > credentials
> > > in the new request to the new destination (maybe I'm wrong).
> >
> > Do you think is possible to force using the pseudovariables ?
>
> No, it's not possible. When a UAAC receives a 302 it generates a completely
> new request with destination the URI of the "Contact" in the 302.
>
>
> > > If you need solving NAT in your OpenSer then you need to forward the
> > > request
> > > in it after make fix NAT.
> >
> > How ? Can explain better ?
>
> If a UAC receives a 302 it will generate a new INVITE. If the UAC has not
> configured your OpenSer as outbound proxy, the new INVITE it generates will
> go directly to the SIP provider, so it's not possible your OpenSer makes
> fix
> the NAT (fix "Contact" and so).
> But maybe your SIP provider makes fix the NAT by itself, or you can try
> STUN
> in your UAC's.
>
>
> > > If not you could use forwarding or redirect.
> >
> > With redirect, openser will send an address and the uer will contact the
> > new address: is it correct ? (I am not shure).
>
> Yes, OpenSer replies a 302 with the new URI in the "Contact" header.
>
>
> > > In OpenSer to get a redirection you must set the RURI ($ru = ...) and
> > > reply a
> > > 302 to the user.
> >
> > Can you send  ma a routine syntax ?
> > For example, I would redirect to sip.voipstunt.com
>
> Something like:
>
> $ru = "sip.voipstunt.com";
> send_reply("302", "Redirect to SIP provider");
> exit;
>
> I need to study much more....
Thank you, I will try and I am shure I wil need your support once again.
Valerio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kamailio.org/pipermail/users/attachments/20080621/3f69271c/attachment.htm 


More information about the Users mailing list