Details

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

      Description

      We would like to explore providing APIs for making common modifications to headers that are currently defined as system headers. Exmaples include:

      1) No way to change outgoing message's record-route. For instance to add a parameter needed by a downstream device.
      2) JSR 289 states that display name in Contact Header can not be modified. There is no good reason to enforce this restriction and most app developers want control over the display name.
      3) In general there is no way to add parameters to system headers which is very common.

        Activity

        bpulito created issue -
        binod made changes -
        Field Original Value New Value
        Assignee nitzann [ nitzann ]
        Hide
        nitzann added a comment -

        We suggest modifying section 6.4.2 System Headers with a looser restriction like this:
        "
        1. The Call-ID and CSeq headers cannot be modified by the application
        2. The Via header can only be modified by adding or removing non-protected parameters
        3. An Address system header can be modified by the application (as long as the modification generates a valid SIP header) in all of its parts except for:
        a. The host/port and scheme part in the Address URI. This restriction does not apply to the To and From headers.
        b. Protected parameters and their value.

        The protected parameters defined by this spec are: method, ttl, maddr, transport, user, branch, received, tag
        These are protected when used either as URI or as Header parameters
        "

        The JSR section about Contact and To/From headers is still relevant, but would need to be modified accordingly. The later clarifications about parameters in Record-Route in section 12.4, and for Path in 12.5, will not be necessary.
        This will also make it clear that a display-name part can be modified in all headers.

        Show
        nitzann added a comment - We suggest modifying section 6.4.2 System Headers with a looser restriction like this: " 1. The Call-ID and CSeq headers cannot be modified by the application 2. The Via header can only be modified by adding or removing non-protected parameters 3. An Address system header can be modified by the application (as long as the modification generates a valid SIP header) in all of its parts except for: a. The host/port and scheme part in the Address URI. This restriction does not apply to the To and From headers. b. Protected parameters and their value. The protected parameters defined by this spec are: method, ttl, maddr, transport, user, branch, received, tag These are protected when used either as URI or as Header parameters " The JSR section about Contact and To/From headers is still relevant, but would need to be modified accordingly. The later clarifications about parameters in Record-Route in section 12.4, and for Path in 12.5, will not be necessary. This will also make it clear that a display-name part can be modified in all headers.
        Hide
        binod added a comment -

        The changes are now part of 0.8 version distributed.

        Show
        binod added a comment - The changes are now part of 0.8 version distributed.
        binod made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 2.0 [ 16851 ]
        Resolution Fixed [ 1 ]
        binod made changes -
        Fix Version/s 2.0-pr [ 16895 ]
        Fix Version/s 2.0 [ 16851 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved: