sipservlet-spec
  1. sipservlet-spec
  2. SIPSERVLET_SPEC-7

Container provides dialog termination behavior

    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

      This is a simplification for developers, as it is not trivial to terminate a dialog correctly especially in races. Container can terminate INVITE and non-INVITE dialogs by sending the correct message sequence. Should also handle multiple dialog usages (RFC5057).

      Note some terminating SIP messages (like NOTIFY) can contain payload. So, we will need to look into the problem more deeply. Also certain non-dialog creating requests such as REGISTER or PUBLISH still have long-lived semantics so we may want to consider them too.

        Activity

        Hide
        binod added a comment -

        Please see section 8.2.5 of the specification draft.

        Show
        binod added a comment - Please see section 8.2.5 of the specification draft.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: