AMC Controller Admin Installation and Configuration Guide

Commercial in Confidence
AMCC and AMC3 Admin

Installation & configuration Guide
Aastra Telecom Ltd Doc. No. ASE/FMC/GEN/0004/0/17

www.aastra.com Date: January 22, 2013
AMCC & AMC3 installation and configuration
AMC 3 with AMC Controller Solution document content:

1.1 Overview.......................................................................................................................................4
1.2 Fixed Mobile Convergence...........................................................................................................4
1.3 Introduction to the User Guide......................................................................................................4
2 Welcome to AMCC ..............................................................................................................................5
3 Installation of the AMC Controller ..................................................................................................7
3.1 AMCC-30 and AMCC-130 ............................................................................................................7
3.2 VMware on ESXi ..........................................................................................................................7
4 Configure MX-ONE............................................................................................................................10
4.1 General MX-ONE configuration..................................................................................................10
4.2 Number analysis and number series ..........................................................................................10
4.3 Initiate number series .................................................................................................................13
4.4 Extensions & Common service profile........................................................................................14
4.5 Routes ........................................................................................................................................15
4.6 Initiate routing .............................................................................................................................16
4.7 Number Conversion....................................................................................................................18
4.8 AMCC MX-ONE Configuration ...................................................................................................24
4.9 Number conversion related to AMCC configuration ...................................................................26
5 Configuring the AMCC.......................................................................................................................30
5.1 Establishing a connection to the AMCC .....................................................................................30
5.2 Configuration of the LAN Interface .............................................................................................31
5.3 Configuration of the default gateway ..........................................................................................32
5.4 Time and date settings ...............................................................................................................33
5.5 Configure the PBX and Users – Global settings.........................................................................34
5.6 Configure PBX and Users – Endpoints ......................................................................................37
5.7 Configure PBX and Users – SIP Trunk ......................................................................................38
5.8 Configure PBX and Users – PBX ...............................................................................................39
5.9 Configuring PBX and Users – FMC Numbers ............................................................................40
5.10 Configure PBX and Registrations ...........................................................................................41
5.11 Configure PBX and Users – User Accounts ...........................................................................41
5.12 Configure PBX and Users – Cellular.......................................................................................42
5.13 Configure PBX and Users – User Settings .............................................................................43
5.14 PBX Access Codes.................................................................................................................44
5.15 Backup the system..................................................................................................................44
6 Other AMCC/MXONE services that could be necessary for the installation......................................46
Doc. No. ASE/FMC/GEN/0004/0/17 2/54

6.1 Other AMCC services – Number conversion..............................................................................46

6.2 An example of configuring the AMCC for internet ......................................................................47
6.3 Security – TLS Certificate Configuration ....................................................................................49
6.4 Network Trace Capabilities.........................................................................................................51
6.5 Number Conversion when using Remote Extension. .................................................................52
7 Troubleshooting. ................................................................................................................................53
Acronyms ..................................................................................................................................................54

Welcome to Aastra
Thank you for choosing this Aastra product. Our product meets the strictest requirements with regard to
quality and design.
The following user's guide will assist you in using the Aastra Mobile Client Plus application and answer
most of the questions that may arise.
If you require further technical support or information about other Aastra products, please refer to our
website at http://www.aastra.com. It provides additional notes and tips on the product.
1.1 Overview
The Aastra Mobile Client Controller brings system telephony features to your mobile telephone in
interaction with your PBX. After installation the Aastra Mobile Client Plus can be used immediately
without spending too much time learning it.
1.2 Fixed Mobile Convergence

Fixed Mobile Convergence (FMC) is the integration of mobile telephones into the fixed-line
communications system of a company.
The Aastra Mobile Client software (AMC) allows you to access the Aastra communications system
services from your mobile phone, enabling complete integration with the communications
system as a normal extension.
Use your mobile phone at the Aastra communications system – the familiar communications
environment accompanies you around the world and is always available.
Switch at any time from mobile telephone to system telephone – even in the middle of a call.
Depending on the situation, select the mobile telephone or stationary system telephone –
accessible worldwide – with the best audio quality.
Be always accessible with one single number – free people calling you from having to keep track
of several network and call numbers.
1.3 Introduction to the User Guide

User information
This user's guide describes installation and configuration of the AMC Controller, AMCC. You will find
other complimentary documents at www.aastra.com or www.aastra.com/docfinder.
For more information please refer to the documentation or to your dealer’s homepage. It is your
responsibility to inform yourself about the scope of functions, operation and proper use of your
equipment.
Check whether you have all the user information available on your product, whether it conforms
to your product’s version and whether it is up to date.
Read through the user information carefully before using the Aastra Mobile Client.
Store the user information within easy reach and refer to it whenever uncertainties arise in
connection with the use of the application.
If individual features differ on the Aastra communications systems, a reference is made in this
user’s guide.
Disclaimer
This product was manufactured in accordance with ISO 9001 quality guidelines. The product and the
user information belonging to it have been produced with the utmost care. The product’s functions have
been tested and approved after comprehensive conformity tests. Nonetheless errors cannot be entirely
excluded. The warranty is limited to the replacement of defective hardware.
The manufacturers shall not be liable for any direct or indirect damage that may be caused by incorrect
handling, improper use, or any other faulty behaviour on the part of a product. Potential hazards are
mentioned in the relevant places in the user information. Liability for loss of profit shall be excluded in
any case.

2 Welcome to AMCC
This Getting Started Guide will help to setup and configure the Aastra Mobile Client Controller (AMCC).
Please read this guide in its entirety before starting to configure the server. It is also strongly
recommended to collect all the customer specific information prior to beginning the setup. To simplify
this, a one-page form is included in this document.
The guide will only help to setup the MX-ONE/AMCC so that basic call/functions can be made. For
additional settings, such as Corporate Phonebook, IM and Presence, refer to document Admin. Guide for
AMC Controller
The AMCC-30 and AMCC-130 server come pre-installed on the server and the VMware image is
downloadable from the AMC portal ready to be installed on a VM host. The AMCC is delivered with an
embedded operating system so no additional software is necessary to run the AMCC application.
(This document contains settings for WAN that is not an option for AMCC-30)
Note: The IT administrator should provide fixed IP-addresses that will be dedicated to the AMCC
installation.

Site specific system data collection forms

We recommend that you collect all applicable information below, before you begin the
AMCC installation and configuration.
MX-ONE
IP-address:
SIP route destination for Call through
SIP route destination for SIM switch
Clients SIP ext. and their mobile
Aastra Mobile Client Controller (AMCC) IP- networking information

External IP-address:
Internal IP address:
Network Mask:
Default IP Gateway:
DNS server address:
NTP server address:
The ports below are used by the AMCC and may need to be opened in the relevant firewall(s)
depending on the network configuration.
Ports that are used externally.
5061 and 5062 5061 for TCP (TLS) and 5062 (none
TLS).
448 TCP (for externally incoming HTTPS
requests, call back, Corporate Directory
etc.)
Ports that are used internally.

5060 Towards MX-ONE
389 or 3268 TCP (for Corporate Directory server LDAP

access, the latter in Active Directory case.)
443 To be able to configure the AMCC via

Web GUI.
11000 – 11xxx SIP Trunk AMCC – MXONE.
NOTE: A port range 35000-65000 (RTP/SRTP) is configurable on AMCC and will be used only as
part of a SIP session (default is 35000 to 35xxx), consider consistency with ports configured to be
open in the firewall. With a SIP- aware firewall/SBC no ports will have to be specifically opened.

3 Installation of the AMC Controller
3.1 AMCC-30 and AMCC-130

Both the AMCC-30 and AMCC-130 are delivered pre-installed with both the embedded operating system
and AMC application so all that is necessary is to power on the server and wait for the application to
start. Then proceed with the configuration of the controller as described later in the document. Note that
with the AMCC-130 the second network port is used for the LAN connection and the first network port is
used for the WAN connection. The AMCC-30 has only one network port which is used for the LAN
connection; there is no WAN connection possibility for the AMCC-30.
If you have legacy hardware for AMCC-125 the following procedure may also be used.
3.2 VMware on ESXi

The AMCC for VMware is delivered as two files AMCC-VMWare-v2.0-rxxxxx.xx-flat.vmdk and AMCC-
VMWare-v2.0-rxxxxx.xx.vmdk which are used to create the new virtual machine for the AMC controller
on the ESXi host running VMware ESXi 5.0. The installation of ESXi is not described here and reference
should be made to VMware installation instructions.
The creation of the virtual machine is done using the VMware vSphere client towards the host machine
or via the VMware vCenter server. The following description describes the installation on a stand alone
host machine using the vSphere client.
1. Using the vSphere client connect to the host ESXi host machine.
2. Before starting to create the new machine the two .vmdk files must be uploaded to the datastore area
of the host machine which is to be found under Summary/Datastore. Right click on the datastore1 to
browse the datastore, and then in the new window which opens upload the two .vmdk files. Note: after
uploading the second file only one file is shown.
3. Now select “new virtual machine” from the Summary/commands menu and then use the following
steps:-
• Configuration – custom
• Name – give a name to the machine
• Datastore – select the datastore1
• Virtual Machine Version – Virtual Machine Version: 7
• Guest Operating System – Linux : Version – Other 2.6x Linux (32-bit)
• Number of virtual processors – select the number depending on the host (minimum 2 is
recommended)
• Memory Configuration – minimum 1GB, recommended 2GB)
• Networks connections – connect 2 NICs

• SCSI controller – leave the defaults

• Disk – Use an existing virtual disk
• Disk File Path – Browse to datastore where the .vmdk files were stored
• Virtual Device Node – leave the defaults
• Finish
4. This step is only required if it is intended to use the WAN interface on the AMC controller
• Select the local host Configuration/Networking
• Select Add Networking
• Connection Types – Virtual Machine
• Create a virtual switch – vmnic1
• Network Label – WAN
• Finish
• Select the local host Configuration/Networking/Virtual Switch:vSwitch0/Properties
• In the new window select Ports/VM network/Edit
• In the new window select General/Network label: - LAN
• OK/Close
• Select the newly created virtual machine - Resource Allocation/Edit/Hardware/Network
adapter 1 /Network Connection – choose WAN
• Select the newly created virtual machine - Resource Allocation/Edit/Hardware/Network
adapter 2 /Network Connection – choose LAN
• OK
5. Resource Allocation and other settings
• Select the newly created virtual machine - Resource
Allocation/Edit/Resources/CPU/Reservation - maximum
• Select the newly created virtual machine - Resource
Allocation/Edit/Resources/Memory/Reservation - maximum
• Select the local host Configuration/Virtual Machine Startup/Shutdown/Properties
o Select “Allow virtual machines to start and stop …..”
o Highlight the newly created virtual machine and move it up under “Automatic Startup”
6. Select “Power on the Virtual machine”
Opening the console of the virtual machine, the boot sequence of the AMC controller can be seen.

NOTE.
At first start up the console shell will give some error printouts, disregard these, as they will not be
present on rebooting after the AMC controller has been configured.
Example:
NOTE. The VMware version of the AMCC requires a serial-number entry. If the AMCC sw is newly
ordered the download link will also have the serial number in it.
The serial number has to be entered within the WebGUI into the controller and the controller checks
online whether it is valid. (DNS has to be configured!)

An internet connection is required for registration, and that, once saved, the serial number can´t be
removed or edited. Please provide our support team with your systems revision number and MAC
address (lower right hand corner in the WebGUI ) if a serial number has to be removed.
__________________________________________________________________________________
Please note that without the serial number further updates of the AMCC, via Install / Update, will not be
possible.
__________________________________________________________________________________

Completing the installation of the AMCC consists of the following steps, which are covered in
this document:
1. Configuring MX-ONE with number plan, number conversion, extensions, SIP-trunk and routes.
2. Setting up the relevant parameters in the AMCC such as IP-address, gateway, PBX-endpoints and
users.
- In this example the AMCC is placed behind the company firewall. (See picture on page 12) This means
only the LAN interface shall be used and NAT activated. When placing the WAN interface directly on the
Internet, NAT should not be activated.
- Always update the AMCC to the latest firmware before starting the installation.
- All the MX-ONE configuration examples shown is based on MX-ONE 5.0
- MX-ONE 5.0 will need a free license for one SIP trunk.
- The examples for AMCC is based on version 10684.16.x
- To setup data for a client please see the Portal help doc. *(see paragraph 5)
4 Configure MX-ONE
4.1 General MX-ONE configuration

In order for a successful implementation the PBX needs to be set up to handle the calls properly, present
numbers correct and convert the numbers passed along to the AMCC in an international format. This
chapter shows a typical MX-ONE setup, usually the settings already exist. In section 4.8 there are the
settings specific for AMCC.
Minimum Baseline for AMCC is MX-ONE 4.1 to support packet size 20 ms.
4.2 Number analysis and number series

For the system to be able to state to which function a number belongs, it is necessary for the number to
be defined as a specific number type. This is achieved with commands that affiliate a number or number
series to a number type. First we need to decide which number series we want to use and to what. When
it comes to defining the number series, there are a few things to keep in mind.
Doc. No. ASE/FMC/GEN/0004/0/17 10/54

1. Naming for the same number or number series may be different depending on the application you
are configuring.
2. DID numbers refer to the number series provided by the local service provider and are generally
used to create extension numbers and common numbers like main number or Help desk numbers. As an
example, if the service provider gives you a number series of 08 56867100-67200, we can see that the
08 is the area code and the 568 is the public exchange number. The last 5 digits are what the public
network is sending in to the exchange and also will be the DID number series used to differentiate
between internal extensions (67100-67200). You would then create a 5 digit numbering plan, where
67100-67200 would be the internal number series.
3. You could then decide to reserve 67100 as your main external number. Then, assuming you
have two attendant consoles, you would reserve 67101 and 67102 as attendant extension numbers. You
might want to reserve 67103 for future expansions. You would then use the remaining numbers for user
extensions and service numbers (e.g. Special FMC numbers). Remember that part of this series would
be for user extensions and the rest for the service numbers and help desk, GH and CTI groups. This is
particularly important when configuring DID number range as this range is will be used for defining the
extension numbers that will be used to create user extensions in the system (see 4 and 5 below for
details)
4. f a company has 45 users, they would exclude the 3 numbers mentioned above and user
extensions numbers would begin at 67104 to 67148. These would be the range of numbers used to
create user extensions. The rest of the numbers (67149-67200) can be used to define the special FMC
numbers, help desk numbers, conference bridge numbers, service numbers, common area numbers,
(conference rooms, reception areas, etc…), external access to Voice Mail services or auto-attendant
services.
5. Then there are internal service codes for dialling externally and reaching the attendant, which are
usually 1 or 2 digit codes like 0 and 9 or 00 and 09 respectively. These are defined as common for all
internal users in the system and applications. As an example, 00 would be dialled for accessing the
outside public network and 09 for dialling internally to the operator (attendant).
6. Then there is the international access code or prefix, used to inform the public exchange that you
are dialling an international number. In Europe, this code is 00, whereas in North America it is 011. As an
example, if you were dialling a number from Sweden to France (+33 1 4233 1234). The internal user
would dial the public access code 00 and then the international prefix 00 then the country code for
France (33) and finally the local number (1 4233 1234). So it would look like 00 00 33 1 4233 1234.
Doc. No. ASE/FMC/GEN/0004/0/17 11/54

Used settings in the example configuration:
MX-ONE
IP-address: 10.103.61.13
SIP route destination for Call through 67149
SIP route destination for SIM switch 67150
Clients SIP ext. and their mobile numbers 67104 +46705263966
Clients SIP ext. and their mobile numbers 67105 +46705267786
Aastra Mobile Client Controller (AMCC) IP- networking information
External IP-address: 89.92.21.18

Internal IP-address: 10.103.61.93
Network Mask: 255.255.255.0
Default IP Gateway: 10.103.61.1
DNS server address: 10.103.61.1
NTP server address: 10.103.61.91
Doc. No. ASE/FMC/GEN/0004/0/17 12/54

4.3 Initiate number series

In the example below, we use 67104 and 67105 as extension numbers for the users
MDSH> number_initiate -numbertype ex -number 67104..67105
To verify your work, type the following command;
MDSH> number_print -numbertype ex
This is a fictitious destination number used for LCR (Least Cost Routing).
MDSH> number_initiate -numbertype ed -number 068
MDSH> number_print -numbertype ed
To initiate Least Cost Routing Access Code.
MDSH> number_initiate -numbertype lc -number 00
MDSH> number_print -numbertype 00
Note: There are a handful of destination numbers which are Emergency numbers (000, 110, 112, 118,
119 and 911). Together with your mobile operators´ service numbers they will result in pure cellular calls
where AMC+ should be inactive. Please make sure these are not part of you number plan.
Doc. No. ASE/FMC/GEN/0004/0/17 13/54

4.4 Extensions & Common service profile

To a generic extension, a number of categories are affiliated. Those categories are collected in a number
of Common Service Profiles (CSP’s) and to every generic extension, a CSP must be affiliated. Virtual
generic extensions are created when directory numbers with a CSP is initiated in the exchange. These
virtual generic extensions then exist in the exchange and it will be named generic extensions when
terminals are affiliated.
In order to create the extensions we must first create a CSP to be used with your AMC-extensions.
Note: The parameters in the example below will need to be adapted to reflect on your local telephony
policies.
MDSH> extension_profile -I --csp 0 --ext-traf 1103151515 --ext-serv

1001000110003000000000000000 --ext-cdiv 111000111010 --ext-roc 000001 --ext-npres 000100
MDSH> extension_profile -p --csp 0

-
Now we can initiate the extensions.
MDSH> extension -i -d 67104 --lim 1 --csp 0 --max-terminals 1

MDSH> extension -i -d 67105 --lim 1 --csp 0 --max-terminals 1
MDSH> extension -p -d 67104,67105
NOTE: For the MX-ONE, prior to release 5.0, it is possible to use dual forking (--max-terminals 2) for
AMC users but you cannot use 2 SIP extensions. Therefore initiate a password on the extension which is
not disclosed to the user. From MX-ONE 5.0 onwards it is possible to have up to 4 SIP terminals.
MDSH> auth_code –i
Then we need to define the IP-extensions, which are going to be used for outgoing calls.
MDSH> ip_extension -i -d 67104,67105
MDSH> ip_extension -p -d 67104,67105
Doc. No. ASE/FMC/GEN/0004/0/17 14/54

4.5 Routes
If no Route to the Public network exists then this is an example:
Initiate route category.

MDSH>ROCAI:ROU=1,SEL=0120000000000010,SIG=111110000030,
TRAF=03151515,TRM=5,SERV=3100000007,BCAP=111111;
Initiate route data.
MDSH> RODAI:ROU=1,TYPE=SL60,VARI=15420000,VARO=06410002,
VARC= 00000210;
Route equipment initiate
MDSH> ROEQI:ROU=1,TRU=1-1&&1-15,EQU=1-1-00-1;
MDSH> ROEQI:ROU=1,TRU=1-16&&1-30,EQU=1-1-00-17;
Route external destination data initiate
MDSH> RODDI:DEST=068,ROU=1,ADC=0005000000000250000001110001,SRT=4;
MDSH> ROCAP:ROU=1;
MDSH> RODAP:ROU=1;
MDSH> ROEDP:ROU=1,TRU=ALL;
MDSH> RODDP:DEST=068;
Synchronization may need to be configured on this route.

MDSH> trsp_synchronization
Doc. No. ASE/FMC/GEN/0004/0/17 15/54

4.6 Initiate routing

With the initiation of Least Cost Routing, we allow the system to make the selection of the most
economical route for an outgoing call. The example below is showing that when a user is trying to
call a colleague by dialling the complete external number (as they should be stored in the phone
book) we analyze the dialled number, truncate the appropriate number of digits to treat it as an
internal number.
MDSH> LCDDI:TAB=ENT,ENTRY=0000468568671,TRC=10,CONF=N;
Calls that are not internal, we route to the new route we created above. You are of course free to
use any in the system existing outgoing route.
MDSH> LCDDI:TAB=FDT,FRCT=1,PRE=068,TZONE=1;
MDSH> LCDDI:TAB=DNT2,ENTRY=00001,FRCT=1,TRC=2;
MDSH> LCDDI:TAB=DNT2,ENTRY=000046,FRCT=1,TRC=6,pre=0; (Sweden national nr)
Doc. No. ASE/FMC/GEN/0004/0/17 16/54

MDSH> LCDDP:TAB=ENT;
MDSH> LCDDP:TAB=DNT2;
Doc. No. ASE/FMC/GEN/0004/0/17 17/54

4.7 Number Conversion

Conversion is performed whenever a number is sent or received to or from the network,
independently of the type of signalling system. The number conversion can be made for the whole
system or depending on the route number of the route that delivers or receives the call.
It is important that numbers are converted correctly so that your AMCC environment will
work properly.
Below are the following types of number conversion handled:
• Sent A-number
• Received national and international A-number for internal number presentation
• Received national A-number number conversion for internal number presentation (SIP
extensions) into international format
• B number conversion from SIP extensions when received in international format
• Received B-number from AMCC trunk, prefix with 0000 (see 4.9)
• Sent public A-number for internal calls via sip trunk (see 4.9)
• Make received national mobile A-numbers into international format before being sent over the
SIP-Route to the AMCC. (see 4.9)
Sent A-number (If required*)

This entry is to format the extension and send the whole public number to the public network.
* Some Network Operators just only allow send out the extension number.
MDSH> number_conversion_initiate -entry 6 -conversiontype 1 -pre 8568

-numbertype 10
MDSH> number_conversion_print -conversiontype 1 –numbertype 10
Received national and international A-number number conversion for internal number presentation.
(none SIP extensions)
This entry is to format national and international incoming number into numbers that can be dialled
from the PBX.
Example; An incoming call from Denmark (international number) would be presented to the PBX as this:
45 6 4114XXX, so now we need to add the leading 4 zeros (00=LCR access, 00=international access
code) to make possible to call back. We also need to take care of incoming national numbers and add 3
zeros (00=LCR access, 0 national access code).
Doc. No. ASE/FMC/GEN/0004/0/17 18/54

MDSH> number_conversion_initiate -entry 1 -conversiontype 2 -numbertype 1 -pre 0000

Doc. No. ASE/FMC/GEN/0004/0/17 19/54


Doc. No. ASE/FMC/GEN/0004/0/17 20/54

Received national A-number number conversion for internal number presentation (SIP extensions) into
international format.
When an international call (numbertype 1) is presented to a SIP extension + is automatically added.

Incoming national numbers (numbertype 2) however, needs to be converted to international (numbertype
1) and add international prefix (46 in this case). Then the SIP extension will add a + in front of the
number.
MDSH> number_conversion_initiate -entry 1 -conversiontype 5 -numbertype 2 -newtype 1 -pre 46

Doc. No. ASE/FMC/GEN/0004/0/17 21/54

B number conversion from SIP extensions when received in international format.

This entry is to format numbers sent from SIP extensions in international format. The + will be
converted as numbertype 1 and prefixed with 00=LCR access and 00=international access code.

Doc. No. ASE/FMC/GEN/0004/0/17 22/54

Doc. No. ASE/FMC/GEN/0004/0/17 23/54

4.8 AMCC MX-ONE Configuration

We need to initiate 67149 and 67150 to be used as Call through number and SIM switch number
(Special FMC Numbers) Be aware that these numbers needs to be in the DID number series.
MDSH> number_initiate -numbertype ed -number 67149,67150
MDSH> number_print -numbertype ed
Setup the connection between MX-ONE and AMCC Controller.
SIP Route to AMCC
Initiate route category.

MDSH> ROCAI:ROU=2,SEL=7110000000000010,SIG=0111110000A0,
TRAF=03151515,TRM=5,SERV=3100000007,BCAP=111111;
Initiate route data.
MDSH> RODAI:ROU=2,TYPE=TL66,VARI=00000000,VARO=00000041,
VARC= 00000040;
MDSH> sip_route -set -route 2 -uristring "sip:?@10.103.61.93" -fromuri1 "sip:+?@10.103.61.13" -

accept REMOTE_IP -match 10.103.61.93 -trusted ID_ASSERT -protocol tcp
Y;
Note
If MTC number is to be used in the AMC Controller -trusted NO_TRUSTED
Initiate a trunk.
MDSH> roeqi:rou=2,tru=1-1;
MDSH> rocap:rou=2;
MDSH> rodap:rou=2;
MDSH> sip_route –print –route 2;
MDSH> roedp:rou=2,tru=all;
-----------------------------------------------------------------------------------------------------
Destinations to AMCC
Doc. No. ASE/FMC/GEN/0004/0/17 24/54

In this case 2 FMC numbers are to be routed into the AMCC Controller.
Route external destination data initiate.

MDSH> roddi:dest=67149,rou=2,adc=0227000000000250002001110001;
MDSH> roddi:dest=67150,rou=2,adc=0227000000000250002001110001;
MDSH> roddp:dest=67149&67150;
Doc. No. ASE/FMC/GEN/0004/0/17 25/54

4.9 Number conversion related to AMCC configuration

Received B-number from AMCC trunk, prefix with 0000 (00=LCR access and 00=international access
code). (Similar to the conversion from SIP extensions earlier….)
This is necessary if the GSM numbers in the controller are programmed in international format (+).

Doc. No. ASE/FMC/GEN/0004/0/17 26/54

Sent public A-number for internal calls via sip trunk
Internal calls to AMC client, not in Wi-Fi, should be present with complete public number.

–newtype 2
Doc. No. ASE/FMC/GEN/0004/0/17 27/54

Make received national mobile A-numbers into international format before being sent over the SIP Route
to the AMCC.
This is used if GSM numbers in the AMC Controller are defined in international format (+).
e.g. Mobile numbers 7xxxxxxx received from PSTN are numbertype 2 (national ).
67149 and 67150 is Call through number and SIM change number.
MDSH> number_conversion_initiate -entry 7 -conversiontype 1 -numbertype 2 -pre 46 –targetdest 67149 –

newtype 1
MDSH> number_conversion_initiate -entry 7 -conversiontype 1 -numbertype 2 -pre 46 –targetdest 67150 –
newtype 1
MDSH> number_conversion_print -conversiontype 1 –numbertype 2 –entry 7
Doc. No. ASE/FMC/GEN/0004/0/17 28/54

Backup the system

MDSH> data_backup
Doc. No. ASE/FMC/GEN/0004/0/17 29/54

5 Configuring the AMCC
5.1 Establishing a connection to the AMCC

For the web configuration, the web browser must support frames, but nowadays this applies to almost
every modern browser. For checking the input, on some pages JavaScript support is also required; make
sure this is enabled in the web browser.
The LAN1 interface of the Aastra AMC Controller is configured to the following parameters by default.
Network protocol: TCP/IP
IP-Address: 10.0.0.205
Subnet mask: 255.255.255.0
Therefore in order to be able to communicate with the AMC Controller a connection has to be
established between web browser on a PC and the controller. This may be done in two ways
1. Change the default IP-address of the controller, via the console interface, to a valid address for the
network. This may be done through the VMware console in the vSphere client or via a locally connected
terminal/screen on the AMCC-30/AMCC-130; logging in with user: root and password: sesam.
From the main menu select “1: Configure first LAN interface” then from the next menu select “2: Change
IP address”. Enter the new IP address, select “S: Save and back to previous menu” and then importantly
select “A: Apply configuration”. It is also required to “Configure Routing”.
After configuring IP address and routing, use the Web Gui. https://10.103.61.93 . Now you will be forced
to initiate a new password. Apply configuration and continue with 5.4
Doc. No. ASE/FMC/GEN/0004/0/17 30/54

2. Configure the PC to an address in the same subnet, as for example 10.0.0.206.

Connect a LAN cable between your PC and the Controller (ETH 0). To enter the graphical user interface
(GUI) of the AMCC and to begin the configuration, enter https://10.0.0.205 in your browser’s address
field. For some products, the correct protocol is HTTP, so you have to enter http://10.0.0.205 to connect
correctly.
Possibly the browser will ask you to accept a certificate and warn you that it is self-signed. To continue
you will have to accept this certificate for establishing an encrypted connection to the AMCC.
Enter the username and password. The defaults values are as follows:
Username: admin
Password: sesam
For security reasons, the password has to be changed directly. Set a new password (Apply Config) and
log into the Controller again. NOTE: You have to change the LAN cable to ETH 1.
After having logged in successfully the HTML front end of the Aastra AMC Controller should be seen.
- Select your language. ENGLISH/DEUTSCH
5.2 Configuration of the LAN Interface

Under Network/LAN int 1 tab in the web GUI of the AMC controller the IP-address and netmask may be
configured.
NOTE: There are two WEB GUI presentations:

GUI MODE BASIC Cover the most basic settings you need for getting started.
GUI MODE ADVANCED. Every setting can be done.
(Some of the pictures are from older AMCC and have not been changed on 16.3)
Doc. No. ASE/FMC/GEN/0004/0/17 31/54

! Remember to “Save” and “Apply the configuration”!
Before getting started...

Whenever the “>>APPLY CONFIGURATION<<” string in the AMC controller
web GUI turns yellow, the configuration needs to be saved internally in the
controller. This is made by clicking on the >>APPLY CONFIGURATION<<
string or you risk losing the setting when you leave the present tab, throughout
the document we try to remind you about this by the recommendation:
! Remember to “Apply the configuration”!
5.3 Configuration of the default gateway

Under Network/Routing tab in the web GUI of the AMC controller, configure the default gateway:
Select Add and then use the following settings as an example:
Destination = 0.0.0.0, Net mask = 0.0.0.0, Gateway = 10.103.61.1, Interface = LAN1
This will give basic connectivity to get started; the routing tables may subsequently need to be modified
dependent on the security arrangements.
Doc. No. ASE/FMC/GEN/0004/0/17 32/54

! Remember to “Apply the configuration”!
Now you can disconnect the temporary LAN cable and connect the controller to the company LAN.
Via a web browser, enter Ex. https://10.102.61.93
5.4 Time and date settings

Under System/Basic tab in the web GUI of the AMC controller:
Set the current time, date and time zone, the IP address of your DNS and system name.
NOTE: Use a city in the same time zone as yours. If you use, like GMT+1, the time will not change when
summer/winter time begins.
Under Network/NTP tab:
Doc. No. ASE/FMC/GEN/0004/0/17 33/54

Select “Add” and configure the available NTP server(s). Select “preferred” to grant the server priority
over any others. This server may be your PBX master server or any other available NTP server; use
hostnames or IP addresses. Tick “Active” to activate the NTP service.
5.5 Configure the PBX and Users – Global settings

Under Telephony/Settings tab in the web GUI of the AMC controller and under Global Settings configure
the following:
Enable Call-Through Progress Indication – gives playback of a progress indication tone for call-through
the PBX calls.
Enable Client Early Media – to get ring tone when calling internal
Enable busy sound in Wi-Fi - to have busy tone when calling to the public network
Disable Inband DTMF detection – if the PBX is going to use RFC2833 or SIP INFO
DON´T disable number conversion – if you have mobile phones like iPhone where the telephony
application does not accept “#” being sent from an external application. For further information on
number conversion – see Features tab!
Enable DTMF invoked handover – makes it possible to invoke a handover by sending the DTMF
sequence **00. Primarily for testing purposes and not needed for handover on Android to work (using
“IMS: to GSM” number defined among FMC numbers).
Unavailable Timeout – default 35s, set longer, 120s, to have the call controlled in the PBX
DTMF Duration – used for RFC2833 signal duration, leave empty, default 100ms.
RTP payload-type for DTMF – leave empty, default 101 will be used
MWI Call Number – not used, function not available in AMC3
Forced ringing on early media – if the PBX does not support early media
Use P-asserted identity – if the PBX is configured to trust the AMC controller
Doc. No. ASE/FMC/GEN/0004/0/17 34/54

Activate APN – Apple Push Notification, to activate a pop-up asking the user if AMC+ should be fronted
in the GUI via the OS on iPhones. For this to work, the Settings - Notifications - settings for AMC+ on the
phone as such must allow and trust them. Notification requests require valid Apple Push Notification
certificates on the AMC Controller. For Apple Push Notifications to work ports 2195 and 2196 have to be
opened in the firewall. NOTE: On iPhone Client 3.5 (AMC3) this is not needed but make sure that all
phones are upgraded before you remove the setting.
Process rinstance tag – to handle the rinstance parameter in the SIP contact header
Number of Cellular-digits to match – default is 10; if the number of digits received from the PSTN side or
the format differs a configuration to fit your needs is possible here.
Don’t send P-Asserted Identity – do not include the P-asserted identity header in the signalling towards
the PBX.
Don’t send P-Preferred Identity – do not include the P-preferred identity header in the signalling towards
the PBX.
Don’t send Remote Party-ID – do not include the Remote Party-ID header in the signalling towards the
PBX.
Don’t send Diversion for SR over reg. - If no SIP Trunk is used, the controller sends a Diversion Header
for Static Roaming calls. Do not include.
! Remember to press “Save”!
Doc. No. ASE/FMC/GEN/0004/0/17 35/54

Under SIP Options:

Registration Timeout Interval – determines the registration timeout interval towards the PBX. The value
in seconds will also be used for subscribers to Pickup Groups and Message Waiting Indications. Re-
registrations will be performed after the first half of the interval specified here. Set the Registration
Timeout interval to 300 (300-600)
Registration Retry Interval. – If a register towards the PBX fails, wait that amount of time (in seconds)
before retrying (default: 30). Blank
External IP for NAT - the external IP address on the outside of the Fire Wall. External IP for NAT shall be
set to the public IP of the controller if it is not directly connected to the internet.
Attempt Near-End NAT Pinhole. – If you experience problems with the RTP-stream (e.g. no speech),
activating this setting might fix this.
TCP keepalive Interval. – Specify when the first keepalive shall be sent. The interval is specified in
seconds after last TCP packet. Default: 0. Blank
SBC call admission control. – This setting lets you specify the maximum number of parallel Wi-Fi calls
over the SBC Blank
Time interval for registrations. – Time interval in seconds for “X” registration to the PBX. Default is 10
seconds. Default: 10 sec. Blank
Max value of simultaneous registrations. – Determine the value of max simultaneous registration for the
time interval. Default: 200 registrations. Blank
! Remember to press “Save” and “Apply the configuration”!
Under RTP Options:

TOS for outgoing media – Specifies the TOS byte that is to be put into the IP-header for all voice
payload traffic leaving the controller. This field is used for DiffServ and Explicit Congestion Notification
(ECN).
Doc. No. ASE/FMC/GEN/0004/0/17 36/54

RTP Session Timeout – consider reducing this setting if you experience no speech in calls at times of
high load. Default value: blank.
! Remember to press “Save” and “Apply the configuration”
Under Load Limit Configuration: (Only on VMWare system)

Max number of calls. Specify the maximum number of concurrent call allowed on this virtual system.
! Remember to press “Save” and “Apply the configuration”
Configuring the PBX and Users – Profiles

Under Telephony/Profiles tab in the web GUI of the AMC controller:
At least one profile name MUST be configured. It might not be really needed for the PBX except for the
setting of the internal number length which is to prevent internal numbers being prefixed with a +.
Name – whatever you like e.g. Dummy
Internal length – a value > internal length e.g. 100 (to effectively disable the restriction)
Minimal Outgoing Format – set to Subscriber
! Remember to press “+” to save!
5.6 Configure PBX and Users – Endpoints

Under Telephony/Endpoints tab in the web GUI of the AMC controller, the network data for the PBX is
configured:
Common name - whatever you like, only used internally e.g. the name of your PBX Hostname/IP -
hostname or IP address of your PBX
Local Interface - LAN 1
Foreign Port – 5060 or leave blank
Doc. No. ASE/FMC/GEN/0004/0/17 37/54

Preferred Codec – first codec offered in the INVITE e.g. g711alaw 20ms (Use 20ms to avoid additional
delays due to trans coding in the controller)
Outbound Proxy – Enables you to statically specify the next hop for all SIP messages towards an
endpoint. A static route header to accommodate statically defined next hop.
NOTE. Also remember to have the same packetization-time for the default “ip_domain” in MX-ONE to
which the AMCC belongs. If there is other equipment that requires 30ms, it needs to belong to another
“ip_domain”.
5.7 Configure PBX and Users – SIP Trunk

Under Telephony/Trunk tab in the web GUI of the AMC controller, the SIP trunk towards the PBX is
configured:
Name – whatever you like, only used internally e.g. HF
Endpoint – Pull down list of previously define endpoints
Port – SIP trunk start port, defaults to 11000
Diversion Prefix – not necessarily used (MX-ONE case)
MTC Prefix – The number entered here will replace any A-party number sent in the From header
towards the PBX . This may be needed if the public network uses number screening and rejects call
attempts where the A-party number does not belong to the PBX number series. See also the SIP route
settings in the MX-ONE.
Active Registration – will require configuration on the PBX side if used, Disabled recommended
For remaining settings use default values.
Doc. No. ASE/FMC/GEN/0004/0/17 38/54

5.8 Configure PBX and Users – PBX

Under Telephony/PBX tab in the web GUI of the AMC controller, an Endpoint and a Profile are
combined:
Common name - whatever you like, only used internally e.g. HF
Endpoint – Pull down list displaying previously defined end points
Use ‘inactive’ for Hold – defaults to Disabled, meaning ‘sendonly’ will be used in SDP body
From Converter Profile – not required
To Converter Profile - Pull down list of previously defined profiles
SIP Trunk - Pull down list of previously defined trunks
Country - Pull down list of installed countries, for server generated tones
DTMF Type – SIPINFO (Cisco) i.e. using dtmf-relay towards the PBX (RFC2833 is for example not
supported if you have an EMG LIM with MX-ONE)
Mode – SIP registration
For remaining settings use default values.
! Remember to press “+” to save (scroll right)!
Doc. No. ASE/FMC/GEN/0004/0/17 39/54

5.9 Configuring PBX and Users – FMC Numbers

Under Telephony/FMC Numbers tab in the web GUI of the AMCC the special numbers are configured
which will be sent from the PBX to access some call services.
Type:
Call-Through – for calls originated in the GSM network (equivalent of the R1 number in MX-ONE)
SIM switch – when a change of SIM card has been made in the mobile phone this number is called to
activate the new GSM number for the user.
IMS: to GSM – to handle handover from WLAN to GSM, Only needed for Android phones. Example not
shown here, follow the same procedure as for Call-Through and SIM switch. (Page 24)
NOTE. GSM to IMS should not be used.
Number – as configured in the PBX. (Destination, created on page 25)

Active – to enable handling of the number
Endpoint - Pull down list of previously defined end points
Note: Port is no longer set here (clients should use 5062 towards the AMCC to avoid strange behaviors
as port 5060 is used internally by the SBC in AMCC!)
More call services (Type), not used in this example:

Call-Reverse – not to be used, does not work
Callback – for GSM call back
MTC – to strip away prefix added by PBX before handled as display and call log info
Voicemail – corporate voice mail number
IMS: to WLAN – for handover GSM to WLAN, can be any arbitrary number, not used
Doc. No. ASE/FMC/GEN/0004/0/17 40/54

5.10 Configure PBX and Registrations

Under Telephony/Registrations tab in the web GUI of the AMC controller, the B2BUA “Back to Back User
Agents” (SIP extensions) are configured towards the PBX:
PBX Username – This should be the same as the PBX number
PBX Password – must be set if configured in the PBX (auth_code)
PBX Number – SIP extension number in the PBX
PBX – a pull down list of previously configured PBX “identities”. In this case we have HF.
5.11 Configure PBX and Users – User Accounts

Under Telephony/User tab in the web GUI of the AMCC, account for the mobile client is configured and
then associated with the PBX registration:
SIP Number – this must be a unique number which is different from the PBX number
SIP User Password – this is the password to be used by the client when registering
Registrations – a pull down list of configured PBX registrations
Activate User – used to enable or disable a user (register/unregister the ext. number in the PBX)
Cellular Number – a pull down list of configured GSM numbers (done later)
Doc. No. ASE/FMC/GEN/0004/0/17 41/54

5.12 Configure PBX and Users – Cellular

Under Telephony/Cellular tab in the web GUI of the AMCC, the Cellular number(s) for a user are
configured. The first number configured for a user is then assigned to that user in the Telephony/User
settings. More than one number may be assigned to a user for use with SIM change:
SIP User – a pull down list of configured users
Cellular Number – this serves two purposes:
a) When the client is out of Wi-Fi, this number is used to make a GSM call. Note that if international
format is not used (taken care of in PBX number conversion) then external line access code and
international prefix must be used e.g. 000046...
b) For authenticating the user when calling from GSM network (note: (Default) the last 10 digits are
matched if not configured differently, in our example we have 9 digits.
Doc. No. ASE/FMC/GEN/0004/0/17 42/54

5.13 Configure PBX and Users – User Settings

Under telephony/User Settings tab in the web GUI of the AMC controller the various services for a user
are configured, below shows the default after a user has been initiated. Edit the user to make changes:
Static Roaming – set to enable to allow incoming calls to reach the mobile via the cellular number, must
be enabled to allow Wi-Fi/GSM handover.
Use DMC for Cellular – (Direct Media Connect)
Call Waiting – use depends on if the PBX shall handle this, if for example only single line access is
configured in the PBX for AMC SIP extensions.
Subscribe MWI – this can be enabled so that the client receives a notification from the PBX when a voice
mail or manual message waiting is present.
Call Reverse – do not use, causes problems if set.
Security – use SRTP between client and controller (note: must be enabled in the client also if enabled in
the controller, to work).
Activate DND – this shows the DND status of the user when activated/deactivated in the client.
Activation makes the user temporarily unavailable. (Note; when enabled, static roaming gets disabled).
The setting may also be activated/deactivated for a user from here.
Allow new Cellular-Number – enables automatic authorization of a new mobile number after a SIM
switch (without having to request the administrator to manually enter it first) but also implies less access
control (the capability has to be supported in the client).
!
Remember to press “+” to save!
Doc. No. ASE/FMC/GEN/0004/0/17 43/54

5.14 PBX Access Codes

Remove all PBX Access Codes, these are not used for MX-ONE.
5.15 Backup the system.

To download the configuration to another server, go to System/Backup and press Save on Download
Configuration. Chose were to save the Configuration.
NOTE: The Apple Push hotfix and private certificates will not be in this backup.
NOTE: The password is also connected to the backup. If you change password and later have to make a
“Restore configuration” the old password is now back.
(This data can then be used for recover a system)
Check the customer backup routines.
Doc. No. ASE/FMC/GEN/0004/0/17 44/54

Under System/Rollback there is a possibility to make a backup of the system using “Save Configuration”.
Saves locally on the Controller and can be used for rollback of the latest data.
Apply Configuration and Restart will automatically create a backup.
Doc. No. ASE/FMC/GEN/0004/0/17 45/54

6 Other AMCC/MXONE services that could be necessary for

the installation
6.1 Other AMCC services – Number conversion

Although number conversion shall normally be done in the PBX, one special number conversion is
required to overcome the barred handling of “#*” by the telephony application in iPhone.
In the AMC client, if a number is entered with a +, the client will translate this to #* in front of the number
in order to send it as DTMF since, of course, there is no DTMF for +. The #* is then replaced with +
again in the controller before sending it to the PBX.
For iPhone Apple has limited what characters sent from an external application will be accepted by the
telephony application. Instead of the non allowed characters * and #, the client in this case will insert
0000 in front of the number so we have to do a number conversion to convert back again to +.
Doc. No. ASE/FMC/GEN/0004/0/17 46/54

6.2 An example of configuring the AMCC for internet
As mentioned in the overview there are several methods of configuring the AMCC and the network to
provide secure internet access without compromising the security of the network
For the cases where only one network interface is used, like for AMCC-30 which has only got one, it is
LAN Int1 that is used together with an external firewall and the example below is not valid.
The AMCC can be connected directly to the internet on the WAN port (eth0) and firewall and routing
rules are set up to provided/restrict access. Firstly the WAN port has to be configured under
Network/WAN Int. Here the public IP address is configured together with the net mask and default
gateway. Address xxx.xxx.xxx.113
! Remember to press “Save”!
Doc. No. ASE/FMC/GEN/0004/0/17 47/54

Next some firewall rules need to be configured to allow the clients’ access to the LAN via the WAN.
In this case three protocols are enabled through the WAN – UDP and TCP on port 5062 and TCP/TLS
on port 5061. In most cases only one is required when it is decided which is to be used in the clients.
Since the client is in the public domain, the source IP and port can be anything - these are left fully open.
However we know the destination IP address is the public IP address of the WAN and which port to be
used.
Two additional protocols are enabled for the Apple Push Notification communication with Apple via ports
2195 and 2196. This is required to display a pop-up in on iPhone to front AMC+, if so desired by the
user. The alternative is to manually front AMC+ on the display.
The above settings will allow connection through the WAN interface to the LAN interface for client
registration and calls from the public internet.
In the case we are using a host name in the client such that when the client is in the local Wi-Fi network
the internal DNS will resolve the hostname to the internal (LAN) IP address and thus register locally.
When in the public network the public DNS will resolve the hostname to the public IP address of the
WAN port.
However to allow access through the WAN it is necessary to configure the AMCC so that it knows to
which domain it belongs. This is configured under Features/FMC Domains.
Doc. No. ASE/FMC/GEN/0004/0/17 48/54

Define the routing rules now that public access is available via the WAN interface, it may be desirable to
modify the routing rules which were initially configured.
The initial setting allowed access to all IP addresses; we now limit the exposure to only the xxx.xxx.y.y
network. This could be defined even further to only allow access to the IP address of the PBX but this
could create problems when calling other SIP terminals if direct media is used.
Note: With multi gateway systems you probably will need to allow the IP addresses of each gateway
through, especially if load distribution is used.
6.3 Security – TLS Certificate Configuration

In the Security – TLS Certificate Configuration you have functionality for handling certificates. You can:
• upload a private key and the corresponding certificate, together with an intermediate certificate
from a trusted Certificate Authority
• create a self signed certificate and private key on the AMCC
Doc. No. ASE/FMC/GEN/0004/0/17 49/54

• download the private key or server certificate from the AMCC

• download TLS certificates for clients
To generate a private key and a Certificate Signing Request to be sent to a trusted Certificate Authority
you have to logon to the AMC Controller via command line. In the example below we do the work with
the certificates in a separate directory created for this purpose, the directory can be named to anything –
in this case /root/amcc-cert/. File names used below are only examples of names, chosen to explain the
content as much as possible. They can just as the directory, have any name you like.
Go to directory /root/amcc-cert/ and run the commands in bold:
create a password file, for example; echo “password” > password.txt
generate the private key; openssl genrsa –out private.key –passout file:password.txt –des3 2048
generate the CSR; openssl req –out certificate_request.csr –new -key private.key -passin
file:password.txt
For the last command some information has to be supplied:
Country: countryOfHeadOffice
State: stateOfHeadOffice
City: cityOfHeadOffice
Common name: amccDomainName
Organzation and Organizational Unit Fields: CompanyName
Send in the CSR to the Certificate Authority and make sure you keep all the files you have worked with
above, for future use!
When you download the certificate from the Certificate Authority, and if an intermediate
certificate/certificate chain is also supposed to be downloaded (different certificate providers have
different setup), they are normally in text format. The file extensions used below follow the convention for
certificates encoded as ASCII PEM. “.crt” has been used to represent certificate files of this type.
As AMCC cannot handle a password protected private key, before the received certificate can be
uploaded via the web GUI on AMCC, the password needs to be removed from the private key. Do this
from the command level on the AMC Controller. Again go to the directory where you work with the
certificates. For example /root/amcc-cert/ and run the commands in bold:
remove the password from the key; openssl rsa -in private.key -out privatenopass.key
verify/display the key; openssl rsa -in privatenopass.key -noout –text
Now move to the web GUI, and browse to get the paths to the file containing the private key without
password, for example privatenopass.key and the file containing the server certificate from the
Certificate Authority, for example certificate.crt, in the WebGUI and press “Upload” for the “Private
Key/Certificate”.
Doc. No. ASE/FMC/GEN/0004/0/17 50/54

Browse to the path of the file containing the intermediate or certificate chain, if you were supposed to
download these as well from your Certificate Authority. Below this file has been called certchain.crt.
Press “Upload” for the “Add CA Certificate” and it will be uploaded.
Press “Apply the configuration” to get the certificates activated.
You might need to restart your web browser before you can connect to the web GUI again, and now use
the AMCC domain name if you earlier used an IP-address.
6.4 Network Trace Capabilities

From the Diagnostics – Network Trace tab you can select which interface to trace on.
Note: If the tracing is allowed to continue too long, it will not be possible to download the Wireshark
trace. (Compare with the situation where your mail inbox has been overloaded with a too big file). There
is even a risk free available disc space will become too small and affect the performance of AMCC.
Doc. No. ASE/FMC/GEN/0004/0/17 51/54

6.5 Number Conversion when using Remote Extension.

Make received national A-number (Remote ext. number) into Cellular format before being sent over the
SIP Route to the AMCC.
e.g. Remote ext. number received from PSTN are numbertype 2 (national ).

–truncate 9 –newtype 1
Doc. No. ASE/FMC/GEN/0004/0/17 52/54

7 Troubleshooting.
Controller cannot register the SIP extension (in MX-ONE).

- PBX Number (page 40). Check that PBX Number and PBX Username are the same as
SIP extension in MX-ONE and, if used, that the auth code matches.
- User Account (p 40). Activate User is Enabled.
- SIP Trunk settings.
SIP extension registered but when I call the ext. the mobile phone is not ringing (AMC
Client).
- GSM Numbers (p 41). Check that the mobile number is correct.
- Number Conversion (p 26).
The AMC Client does not register. (Yellow/Red square)

- User Account (p 40). SIP Number and SIP User Password should be the same as set
in the Portal.
- User Account (p 40). Activate User is Enabled.
- Check ports in Firewall.
- APN setting on the mobile phone. (Make sure 3G is enabled.)
Client is registered (blue) but I cannot make any AMC calls from it.
- GSM Numbers (p 41). Check that the mobile number is correct and in right format.
(Diagnostic/Network trace on AMCC. Check that right mobile number is coming in)
- Call through number could be a DID number. (In the Portal it is named PBX dialling-in no.)
- Number Conversion (p 28).
- Check ports in Firewall.
Doc. No. ASE/FMC/GEN/0004/0/17 53/54

Acronyms
AMCC Aastra Mobile Client Controller

XMPP Extensible Messaging and Presence Protocol
PSTN Public Switched Telephone Network
PBX Private Branch Exchange
TON Type of number
Copyright
© Copyright Aastra Technologies Limited 2011. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written permission of the
copyright owner.
The contents of this document are subject to revision without notice due to continued progress
in methodology, design and manufacturing. Aastra shall have no liability for any error or
damage of any kind resulting from the use of this document.
.
Doc. No. ASE/FMC/GEN/0004/0/17 54/54

AMC Controller Admin Installation and Configuration Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

AMC Controller Admin Installation and Configuration Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Commercial in Confidence

AMCC and AMC3 Admin

Aastra Telecom Ltd Doc. No. ASE/FMC/GEN/0004/0/17

AMC 3 with AMC Controller Solution document content:

Doc. No. ASE/FMC/GEN/0004/0/17 2/54

6.1 Other AMCC services – Number conversion..............................................................................46

Doc. No. ASE/FMC/GEN/0004/0/17 3/54

1.2 Fixed Mobile Convergence

1.3 Introduction to the User Guide

Doc. No. ASE/FMC/GEN/0004/0/17 4/54

Doc. No. ASE/FMC/GEN/0004/0/17 5/54

Site specific system data collection forms

Aastra Mobile Client Controller (AMCC) IP- networking information

Ports that are used internally.

389 or 3268 TCP (for Corporate Directory server LDAP

443 To be able to configure the AMCC via

11000 – 11xxx SIP Trunk AMCC – MXONE.

Doc. No. ASE/FMC/GEN/0004/0/17 6/54

3 Installation of the AMC Controller

3.1 AMCC-30 and AMCC-130

3.2 VMware on ESXi

Doc. No. ASE/FMC/GEN/0004/0/17 7/54

• SCSI controller – leave the defaults

Doc. No. ASE/FMC/GEN/0004/0/17 8/54

Doc. No. ASE/FMC/GEN/0004/0/17 9/54

4.1 General MX-ONE configuration

4.2 Number analysis and number series

Doc. No. ASE/FMC/GEN/0004/0/17 10/54

Doc. No. ASE/FMC/GEN/0004/0/17 11/54

Used settings in the example configuration:

SIP route destination for SIM switch 67150

Clients SIP ext. and their mobile numbers 67104 +46705263966

Clients SIP ext. and their mobile numbers 67105 +46705267786

Aastra Mobile Client Controller (AMCC) IP- networking information

External IP-address: 89.92.21.18

Default IP Gateway: 10.103.61.1

DNS server address: 10.103.61.1

NTP server address: 10.103.61.91

Doc. No. ASE/FMC/GEN/0004/0/17 12/54

4.3 Initiate number series

MDSH> number_initiate -numbertype ex -number 67104..67105

To verify your work, type the following command;

MDSH> number_print -numbertype ex

MDSH> number_initiate -numbertype ed -number 068

To verify your work, type the following command;

MDSH> number_print -numbertype ed

To initiate Least Cost Routing Access Code.

MDSH> number_initiate -numbertype lc -number 00

To verify your work, type the following command;

MDSH> number_print -numbertype 00

Doc. No. ASE/FMC/GEN/0004/0/17 13/54

4.4 Extensions & Common service profile

MDSH> extension_profile -I --csp 0 --ext-traf 1103151515 --ext-serv

MDSH> extension_profile -p --csp 0

MDSH> extension -i -d 67104 --lim 1 --csp 0 --max-terminals 1

To verify your work, type the following command;

MDSH> extension -p -d 67104,67105

MDSH> ip_extension -p -d 67104,67105

Doc. No. ASE/FMC/GEN/0004/0/17 14/54

Initiate route category.

To verify your work, type the following command;

Synchronization may need to be configured on this route.

Doc. No. ASE/FMC/GEN/0004/0/17 15/54

4.6 Initiate routing