IBM Support

PM35951: UNNECESSARY FLOW TOKEN IN THE RECORD-ROUTE

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
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.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
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
PM35951; 7.0.0.17: unnecessary flow token in the record-route
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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

  • The Session Initiation Protocol (SIP) Container should not
    create a flow-token for an initial INVITE request sent by
    non-SIP outbound client.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Session Initiation Protocol (SIP) users     *
    *                  of IBM WebSphere Application Server V7.0    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The server applies RFC 5626             *
    *                      ("outbound") processing to a request,   *
    *                      although the client is not "outbound"   *
    *                      enabled.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when the Websphere Application Server SIP
    container acts as a proxy/registrar between two elements, a
    client and an edge proxy, in a call flow such as this:
    
       Alice   NAT   Edge Proxy   Proxy/Registrar    Bob
         |      |       |              |              |
    1    |-- REGISTER ->|              |              |
    2    |      |       |-- REGISTER ->|              |
    3    |      |       |<-- 200 OK ---|              |
    4    |<-- 200 OK ---|              |              |
    5    |      |       |              |<-- INVITE ---|
    6    |      |       |<-- INVITE ---|              |
    
    In step 1, Alice, who resides behind a NAT (network address
    translator), registers itself by sending a REGISTER, through
    the NAT, indicating support for RFC 5626 ("outbound").
    In step 2, the edge proxy creates a flow token (as specified
    in RFC 5626 chapter 5) and sets the flow token in a new Path
    header field that it pushes onto the forwarded REGISTER message.
    In step 5, Bob attempts to call Alice through the proxy. Bob
    does not indicate support for RFC 5626.
    In step 6, the proxy/registrar forwards the INVITE downstream.
    It pushes a Route header field value onto the outgoing INVITE
    message, copying the Path URI that it received in step 2 into
    the new Route. This URI contains a flow token. This is normal.
    But when the underlying SIP container forwards the INVITE, it
    adds a Record-Route with another flow token, which describes
    the connection with Bob. This is an error, because Bob has not
    indicated "outbound" support.
    
    This is a violation of RFC 5626 (5.3) specifying that the
    procedure is only applied if the proxy is the host in the
    topmost Route header field value, and the Route header field
    value contains a flow token.
    
    As the top Route does not match the proxy/registrar host, the
    SIP container must ignore it, and send out the INVITE without
    applying "outbound" processing.
    

Problem conclusion

  • The problem is fixed in the SIP container code. With this fix,
    RFC 5626 (5.3.2) processing is only applied if the top Route
    matches the local host.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19.  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

    PM35951

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-30

  • Closed date

    2011-05-04

  • Last modified date

    2011-05-04

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM35951

Modified date: 04 May 2011