|
Aricent's SIP B2BUA Framework provides a scalable,
reliable, and feature-rich environment for rapid service
creation. The framework exposes a set of well-defined
APIs to the application to develop various services,
such as Prepaid, Nat Traversal, Call Queuing, Click-to-Dial,
and Call Pick-Up. These APIs as well as their parameters
are Open Service Architecture (OSA)-compliant. In addition,
Aricent's SIP B2BUA Framework also supports additional
APIs to create innovative applications.
Salient Features
- RFC compliant: RFC 3261 (OSA) compliant B2BUA
- Scalability: Highly scalable feature distribution
- Availability: Reliable high availability support
- Comprehensive support: Support for multi-party,
multimedia call control
- Flexible: Provides the applications complete access
to SIP messages
- Multiple deployment options: Single node or multi
node deployment
- Complete access to SIP messages for the SIP interface
to Proxy/Media Servers
- Multi operating system portability
- Support for multi-party and multi-media call control
Architectural Features
- High availability APIs to allow the applications
back up serialized critical data and reconstruct the
state based on critical data
- APIs to send SUBSCRIBE, NOTIFY, MESSAGE, and proprietary
SIP messages in order to facilitate development of
presence-based applications and chat applications
- APIs to move call-legs from one call to another
in order to facilitate development of applications,
such as Call Pick-Up
- In-built Load Monitor to protect against overload
conditions
- Event criteria filtering mechanisms
Key Standards Compliance
SIP Protocol Compliance
- 'SIP: Session Initiation Protocol', RFC 3261, June
2002, Rosenberg et al.
- Session Description Protocol, RFC 2327
- An Offer/Answer Model with the Session Description
Protocol (SDP), RFC 3264, June 2002
- Reliability of Provisional Responses in the Session
Initiation Protocol (SIP), RFC 3262, June 2002
- SIP INFO Method, RFC 2976, October 2000
Open Service Access (OSA) Compliance
- 3GPP TS 29.198-04-3-600 OSA API Part4-SubPart3-MPCC
SCF
- 3GPP TS 29.198-04-3-600 OSA API Part4-SubPart4-MMCC
SCF
- 3GPP TS 29.998-04-4-500 Part4-SubPart4-MPCC ISC
|
