[JIRA] Commented: (SIPSERVLET_SPEC-20) System header modification changes
- From: "nitzann (JIRA)" <
- Subject: [JIRA] Commented: (SIPSERVLET_SPEC-20) System header modification changes
- Date: Thu, 6 Feb 2014 15:30:49 +0000 (UTC)
- Auto-submitted: auto-generated
nitzann commented on SIPSERVLET_SPEC-20:
We suggest modifying section 6.4.2 System Headers with a looser restriction
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
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
This will also make it clear that a display-name part can be modified in all
> System header modification changes
> Key: SIPSERVLET_SPEC-20
> URL: https://java.net/jira/browse/SIPSERVLET_SPEC-20
> Project: sipservlet-spec
> Issue Type: Improvement
> Reporter: bpulito
> Assignee: nitzann
> 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.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira