| < Previous by Date | Date Index | Next by Date > |
| Thread Index | Next in Thread > |
Hi, In the past, people in my company had some troubles of interoperation of reSIProcate user-agent with other systems, involving operation of session-timers. I don't have details but I am reviewing that feature in reSIProcate, so the questions below: 1. Non-compliance I observed that when a reSIProcate-based UAS receives an initial INVITE with Session-Expires and Min-SE headers it replies with a 200 OK response that contains both Session-Expires and Min-SE headers. That behaviour disagrees with RFC 4028 Sec.5 that says "The Min-SE header field MUST NOT be used in responses except for those with a 422 response code. It indicates the minimum value of the session interval that the server is willing to accept." What implications that non-compliance could have in terms of interoperability ? 2. Selectable Min-SE What is the feasibility of allowing in the DUM the selection of Min-SE the same way that today can be done with default session time ? That would allow for easier simulation and tests of interoperability between entities with non-default (90 s) Min-SE requirements. Best regards, Julio. |