Re: [repro-devel] ACK uses wrong interface?

[Byron Campen <bcampen@xxxxxxxxxxxx>]

Not sure what's going on with the ACK, but do keep in mind that the next hop for the ACK can very easily be different from the next hop for the INVITE. The stack will send stuff on whatever interface the routing tables tell it to; if the next hop for the ACK is different from the next hop for the INVITE, the routing tables might cause it to be forwarded from a different interface than the INVITE was.

If you can send some debug logging, I can try to pinpoint the precise reason your ACK is being sent on the interface it is.

In addition, repro does use DUM to handle registrations, so there is more to it than ContactInstanceRecord.

Best regards,

Byron Campen

Hi,

I just updated my proxy to use the latest code and now my ACK is being sent out using the wrong interface. I want the ACK to be sent out using the same interface it was received on. This works correctly in the INVITE - but not in the ACK, for the ACK it uses the primary interface of the machine. 

 

Any pointers would be appreciated.

 

(Also a small comment, the class ContactInstanceRecord is used by repro - but is part of dum, since repro as a proxy doesn't require dum for anything else, really this class should be part of the stack).

 

Thanks,

Brocha

 

 

 

 

_______________________________________________

repro-devel mailing list

repro-devel@xxxxxxxxxxxxxxx

https://list.resiprocate.org/mailman/listinfo/repro-devel