You can associate custom events to Sipelia™ entities
to monitor when a device or a user registers to your SIP server, for example, or goes offline. You can
also associate custom events to call states to be notified, for example, when a call was missed or to
monitor errors on intercom devices.
What you should know
Any type of custom events from
Security Center can be associated to a
Sipelia™ entity state or to a call state. A call
state represents the different phases of a call. It tells us, for example, that the call
is ringing, busy or in progress.
The entity state shows when the entity is online or offline. Two types of entities can
be associated to custom events: users and intercoms.
IMPORTANT: You can associate custom events in the following way:
- Call states
- They can be associated with users, local intercoms (intercoms connected directly to
Sipelia™ server, not to a trunk) and with
intercoms connected to a trunk.
- Entity states
- They can be associated with users and local intercoms only. To get the state of
an intercom connected to a trunk, you need to monitor the state of
the trunk itself.
Procedure
To associate a Security Center
custom event with the state of a Sipelia™
entity or the state of a call:
-
Open Config
Tool and choose one of the
following:
- For users:
- Open the User Management task and select the user you want
to associate with the event.
- For intercoms:
- Open the Area view task and select the intercom you
want to associate with the event.
-
Click the VoIP tab to access the Sipelia™ parameters.
To associate a custom event to a call state:
-
In the Custom events association section, under the
Call state events list, click Add an
item ().
-
In the Assign custom event to call state window, select the
call state you want from the Call state drop-down
list:
- Ringing
- A call to or from an intercom or user is ringing.
- On a call
- A call with an intercom or user is established.
- Busy
- A call with an intercom or user cannot be established
for any of the following reasons:
- The intercom or user is already in a call with another participant.
- The intercom or user rejects the call.
- The intercom is connected through a trunk server and the trunk server
is not able to reach this intercom.
- Not answered
- The intercom or user does not accept or reject the call.
The call stops after the ringing timeout.
- Error
- Unexpected errors occurred during the call.
- End call
- A call was established without error and is properly
closed by any of the participants.
-
Select the required custom event from the list and click Add.
-
Click Apply to confirm your selection.
The associated event now appears in the Call state events list.
To associate a custom event to an entity state:
-
In the Custom events association section, under the
Entity state events list, click Add an
item ().
-
In the Assign custom event to entity state window, select the
entity state you want to associate from the Entity state drop-down
list:
- Online
- The entity first registers or registers back after being offline.
- Offline
- The entity fails to register or to re-register within the configured period of
time.
-
Select the required custom event from the list and click Add.
-
Click Apply to confirm your selection.
The associated event now appears in the Entity state events list.
Results
The custom events you have selected are now linked to the
Sipelia™ entity or call states of your choice. You
can now associate an action to these events, monitor them or include these events in a
report.