IBM Support

PK79887: SIP REQUEST LOOPS BACK INTO THE SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A request is sent to the Session Initiation Protocol (SIP)
    container. The request contains a Route header that represents
    the address of the container. A proxy application handles this
    request, and attempts to forward it to some destination. The
    Route header is removed by the container, as expected.
    But instead of coming out to the network, the request loops
    back in to the container.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Session Initiation Protocol (SIP) users of  *
    *                  WebSphere Application Server V6.1           *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a SIP application proxies a        *
    *                      request, it loops back in.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when a request arrives in the SIP container
    with a Route header that matches the local address. For
    example, if the local address is 1.2.3.4 and the local SIP
    port is 5060, and the request comes in from the network with a
    header such as:
    Route: <sip:1.2.3.4:5060>
    
    The application attempts to proxy this request out, by calling
    Proxy.proxyTo(destination).
    
    The request is not sent to its destination. Instead, it "loops
    back" and re-visits the container.
    
    The problem is caused by a bug in the container sending the
    request to the same address as specified in the top Route
    header field value. The request should not be sent to the
    address that is specified in the top Route, if that header was
    present in the original request as it came in from the
    network, and if the address in the header matches the local
    address.
    

Problem conclusion

  • The problem is fixed in the SIP (Session Initiation Protocol)
    container code. The container no longer sends a request to the
    address that is specified in the top Route header field value,
    if that header was part of the original message that came
    in from the network, and if the header address matches the
    local address.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.1.0.23.  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

    PK79887

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-03

  • Closed date

    2009-02-10

  • Last modified date

    2009-02-10

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
10 February 2009