PM61816: SIP CONTAINER PROCESSING % IN TO TAG AS ESCAPE CHARACTER

Fixes are available

APAR status

Closed as program error.

Error description

Product Version:WAS ND 7.0.0.5
OS and Additional Information: Sun Solaris
JDK 1.6
Problem Description:

SIP container processing % in To tag as escape character

Client who is sending a From tag containing a %.
For example

From: "JOE JOHN" <sip:">16025553453@123.45.678.:4321>;tag=SD%;
OTG=10000

Appserver logs show
jain.protocol.ip.sip.SipParseException: Illegal escaping -
expected 2 hex digits, found end of component

It is interpreting the % in the From tag as an escape character.

According to the RFC:

from-param = tag-param / generic-param

tag-param = "tag" EQUAL token

token = 1*(alphanum / "-" / "." / "!" / "%" / "*"
/ "_" / "+" / "`" / "'" / "~" )

Note that the token lists "%" -- while % is the escape
character listed in BNF, it means a literal %.  Otherwise, it
uses the escaped word.

As opposed to this example:
user = 1*( unreserved / escaped / user-unreserved )

escaped = "%" HEXDIG HEXDIG

Logs shows the following exception,

[3/28/12 19:58:12:344 GMT] 00000028 MessageParser 3
MessageParser
parseHeaders Failed parsing header: From

jain.protocol.ip.sip.SipParseException:
Illegal escaping - expected 2 hex digits, found end of component
 at com.ibm.ws.sip.parser.Coder.decode(Coder.java:460)
 at
com.ibm.ws.sip.parser.SipParser.parseParametersMap(SipParser.jav
a:123)
 at
com.ibm.ws.jain.protocol.ip.sip.header.ParametersHeaderImpl.pars
eValue(P
arametersHeaderImpl.java:178)

The issues is seen when customer has the % followed by
alphabetic characters in the samples.

If an alpha characters added after the %, then the exception
wording changes slightly, but the issue remains same.

 jain.protocol.ip.sip.SipParseException: Illegal escaping -
expected 2 hex digits, found some other character

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server SIP Container                        *
****************************************************************
* PROBLEM DESCRIPTION: SIP container processing % in To tag    *
*                      as escape character.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
SIP stack treates % in To/From tag as escape character, which
contradicts the RFC 3261:
"from-param = tag-param / generic-param
tag-param = "tag" EQUAL token
token = 1*(alphanum / "-" / "." / "!" / "%" / "*"
/ "_" / "+" / "`" / "'" / "~" )"

Problem conclusion

Changed the code in "EndPointHeaderImpl" class such that "%"
will no longer be considered escape character.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.25, 8.0.0.4,and 8.5.0.1  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
PM61816
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
2012-04-03
Closed date
2012-06-07
Last modified date
2012-06-07

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

PM62056 PM67742

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

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

PM61816: SIP CONTAINER PROCESSING % IN TO TAG AS ESCAPE CHARACTER

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

R850 PSY

Document Information

Share your feedback

Need support?