PM50232: SIP PROXY IS NOT RE-USING TCP/TLS CONNECTIONS FOR OUTBOUND SIP REQUESTS

Fixes are available

APAR status

Closed as program error.

Error description

Previous to Fix Pack 15, the SIP Proxy used currently
existing inbound TCP/TLS connections for outbound SIP requests.
A regression occurred in Fix Pack 15 so that under some
scenarios, the SIP Proxy does not re-use the connection, but
instead attempts a new outbound connection.   This attempt
sometimes fails because in certain environments, we hit TLS
certificate issues or firewall issues.

Local fix

Rollback 7.0.0.15 appserver fixpack to previous working version

Problem summary

****************************************************************
* USERS AFFECTED:  All users of the IBM WebSphere Application  *
*                  Server Session Initiation Protocol (SIP)    *
*                  Proxy                                       *
****************************************************************
* PROBLEM DESCRIPTION: SIP Proxy does not re-use inbound       *
*                      client TCP/TLS connections for          *
*                      outbound requests.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In some scenarios, the SIP Proxy will fail to re-use inbound
client TCP/TLS connections for outbound requests. In a
scenario where the client issues a SIP REGISTER on a client
connection, the SIP Proxy normally uses the same client
connection for outbound requests (based on the CONTACT headers
registered). This behavior changed starting in Fix Pack 15.
Currently, the SIP Proxy will attempt a new TCP/TLS connection
to the client. In some network environments, this may not be
possible, resulting in a dropped SIP request.

Problem conclusion

Code has been correct to re-use the connection.
The fix for this APAR is currently targeted for inclusion in
fix pack 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
PM50232
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-17
Closed date
2011-12-01
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:

PM63079

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

PM50232: SIP PROXY IS NOT RE-USING TCP/TLS CONNECTIONS FOR OUTBOUND SIP REQUESTS

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?