IBM Support

PM61816: SIP CONTAINER PROCESSING % IN TO TAG AS ESCAPE CHARACTER

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Product Version:WAS ND 7.0.0.5
    OS and Additional Information: Sun Solaris
    JDK 1.6
    Problem Description:
    
    SIP container processing % in To tag as escape character
    
    Client who is sending a From tag containing a %.
    For example
    
    From: "JOE JOHN" <sip:">16025553453@123.45.678.:4321>;tag=SD%;
    OTG=10000
    
    Appserver logs show
    jain.protocol.ip.sip.SipParseException: Illegal escaping -
    expected 2 hex digits, found end of component
    
    It is interpreting the % in the From tag as an escape character.
    
    According to the RFC:
    
    from-param = tag-param / generic-param
    
    tag-param = "tag" EQUAL token
    
    token = 1*(alphanum / "-" / "." / "!" / "%" / "*"
    / "_" / "+" / "`" / "'" / "~" )
    
    Note that the token lists "%" -- while % is the escape
    character listed in BNF, it means a literal %.  Otherwise, it
    uses the escaped word.
    
    As opposed to this example:
    user = 1*( unreserved / escaped / user-unreserved )
    
    escaped = "%" HEXDIG HEXDIG
    
    Logs shows the following exception,
    
    [3/28/12 19:58:12:344 GMT] 00000028 MessageParser 3
    MessageParser
    parseHeaders Failed parsing header: From
    
    jain.protocol.ip.sip.SipParseException:
    Illegal escaping - expected 2 hex digits, found end of component
     at com.ibm.ws.sip.parser.Coder.decode(Coder.java:460)
     at
    com.ibm.ws.sip.parser.SipParser.parseParametersMap(SipParser.jav
    a:123)
     at
    com.ibm.ws.jain.protocol.ip.sip.header.ParametersHeaderImpl.pars
    eValue(P
    arametersHeaderImpl.java:178)
    
    The issues is seen when customer has the % followed by
    alphabetic characters in the samples.
    
    If an alpha characters added after the %, then the exception
    wording changes slightly, but the issue remains same.
    
     jain.protocol.ip.sip.SipParseException: Illegal escaping -
    expected 2 hex digits, found some other character
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server SIP Container                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: SIP container processing % in To tag    *
    *                      as escape character.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SIP stack treates % in To/From tag as escape character, which
    contradicts the RFC 3261:
    "from-param = tag-param / generic-param
    tag-param = "tag" EQUAL token
    token = 1*(alphanum / "-" / "." / "!" / "%" / "*"
    / "_" / "+" / "`" / "'" / "~" )"
    

Problem conclusion

  • Changed the code in "EndPointHeaderImpl" class such that "%"
    will no longer be considered escape character.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.25, 8.0.0.4,and 8.5.0.1  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

    PM61816

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-03

  • Closed date

    2012-06-07

  • Last modified date

    2012-06-07

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

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

    PM62056 PM67742

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM61816

Modified date: 07 June 2012