IBM Support

PM71036: CONTAINER GENERATED RECORD-ROUTE IS FOR TCP WHEN SIPS WITH TRANSPORT=TCP IS IN THE REQUEST-URI

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server thinks that the request was sent
    out over TCP. The Via headers show correctly that it is being
    sent via TLS.  The top  record-route should not have been
    inserted by the container.  The  impact of this is that
    in-dialog requests from the UAS fail because  they are sent
    via TLS to WebSphere Application Server's TCP listen port.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5 Session Initiation     *
    *                  Protocol (SIP) container                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Double record route feature is          *
    *                      invoked in a case of SIP URI with       *
    *                      transport parameter.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a case where next route is a SIPS scheme but has a
    transport parameter the SIP container evaluates the next
    outgoing tranpsort according to the transport parameter and not
    autmatically as TLS transport which is the case for all the
    SIPS URIs. This in turn invokes the Double Record Route
    feature which should be only invoked if the incoming transport
    and outgoing transport differ.
    

Problem conclusion

  • In all cases where the SIPS URI is used we assume the next
    outgoing transport will be TLS without regard to the transport
    parameter.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.5 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

    PM71036

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-16

  • Closed date

    2012-08-31

  • Last modified date

    2012-08-31

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021