PM22586: SIP CONTAINER STARTS HANDLING SIP MESSAGES BEFORE SIPLET MAPPING HAS COMPLETED.

APAR status

• Closed as program error.

Error description

• SameTime Gateway starts accepting Session Initiation Protocol
  (SIP) messages before the server startup has completed. The
  container returns 403 for this subscription. From the trace,
  the SIP container starts handing SIP messages before the
  siplet mapping has completed.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server Feature*
  *                  Pack for Communications Enabled Applications*
  *                  (CEA) users                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: SIP container responded with 403        *
  *                      Forbidden when request didn't match     *
  *                      any application.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The default behavior was to respond with 403 when SIP
  container couldn't match any application to a new request.
  

Problem conclusion

• Introduced a new custom property which allow administrator to
  customize the returned error code in tnose scenario's.
  Custom property is a server property, sip.no.route.error.code,
  it's value is the needed error code.
  The default value for this is 403.
  
  In order to set the custom property follow these steps:
  1. Log in to the Administrative Console
  2. For each server in the cluster (or for the standalone
  server) goto: Application servers > <server_name> > SIP
  container > Custom properties
  3. Add new custom property by clicking on New
  4. In the Name field enter: sip.no.route.error.code
  5. In the Value field enter the desired return code
  6. Click on the OK button
  7. Restart the server
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 1.0.0.9. 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:

  PM22471

• 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