PK80806: SIP PROXY DOES NOT INFORM SIP CONTAINERS THAT IT IS UNABLE TO COMMUNICATE WITH SIP NETWORK.

Fixes are available

APAR status

Closed as program error.

Error description

When you have dual network interfaces (one for SIP traffic and
one for the management network), if for some reason the
Session Initiation Protocol (SIP) proxy can not communicate on
the SIP network it does not inform the SIP containers of this
state and the SIP containers will continue to send outbound
SIP messages to this proxy even though it is unable to receive
them.  This scenario causes a large amount of retransmissions
which eventually lead to call timeouts.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: When the Session Initiated Protocol     *
*                      (SIP) network cable is pulled           *
*                      from either the SIP proxy or any        *
*                      device that it uses to communicate      *
*                      with the rest of the cell it needs to   *
*                      inform the SIP containers in the rest   *
*                      of the cell that it is no longer able   *
*                      to process SIP data.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the SIP network cable is pulled from either the SIP proxy
or any device that it uses to communicate with the rest of the
cell it needs to inform the rest of the cell that it is no
longer able to process SIP data.

Problem conclusion

When the SIP proxy is no longer receiving any SIP advisor
requests from the load balancer, the SIP proxy needs to inform
the SIP containers that it is no longer available for them to
use to send outbound SIP messages.  Once the SIP containers
receive this notification, they will remove this SIP proxy
from its list of available proxies to use.  The SIP proxy
custom property 'numFailuresSipAdvisorRequests' must be used
in order for the SIP proxy to notice any failure to receive
load balancer advisor requests.  This custom property should
be set under the SIP Proxy settings custom properties section.
This setting indicates the number of SIP advisor requests
that should be missed before it considers itself not
processing any data.  It defaults to not being enabled and it
is recommended to be set to '3' if used.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.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
PK80806
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-02-17
Closed date
2009-02-27
Last modified date
2009-02-27

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

PK80806: SIP PROXY DOES NOT INFORM SIP CONTAINERS THAT IT IS UNABLE TO COMMUNICATE WITH SIP NETWORK.

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?