PM49349: SIP PROXY DOES NOT WORK PROPERLY IN A "FLOATING IP" DEPLOYMENT CONFIGURATION.

Fixes are available

APAR status

Closed as program error.

Error description

In an environment where the client-side IP address floats
between Session Initiation Protocol (SIP) Proxies, the inactive
proxy is unable to send outbound SIP messages.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 and V8.0 Session Initiation     *
*                  Protocol (SIP) Proxy Server                 *
****************************************************************
* PROBLEM DESCRIPTION: In a floating IP deployment, UDP        *
*                      messages are lost because the Proxy     *
*                      does not have a functional client-side  *
*                      interface.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The SIP Proxy is unable to send UDP messages outbound because
it does not have a client-side interface open.   The SIP Proxy
normally sends a UDP message to the client-side interface to
force it up.   In this environment, this is not possible.
As a result, SIP messages are sent from the container to the
Proxy, but are then dropped.

Problem conclusion

Problem was fixed by forcing the UDP client-side interface
active without actually receiving packets over it.

To enable the feature, create an "autoCreateConnLink"
custom property and set the value to "true".   This custom
property should be located in the SIP Proxy transport custom
properties.   Here is an example of the custom property
location:    "WebSphere proxy servers > proxy1 > Transport
Chain > UDP_SIP_PROXY_CHAIN > UDP_inbound_chain (UDP_1) >
Custom properties"

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.23 and 8.0.0.3.  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
PM49349
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
2011-10-05
Closed date
2011-12-05
Last modified date
2011-12-05

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
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
28 October 2021

Tips

PM49349: SIP PROXY DOES NOT WORK PROPERLY IN A "FLOATING IP" DEPLOYMENT CONFIGURATION.

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

R800 PSY

Document Information

Share your feedback

Need support?