APAR status
Closed as program error.
Error description
In zOS environment the SIP container should not connect the proxy directly, all traffic should be sent thru the CR. since the container got notification from the proxy the container sent traffic directly to the proxy what cause the message to fail.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Websphere SIP container users * **************************************************************** * PROBLEM DESCRIPTION: SIP outgoing traffic is failing in z/OS * **************************************************************** * RECOMMENDATION: * **************************************************************** In z/OS environment the SIP container should not connect the proxy directly, all traffic should be sent through the controller region, since the container got notification from the proxy the container sent traffic directly to the proxy what cause the message to fail.
Problem conclusion
The SIP container is now sending all traffic through the controller region and not directly to the SIP proxy.
Temporary fix
Comments
APAR Information
APAR number
PM25335
Reported component name
CEA FEATUREPACK
Reported component ID
5655N0255
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-27
Closed date
2010-11-30
Last modified date
2012-08-08
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
5655N0255
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
08 August 2012