sipservlet-spec
  1. sipservlet-spec
  2. SIPSERVLET_SPEC-25

Clarification on how to handle Replaces in JSR 289

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-pr
    • Labels:
      None

      Description

      RFC 3891 states this when an INVITE is received with a Replaces header: "If no match is found, the UAS rejects the INVITE and returns a 481 Call/Transaction Does Not Exist response. likewise, if the Replaces header field matches a dialog which was not created with an INVITE, the UAS MUST reject the request with a 481 response. "

      JSR 289 states that:
      "1) If a container supporting [RFC 3911] or [RFC 3891] receives an initial INVITE request with Join or Replaces header, the container must first ensure that the request passes the RFC-defined validation rules."

      JSR 289 also states that:
      "If no SipSession matching the tuple is found, the container MUST pass the request to the Application Router as an untargeted request, i.e., where the SipTargetedRequestInfo argument to getNextApplication() is null."

      This is a contradiction between the RFC and the JSR. So its not clear if the SIP container needs to override the validation rules of the RFC. If the request is routed to a UAS application, and there is no match, is it the applications responsibility to respond with a 481?

        Activity

          People

          • Assignee:
            binod
            Reporter:
            bpulito
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: