PM07007: LARGE TIMESTAMPS IN SIP REQUEST CAUSE FAILED REQUESTS.

Fixes are available

APAR status

Closed as program error.

Error description

Large timestamps in a Session Initiation Protocol (SIP) request
can cause problems due to the format of the timestamp. When
large timestamps are use, SIP does not write out the Timestamp
header correctly.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  Session Initiation Protocol (SIP) users     *
*                  of IBM WebSphere Application Server V6.1    *
*                  and V7.0                                    *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect Timestamp header field        *
*                      syntax in messages sent by the          *
*                      application server.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem occurs when the application server sends a SIP
message, and the message contains a Timestamp header field.
The Timestamp value is written in scientific notation instead
of the ordinary decimal notation.

For example, the server receives an INVITE request with a
standard Timestamp header field:

INVITE sip:example.com SIP/2.0
Timestamp: 1262304000000
...

The server replies with a Timestamp header field such as this.
The numeric value is the same, but the format is different:

SIP/2.0 100 Trying
Timestamp: 1.262304E12
...

Scientific notation is not compliant with the standard syntax,
as defined in section 25.1 of RFC 3261.

Problem conclusion

The problem is fixed in the SIP (Session Initiation Protocol)
container code. With this fix, the value of the Timestamp
header field is written in ordinary decimal notation only.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.33 and 7.0.0.11.  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
PM07007
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-08
Closed date
2010-02-22
Last modified date
2010-06-03

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM10535 PM15861

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM07007: LARGE TIMESTAMPS IN SIP REQUEST CAUSE FAILED 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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?