APAR status
Closed as program error.
Error description
According to section 15.4.1 of the SIP specification JSR 289. WebSphere Application Server Session Initiation Protocol (SIP) container does not properly implement the described behavior. This section is the procedure for routing an initial request. It states that if the route modifier is NO_ROUTE, and the application name is null, and there is a route header, then the request will be routed externally. In this scenario is that the container is responded with "403 Forbidden." From traces you will see as follows ------------------------------------------------- ApplicationPa 3 ApplicationPathSelector findSippletMatch appinfo: javax.servlet.sip.ar.SipApplicationRouterInfo@2f692f69; Data: nextApplicationName=null, sipRouteModifier=NO_ROUTE, routes = null, sipApplicationRoutingRegion = null SipRouter CWSCT0017E: Mapping for nonexisting siplet: Method=INVITE, [email protected], Application: Unknown. TransportComm 3 TransportCommLayerMgr TransportCommLayerMgr Out Message: SIP/2.0 403 Forbidden Call-ID: [email protected] CSeq: 384 INVITE --------------------------------------------------
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 7.0 Feature Pack for Communications * * Enabled Applications (CEA) Session * * Initiation Protocol (SIP) users * **************************************************************** * PROBLEM DESCRIPTION: The SIP container does not properly * * implement the described behavior in * * section 15.4.1 of the SIP * * specification JSR 289. * **************************************************************** * RECOMMENDATION: * **************************************************************** Section 15.4.1 of JSR 289 states that if the route modifier is NO_ROUTE, and the application name is null, and there is a route header, then the request will be routed externally. The container responded to this scenario with "403 Forbidden." In ApplicationPathSelector.findSippletMatch(), if the application name is null there is no check if there's a Route header.
Problem conclusion
In ApplicationPathSelector.findSippletMatch(),if the application name is null, and if there's a a Route header, set the external route on the request to true. The fix for this APAR is currently targeted for inclusion in fix pack 1.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
PM23991
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
2010-10-06
Closed date
2011-01-06
Last modified date
2011-01-06
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
CEA FEATUREPACK
Fixed component ID
5724J0855
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 February 2022