PM87004: SIP CONTAINER COULD NOT FIND A CONNECTION TO CLIENT

PM87004; 8.5.5: sip container could not find a connection to client
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
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

APAR status

• Closed as program error.

Error description

• A call to a client that supports the - Session Initiation
  Protocol (SIP) outbound specification fails with a 430 Flow
  Failed error when the com.ibm.ws.sip.sent.by.host custom
  property is set to FQDN.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: A call to a client that supports        *
  *                      the SIP outbound specification fails    *
  *                      with a 430 Flow Failed error when the   *
  *                      com.ibm.ws.sip.sent.by.host custom      *
  *                      property is set to FQDN                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the com.ibm.ws.sip.sent.by.host custom property is set to
  FQDN the SIP container does not set a port for outbound calls
  that later causes the calls to be failed.
  

Problem conclusion

• The SIP conatiner now sets a proper port for outbound calls
  when com.ibm.ws.sip.sent.by.host custom property is set.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.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 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