APAR status
Closed as program error.
Error description
If customer sends a multi-value diversion header: Diversion: First <sip:+13103429200@72.11.192.10;user=phone>; privacy=off;reason=unconditional;counter=1, second<sip:+13103429100@72. 11.192.10;user=phone>;privacy=off;reason=unconditional;counter=1 Only the first diversion header is sent on the outgoing invite and diversion_params are changed to be part of the name_address: Diversion: "First" <sip:+13103429200@72.11.192.10;reason=unconditional; counter=1;privacy=off;user=phone>
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Session Initiation Protocol (SIP) * * container IBM WebSphere Application Server * * Feature Pack for Communications Enabled * * Applications (CEA) users * **************************************************************** * PROBLEM DESCRIPTION: Headers with multiple values are * * parsed and serialized as line * * seperated headers. * **************************************************************** * RECOMMENDATION: * **************************************************************** The SIP container parses extended headers as line seperated headers by default even if you wanted to parse them as comma separated. The same issue exists in the outgoing side when you only have the ability to add line separated headers and not comma separated headers.
Problem conclusion
A new SIP container custom propery was added to control the header separation process. It affects the parsing of extension header fields, as well as the serialization of both standard and extension header fields. The default behavior is: 1. Parse all extension header fields as if they are line-separated. 2. Serialize all header fields as line separated, except for a specified set of header fields that are to be comma-separated. There is a configuration property that allows customizing separation. If set, it is processed on top of the default setting. Format: HeaderSeparation[,HeaderSeparation,...] HeaderSeparation = header[:separation] header = (either header name or *) separation = on/off/in/out (default is on) The default string is: "Accept,Accept-Encoding,Accept-Language,Allow,In-Reply-To,Proxy- Require,Require,Supported,Unsupported" During initialization, the custom string, if set, is appended on top of the default, before parsing the string. Duplicate entries are allowed, and the latter wins. If a header field name of "*" is specified, it erases all entries that come before it, and it specifies the default separation. For example, setting the custom property to "*:off,My-Header-Field:on" produces: "Accept,Accept-Encoding,Accept-Language,Allow,In-Reply-To,Proxy- Require,Require,Supported,Unsupported,*:off,My-Header-Field:on" which means all header fields are line-separated (including the default) except for My-Header-Field which is comma-separated. For setting the new SIP container custom property: 1. log in to the Websphere administrative console 2. go to Application servers > server1 > SIP container > Custom properties 3. click on the new button 4. set the following: name:comma.separated.headers value: as described above 5. click on the OK button 6. restart the SIP server The fix for this APAR is currently targeted for inclusion in fix pack 1.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM49196
Reported component name
CEA FEATUREPACK
Reported component ID
5724J0855
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-10-03
Closed date
2012-02-20
Last modified date
2012-02-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
CEA FEATUREPACK
Fixed component ID
5724J0855
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 February 2022