IBM Support

PM15861: LARGE TIMESTAMPS IN SIP REQUEST CAUSE FAILED REQUESTS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Large timestamps in a Session Initiation Protocol (SIP) request
    can cause problems due to the format of the timestamp. When
    large timestamps are use, SIP does not write out the Timestamp
    header correctly.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Session Initiation Protocol (SIP) users     *
    *                  of IBM WebSphere Application Server V6.1    *
    *                  and V7.0                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect Timestamp header field        *
    *                      syntax in messages sent by the          *
    *                      application server.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when the application server sends a SIP
    message, and the message contains a Timestamp header field.
    The Timestamp value is written in scientific notation instead
    of the ordinary decimal notation.
    
    For example, the server receives an INVITE request with a
    standard Timestamp header field:
    
    INVITE sip:example.com SIP/2.0
    Timestamp: 1262304000000
    ...
    
    The server replies with a Timestamp header field such as this.
    The numeric value is the same, but the format is different:
    
    SIP/2.0 100 Trying
    Timestamp: 1.262304E12
    ...
    
    Scientific notation is not compliant with the standard syntax,
    as defined in section 25.1 of RFC 3261.
    

Problem conclusion

  • The problem is fixed in the SIP (Session Initiation Protocol)
    container code. With this fix, the value of the Timestamp
    header field is written in ordinary decimal notation only.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 1.0.0.5. 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

    PM15861

  • Reported component name

    CEA FEATUREPACK

  • Reported component ID

    5724J0855

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-03

  • Closed date

    2010-06-03

  • Last modified date

    2010-06-03

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

    PM07007

  • 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