5 Parlay X 2.1 Call Notification Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Call Notification communication service and how the interfaces and protocols comply to standards.

Parlay X 2.1 Call Notification Statement of Compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Call notification:

The Parlay X 2.1 interface complies to ETSI ES 202 391-3 Open Service Access (OSA); Parlay X Web Services; Part 3: Call Notification (Parlay X 2).

See Table 1-2, "Call Notification Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 5-1 Statement of Compliance, Parlay X 2.1 Call Notification

Method Compliant? Comment

Interface: CallDirection

NA

NA

handleBusy

Yes

NA

handleNotReachable

Yes

NA

handleNoAnswer

Yes

NA

handleCalledNumber

Yes

NA

Interface: CallNotification

NA

NA

notifyBusy

Yes

NA

notifyNotReachable

Yes

NA

notifyNoAnswer

Yes

NA

notifyCalledNumber

Yes

NA

Interface: CallDirectionManager

NA

NA

startCallDirectionNotification

Yes

NA

stopCallDirectionNotification

Yes

NA

Interface: CallNotificationManager

NA

NA

StartCallNotification

Yes

NA

stopCallNotification

Yes

NA


SIP for Parlay X 2.1 Call Notification

The SIP plug-in for Parlay X 2.1 Call Notification is an integration plug-in that utilizes the Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The SIP Servlet uses the SIP API provided by the WebLogic SIP server, which in its turn converts the API calls to SIP messages.

The SIP servlet acts as both as a SIP User Agent and a SIP Proxy. Depending on which Parlay X operation and state of the call the SIP servlet acts either as a proxy or as the calling party. This means that the calling UA must use WebLogic SIP server as a SIP Proxy.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261. See Table 1-1, "Audio Call Specification Compliance Table" for a link to this specification's location.

Table 5-2 Statement of Compliance, SIP for Parlay X 2.1 Call Notification

Message/Response Compliant(Yes/No) Comment

REGISTER

NA

Not used in the context.

INVITE

Yes

NA

ACK

Yes

NA

CANCEL

Yes

NA

BYE

Yes

NA

OPTIONS

NA

Not used in the context.

INFO

NA

Not used in the context.

100 Trying

Yes

NA

180 Ringing

Yes

NA

181 Call Is Being Forwarded

Yes

Not used in the context.

182 Queued

Yes

Not used in the context.

183 Session Progress

Yes

Not used in the context.

200 OK

Yes

NA

300 Multiple Choices

Yes

UA treated as unreachable.

301 Moved Permanently

Yes

UA treated as unreachable.

302 Moved Temporarily

Yes

UA treated as unreachable.

305 Use Proxy

Yes

UA treated as unreachable.

380 Alternative Service

Yes

UA treated as unreachable.

400 Bad Request

Yes

UA treated as unreachable

401 Unauthorized

Yes

UA treated as unreachable

402 Payment Required

Yes

UA treated as unreachable

403 Forbidden

Yes

UA treated as unreachable

404 Not Found

Yes

UA treated as unreachable

405 Method Not Allowed

Yes

UA treated as unreachable

406 Not Acceptable

Yes

UA treated as unreachable

407 Proxy Authentication Required

Yes

UA treated as unreachable

408 Request Timeout

Yes

Treated as no answer from UA.

410 Gone

Yes

UA treated as unreachable

413 Request Entity Too Large

Yes

UA treated as unreachable

414 Request-URI Too Long

Yes

UA treated as unreachable

415 Unsupported Media Type

Yes

UA treated as unreachable

416 Unsupported URI Scheme

Yes

UA treated as unreachable

420 Bad Extension

Yes

UA treated as unreachable

421 Extension Required

Yes

UA treated as unreachable

423 Interval Too Brief

Yes

UA treated as unreachable

480 Temporarily Unavailable

Yes

UA treated as unreachable

481 Call/Transaction Does Not Exist

Yes

UA treated as unreachable

482 Loop Detected

Yes

UA treated as unreachable

483 Too Many Hops

Yes

UA treated as unreachable

484 Address Incomplete

Yes

UA treated as unreachable

485 Ambiguous

Yes

UA treated as unreachable

486 Busy Here

Yes

NA

487 Request Terminated

Yes

UA treated as unreachable

488 Not Acceptable Here

Yes

UA treated as unreachable

491 Request Pending

Yes

UA treated as unreachable

493 Undecipherable

Yes

UA treated as unreachable

500 Server Internal Error

Yes

UA treated as unreachable

501 Not Implemented

Yes

UA treated as unreachable

502 Bad Gateway

Yes

UA treated as unreachable

503 Service Unavailable

Yes

UA treated as unreachable

504 Server Time-out

Yes

UA treated as unreachable

505 Version Not Supported

Yes

UA treated as unreachable

513 Message Too Large

Yes

UA treated as unreachable

600 Busy Everywhere

Yes

UA treated as unreachable

603 Decline

Yes

UA treated as unreachable

604 Does Not Exist Anywhere

Yes

UA treated as unreachable

606 Not Acceptable

Yes

UA treated as unreachable


Note:

When a Parlay X application returns ActionValues.Route in Action.actionToPerform as a response to operations in Interface: CallDirection, a record-route header is inserted in the SIP Message the in order to stay in the call path.