Oracle® Communications Services Gatekeeper Statement of Compliance Release 5.1 E37532-01 |
|
|
PDF · Mobi · ePub |
The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Call Notification communication service and how the interfaces and protocols comply to standards.
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 V1.2.1 (2006-12) Open Service Access (OSA); Parlay X Web Services; Part 3: Call Notification (Parlay X 2). See
ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip
for links to the specification.
Table 3-1 Statement of Compliance, Parlay X 2.1 Call Notification
Method | Compliant(Yes | No) | Comment |
---|---|---|
Interface: CallDirection |
||
handleBusy |
Y |
|
handleNotReachable |
Y |
|
handleNoAnswer |
Y |
|
handleCalledNumber |
Y |
|
Interface: CallNotification |
||
notifyBusy |
Y |
|
notifyNotReachable |
Y |
|
notifyNoAnswer |
Y |
|
notifyCalledNumber |
Y |
|
Interface: CallDirectionManager |
||
startCallDirectionNotification |
Y |
|
stopCallDirectionNotification |
Y |
|
Interface: CallNotificationManager |
||
StartCallNotification |
Y |
|
stopCallNotification |
Y |
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.
The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261.
The specification is found on http://www.ietf.org/rfc/rfc3261.txt
Table 3-2 Statement of Compliance, SIP for Parlay X 2.1 Call Notification
Message/Response | Compliant(Yes/No) | Comment |
---|---|---|
REGISTER |
- |
Not used in the context. |
INVITE |
Y |
|
ACK |
Y |
|
CANCEL |
Y |
|
BYE |
Y |
|
OPTIONS |
- |
Not used in the context. |
INFO |
- |
Not used in the context. |
100 Trying |
Y |
|
180 Ringing |
Y |
|
181 Call Is Being Forwarded |
Y |
Not used in the context. |
182 Queued |
Y |
Not used in the context. |
183 Session Progress |
Y |
Not used in the context. |
200 OK |
Y |
|
300 Multiple Choices |
Y |
UA treated as unreachable. |
301 Moved Permanently |
Y |
UA treated as unreachable. |
302 Moved Temporarily |
Y |
UA treated as unreachable. |
305 Use Proxy |
Y |
UA treated as unreachable. |
380 Alternative Service |
Y |
UA treated as unreachable. |
400 Bad Request |
Y |
UA treated as unreachable |
401 Unauthorized |
Y |
UA treated as unreachable |
402 Payment Required |
Y |
UA treated as unreachable |
403 Forbidden |
Y |
UA treated as unreachable |
404 Not Found |
Y |
UA treated as unreachable |
405 Method Not Allowed |
Y |
UA treated as unreachable |
406 Not Acceptable |
Y |
UA treated as unreachable |
407 Proxy Authentication Required |
Y |
UA treated as unreachable |
408 Request Timeout |
Y |
Treated as no answer from UA. |
410 Gone |
Y |
UA treated as unreachable |
413 Request Entity Too Large |
Y |
UA treated as unreachable |
414 Request-URI Too Long |
Y |
UA treated as unreachable |
415 Unsupported Media Type |
Y |
UA treated as unreachable |
416 Unsupported URI Scheme |
Y |
UA treated as unreachable |
420 Bad Extension |
Y |
UA treated as unreachable |
421 Extension Required |
Y |
UA treated as unreachable |
423 Interval Too Brief |
Y |
UA treated as unreachable |
480 Temporarily Unavailable |
Y |
UA treated as unreachable |
481 Call/Transaction Does Not Exist |
Y |
UA treated as unreachable |
482 Loop Detected |
Y |
UA treated as unreachable |
483 Too Many Hops |
Y |
UA treated as unreachable |
484 Address Incomplete |
Y |
UA treated as unreachable |
485 Ambiguous |
Y |
UA treated as unreachable |
486 Busy Here |
Y |
|
487 Request Terminated |
Y |
UA treated as unreachable |
488 Not Acceptable Here |
Y |
UA treated as unreachable |
491 Request Pending |
Y |
UA treated as unreachable |
493 Undecipherable |
Y |
UA treated as unreachable |
500 Server Internal Error |
Y |
UA treated as unreachable |
501 Not Implemented |
Y |
UA treated as unreachable |
502 Bad Gateway |
Y |
UA treated as unreachable |
503 Service Unavailable |
Y |
UA treated as unreachable |
504 Server Time-out |
Y |
UA treated as unreachable |
505 Version Not Supported |
Y |
UA treated as unreachable |
513 Message Too Large |
Y |
UA treated as unreachable |
600 Busy Everywhere |
Y |
UA treated as unreachable |
603 Decline |
Y |
UA treated as unreachable |
604 Does Not Exist Anywhere |
Y |
UA treated as unreachable |
606 Not Acceptable |
Y |
UA treated as unreachable |
Note:
When a Parlay X application returnsActionValues.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.