PI11757: AFTER DNS ISSUE IS RESOLVED, SIP PROXY IS NOT CONNECTING TO CLIENT

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• After DNS issue is resolved, SIP Proxy is not connecting to
  client. After SIP Proxy fails to connect to client because of
  DNS issues, it does not retry in subsequent requests.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server that use the WebSphere Session       *
  *                  Initiation Protocol (SIP) Proxy.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: If the SIP Proxy fails to connect to    *
  *                      a client because of DNS issues, it      *
  *                      will not re-attempt to connect to the   *
  *                      client.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the SIP Proxy does not attempt an outbound connection to a
  client (using either TCP or TLS), it could be experiencing
  this issue.
  

Problem conclusion

• We fixed the issue by removing the routing information from
  the routing tables if the DNS resolution fails.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.3.  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 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

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP