Cloud CM-IPMP Anleitung zur Fehlerbehebung PDF herunterladen (Seite 159)

Figure 23.2: Diagrammatic representation of the Call Forwarding Service

2. It determines whether the called party has call forwarding enabled, and to which number.

3. If so, the call is routed:

Call.routeCall(...);

4. The service completes:

Connection.continueProcessing();

The Call Forwarding Proﬁle contains the following user subscription information:

• Address: address of the terminating party.

• Forwarding address: address where the call will be forwarded.

• Forwarding enable: Boolean value which indicates if service is enabled for a determined user.

Event Handling

Calls made between two parties, such as from user A (1111) and user B (2222), cause new JCC events to be released into the

SLEE. This service is executed for the terminating party (user B), so the JCC event which arrives to the JCC Resource Adaptor

is the Connection Authorize Call Attempt event.

This is the deployment descriptor (stored in sbb-jar.xml) for the service:

<event-name>CallDelivery</event-name>

<event-type-ref>

<event-type-name>

javax.csapi.cc.jcc.JccConnectionEvent.CONNECTION_AUTHORIZE_CALL_ATTEMPT

</event-type-name>

<event-type-vendor>javax.csapi.cc.jcc</event-type-vendor>

<event-type-version>1.1</event-type-version>

</event-type-ref>

<initial-event-select variable="AddressProfile"/>

<event-resource-option>block</event-resource-option>

</event>

The service has an initial event, the Connection Authorize Call Attempt event. The initial event is selected using the

“

initial-event="True"

” line. The variable selected to determine if a root SBB must be created is AddressProﬁle

Open Cloud Rhino 1.4.3 Administration Manual v1.1 150

1 2 ... 154 155 156 157 158 159 160 161 162 163 164 ... 200 201

Keine Kommentare

Cloud CM-IPMP Anleitung zur Fehlerbehebung Seite 159