Raphael, On 10/07/2010 05:34 PM, Raphael Coeffic wrote:
it seems that we should wipe the session timers headers before the INVITE is passed to the other side. Could you please file a report on bugtracker.iptel.org?
There are proxies on both sides of SEMS between it and GWs A/B that I could use to strip out the header as a short-term solution, but I was not sure what unintended effects this could have.
I am more curious as to why the reinvite is being passed to the other side. A reinvite is between two endpoints (a UAC and a UAS), right? So when GW B sends a reinvite to SEMS, SEMS is the logical target of that reinvite and should respond. This event may trigger SEMS to generate a new and logically different reinvite to GW A, but it should not have any direct causal relation to the reinvite received from GW B?
Or are you passing along the reinvite as some kind of optimisation of convenience / to simplify code?
Thanks, -- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/ _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
