Hi Will,
the 200 OK retransmission is done by the end client (UAS) and not by the
proxy. Check if the ACK actually gets to the UAS. Maybe the change of
DNS server changes the routing...
regards,
bogdan
Will Quan wrote:
I have a primary and secondary dns server setup in
resolv.conf, with a
timeout option of 1 second.
The idea is when the primary fails, my secondary server picks up the
workload.
When openser is running, and primary dns is down, I am seeing several
re-transmissions of 200 OK (invite) to my originator *after* openser
has finished processing ACK. I was thinking the final responses would
stop reTX after the ACK was t_relayed.
Have you seen such behavior? And better yet- Is there a solution for this?
Thanks, Will
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users