IBM Support

PI83395: In a multi-homed environment, multiple 200 responses are not proxied back to the originating endpoint.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an INVITE is parallel-forked to multiple devices,
    WebSphere receives a 200 response, CANCELs the remaining
    INVITES, but gets a second 200 before the CANCEL reaches the
    endpoints.  In this case, both 200 responses are required to be
    proxied back to the originating endpoint. Instead, WebSphere
    drops the second 200 response.
    The problem happens in a multi-homed environment.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Session Initiation Protocol (SIP)           *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an INVITE is parallel-forked to    *
    *                      multiple devices,                       *
    *                      WebSphere receives a 200 response,      *
    *                      CANCELs the remaining                   *
    *                      INVITES, but gets a second 200 before   *
    *                      the CANCEL reaches the                  *
    *                      endpoints.  In this case, both 200      *
    *                      responses are required to be            *
    *                      proxied back to the originating         *
    *                      endpoint. Instead, WebSphere drops the  *
    *                      second 200OK response.                  *
    *                      The problem happens in a multi-homed    *
    *                      environment.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an INVITE is parallel-forked to multiple devices,
    WebSphere receives a 200 response, CANCELs the remaining
    INVITES, but gets a second 200 before the CANCEL reaches the
    endpoints.  In this case, both 200 responses are required to be
    proxied back to the originating endpoint. Instead, WebSphere
    drops the second 200OK response.
    The problem happens in a multi-homed environment.
    

Problem conclusion

  • The following custom property should be applied so the SIP
    Container chooses a default listening point according to IP
    address family
    
    Name: javax.default.lp.by.address.type
    
    Value: true
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.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

    PI83395

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-20

  • Closed date

    2017-08-16

  • Last modified date

    2017-08-16

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021