Commercial in Confidence
ASE/FMC/PLM
/
0003 / EN
Solution Architecture Description
AMC+ 2.0 with AMC Controller 2.0
Aastra Telecom Sweden AB
SE
-
126 37 Hägersten, Sweden
www.aastra.com
Solution Architecture Description
2010
-
09
-
20
2
/
12
AMC+ 2.0 with AMC Controller Solution document conte
nt
1
Introduction
................................
................................
................................
...........................
3
1.1
Scope
................................
................................
................................
................................
........
3
2
Overview Description AMC+ 2.0 & AMC
Controller 2.0
................................
.........................
3
3
AMC Controller 2.0
................................
................................
................................
................
5
3.1
Architecture
................................
................................
................................
...............................
5
3.2
AMCC Server Engine
................................
................................
................................
.................
5
3.3
AMCC 2.0 Server Requirements
................................
................................
................................
6
3.3.1
Hardware Requirements
................................
................................
................................
.....
6
3.3.2
Software Requirements
................................
................................
................................
......
6
3.3.3
WLAN Requirements
................................
................................
................................
..........
6
3.4
AMCC 2.0 capacity options (SME & Large)
................................
................................
...............
6
4
AMCC Manager
................................
................................
................................
.....................
6
4.1
Features
................................
................................
................................
................................
....
6
5
Aastra Mobile Client plus 2.0
................................
................................
................................
.
7
5.1
AMC+ 2.0 Features
................................
................................
................................
....................
7
6
AMCC 2.0 Features
................................
................................
................................
...............
8
6.1
Key Features
................................
................................
................................
.............................
8
7
Deployment
................................
................................
................................
...........................
8
7.1
Installation and Configuration
................................
................................
................................
.....
8
7.2
Communica
tion system Integration
................................
................................
............................
8
7.3
AMC+ 2.0 Provisioning
................................
................................
................................
..............
8
8
Operation and Maintenance
................................
................................
................................
..
9
9
Additional Features
................................
................................
................................
...............
9
9.1
High Availability
................................
................................
................................
.........................
9
9.1.1
Linux HA
-
based Failover
................................
................................
................................
.....
9
9.1.2
General Information
................................
................................
................................
..........
10
9.2
Security
................................
................................
................................
................................
....
10
9.2.1
Security Guidelines
................................
................................
................................
...........
10
9.3
Unified Communication AMCC functions
................................
................................
.................
11
9.3.1
AMC Corporate Phonebook
................................
................................
..............................
11
9.3.2
AMC Instant Message & Presence
................................
................................
...................
12
Solution Architecture Description
2010
-
09
-
20
3
/
12
1
Introduction
Aastra Mobile Client plus (AMC+) solution is designed to work with all Aastra communications
system platforms. The Aastra Mobile Client plus version 2.0 (AMC+ 2.0) requires th
e AMC
Controller (AMCC) to work. The AMCC is used for connecting AMC+ to the Aastra
communications platforms via SIP user interface and to back office UC application via
Lightweight Directory Access
Protocol
(
LDAP)
and Extensible Messaging and Presence
Pro
tocol (XMPP). AMC+ 2.
0 offers the following features & functions:
Mobile connect SIP integration
Dual mode (Wi
-
Fi / mobile network)
Directory Search (LDAP)
Mobile Presence (XMPP)
Mobile Instant Messaging (XMPP)
Encrypted VoIP (SRTP)
AMC+ 2.0 also support
s all features released in AMC 1.0 and AMC 1.5.
1.1
Scope
This document provides a high level description of the AMC+ 2.0 with the AMC Controller
2.0 solution for mobile SIP integration with dual mode and mobile Unified Communication.
It includes a descripti
on of the solution system components and functions, different
configurations, and the applicable management functions. In this context, the term user is
defined as an end
-
user within the enterprise that uses the AMC Controller 2.0 solution.
Throughout this
document there will be references to other documents that provide more
detailed information about different subjects.
2
Overview Description AMC+ 2.0 and AMCC 2.0
The AMC+ 2.0 and AMCC 2.0 solution is a client
-
server based solution offering mobile
phone in
tegration over SIP, as well as seamless and automatic call continuity as the user
moves back and forth between cellular (2G/3G) and Wi
-
Fi networks. The user having a
SIP
-
based AMC+ installed on a smart phone, supporting connections to both cellular and
Wi
-
Fi (802.11) networks in parallel, interacts with the communications system through the
AMCC. The AMC+ and the AMCC jointly manage the call and perform the handover
seamlessly between the alternative networks. Handover is initiated automatically and is
tran
sparent for the user. The AMC+ runs on Symbian Series 60 operating system, RIM
(Black Berry), iPhone (Apple) and Android. Please see the document
“AMC supported
phone list”
in order to get more info about which phone models Aastra recommends.
The AMCC Ma
nager handles the configuration data for the AMC+ 2.0 users in the AMCC.
Once the AMC+ users are configured via the AMC portal and the AMCC management GUI,
the AMCC manages the user registration in communications system and keeps track of the
users’ presen
ce on the network. Together with the AMC+, the AMCC also manages central
and communications system related parts of the handover activity.
The call setup to and from the Public Land Mobile Network (PLMN) is made through the
communications system where the
public trunk interface is converted to and from a SIP
network interface to the AMCC. The AMCC also converts DTMF tones received (requests
Solution Architecture Description
2010
-
09
-
20
4
/
12
for telephony services generated from the AMC+) to SIP info messages that is handled by
the communications system. AM
CC solution also supports corporate phone book search
(over LDAP), Instant Messaging and Presence Federation over XMPP.
Figure 1: AMC Controller Solution
The AMC Controller solution consists of the following parts:
The AMCC which is a server
-
based mobi
le integration, dual mode handover and
Unified Federation engine, providing Fixed Mobile Convergence (FMC) capabilities for
enterprise users. The dual mode solution with automatic handover (in both directions) is
often referred to as a core part of the FMC
concept. FMC can be both operator
-
controlled and enterprise
-
controlled (CPE). The users use their mobile phones within
the enterprise, as if they were traditional enterprise phones (fixed or wireless); the
traditional phones can be replaced by the new typ
e of phones and dual mode telephony
systems. The convergence happens on the end
-
user side as the user only needs one
phone.
The AMCC Manager is a web
-
based system used for configuration and administration
of the AMCC. AMCC Management software resides enti
rely in the AMCC server and is
accessible through any standard Internet browser.
The AMC+ is a mobile client application installed on a smart phone with 3G/GSM. The
AMC+ communicates with the AMCC using the SIP protocol. Voice communication is
either SIP
-
based or traditional circuit switched
-
based, depending on available networks.
Solution Architecture Description
2010
-
09
-
20
5
/
12
3
AMC Controller 2.0
This section describes the AMC Controller, its components and requirements.
3.1
Architecture
The AMCC overview architecture described in picture 2
Figure 2:
AMCC Architecture
The AMCC consist of the following:
The AMCC server engine which is the core application responsible for providing
the seamless handover between GSM/3G and VoIP/WIF, AMCC Directory
search, IM and presence federation.
The AMCC Manager is
a set of functions used for system operations and
management. The AMCC Manager is used for server configuration and supports
reporting functionality concerning performance.
3.2
AMCC Server Engine
The AMCC server engine monitors the AMC+ for any handover act
ivity.
When the AMCC receives a request for handover from the AMC+, the AMCC determines
the type of vertical handover to be performed between the two mediums, VoIP and GSM. If
a request for handover from VoIP to GSM is detected, the AMCC engine establishes
a
second call on the cellular interface for the same client. Then the AMCC engine bridges the
first call with the second call so that the A
-
party is now connected with the B
-
party using
the GSM interface. Similarly, it can perform a seamless handover for
the call from GSM to
VoIP.
Solution Architecture Description
2010
-
09
-
20
6
/
12
3.3
AMCC 2.0 Server Requirements
3.3.1
Hardware Requirements
The AMCC can be delivered as an appliance (HW/SW) for up to 125 AMC+ users or as a VM
Ware solution that can be installed on any type of server that can support VM Ware.
The s
ystem requirements depend on the size of the installation for the users to be supported.
At a minimum the AMCC can run on any x86 processors that can support VoIP applications.
The server requirements are as follows:
1.4 GHz processor speed or more
256 MB
of RAM
1 GB Flash or any larger hard disk drive space
3.3.2
Software Requirements
The software AMCC VM ware solution ships with an embedded Linux operating system so that
no additional SW is necessary.
3.3.3
WLAN Requirements
The WLAN should have the key performan
ce indicators such as signal strength and voice
latency up
-
to a good level to support Voice over IP communications. The AMCC communicates
over the IP and MAC layer with the AMC dual mode application.
3.4
AMCC 2.0 Capacity Options (SME & Large)
AMCC 2.0 is plan
ned to have two capacity hard drive image installation options:
SME AMCC 2.0 installed on ESU1 for up to 125 AMC+ 2.0 users.
Large AMCC 2.0 VM ware server installation. No capacity limits.
4
AMCC Manager
The AMC Manager is a web
-
based configuration tool for
the AMCC. For the system
administrator, the AMCC is a Linux
-
based application server, making it possible to perform
all the necessary configurations from its web interface. It has a basic system reporting.
For more information regarding AMCC Manager, see
AMCC 2.0 Administrator guide
.
4.1
Features
The AMCC Management GUI provides a single point of configuration for the AMC
controller through the Web.
Create, remove and edit the Telephony Server data
Create, remove and edit the AMC extensions and sip account
s
View the current registration status of the dual mode users
System Management
Activation of the changed system data
System restart and shutdown
System data backup and restore
Solution Architecture Description
2010
-
09
-
20
7
/
12
System health reporting
5
Aastra Mobile Client plus 2.0
The AMC+ 2.0 suppor
ts the feature set of AMC 1.5, dual mode, directory search, encrypted
VoIP, Presence and IM federation application.
5.1
AMC+ 2.0 Features
The SIP compatibility in the AMC+ 2.0 supports the following functionality:
AMC integration options
AMC+ Mobile SIP Int
egration with communication system (SIP)
AMC Not in call service
Voice mail
Call forward to any extension
Message Waiting indication
Time group
Call protect
Diversion services, Meeting, lunch, vacation...
AMC In call service
Fast Forward number
Take
New Li
ne / Enquiry
Brokering / Toggling
Conference
Call Back
Call Waiting
Call Park
AMC Mobile LCR
HTTPS call back & DTMF Call through
AMC Travel SIM
Dual mode (3G/GSM <
-
> Wi
-
Fi/VoIP) seamless automatic handover*
AMC Unified Communication
Corporate directory sea
rch
Instant Messaging
Mobile Presence
* Note: iPhone does not support automatic handover from Wi
-
Fi to GSM, only from GSM to
Wi
-
Fi.
Solution Architecture Description
2010
-
09
-
20
8
/
12
AMC Encrypted VoIP
TLS (signaling)
SRTP (Media)
AMC OTA Provisioning and License Management
Hosted Mobile LCR server
6
AMCC
2.0 Features
6.1
Key Features
Support for AMC1.5 feature set
Dual mode two
-
way seamless handover between VoIP and cellular networks
Support of MX
-
ONE, A5000 & OC1000 SIP extension features
DTMF translation between in
-
band, out
-
of
-
band and SIP info formats
N
etwork operator supported routing and AMC based routing
Authentication at incoming calls
Corporate directory search via LDAP
IM & Presence federation via XMPP
Encrypted VoIP
7
Deployment
7.1
Installation and Configuration
The AMCC software is delivered either
pre
-
installed on an AMCC 2.0 or as a VM Ware
software downloaded from the AMC Portal. For instructions on how to install the system,
see the “
AMCC Installation Guide”.
Once an AMCC is switched on, it is connected to the
Ethernet, using the static IP addre
sses that were assigned during installation.
For instructions on how to configure the system, see the “
AMCC Administrator User's
Guide”
.
Note:
The AMCC should be installed by an authorized system personnel.
7.2
Communication system Integration
The system a
dministrator integrates the AMCC with the communication by creating an IP
extension for each user in the communication system and configuring the SIP trunk in the
communication system towards the AMCC.
7.3
AMC+ 2.0 Provisioning
The AMC+ 2.0 has to be manuall
y provisioned on each AMC hand
-
sets. This can be done
through the AMC provisioning & license portal (
http://amc.aastra.com/portal
) via Over the Air
Provisioning (OTA) or via the phone suppliers’ software insta
llation tools using USB or
Bluetooth.
For more information on how to install the AMCC application, see
installation instructions
“
AMCC Installation Guide”
.
Solution Architecture Description
2010
-
09
-
20
9
/
12
8
Operation and Maintenance
All operation and maintenance tasks on the server are done using the AMC
C web
-
based
management tool. Aspects such as fault management, configuration management,
performance management information and certain reporting capability, along with backup
and restore are provided. The AMCC manager includes the following tasks:
Config
uration of server and extensions
System restart
System shutdown
System status
System backup and restore
For more information on the AMCC manager, see the
“
AMCC 2.0 Administrator User's
Guide”
.
9
Additional Features
9.1
High Availability
9.1.1
Linux HA
-
based Fai
lover
AMCC supports Linux HA
-
based failover. There are two dual mode servers running the
high availability application to act as a hot standby of each other. One of the servers
providing dual mode service is called the primary server and the other
one, ac
ting as its
standby, is called the backup server. The backup server is continuously checking the
status of the primary server ensuring its availability. In case the primary server goes down,
the backup server takes over its role. This is called the failove
r and it occurs within few
seconds.
The synchronization of the user data between two AMC Controllers is ordinarily used in a
redundancy configuration. In such configuration, we have two appliances, one serving as a
master, and the other one serving as a s
lave. The slave will obtain its configuration from
the master server. Therefore, this is not a real synchronization, but rather having a master
containing the configuration. The slave will however keep a copy of the configuration ready
to fill in if the ma
ster fails. This applies only to the FMC part of the configuration. Functions,
such as IP addressing etc., are considered separately. This automatically synchronized
configuration however includes all users, endpoints, and registrations, numbering profiles
,
etc. The synchronization is done directly by accessing the configuration database of the
master server. All changes to users, endpoints, or registrations will become effective
immediately and will therefore also be scheduled for synchronization right aft
er pressing
"Save" in the AMCC Management Web GUI.
In order to lower the network load, several changes are collected and then synchronized in
one step. It can take up to
3 minutes
until all changes have been properly synchronized to
the slave device.
Con
figuration: The AMC Controller will display a
"Database is currently not available"
message on the pages TELEPHONY and FEATURES if it is run in slave
-
mode.
The AMCC database will not be available for changes and new data if database
synchronization takes
place and the AMC Controller is used in slave mode. All FMC
services will be rendered by the master. Therefore, changes of registrations, user
Solution Architecture Description
2010
-
09
-
20
10
/
12
accounts, etc. can only be done on the master AMC Controller. The data on the slave AMC
Controller will be synchr
onized (refreshed). If the master
-
AMC Controller fails, the slave
-
AMC Controller will take over. Only in that case data modifications can be done on the
(former) slave.
9.1.2
General Information
Preparation to configure both master and slave network connection
s has to be set up. In
theory a standard routed connection is enough, but since this feature is used in conjunction
with VRRP, you need to have a connection supporting multicast requests, usually a
switched connection.
Updates: to update the AMC Controlle
r it is very important to switch a master AMC
Controller into standalone mode first and then update its systems.
For the slave, no special considerations have to be taken. You can simply update it. After
both systems have the same software version, the ma
ster can be switched into master
mode again. This procedure is only necessary if the database has been changed between
the two versions. When in doubt, please adhere to this approach nevertheless.
9.2
Security
In the normal case AMCC is placed in a closed ne
twork with end to end security. The
AMCC offers SIP authentication based on message digest. It is also possible to extend it to
use LDAP and RADIUS authentication. An industrial strength open source packet filtering
based firewall,
iptables
, is included an
d can be configured if the need arises.
Ordinarily, the enterprise has its own perimeter security measures and the AMCC does not
play any critical role in enhancing the system or network security.
Please, see AMCC controller 2.0 Administrator guide for mo
re info.
9.2.1
Security Guidelines
The AMC+ 2.0 dual mode handset requires corporate WLAN access. The service can be
based on the unique SSID using wireless authentication and encryption using WPA/WPA2
-
PSK. A typical secure deployment is shown on next page.
Solution Architecture Description
2010
-
09
-
20
11
/
12
Figure 3: Voice over WLAN for dual mode solution
9.3
Unified Communication AMCC functions
With the AMCC UC functions you have the possibility to give configured user accounts to
use an HTTPS connection to the Aastra AMC Controller via their AMC application.
There
are many different usage scenarios of this HTTPS connection. One of them is enabling
users to access the complete company or branch directory, or the address book of just one
department. This is supported already and has to be configured in this sub
-
menu.
However, more applications are to follow.
9.3.1
AMC Corporate Phonebook
The Corporate phonebook server, to which you can configure a connection, has to be
reachable via LDAP. Most commonly this will be an Active Directory server. The amount of
informatio
n made available for the AMC via this feature of the AMC Controller hence
depends on the information available on that server.
Solution Architecture Description
2010
-
09
-
20
12
/
12
9.3.2
AMC Instant Messaging & Presence
XMPP is used for both Presence and Instant Messaging. For those features, the AMC
Controller be
haves very similarly to the SIP
-
telephony scenario. It will act as an XMPP
client and connect to any standard XMPP server. XMPP is the most used Presence and
Instant Messaging protocol and used for example by the Jabber or Openfire servers. There
are both
free and commercial servers available. You can also hook up to a Hosted
Presence Network as for example GoogleTalk and bring the full functionality of your
account there to the mobile phone. For a longer list of publicly available Instant Messaging
servers
, look at the
XMPP website
.There are also gateways available allowing connection
to non
-
XMPP Servers (e.g. SIMPLE) via the XMPP protocol. With this, the integration of
any Presence / Instant Messaging server should be possible.
In order to use the XMPP f
unctionalities you have to configure XMPP endpoints and XMPP
users. As mentioned, this approach is very similar to the IP telephony approach. The
concept of XMPP endpoints and XMPP users is essentially identical to the concept of SIP
endpoints and SIP user
accounts.
For more information, please, read the AMCC 2.0 Administrator guide.
- Αρχική
- Περιήγηση
- Όλες οι Κατηγορίες
- Internet και Εφαρμογές Web
- Αποθήκευση
- Ασφάλεια
- Βιοτεχνολογία
- Δίκτυα και Επικοινωνίες
- Διακομιστές
- Διαχείριση
- Διαχείριση Δεδομένων
- Επιχειρησιακές Εφαρμογές
- Ηλεκτρονική - Συσκευές
- Ημιαγωγοί
- Κινητά – Ασύρματες Τεχνολογίες
- Λογισμικό & κατασκευή λογ/κού
- Μηχανική
- Περιβαλλοντική Τεχνολογία
- Πετρελαϊκά και Εξόρυξη
- Πολεοδομικά Έργα
- Τεχνίτη Νοημοσύνη και Ρομποτική
- Τηλεπικοινωνίες
- Ψυχαγωγία
- Κοινότητα
- Μεταφόρτωση
Σχόλια 0
Συνδεθείτε για να κοινοποιήσετε σχόλιο