Statement of Compliance

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Parlay X 2.1 Presence

The following chapter describes the standard Oracle Communications Services Gatekeeper communication services and how the interfaces and protocols complies to standards.

 

Parlay X 2.1 Presence

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

The Parlay X 2.1 interface complies to ETSI ES 202 391-14 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 14: Presence (Parlay X 2).

See http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html for links to the specification.

Table 11-1 Statement of Compliance, Parlay X 2.1 Presence
Method
Compliant
(Yes | No)
Comment
Interface: PresenceConsumer
subscribePresence
Y
 
getUserPresence
Y
 
startPresenceNotification
Y
 
endPresenceNotification
Y
 
Interface: PresenceNotification
statusChanged
Y
 
statusEnd
Y
 
notifySubscription
Y
 
subscriptionEnded
Y
 
Interface: PresenceSupplier
publish
N
 
getOpenSubscriptions
N
 
updateSubscriptionAuthorization
N
 
getMyWatchers
N
 
getSubscribedAttributes
N
 
blockSubscription
N
 

 

SIP for Parlay X 2.1 Presence

The SIP plug-in for Parlay X 2.1 Presence is an integration plug-in that utilizes the BEA WebLogic SIP Server to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The controller utilizes the SIP API provided by the WebLogic Server to create and send SUBSCRIBE requests. The WebLogic SIP server converts the API calls to SIP and actually sends the requests out to the network. The SIP servlet on the other hand acts as a listener for responses to the SUBSCRIB requests that were sent from the controller. In this case the WebLogic SIP server receives the SIP messages an converts them to API calls invoked on the SIP servlet.

Standards Compliance

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

Additionally the following IETF specification are used by WebLogic SIP Server

Session Initiation Protocol (IP) - specific Event Notification

The specification is found on http://www.apps.ietf.org/rfc/rfc3265.html

A Presence Event package for the Session Initiation Protocol (SIP)

The specification is found on http://www.apps.ietf.org/rfc/rfc3856.html

PRID: Rich Presence Extensions to Presence Information Data Format (PIDF)

The specification is found on http://www.apps.ietf.org/rfc/rfc4480.html

Table 11-2 Statement of Compliance, SIP for Parlay X 2.1 Presence
Message/Response
Compliant
(Yes/No)
Comment
ACK
-
Not used in the context.
REGISTER
-
Not used in the context.
INVITE
-
 
CANCEL
-
 
BYE
-
 
OPTIONS
-
Not used in the context.
SUBSCRIBE
Y
 
NOTIFY
Y
 
100 Trying
-
Not used in the context.
180 Ringing
-
Not used in the context.
181 Call Is Being Forwarded
-
Not used in the context.
182 Queued
-
Not used in the context.
183 Session Progress
-
Not used in the context.
200 OK
Y
 
202 Accepted
Y
 
300 Multiple Choices
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
301 Moved Permanently
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
302 Moved Temporarily
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
305 Use Proxy
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
380 Alternative Service
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
400 Bad Request
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
401 Unauthorized
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
402 Payment Required
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
403 Forbidden
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
404 Not Found
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
405 Method Not Allowed
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
406 Not Acceptable
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
407 Proxy Authentication Required
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
408 Request Timeout
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
410 Gone
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
413 Request Entity Too Large
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
414 Request-URI Too Long
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
415 Unsupported Media Type
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
416 Unsupported URI Scheme
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
420 Bad Extension
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
421 Extension Required
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
423 Interval Too Brief
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
480 Temporarily Unavailable
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
481 Call/Transaction Does Not Exist
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
482 Loop Detected
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
483 Too Many Hops
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
484 Address Incomplete
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
485 Ambiguous
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
486 Busy Here
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
487 Request Terminated
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
488 Not Acceptable Here
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
489 Bad Event
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
491 Request Pending
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
493 Undecipherable
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
500 Server Internal Error
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
501 Not Implemented
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
502 Bad Gateway
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
503 Service Unavailable
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
504 Server Time-out
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
505 Version Not Supported
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
513 Message Too Large
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
600 Busy Everywhere
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
603 Decline
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
604 Does Not Exist Anywhere
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.
606 Not Acceptable
Y
From a Parlay X 2.1 Presence standpoint the subscription will not be established.


  Back to Top       Previous  Next