Hi all!I have a short question regarding how SEMS handles SRV-records.I'm using SEMS and the auth_b2b module, which mostly works just fine. However, by using a hostname that has SRV-records (it has no A-records what so ever), I'm having trouble to authenticate correctly with the other end and I'm not sure if this is due to SEMS handling SRV-records or if I'm doing something wrong.Let's say the hostname is "gw.sip.com" and behind that there are two SRV-records pointing to addresses A "192.168.10.1" and B "192.168.20.1" and they are load shared equally.My problem is that SEMS sends out the first INVITE to A, receives a 407, injects the auth response into the INVITE but now it sends the INVITE to B. B has no clue about this call/auth and therefore responds with a 403.Calls in this setup work fine 50% of the time because SEMS picks the correct SRV-record... =) Shouldn't SEMS remember and reuse the first address it talks to when resending the INVITE?Am I doing something wrong or is this by design?Best regards,/Tobias
_______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
