----- Original message ----- > On 10/08/2010 08:28 AM, Raphael Coeffic wrote: > > > Ok, so do we consider that this should be fixed by some SIP proxy on > > the way between SEMS and Asterisk? I would prefer that solution rather > > than implementing a solution for a bug which is fixed by now. > > Sure, unless you think that there is some other, more abstract reason, > rooted in SEMS' role as the SST facilitator, that compels the deletion > of timer-related headers from an endpoint in this scenario.
As with the SST headers, I think "Supported" and "Require" are headers for which the semantics touch the role of the intermediate (sems) and thus should be properly set - e.g. if on one side timer is required, it doesn't necessarily need to be required on the other side, and it also should be Supported on both sides. So even if that specific interop problem is related to a bug in *, I would say that Supported/Require handling for relayed requests should be improved in sems' B2B. Stefan > > -- > 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
_______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
