PK88497: SIP PROXY INCORRECTLY INFORMS THE SIP CONTAINER ITS INTERFACE IT IS USING TO CONNECT TO THEM

Fixes are available

APAR status

Closed as program error.

Error description

If the Session Initiation Protocol (SIP) proxy resides on a
multihomed system, the SIP proxy incorrectly informs the SIP
containers what interface it is using to connect to it with if
it is using the custom property 'localOutboundTCPAddress'.

Local fix

The System Administrator should SIP proxy settings admin panel
to configure these settings.   These settings are under the C
ontainer Facing network interface section with the TCP and TLS i
nterface settings.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: Multihomed Session Initiation           *
*                      Protocol (SIP) proxy fails to send      *
*                      the correct interface to the SIP        *
*                      containers that it will be using to     *
*                      send TCP and TLS SIP packets from.      *
****************************************************************
* RECOMMENDATION:  There is currently separate administrative  *
*                  console configuration items for this custom *
*                  property.  These items are under SIP proxy  *
*                  Settings in the Container Facing Network    *
*                  Interface section.                          *
****************************************************************
The custom property 'localOutboundTCPAddress' was not
being used to inform the SIP Container what address it was
using to connect to them with.  The SIP container did not
recognize the TCP and TLS connections as being from a proxy
and rejected packets from it.

Problem conclusion

The SIP proxy now correctly informs the SIP containers what
interface it is using to communicate with them using the
custom property so that these connections can be properly
identified as being from a SIP proxy server.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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 number
PK88497
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-10
Closed date
2009-06-23
Last modified date
2009-06-23

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK88497: SIP PROXY INCORRECTLY INFORMS THE SIP CONTAINER ITS INTERFACE IT IS USING TO CONNECT TO THEM

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?