PK59303: ALLOW MULTIPLE UDP CHANNEL CHAINS TO BE STARTED IN AN ODR.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When multiple ODRs are running, one ODR may forward a UDP
  message to another ODR.  This means that an ODR must have a UDP
  listening endpoing configured with it's own address.  When fr
  onted by a load balancer (LB), however, a UDP endpoing must be c
  onfigured with the LB's cluster address.  So the proxy must supp
  ort having multiple UDP listening endpoints.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Extended Deployment Session    *
  *                 Initiation Protocol (SIP) users using        *
  *                 multiple On-Demand Routers (ODR's).          *
  ****************************************************************
  * PROBLEM DESCRIPTION: The SIP Proxy core only was coded with  *
  *                      one inbound UDP channel chain in mind.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The SIP Proxy core only was coded with one inbound UDP channel
  chain in mind. When multiple ODR's are used with ODR to ODR
  communication, there must be another inbound UDP channel chain.
  One used exclusively for ODR to ODR transactions.
  

Problem conclusion

• A new custom property has been added for WebSphere Extended
  Deployment to tell the core SIP proxy what is the outbound
  interface to use for sending packets to clients.
  
  The fix for this APAR is currently targeted for inclusion
  in fix pack 6.1.0.17.
  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

• R60A PSN

     UP

• R60H PSN

     UP

• R60I PSN

     UP

• R60P PSN

     UP

• R60S PSN

     UP

• R60W PSN

     UP

• R60Z PSN

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSN

     UP