Clearspan® Product Overview R19
Aastra – 2740-007
2014 Clearspan® is a Registered Trademark of Aastra Technologies Ltd.
Page 85 of 93
5.3.1
Access Profiles
Before an access device can connect to Clearspan, a corresponding “access profile” must be
defined for that device. An access profile specifies the signaling and media capabilities of the
device. This allows Clearspan to tailor service delivery to match the specific capabilities of each
device in the network. For instance, one device may support dynamic registration, while another
may need to have its contact address provisioned statically. Another device may support multiple
call appearances, while another may require waiting calls to be managed in the network. By
defining unique access profiles for each of these device types, Clearspan can adjust the way it
signals to each device accordingly. The access profile also defines the number of “ports” or unique
line addresses that the device supports. As ports are assigned to line addresses, Clearspan keeps
track of which port is allocated and which port is free. This helps operators manage not only the
inventory of devices in the network, but also the number of ports that are in use.
5.3.2
Configuration Profiles
To simplify deployment, Clearspan allows “configuration profiles” to be defined for each device it is
managing. A configuration profile defines the attributes and settings required for the device to
connect to the network and deliver service. Configuration profiles are optional. If Clearspan is not
responsible for the configuration profile of the device, then this part of Device Management can be
disabled.
When enabled, Clearspan uses the configuration profile to generate configuration files.
Configuration files are stored on the Profile Server and made accessible to the devices over the
access network. The Clearspan Application Server uses either File Transfer Protocol (FTP) or
Hypertext Transfer Protocol (HTTP) to deposit files in the repository. File transfers occur on the
private side of the Clearspan server complex.
5.3.3
Service Integration
One of the most powerful features of Device Management on Clearspan is the ability to easily
integrate Clearspan user services with features on the access device. This is most applicable for
advanced business services, such as Shared Call Appearances (SCA) and Busy Lamp Field
(BLF), which require attribute values to be set in both Clearspan and the access device before the
service operates properly. For instance, the Busy Lamp Field service on Clearspan requires the
use of the Session Initiation Protocol (SIP) dialog event package. To access the service, the device
must SUBSCRIBE to a specific SIP URI representing the specific user’s Busy Lamp Field state.
This SIP URI must be provisioned on both the user’s service profile as well as any device he or she
wishes to use to access the service. When using Device Management, the provisioning system
only needs to set this value once on the user’s service profile. This triggers Clearspan to update
any corresponding device configuration files and deposit them in the configuration file repository on
the PS. If the changes are to take effect immediately, the administrator can initiate a remote reboot
of the affected access devices to force a reload of modified the configuration files.
Clearspan supports a long list of service attributes that can be integrated with device profile
settings, including, but not limited to:
Shared Call Appearances
Busy Lamp Field
Any service using a feature access code
Voice Portal and Voice Mail
Language and Locale
