Re: [reSIProcate-users] ACK being sent to the contact instead of the place it received it from
Ok, I got through this and I've worked around it by forcing record route
on repro, and it is now sending the ACK back to repro, but repro isn't
sending it to the right destination after it receives it... (e.g.
sending back to the private address that is listed in the 200 OK).
Eerily enough, it appears that even though with rport and TCP the
contact is fixed on the registrations, nothing seems to fix the contact
in on going dialogs that are created after that with DUM. I suspect
repro is reading the contact in the 200 OK instead of processing it back
through itself. In either case, if there is a way to fix both pieces so
that dum puts the right contact, and repro properly routes back the ACK,
I think this would be much better.
Dan
On 01/24/2011 12:27 AM, Dan Weber wrote:
> Hi guys,
>
> I'm trying to debug an issue where a dialog is created over TCP through
> repro or such, and the INVITE and 200 make it to the respective
> locations properly, but the ACK from the sender goes directly to the
> contact in the 200. I've even set outbound proxy settings. How do I
> make it so that the ACK gets sent back through repro?
>
> Dan
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/