Thomas, The UAS at 10.30.9.11 has failed to process the two Record-Route headers sent in the INVITE. It should send the Route Set back as part of the Response - i.e. within the 200 OK. But it hasn't. It has just absorbed the Record-Route headers and ignored them. I would say that is faulty UAS behaviour, but maybe Bogdan could confirm.
Consequently, the ACK has no Route headers. That means OpenSIPS is treated as the final destination - it doesn't know that it is meant to relay the ACK to 10.30.9.11 If you can't fix the UAS, you could try using the Topology hiding module in OpenSIPS. That would probably overcome the problem because Topology hiding doesn't send Record-Route headers downstream. John Quick Smartvox Limited Web: www.smartvox.co.uk _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
