
To undeploy all the SIP example applications, including the SIP resource adaptor, run:
ant undeployexamples
At this point, the Ant system has been successfully used. An example SBB implementing a SIP Registrar has been
modified and that SBB’s deployment descriptor has had a new environment entry added to it. The JAIN SIP API has
been demonstrated, and the logging system’s management has been used to enable or disable the application’s debugging
messages.
24.4 Extending with Profiles
The example in Section 24.3 introduced a feature whereby the SIP Registrar would only accept Registration requests from users
within its own domain. A more challenging exercise for the developer is to use the JAIN SLEE Profiles concept to provide more
fine grained access control whereby only users who are part of an “allow list” are able to register. Two examples provided with
this distribution use Profiles and these illustrate the use of Profiles.
Briefly, the “Find Me Follow Me” service uses Profiles to represent a list of SIP addresses which will be tried if the user is
unavailable at their primary address. The code and deployment descriptors for the Find Me Follow Me Service are found in
$RHINO_HOME/examples/sip/src/com/opencloud/ slee/services/sip/fmfm
.
Additionally, the JCC Call Forwarding example uses a custom Address Profile to store the forwarding address of the user. The
source code for this service is in
$RHINO_HOME/examples/jcc/src/com/opencloud/ slee/services/callforwarding
.
The developer can refer to the JAIN SLEE 1.0 API and 1.0 specification document to review the revelant documentation on
Profiles.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 172
Comentarios a estos manuales