Cloud CM-IPMP Guía para resolver problemas Pagina 138

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 201
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 137
Chapter 22
SIP Example Applications
22.1 Introduction
The Rhino SLEE includes a demonstration resource adaptor and example applications which use SIP (Session Initiation Protocol
- RFC 3261). This chapter explains how to build, deploy and demonstrate the examples. The examples illustrate how some
typical SIP services can be implemented using a SLEE. They are not intended for production use.
The example SIP services and components that are included with the Open Cloud Rhino SLEE are:
SIP Resource Adaptor The SIP Resource Adaptor (SIP RA) provides the interface between a SIP stack and the SLEE.
The SIP stack is responsible for sending and receiving SIP messages over the network (typically UDP/IP). The SIP RA
processes messages from the stack and maps them to activities and events, as required by the SLEE programming model.
The SIP RA must be installed in the SLEE before the other SIP applications can be used.
SIP Registrar Service This is an implementation of a SIP Registrar as defined in RFC3261, Section 10. This service
handles SIP REGISTER requests, which are sent by SIP user agents to register a binding from a user’s public address to
the physical network address of their user agent. The Registrar Service updates records in a Location Service that is used
by other SIP applications. The Registrar service is implemented using a single SBB (Service Building Block) component
in the SLEE, and uses a Location Service child SBB to query and update Location Service records.
SIP Stateful Proxy Service This service implements a stateful proxy as described in RFC3261, Section 16. This proxy
is responsible for routing requests to their correct destination, given by contact addresses that have been registered with
the Location Service. The Proxy service is implemented using a single SBB, and uses a Location Service child SBB to
query Location Service records.
SIP Find Me Follow Me Service This service provides an intelligent SIP proxy service, which allows a user profile to
specify alternative SIP addresses to be contacted in the event that their primary contact address is not available.
SIP Back-to-Back User Agent Service This service is an example of a Back-to-Back User Agent (B2BUA). This behaves
like the Proxy Service but maintains SIP dialog state (call state) using dialog activities.
UAS & UAC Dialog SBBs These SBBs are child SBBs, used by the B2BUA SBB for managing the UAS and UAC (User
Agent Server/Client) sides of the SIP session.
AC Naming & JDBC Location Service SBBs These SBBs provide alternate implementations of a SIP Location Service,
which is used by the Proxy and Registrar services. By default the AC Naming Location Service is deployed, which uses
ActivityContext Naming facility of the SLEE to store location information. Alternatively the JDBC Location Service can
be used, to store the location information in an external database.
22.1.1 Intended Audience
The intended audiences are SLEE developers and administrators who want to quickly get demonstration applications running
in Rhino SLEE, and become familiar with SBB programming and deployment practices. Some basic familiarity with the SIP
protocol and concepts is assumed.
129
Vista de pagina 137
1 2 ... 133 134 135 136 137 138 139 140 141 142 143 ... 200 201

Comentarios a estos manuales

Sin comentarios