PM54785: INCORRECT ENCODING WHEN 'FROM' HEADER IN THE INVITE IS OF TYPE 'TEL:' AND THE PARAMETERS ARE OUTOF <>.

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• when sending INVITE with 'From' header of type 'tel:' , without
  triangle brackets <>,
  (e.g: From: tel:123456;tag:12345)
  
  brackets <> are added, and the whole 'From' header value,
  including the 'tag' is put inside the brackets <>
  (e.g: From: <tel:123456;tag:12345>).
  
  afterwards, when the application send the INVITE out, it adds
  another 'tag' to the 'From' value
  (e.g: <tel:123456;tag:12345>;tag:334455)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All Session Initiation Protocol (SIP)       *
  *                  container users of IBM WebSphere            *
  *                  Application Server V8.0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: SIP container is not parsing tel URI    *
  *                      correctly in From header                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When parsing tel URI in From header the SIP container is
  considering the tag parameter as a URI parameter instead of
  header parameter.
  

Problem conclusion

• The SIP container is parsing tel URI correctly, From header
  parameters outside of the brackets are considered header
  parameters and not URI parameters.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.3.  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 is sysrouted FROM one or more of the following:

  PM50936

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP