Cloud CM-IPMP Guide de dépannage Page 157

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 201
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 156
Chapter 23
JCC Example Application
23.1 Introduction
The Rhino SLEE includes a sample application that makes use of Java Call Control version 1.1 (JCC 1.1). This section explains
how to build, deploy and use this example. JCC is a framework that provides applications with a consistent mechanism for
interfacing underlying divergent networks. It provides a layer of abstraction over network protocols and presents a high-level
API to applications. JCC includes facilities for observing, initiating, answering, processing and manipulating calls.
The example code demonstrates how a simple JCC application can be implemented using the SLEE. This application is not
intended for production use.
23.1.1 Intended Audience
The intended audiences are SLEE developers and administrators who want to become familiar with SBB and JCC programming
and deployment practices. Some understanding of Java Call Control is assumed.
23.1.2 System Requirements for JCC example
The JCC examples run on all supported Rhino SLEE platforms. Please see Appendix A for details.
Required software:
Java Call Control Reference Implementation
http://www.argreenhouse.com/JAINRefCode
In order for the JCC Resource Adaptor and JCC Call Forwarding Service to function, the Reference Implementation of JCC 1.1
must be downloaded, see section 23.4.1 for installation instructions.
23.2 Basic Concepts
The JCC API defines four objects which model the key call processing functionality: “Provider”, “Call”, “Connection” and
Address”. Some of these objects contain finite state machines that model the state of a call. These provide facilities for
allowing applications to register and be invoked, on a per-user basis, when relevant points in call processing are reached. These
four objects are:
Provider: represents the “window” through which an application views the call processing.
Call: represents a call and is a dynamic “collection of physical and logical entities” that bring two or more endpoints
together.
Address: represents a logical endpoint (e.g., directory number or IP address).
148
Vue de la page 156
1 2 ... 152 153 154 155 156 157 158 159 160 161 162 ... 200 201

Commentaires sur ces manuels

Pas de commentaire