PM04764: INVALID HEADER IN SIP PROXY LOGS

Fixes are available

APAR status

Closed as program error.

Error description

The Cisco IP PBX was leaving off the max-forwards header which
caused the Session Initiation Protocol (SIP) Router to log a w
arning message for each packet that was received.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: The Cisco IP PBX left off the           *
*                      max-forwards header which caused the    *
*                      Session Initiation Protocol (SIP)       *
*                      Router to log a warning message.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
On the distributed platforms, there is a
custom property that can be set to disable all SIP compliance
checking.  On z/OS, there is no SIP Proxy configuration
available to the SIP Router and there is no way to set this
custom property.

Problem conclusion

For z/OS we added the capability of setting a system property
'isSipComplianceEnabled' to disable the SIP compliance
checking.  This should be set in the JVM properties under the
Generic JVM arguments "-DisSipComplianceEnabled=false".

APAR PM04764 requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

http://www.ibm.com/software/webservers/appserv/library

The following changes to the WebSphere Application Server
Version 7.0 Information Center will be made available in
March, 2010.

The following note will be added to the description of the
isSipComplianceEnabled custom property that is included in
the "SIP proxy server custom properties" topic:

Avoid Trouble: Starting with Fix Pack 7.0.0.9, if you are
running a proxy server in a z/OS ND environment, and your
proxy server is not part of a cluster, you can use this
custom property to enable or disable SIP compliance checking
for that SIP proxy server. However if you are running a
stand-alone application server or your proxy server is part
of a cluster, you must use the isSipComplianceEnabled
generic JVM argument to enable or disable SIP compliance
checking.

The following description of the isSipComplianceEnabled
JVM argument will be added to the Generic JVM arguments
section of the "Java virtual machine settings" topic:

-DisSipComplianceEnabled=true|false

Specifies whether SIP compliance checking is enabled in the
SIP proxy server. SIP compliance checking ensures that the
SIP messages conform to the Session Initiation Protocol
standard. When this property is set to true, SIP compliance
checkingis enabled.

Avoid Trouble: If you are running a proxy server in a z/OS
ND environment, and your proxy server is not part of a
cluster, you can use the isSipComplianceEnabled SIP proxy
server custom property to enable or disable SIP compliance
checking for that SIP proxy server. However if you are
running a stand-alone application server or your proxy
server is part of a cluster, you must use this generic JVM
argument to enable or disable SIP compliance checking.

APAR PM04764 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.9 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM04764
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-08
Closed date
2010-02-04
Last modified date
2010-04-03

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
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK55155
UP10/03/26 P F003

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
24 October 2021

Tips

PM04764: INVALID HEADER IN SIP PROXY LOGS

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 UK55155

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?