RE: [reSIProcate] 302 Invite Handling
Are you using DUM? Dum already contains a Redirect Manager. You might
want to have a look at RedirectManager.cxx. Although if you have an
outbound proxy configured - all requests will still go through that
proxy and the outbound proxy should direct the request to the maddr -
which should now be on the Request line.
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Shraddha
> Sent: Wednesday, March 22, 2006 2:08 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] 302 Invite Handling
>
> Hi,
>
> I am adding 302 INVITE handling support to resiprocate.
>
> In my case,
> Resiprocate is set to use outbound proxy.
>
> When resiprocate receives "302 Moved Temporarily" in response to
> INVITE request,all the requests(RE-INVITE,ACK,BYE) for that session
should
> go the IP
> address specified as "maddr" parameter in 302 response Contact header.
> Though all REGISTER and initial requests including INVITE should go to
> outbound proxy.
>
> Can anyone suggest, what would be the minimum changes required
> to implement this?
>
> Regards,
> Shraddha
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel