AASTRA Re-direction Services (RCS) User Guide EN - Manual (Page 7)

Redirection and Configuration Service (RCS)
41-001302-01 Rev 00 – 06.2010
3
Redirection and Configuration Service (RCS)
Introduction
This section provides an overview of the Redirection and Configuration Service (RCS) features, as well as basic operating
procedures.
Features
The Aastra Redirection and Configuration Service (RCS) is a service that offers Service Providers the option of auto-con-
figuring the Aastra IP Phones when they are first powered up. Service providers can choose to redirect the phones to their
own configuration server, “soft” brand the phone and Web user interface (UI), and use the RCS to send firmware and/or
branding information to the phones. This service can prevent the end-user customers from manually configuring their
Aastra IP phones in the field upon first bootup or any time thereafter.
On the first bootup, the supported Aastra IP phones contact the RCS over the internet using HTTPS and certificate valida-
tion. If the phone’s MAC address is already registered on the RCS, the phone downloads any files specified by the server.
The end user does not need to manually configure the phone, simplifying the set-up of the phones in the network.
Using the RCS, Service Providers can simplify the configuration and maintenance of the end-user phones by pre-configur-
ing them to access the RCS automatically after the end-user plugs in the phone at their location. Phone users no longer
need to download the latest firmware file manually or enter the address of the Service Provider’s configuration server
using the phone’s user interface. Configuration of the Aastra IP phones deployed in the field becomes an automated proc-
ess.
Redirection of the Aastra IP Phones
The core feature of the RCS is to redirect unconfigured phones to configuration servers that provide the configuration to
the phones, allowing the end-user a plug-and-play provisioning capability. When the Aastra IP Phone is plugged in and
boots up for the first time, it contacts the RCS which then redirects the phone to the Service Provider’s configuration
server.
A phone only contacts the RCS during initial phone setup (factory default state), or when the local phone settings are reset
to the factory default. The IP Phone requirements for contacting the RCS are as follows:
• Must be loaded with Aastra IP Phone Release 2.4 or above
• Must have NO configuration loaded at all on first-time startup
If a factory default occurs on the phone, the phone attempts to contact the RCS automatically to request a configuration.
The following illustration shows the Aastra RCS process flow.
Note:
The branding features can be created/edited by a Super User only. A User can load the pre-configured branding files to
the phone(s) as applicable but cannot edit or change the branding information.