PM31252: DOUBLE RECORD ROUTE SIP OPERATION IS NOT WORKING WHEN PORT IS DIFFERENT

APAR status

• Closed as program error.

Error description

• When the outgoing interfaces have different transport and
  port, the sip container only changes the transport so the
  outgoing record route has a wrong port.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Websphere Application Server version    *
  *                  7.0 Feature Pack for Communications         *
  *                  Enabled Applications (CEA) Session          *
  *                  Initiation Protocol (SIP) users             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The second Record-Route header does     *
  *                      not contain the correct host and port.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When we cloned the second Record-Route URI in
  BranchManager.proxy() we didn't set the host and port.
  

Problem conclusion

• When cloning the second Record-Route header, we now get the
  preferred outbound interface of the outbound transport and set
  the port and host according to it.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 1.0.0.11. 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

  CEA FEATUREPACK

• Fixed component ID

  5724J0855

Applicable component levels

• R700 PSY

     UP