Getting Started Guide
Aastra 700 Configuration The open path to UC and Mobility
Aastra Telecom Sweden AB Box 42214, SE-126 17 Stockholm Visitors address: LM Ericssons väg 30, Hägersten Sweden Tel +46 8 568 67000
Doc. No. ASE/MXO/PLM/0162 Rev D Date: January - 2011
Contents 1 1.1
Welcome
3
About Number Series
3
2
Aastra 700 system overview
5
3
Site specific system data collection forms
6
4
Introduction
8
5
Setting MGU Control Data IP address on the Media Gateway
8
6
Accessing the VMware hypervisor and the vSphere client
10
6.1
Step 1: Setting up the Aastra 700 VMware ESXi host the first time after initial power up
10
6.2
Step 2: Install the vSphere client on the administrator’s workstation
13
6.3
Step 3: Connect the vSphere client to the ESXi host and open up the virtual machines
18
6.4
Useful Tips on Using the vSphere Client
21
7
Accessing the Linux virtual machine and finishing the installation
23
8
Accessing the Windows 2008 Server virtual machine to finish installation
26
9
Running the Aastra 700 Configuration Utility
32
10 Running the OneBox configuration wizard
39
11 The Manager Provisioning configuration wizard
55
12 Finishing the Aastra 700 Configuration Process
61
12.1
Finalizing the Configuration and Useful Tips
61
12.2
Don’t forget to back-up your system
62
12.3
Optional Windows configuration settings
62
2
1
Welcome
This Getting Started Guide will help you configure your Aastra 700 system once the Hardware is installed. You should collect all necessary customer specific information prior to beginning the setup. You will need five fixed IP addresses from the internal LAN and information about the telephonynumbering plan. To simplify the collection of data, a two-page form is available in the beginning of this document. Your Aastra 700 server comes pre-installed with MX-ONE Telephony Server and Management Suite and the Aastra 700 applications. Completing the installation of Aastra 700 applications consists of the following steps, which are covered in this document: 1.
Configure the network interface on the MGU
2.
Set a password and an IP-address for the VMware Hypervisor
3.
Install the VMware vSphere client on your PC
4.
Finalize the Aastra 700 Telephony System and Manager Provisioning (MP) software installation and configuration on the SUSE Linux virtual machine
5.
Finalize the Windows setup on the Application Server virtual machine
6.
Run the Aastra 700 Configuration Utility to set up the network parameters for the Application server, the IP address of the Telephony Server virtual machine, and configure the customer specific information for CMG and Solidus eCare
7.
Run the OneBox installation wizard
8.
Using the Manager Provisioning Aastra 700 Wizard to set up the Telephony Server
9.
Finalizing the configuration and backing up your system.
1.1 About Number Series When it comes to defining the number plan, there are a few things to keep in mind. 1.
Naming for the same number or number series may be different depending on the application you are configuring. See the site information pages to get details on these different names used by Telephony Server and the different applications.
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 5686 7000-7300, we can see that the 08 is the area code and the 5686 is the public exchange number. The last 4 digits are what differ in the range, which is the DID number series used to differentiate between internal extensions (7000-7300). You would then create a 4 digit numbering plan, where 7000-7300 would be the internal number series.
3.
You could then decide to reserve 7000 as your main external number. Then, assuming you have two attendant consoles, you would reserve 7001 and 7002 as attendant extension numbers. You would then use the remaining numbers for user extensions and service numbers (e.g. OneBox VM Hunt Group, CTI groups for Solidus, etc…).
3
4.
If a company has 150 users, they would exclude the 3 numbers mentioned above and user extensions numbers would begin at 7003 to 7153, as defined by the “DID number series” in the Manager Provisioning (MP) wizard. These would be the range of numbers used by MP to create user extensions in Telephony Server and CMG as well as OneBox mailboxes. The rest of the numbers (7154-7300) can be used to say define 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.
CMG on the other hand uses the term “extension range” which refers to the combination of 3 and 4 above, so it would expect the 7000-7300 be defined as the extension range, as will enable users and attendants to see and reach all numbers in this range from the CMG directory.
6.
Things like Voice mail media ports for OneBox and IVR ports for OAS are kept outside of the DID number range and are internal SIP extension numbers with the same number length used by the system to register the media ports needed for these applications. The reason they are kept outside the DID number range is to avoid them being accessed directly from the outside.
7.
Then there are internal service codes for dialing 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 dialed for accessing the outside public network and 09 for dialing internally to the operator (attendant). If a single digit approach is used, such a 0 and 9, then no other numbers can be used in the number plan with 0 or 9 as leading digits.
8.
Then there is the international access code or prefix, used to inform the public exchange that you are dialing an international number. In Europe, this code is 00, whereas in North America it is 011. As an example, if you were dialing a number from Sweden to France (+33 1 4233 1234). The internal user would dial the public access code 0 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 0 00 33 1 4233 1234.
9.
This covers the basics you need to know prior to beginning the configuration process. It is a good idea to fill in the information in the “Site specific data collection forms” located in chapter 3 of this guide prior to starting the configuration.
4
2
Aastra 700 system overview
The picture above shows the principal architecture of the Aastra 700 system. All software is based on the MX-ONE product portfolio, but it has been consolidated into one physical server. The system is running on a single ASU-E server board, utilizing VMware ESX 4.0 to be able to share the hardware between the Telephony Server (Linux based) and the Application server (Windows based). The gateway functions required by the telephony system are taken care of by the Media Gateway Unit (MGU) inside the 3U box.
Some notes about networks, virtual machines and Aastra 700 Inside the VMware hypervisor, there is a virtual network environment that connects all the virtual machines together with each other and with the physical Ethernet port on the ASU-E. A virtual switch inside the hypervisor handles the network traffic between the virtual machines and the outside. It also provides a link aggregation (bonding) feature as standard, giving the Aastra 700 system network redundancy. The result of this is that each virtual machine still needs their own IP-address as their virtual network interfaces behaves like real interfaces for the operating systems. So, one IP-address is needed for each virtual machine. The hypervisor itself also needs an IP-address for the management through vSphere. This sum up to the total of five IP-addresses needed for an Aastra 700: three for the server and two by the MGU.
5
3
Site specific system data collection forms
We recommend that you collect all applicable information below, before you begin the Aastra 700 installation and configuration.
Media Gateway Unit (MGU) IP- networking information Control Data IP-address: Media Data IP-address: Network Mask (common for both ports): Default IP Gateway (common for both ports):
VMware Hypervisor IP- networking information IP-address: Network Mask: Default IP Gateway: DNS server address: Host name:
Windows Application Server IP- networking information IP-address: Network Mask: Default IP Gateway: Computer name: (preconfigured and should not be changed)
A700AppServer
DNS server addresses: WINS server address:
Aastra 700 Telephony Server information (a.k.a. PBX, SIP Proxy) IP-address: Network Mask: Default IP Gateway: Host name: Domain name: NTP-server (optional):
6
Aastra 700 Number series information This section focuses on the internal number series to be used by the call control server (Telephony Server) as well as the applications running in windows that interface with it. For historical reasons, the terminology used is different for the same number series or parameter depending on the application. Therefore, if applicable, we will list the aliases to help make the relation between specific numbers or parameters when used with the different applications or wizards described in this guide. As an example, when we specify the “OneBox Group Number” in Telephony Server (MP wizard), it is referred to as the “VM forwarding number” in CMG and “Hunt Group Access Code” in OneBox, but they are all mean the same thing. Aastra 700 Number series information Aastra 700 Number length (e.g. typically 3-5 digits corresponding to the length of the DID number series and should match Mailbox Number length in OB):
CMG “Extension” number range (low to high). This corresponds to the “DID number series” for user extensions in MP (excluding attendant DID and extension numbers):
__________________________________________
__________________________________________
CTI Group range and OAS IVR port range (low-high) – These ranges correspond to CTI groups and IVR media ports used on Telephony Server for Solidus eCare:
Common operator number (e.g. typically 09 or 0 used internally to dial the attendant) a.k.a. Operator Number in CMG:
__________________________________________
__________________________________________
Individual Operator 1 & 2 extension numbers. This should be outside “DID number series” range in MP:
OneBox Group number (a.k.a. Hunt Group Access Code in OB or CMG VM forward destination:
__________________________________________
__________________________________________
First OneBox port number (for OB media ports)a.k.a. “first extension” in OB wizard:
Public Access Code to dial out (e.g. commonly 0 or 00 or 9 depending on the market:
__________________________________________
__________________________________________
Local area code (commonly 2-3 digits like 08 or 212):
International access code/prefix (e.g. 00 or 011), which precedes the country code:
__________________________________________
__________________________________________
7
4
Introduction
It is assumed that the service engineer setting up the Aastra 700 has been properly trained and certified on the relevant Aastra 700 hardware and software. As such, the service engineer should be familiar with the installation and configuration procedures for the 3U Media Gateway, ASU-E Server and relevant accessories, which are described in the CPI documentation. Before starting the configuration process described in this guide, the hardware should have been unpacked, installed and powered up according to the Aastra 700 Quick Setup Guide, Document 2/1531-ASP 114 01 Uen, delivered in the box with the unit. This document can also be found in the CPI documentation for Aastra 700.
5
Setting MGU Control Data IP address on the Media Gateway
You should configure the MGU Control Data IP address, network mask and default gateway address on the MGU for eth0 only. This is necessary to set-up prior to running the Aastra 700 Manager Provisioning wizard step so the Telephony Server can communicate with the Media Gateway.
Connecting the administrator PC to the MGU There are two ways to access the MGU board to make the configuration depending on network configuration: SSH If the MGU is connected to the same subnet as your PC or using an RJ45 cross-cable connected to LAN0, then you can use SSH to login to the MGU with the default IP address 192.168.1.2. Just note that when you change this address and re-boot the box, you will lose the connection. TTY When using a serial connection, the following prerequisites should be done in order to access the MGU board: •
Make a terminal connection to the USB port in the front of the MGU. Use cable TSR 899135/1, which is a USB to D-Sub cable, plus a 9 pin D-Sub female to female adaptor which can be plugged into a serial port on your PC.
•
Use a terminal program, for example, Putty, Kermit or Hyper Terminal. o Baud rate is set to 9600 bits/sec, 8 data bits, no parity, 1 stop bit. o No HW or SW flow control.
Configuring the network parameters for MGU The default address for eth0 is: 192.168.1.2/24, which needs to be changed to a fixed IP- address provided by the customer. Once connected, perform the following steps: 1.
Login userid: admin password: admin
8
2.
Switch to root, by typing: su The default password is root. i.Note: It is recommended to change the root password (use passwd command).
3.
Set the Control Data IP address and subnet mask of interface 0. Use the command: nvparams -setpar eth0_ip IP-address/netmask Example: nvparams -setpar eth0_ip 10.10.75.61/24
4.
Set the IP address for the default gateway. Use the command: nvparams -setpar def_route IP-address Example: nvparams -setpar def_route 10.10.75.1
5.
Check and verify the settings Use the command: nvparams -dispar all
6.
Make a manual reboot of the MGU board Use the command: reboot
Use the command nvparams -help for guidance. Note: the Media Data IP-address (eth2) will be setup with the Manager Provisioning configuration wizard, so it is not to be configured here. Important: At this stage, do not connect the LAN1 port on the MGU, as this is only used for redundancy purposes after the initial Manager Provisioning (MP) configuration is completed. If it is connected, the MGU will not be able to communicate properly with the MP wizard during initial configuration phase.
9
6
Accessing the VMware hypervisor and the vSphere client
It is necessary to connect a keyboard and a PC monitor/display via the appropriate connectors on the front of the ASU-E server unit.
6.1 Step 1: Setting up the Aastra 700 VMware ESXi host the first time after initial power up 1. On the initial screen, press the F2 key to enter the System Customization screen.
Select the top option Configure Password.
As this is the first time, the old password is just empty, don't enter anything at that field. Type the new password two times and then, press Enter to save. 10
Important: Note that you must enter a password with a minimum of eight characters, which are a mix of digits and letters to meet the complexity criteria for a valid password. 2. Select Configure Management Network from the System Customization page to set up the network parameters for the hypervisor (not the same as those needed by each virtual machine). When the below page is displayed, scroll down and select IP Configuration and press Enter.
3. At the IP Configuration page, select: (o) Set static IP-address and network configuration by using the Space-key to activate. Then move down to enter the values for VMware Hypervisor IPaddress, Network mask and default IP gateway you have put in the information page. Save settings by pressing Enter.
11
4. At the DNS Configuration-page, you can (optionally) set the VMware Hypervisor DNS-servers and the host name you put in the information page.
5. Finally, you will have a question, asking for restart of the management network. Press . This will load the new settings for the network.
This process will only restart the network interface. Then VMware will display the IP configuration screen with the updated IP address information. Just press escape to back to the initial VMware 12
System Customization Screen. If you press escape again, you will logout of the VMware server and return to the initial VMware screen. From this point on you no longer need the keyboard and screen connected to the ASU-E board. You should now go to your normal administrator PC with access to a web-browser to continue with the setup process.
6.2 Step 2: Install the vSphere client on the administrator’s workstation 1. In a web-browser, enter the address to the VMware host: https:// (the VMware Hypervisor IP-address set in the previous section). Accept any temporary certificates if asked for.
Click on the link "Download vSphere Client" and click on “Run” to initiate the installation.
13
Just accept the windows dialog to confirm the Installation request and the following screen will appear. Just follow the installation wizard to complete the installation.
Select Agree to continue and click Next.
14
Enter the company information as needed (above is just an example).
The above check box should not be selected, as it is not needed - just click Next.
15
Select the folder where the vSphere software should be installed. Shown above is the default one. Select Next.
Now select Install to start the actual installation. It will take a while, depending on your computer.
16
Installation completed. Click Finish to close the installer.
Now, you can start the vSphere client by clicking on the new icon on the desktop:
17
6.3 Step 3: Connect the vSphere client to the ESXi host and open up the virtual machines Log on to the ESXi host via vSphere.
The IP-address and the root password is the same as we gave to the VMware ESXi host during initial hypervisor configuration (see chapter 5). Click Login to start vSphere. Note.: During log on, a certificate warning might appear. Just ignore it (select "Install this…" to prevent the dialog to appear in the future).
18
After the log on, the initial page of vSphere will show up.
Select "Inventory" and you will be presented with the page below where the host is displayed. Click on the [+] at the left tree view to expand the content of the host (the virtual machines running on it). They should be running, indicated by a green arrow on them.
Note: At this point you should consider setting the time on the VMware hyper-system by going to the 19
Configuration tab for the host and then Time Configuration. You can then point to an NTP server and/or set the time and date. 1. To access the console of a virtual machine, begin with selecting one of them by clicking on their names in the left tree structure:
2. Next, click the small screen icon in the tool bar (
) to open up a separate console window.
NOTE: Sometimes the console window comes up black. This could be normal as the default screensaver is black. In this case you must click the cursor inside the window or possibly press enter to get some reaction. The console window does have its own toolbar for the most common functions needed to control the virtual machine:
From left to right: • Stop the virtual machine (like the power button on a physical computer) • Suspend the running of the virtual machine • Start the virtual machine • Restart the virtual machine • Take snapshot of the virtual machine • Revert to current snapshot • Open up the snapshot manager • Connect/disconnect the floppy device to the virtual machine • Connect/disconnect the CD-ROM device to the virtual machine
20
6.4 Useful tips on using the vSphere client To continue with the setup phase, you may go directly to the next chapter. However, the remainder of this section gives some useful information on how the VMware client application works and how to navigate between virtual machines.
NOTE: Stopping and starting the virtual machines from the toolbar They require VMware Tools to be installed on the virtual machine operating system. This is only valid for the Application Server that runs Windows 2008 Server. The Telephony Server running on SLES10 does not support these functions. Stopping the Telephony Server should be done either from the Linux environment itself or from the Inventory menu in the main window of vSphere:
Another way to access the console of a virtual machine is to use the tabs in the main window of vSphere:
The function is identical to the separate console window and the toolbar is the same. The only difference is that the console output is running in the main window of the vSphere application instead of a separate window. It is just a personal preference on which one to use.
21
Important: Shifting the keyboard/mouse input between the virtual machines. The vSphere software does have a special way to capture keyboard and mouse events and redirect them to the virtual machine. This could be confusing in the beginning until you are used to it. This is especially important to remember if the virtual machine is running a non-Windows operating system (like the Telephony Server that runs on SUSE Linux (SLES10). You have a special procedure to handle the keyboard (we cannot use the mouse when in the Telephony Server VM). 1.
To activate keyboard input to the SUSE Linux virtual machine, simply click in the console window. The mouse pointer will disappear and all keyboard entries will end up in the Linux shell.
2.
When going back to the Windows environment of the workstation, it requires the user to press CTRL + ALT to switch the mouse pointer and the keyboard input back to the workstation.
3.
For virtual machines running Windows (our Application Server) it's easier. The VMware Tools takes care of the capture and it is enough to bring the mouse in to the console window of the virtual machine to start interact with it. Remember: If the mouse is outside virtual machine console = no input. When the mouse is inside, then the input goes to virtual machine. If you find your Application Server does not respond to your keyboard inputs - check where the mouse pointer is. This section was just a brief introduction to the vSphere client. The software does have many more features, but they are outside the scope of this document as they are not needed to proceed with the installation procedure of the Aastra 700 system.
22
7
Accessing the Linux virtual machine and finishing the installation
This section covers the installation and Configuration of the Linux virtual machine with the Telephony Server and Manager Provisioning applications. 1. Open up the console of the virtual machine for the Telephony Server. To access the console of this virtual machine, select the Telephony Server by clicking on its name in the left tree structure:
Next, click the small screen icon in the tool bar (
) to open up a separate console window.
Note: Sometimes the console window comes up black. This could be normal as the default screensaver is black. In this case you must move the cursor inside the window and click on it or possibly press enter to get some reaction. 2. The virtual machine should be up and running, displaying the welcome-dialog.
Select Yes to start the configuration/installation. Selecting No will just shut down the (virtual) server (nothing will be damaged by doing that, just start up the server and you will be back to this point).
23
3. Enter the IP-configuration data for the Telephony Server Virtual Machine, the hostname and customer domain name (Domain name cannot end with .local). Don’t forget to also set the NTPserver used for the date and time sync. If there is no NTP-server available, use the default setting that point to the local host. Also, enter the user name and password to be used in Manager Provisioning (MP). Select OK to start the installation of the Telephony Server part. It will run for about five minutes, printing the installation log onto the console.
Note: The values shown above and in upcoming dialogs are just examples of a possible configuration.
24
4. When the SUSE Linux welcome message and the SLES login prompt appears, then the installation of the Telephony Server is completed and it is time to proceed with the Windows Application Server, as described in the next section. Note: You don't need to wait for the Telephony Server installation to finish before starting the Application Server setup procedure in the next section. As these Virtual machines are totally independent of one another, you can start to work with the Windows Application Server while the Telephony Server setup is running in parallel on the Linux virtual machine.
25
8
Accessing the Windows 2008 Server virtual machine to finish installation
To access the console of a virtual machine, go back to the vSphere client and click on the Application Server VM in the left tree structure:
Next, click the small screen icon in the tool bar (
) to open up a separate console window.
Setting up the Application Server after initial boot up: Important Note: During the following procedure, do not power off the system until the Windows installation process has completed as it will corrupt the Windows system and prevent it from working properly! The Windows process is fully automatic and will set certain values to defaults. The only information needed by the user during this process is the country settings for localization and the Windows 2008 Server Standard edition product key (it is printed on a Microsoft COA label on the Aastra 700 unit, which you should have noted down prior to installing the HW). The computer name and the password for the local administrator account are set to default values. •
The computer name is pre-set to Aastra 700AppServer as required by the preinstalled applications. It should NOT be changed in any case; otherwise all applications will stop working.
•
The password for the local Administrator account is set to Aastra#1 (this could be changed later if needed by using the Configuration Utility).
26
Powering up the Windows server At the initial power-on of the Windows server, this image might be shown. Just wait and let the system do its internal work…
The Windows installation/preparation will take some time as it performs basically a new, unattended, installation in the background. So, be patient - this is fully normal and not a sign of any problems.
27
1. Enter the Windows setup information:
The first dialog to show up after the initial boot of the server. You have to select your localization settings and keyboard layout (simply select country/region and the other values will be adjusted to match).
Enter the product key for the Windows 2008 Server that you noted down from the Microsoft COA label delivered with the server unit.
28
And finally, just at friendly confirm to start the Windows setup process. From this point, there will be no more dialogs until the system installation is completed. There will be only a blank grey screen in the window during this phase, which takes about 5 minutes to finish. Then the system will restart and the standard Windows login prompt is displayed as shown below.
29
2. Windows installation and configuration completed - first log-on to the server.
NOTE: Initial log on screen. Use CTRL + ALT + INS instead of doing the traditional Microsoft- Ctrl + Alt + Del – otherwise, this combination will be captured by your own workstation, making the behavior a little bit awkward.
Select the Administrator user.
30
Enter the default password Aastra#1 to log on. This will launch the Windows desktop.
The screen above is what you will see when the Windows installation has completed. From this point, you may go to the next step and start with the Aastra 700 Configuration Utility.
31
9
Running the Aastra 700 configuration utility
At this point, the installation and initial configuration of Windows is complete. The configuration of the basic (and mandatory) network settings in Windows will be done with the Aastra 700 Configuration Utility. 1.
Prior to starting up the configuration utility, the ELM licenses for Solidus eCare must be loaded. These can be a trial license or a permanent license if the customer has already received one. To access the ELM configuration, go to Start->All Programs>Aastra->Enterprise License Manager and select License Administration. This will start the ELM management web-page. From the top menu, select Manage->Install Licenses. As a note, a trial license for Solidus eCare has been placed under D:\Setupfiles\SeC\Temporary License. It can be used until a proper retail license has been obtained.We recommend that you collect all applicable information below before you launch the Aastra 700 Configuration Utility. The screenshots below will show an example configuration for a system with 4-digit numbers.
3.
Once you log on as the Windows Administrator, you will find the Aastra 700 Configuration Utility icon on the desktop. Just click it to start the application. Note: the utility resides in the D:\Setup-files\Configuration Wizard\ folder.
4.
Launch this program to complete the installation of your Aastra 700 applications. The Configuration Utility will lead you through the following configuration dialogs (working through them from top to bottom) as seen below:
32
Network (Mandatory)
You will be requested to enter the PBX IP-address, or the Telephony Server IP address you entered in the information sheet, which you used to configure the Linux/Telephony Server virtual machine. This information is used by all Aastra 700 applications that require connections to the Telephony Server side of Aastra 700. The IP-settings for the Windows 2008 Server is also set at this page. Check the Change local network settings to enable all fields. Fill in the values (these marked with a star are required). This procedure will change the IP-settings of the Windows server from DHCP (the default setting at initial startup) to fixed values. Note: most of the settings, like Network mask, Default GW or the DNS and Wins server addresses were already obtained from the DHCP server and are valid, but it is possible to change them, if applicable. The only thing that needs to be changed is the Windows Server IP address to a fixed (static) value.
33
CMG (Mandatory)
You will be asked to enter the following information for the CMG configuration: •
Voice Mail forward destination: The directory number of the OneBox Voice Mail hunt group (This corresponds to the Hunt Group access code defined in the OneBox configuration in the next section). This value can be outside the extension range set below, but must adhere to the same number length.
•
Operator number: The directory number of the operator/attendant common access code for internal users. This value must not be inside the number series below and is generally 1 or 2 digits (e.g. 9 or 09)
•
Extensions: The extension range (low to high) for CMG users in the system (corresponds to Aastra 700 Telephony Server extension range, but can also includes things like HGs, individual attendant number or common external DID number). It shall not include Solidus CTI groups or OAS IVR groups. These must be in a separate range outside this extension range.
Note about number lengths: All numbers in the system must have the same length except for the Operator number that could be shorter (it is very common to use "9", or "09" for the operator even if all other numbers in the system are longer). Also, the Voice Mail forward destination and the Operator number can be inside the Extension range (overlapping), although it’s not normally the case.
34
Solidus / OAS (Optional)
If you plan to use Solidus, then check the Configure Solidus and OAS checkbox and fill in the following information: •
CTI groups: The wizard will create 13 CTI groups. The highest CTI group number is calculated from the start CTI group number entered. Basic Virtual Devices (BVDs) will be created from the range of CTI-groups entered by the user in the Wizard. These BVDs will be assigned to Service Accesses that will already exist in the SQL database included in the image. These must be outside the extension range defined for CMG in the previous screen.
•
IVR ports: The wizard will create 15 IVR ports. The highest IVR port number is calculated from the start IVR port number entered. These must be outside the extension range defined for CMG in the previous screen.
•
Monitored devices: The range of monitored devices in OAS.
•
Base features code on: The application (country) code of the switch on which the features codes are based. Default value is Standard.
•
Number length is displayed in the status bar.
35
•
If there is something wrong with the numbers (overlapping where it is it not allowed or different lengths), an error message is displayed and the user cannot apply the configuration. Example: If you have used a 4 digit number length in the CMG screen, then this must be maintained in the Solidus screen as well. If the number series entered for CTI groups or IVR are overlapping with the extensions defined for CMG, this will also cause this error message to be displayed.
Windows Password (Optional)
Here you can change the password of the local Administrator account in Windows. The system is delivered with the password pre-set to Aastra#1. This page gives you the option to change it. The new password must meet the Windows password criteria; otherwise, an error message is displayed.
36
1. When all parameters have been set, the user presses the Apply button, which propagates all configuration parameters to the different applications.
Note: applying the configuration to the system will take between five to ten minutes so please be patient. There is a green status bar on the bottom that shows the progress of the updates. •
Traces of all configuration changes are visible in the GUI, and are output to a file in the D:\Setup-files\Configuration Wizard\log\ directory. A new log file is created for each execution of the program and it is labeled with date and time when the utility was run. Inside the log file, there is a summary of all values entered during the configuration, just as a reminder.
•
User settings are saved when closing inside an XML-file (Aastra 700Config.exe.xml) that could be found in the same directory as the Configuration Utility (D:\Setupfiles\Configuration Wizard\).
37
2. Once the configuration is completed, press Close to continue.
Note: In some cases, the services for the application might not restart properly while applying the configuration. This will require a complete reboot of the application server. In that case, the utility will indicate if a reboot is required in the status field:
Important: Although it is possible to launch the Manager Provisioning in the local web browser from this dialog, the tickbox “Launch when closing this window” should be left unchecked, as you still must run the OneBox utility prior to launching the MP wizard. In addition, the log file generated during the configuration process could be opened. Just check the appropriate checkbox before closing the utility.
38
10
Running the OneBox configuration wizard
Once you finish the Aastra 700 Configuration Utility, you should look for the Initialization Wizard for OneBox icon on the Windows Desktop that will start the OneBox configuration. It is required to be run to finalize the installation and basic configuration settings for the OneBox Unified Messaging application with Aastra 700. Launch this Initialization Wizard to get started with your OneBox configuration. This wizard will go though the different configuration options for your OneBox server. The Configuration Wizard will lead you through the following configuration screens: Wizard Welcome:
Click Next to start the configuration process.
39
License Agreement:
Click Yes to accept the agreement and to continue with the configuration. Start Copying Files:
Click Next to start the file copying process that must be done before the actual configuration.
40
Service configuration:
New System Installation should be (pre-) selected. Click Next to proceed.
41
Local Server Settings:
Accept the default values - do not change anything; Click Next to proceed. As this is a combined system server and call server configuration, then System Server must be selected and the “include Call Services” box must be checked. Also, the computer name should not be changed.
42
Database Initialization Parameters :
You will be asked to specify how you are connecting (integrating) OneBox Voice Mail to the Aastra 700 Telephony Server. You will also be asked to enter the desired Mailbox Length and if any other language then US English only should be installed and/or the VIM connection should be configured. •
Configure the Switch options to match the telephony system used (Aastra 700 is based on the MX-ONE software and uses the same integration): • Manufacturer: Aastra • Model: MX-ONE/MD110 • Integration Type: SIP
•
In the port extension field (First Extension) you must enter the first SIP extension number to be used for the media port connections. This information must correspond to the First OneBox Port Number that will be defined on the Aastra 700 Telephony Server side with the Manager Provisioning wizard in a later step. The value Mailbox Length must correspond to the number length that was defined in the Aastra 700 Configuration Utility in the previous section. Checking the American English only checkbox under Language will install US English only without the option to add more languages later during the configuration process. Checking VIM under Configure Now will open up the configuration for the VIM interface, used to integrate the OneBox with CMG for message diversion information.
• • •
When done, click Next to continue.
43
Integration Information: You will need to supply more detailed information specifying how your system is integrated to the Aastra 700 Telephony Server PBX. You have the possibility to enter different information depending on the integration you are using. In the case of Aastra 700, we are using SIP integration. An information dialog, telling you that no line cards are detected in the system, will be shown before you are able to set the SIP integration parameters. Click Yes to proceed.
Configure virtual board: the board type shall be Radvision, which corresponds to the SIP stack. The number of possible lines are controlled by the license loaded from the factory (as default, a temporary license is loaded, giving you four lines). Click OK when done.
Note: the license and the number of lines available could be updated later when the system is up and running by using the Configuration tool that is installed together with the OneBox
44
A Switch Options dialog will then show up where the values can be left as default. Just press OK to continue.
45
In the Integration Options dialog, you will be asked to fill in the Aastra 700 SIP connection information. There are three mandatory fields that must be set for the integration (as shown below). Press OK when done.
Fields that must be set (Local Integration Settings): • SIP Server Address: The IP-address of the Telephony Server part of Aastra 700. • Local IP Address to bind on: The IP-address of the Application Server (it is a pre-defined dropdown list with only one value to select). • SIP parser qualifier string: Should be set to the same IP-address as the Application Server. All other fields should be left with the default values.
46
Then the Switch Section Options dialog will appear:
Here you should add the voice mail Hunt Group Access Code according to what will be defined as the VM group number in Aastra 700 Telephony Server via the MP Configuration Wizard (see next section). This value must correspond to the Voice Mail forward destination set in the CMG section of the Aastra 700 Configuration Utility. Press OK to proceed
47
VIM Support (Optional)
If your system is licensed for Voice Intercept Message (VIM) handling for activity settings with CMG (and you have selected VIM in the beginning of the OneBox configuration), then select TCP/IP for the Connection Type and fill in the computer name (Aastra 700AppServer) of the Aastra 700 Application Server.
48
Language Prompts (Optional to add prompts, one default is always loaded)
This dialogue screen lets you choose which language prompts to install. First copy the OneBox 5.0 Telephony Server media kit on a network drive. Then you browse to the folder where the media kit is located. You then select (Add) up to as many languages as you are licensed for (Minimum two and maximum five languages). Be sure to mark one language as default. For support reasons, it is recommended that at least one of the installed languages is English. NOTE: You will only find µ-law prompts on the media kit. This is normal. OneBox 5.0 converts the µlaw to A-law automatically during playback if needed.
49
Initialize Database
The configuration of the initial database is using the standard Call Processors and the mailboxes uses the default options except for the Call Transfer Type. Change "Call Processor Transfer Type" to Monitor and then click on Finish, which will end the configuration of the integration and display the following informal dialog:
50
Administrators
This dialog shows the available administrator accounts. Just click OK to finish the initialization process and when it is finished the informal dialogs below are shown:
Note: during the configuration of the OneBox, a default administrator account is created with the name "Administrator" and a blank password.
51
Then the final screen will re-appear indicating the install is finished.
Click Finish to end the configuration (all setting are now saved). The OneBox Utility will finish and clean up the installation. The icon will be deleted from the desktop when the server is rebooted, as this utility only needs to be run once. You must now start the OneBox service after this configuration phase is finished. As this was an initial configuration phase, you must go into the OneBox Configuration tool via the Windows Start menu (Start -> All Programs -> OneBox Desktop -> Configuration) and start the OneBox service prior to going the Manager Provisioning configuration phase. When this tool is started, first set the Automatic Startup checkbox, so OneBox will start automatically in the future. Now click on Startup to initiate the start-up procedure, which takes about 10 to 15 seconds. Note that startup status messages are displayed in the Current Status display area. When the start-up process is complete, press the OK button to exit the OneBox Configuration tool and return to the Windows desktop.
52
You may now proceed to the next section to start the Manager Provisioning Wizard to finalize the last step of the Aastra 700 setup. Important Reminder: Don’t forget to install a permanent license for OneBox 5.0 You don’t need to do this now, as the system comes delivered with a temporary license with four ports active. It is sufficient to setup and use the OneBox system initially until the permanent license can be added. If you have not received this license file with your order, a fingerprint of the system must be taken and sent via the Aastra EPI to the Enterprise License center so a permanent license can be generated. The EPI can be reached either by logging into the Aastra Info Channel or using the following link: http://ebusiness.aastra.com/webapp/wcs/stores/servlet/HelpDeskEPIDisplayView
53
To obtain this fingerprint, please go to the D:\Setup-files\OneBox\EchoID\ folder and execute echoid.exe. You will then be presented with a dialog box:
The Locking Code 1 : (With the hexadecimal number format 10-XXXXX), should be included in the EPI request along with the Aastra order number so a permanent OneBox license can be generated for the Aastra 700. The second locking code has a value of 0-0 and is only used if a dongle is attached to the system via a USB port (then it would display 80-XXXX. With Aastra 700, this Locking Code 2 is not used under normal circumstances as Windows is running on a VMware virtual machine without this dongle). Once you have received the license file from the license center via e-mail, down load the license .zip file to a network drive or copy it into the Windows D:\ drive so it is accessible by the Windows server. Then do the following steps to install the permanent license file: 1. 2. 3. 4. 5. 6. 7.
Start the System Configuration utility, and then shut down OneBox (shutdown the services). Click the Features tab. Click Import New License. In the License Import window, click Browse to locate the license.zip file. In the Select License File window, select the license package zip file, and then click Open. To install the files, click Import, and then click OK. Restart OneBox (startup the services).
You may have to go to the administration tool and activate features in the permanent license file or add VM ports (lines) as needed.
54
11 The Manager Provisioning configuration wizard With Aastra 700 a configuration Wizard has been added to manager provisioning that enables the customer data to be entered, either manually or via a text template into a wizard when Manager Provisioning system is initially installed. This allows the administrator to enter the relevant customer information such as: • Setup the CMG and OneBox subsystems • Configure the Media Gateway IP addresses • DID number range • Operator access code and attendant extensions • Number plan, e.g. outside access code, local area code, international access code etc. • PSTN trunk information • The IP/SIP phone extension ranges • Import user names • OneBox VM port integration data and VM Hunt Group Step 1 – Initiating the Manager Provisioning Configuration Wizard to configure the Aastra 700 Telephony Server and user and extension data in the CMG and OneBox applications. Open a web browser in Windows and type in http:///mp
Enter the Manager Provisioning user name and password that you created when you installed the Telephony Server (chapter 6).
55
When you click on Login, this will bring you to a page where you have to select the Aastra 700 Wizard as configuration method. Choose the language you want the wizard to use via the drop down box: English is the default.
When you press Next, you will come to a screen, as shown on the next page, where all the required information should be filled in. Please note the following prior to starting the wizard: • • •
The input fields preceded by an * (red asterisk) in the screen below are mandatory and must be filled in for the wizard to complete successfully. To the left of each input area is a help button (?) that if pressed will give details on the required data for that field. If you plan to input user data using the template provided at the bottom of the wizard screen, it would be recommended to read and prepare this template prior to starting the MP wizard. As it is a .txt file with comma separated fields, a excel sheet with the customer data can be organized with the columns in the correct order with the relevant information and then saved as a comma delimited file (.csv) or a text (.txt) file.
56
This is the Aastra 700 wizard screen that allows the configuration of the Telephony Server and the customer specific User data. Note that the help screen will be open on the right hand side. This can be hidden by pressing the II> button at the blue help frame:
57
Fill in the fields as follows: Subsystems Here you fill in the IP address of the Windows 2008 Server Virtual Machine and the user name (default values are pre-set) and password to be used with each subsystem. If you have not changed them (recommendation is to change them before proceeding): -
OneBox user-id: Administrator with no password is the default for OneBox 5.0 CMG user-id: niceadmin with password aastra is the default for CMG 7.5
System Configuration The Site Name can be any name, but it must be filled in. Select the appropriate Market from the drop down menu corresponding to your country. This information is to identify the Aastra 700 telephony system and to select the application system that shall be used in the Telephony Server. MGU Fill in the IP network information based on the IP addresses for the Media Gateway (MGU). Here we need to fill in the 2 IP-addresses that should have been reserved for the Media Gateway, which you have put in the information sheet. The first address (Control Data) is the eth0_IP address (e.g. 10.10.75.61) you configured in the MGU in the initial step and the second one is the "Media Data" IP-address reserved for the MGU (as a note, the control port is used for signaling and the media port is used for RTP/audio data). As an example, you could have 10.10.75.61 and 10.10.75.62 as the 2 addresses. You also need to fill in the Subnet Mask and the Default G/W address, which correspond to the site specific LAN settings. As a reminder, the Default G/W corresponds to the def_route parameter you configured in the MGU in the initial step (example 10.10.75.1). These values need to be entered for both MGU IP-addresses. Numbering Plan This is the site specific information on the numbering plan for the Public network DID (direct in-dialing) number series and access/dial codes that will be used for access to certain services. The DID number series entered here will be the basis for the internal number range used to create IP extensions below. In general, the DID number series should exclude attendant numbers, VM HG number, VM ports and Solidus CTI and IVR ports. These shall use extension numbers outside this range. As an example, if the public DID number series for the company is 08 568 2000-2199, then the DID number series entered would be 2003-2199, as you would reserve 3 numbers outside this range for the Common Operator DID number (Main number) and 2 numbers for the Individual Operator numbers. The number 2000, in this example, would be reserved as the company’s main public number for outside callers to reach the operator/attendant. See Common Operator DID Number below. Numbers 2001 and 2002 would be reserved as the extension numbers for the attendants as described below in the Individual Operator numbers 1 & 2 section. The Common Operator Number is the number used to dial the operator from internal extensions in the PBX. It should be consistent with the one you set up with the Windows Configuration Utility for CMG and should be unique and not part of the DID number series. 9 or 09 are commonly used for this. The Common Operator DID Number is the last part of the company’s public outside number or main number, which is routed internally to the attendant for external callers. Its length is usually from 3-5 digits and should correspond to the number length you defined in the Aastra 700 configuration Utility. This number must be unique and not part the DID number series above, which is used to access specific user extensions and services. Example: if a company’s main number is 08 568 2000, then the 2000 part of this number would correspond to the Common Operator DID number. It is usually the first number in the DID number series provided by the local service provider.
58
The Individual Operator Number 1 and 2 are the actual extension numbers assigned to the attendants. With the example above, if the main number is 2000, then the Individual Operator number 1 and 2 would be 2001 and 2002 respectively. They must be outside of the range defined in the DID number series . Public Access Code is the code used by internal callers to dial out (e.g. 0 or 00 or 9 are commonly used) Own Area Code – a 2 or 3 digit prefix to the local number (e.g. for a main number in Stockholm of 08 568 6700, the 08 is the Own Area Code and the rest is the number. International Prefix is the code dialed after the Public Access Code to be able to make international calls. Example: In Europe, to dial an international number from a fixed phone, you must dial 00 first. In North America, this corresponds to 011. So, if someone from their home phone in Stockholm wanted to dial a number in Paris, they would dial 00 33 1 40004040, where 00 is the International Prefix and 33 is the country code for France. Route This information corresponds to the PSTN trunks (ISDN PRI only) that shall be setup for the system, based on the public ISDN trunks provided by the local SP. Should SIP-trunking or some other type of interface also be used, these shall be defined later after this wizard is finished. Select 1 or 2 PRI interfaces. Select the ISDN PRI type E1 (30B+D) or T1(23B+D) interfaces based on the trunk type provided on your market. The system will setup the trunk parameters based on the Market setting selected earlier. If more PRIs are needed, then these may be added later after the wizard is finished. Also, trunks of other types (SIP/H.323 or analog, for example) could be added later in the same way. OneBox This is to define the number of VM ports to be defined in the system. You also enter the OneBox (VM) Group number and the First OneBox Port Number (first Telephony Server extension number used for the VM media ports/lines). These should be the same values as you entered in the configuration utility for OneBox (Previous section). User and Extension Configuration There are 2 ways to enter this information: 1. Manually by putting in the number of extensions (fill in an amount) per class of service type (internal, regional, national, International). Optionally, you may select the OneBox or CMG tick boxes to create a VM box and a CMG directory entry for the users of each type. The system will automatically attribute extension numbers based on the “DID number series” range above. As an example, you could create 10 internal numbers for common areas and 50 international numbers for normal users with CMG and OneBox configurations checked. 2. Importing a .csv file with user information already filled in (this is the recommended method). In this case, download the provided template in txt format that you would import into excel to create the csv file. The template contains the instructions of how the file should look. Once you have entered the customer data, you then save the template and import it into the wizard using the data file option and pressing the Browse button. The advantage to this method is that you can enter the names of users and attribute their class of service, whether or not they have a VM mail box and a CMG directory entry. The system will attribute an IP extension number in the order in which the names are entered and grouped by class of service. If the extension type is a Mobile Extension, then the user’s mobile number and presented A-number must be provided in the template. When IP extensions are setup, the system will choose DBC 422 by default as the terminal type. It may be necessary to go in after the fact to change the terminal type for certain extensions to match the customer specific requirements. Additionally, the OneBox mailbox 59
number and CMG extension for that user will be the same as the extension number assigned to the user. Once this information has been entered or imported, click on Apply to finalize the process. If the configuration is successful, an automatic backup of the system will be performed. But if there are any errors in the entered information, an error message will be show, the system will be restored to initial state and you will have the option to correct and then rerun the wizard.
This will trigger a series of scripts that will pre-configure the Telephony Server, CMG and OneBox with the appropriate customer data to setup the system. As Manager Provisioning communicates with Manager TS, OneBox and CMG through Web-Services, then all necessary configuration changes can be handled at the same time. Once the scripts are run, the basic setup of the system is now completed. Changes can be done now in MP as per normal to do moves, adds or changes, as deemed necessary to adjust the basic setup to match the customer specific environment. YOU ARE NOT FINISHED JUST YET! Please read the next section to learn about some suggestions or things to look out for, as MP uses default settings that may need to be adjusted to fit the customer scenario.
60
12 Finishing the Aastra 700 configuration process 12.1 Finalizing the configuration and useful tips At this point, the system is up and running with the basic configuration in place. As this is a basic configuration from a Telephony Server perspective, where MP is using mostly default values, there may be some additional operations to be performed after the configuration wizard is completed to adjust or add some feature settings to correspond to the actual customer environment. Some examples of these are: •
Modify market specific trunks setting for access to the PSTN
•
Initiate/change e Common Diversion settings
•
Modify Hunt group settings to allow external access (VM HG for example)
•
Initiating the GICI interface in Telephony Server for CMG activity setting
•
initiating Solidus CTI groups in Telephony Server or IVR media ports in Telephony Server.
•
Activating the CTI interface for Application Link in Telephony Server.
Configuration changes or updates are mostly handled through accessing Manager Provisioning or Manager TS using a standard web browser and using standard operation and maintenance procedures. Once this is done, all you need is to add terminals and you are ready to go. If you are using IP or SIP sets, then it is generally a matter of setting the proper options with the customer DHCP server so the phones will be directed to the software server in the Aastra 700 when they are plugged in to retrieve their configurations. For instructions on how to set this up, please follow the appropriate Installation Instruction for the different terminals, which is provided in the CPI documentation. If you are using other terminal types than the Dialog series IP sets, you may need to go into Manager TS to setup the appropriate phone configuration files for IPP. You may also want to go into MP and change the terminal type to correspond to the actual terminals assigned to specific user extensions. Note: If you will be using Solidus or adding In-touch clients, verify that the Solidus “tools” folder on the Media Kit is copied onto the Windows server. Additionally, you will have to go in and put in permanent licenses for the applications if you did not have them in time for the initial setup. This is done using the standard tools provided with the applications to do this. Refer to the relevant documentation for details. It is strongly recommended to go the service plaza to check for any service advices for Aastra 700 around the configuration processes to avoid losing time.
61
12.2 Don’t forget to back-up your system Once you have finished your configuration it would be strongly advised to take a snapshot of both VMs to save the work you have done. Furthermore, it would be recommended to do standard data backups for Telephony Server and the applications as an added precaution. Finally, if you are familiar with the VMware Converter utility (standalone version), this would be a good time to do an image back-up of both Aastra 700 virtual machines to an external network drive. This would enable a complete recovery of your system in the unlikely event of a disk crash on your Aastra 700 system.
12.3 Optional Windows configuration settings This section is optional, but highly recommended, and can be done at any point after the setup is complete. When the application server is on the network, it is suitable to put it in to the domain if there is one. Select Change System Properties from the Server Manager page (Start -> Server Manager). The "System Properties"-dialog shows up.
Click on the Change-button to open up the dialog that allows you to change the domain settings. Important: Do not change the Computer name or the installed applications may fail to work properly.
62
Enter the domain name and press Ok. A request for user name and password appears:
What you need here is a user with rights to register new machines in the Windows Domain. The ITdepartment should have this information or at least, be able to help you out. If successful, you will be prompted for a reboot of the server. Initiate the reboot and when the server is back, log on again with the same Administrator user as in the beginning of this guide. Windows Update The Windows Update function should be configured and run according to the customer IS/IT department policies.
63
A note about optional updates: It is generally recommended to avoid installing them , unless it is the company IT policy to do so. Check what they are intended for and hide those that are not needed on the server (examples are Microsoft Live and Internet Explorer 8). Hiding them will keep them away in the future, not disturbing you with their presence. If they are needed in a later time, they can always be restored and installed. Some things to consider: •
SET THE PROPER TIME AND DATE or configure the appropriate NTP server address. Otherwise, when you install the temporary ELM licenses for the Solidus eCare application, they will expire.
•
Install the corporate anti-virus software according to the company IS/IT policies. This should be done as soon as possible to prevent infection. If the customer network provides a centralized anti-virus solution, this is not needed. Note: the anti-virus solution must be provided by the customer. It is not included in the Aastra 700 package. A scanner with low system impact is recommended due to the nature of the virtual environment.
•
The Windows firewall on the server is by default disabled. Keep it in that way to prevent problems with the applications. The firewall solution should be in the network instead.
•
For remote administration without vSphere, either enable the Remote Desktop function or install the remote control software used by the customer. By default, Remote Desktop is disabled.
Now you are finished with the setup and configuration of the Aastra 700 and are ready to put it into service.
64
Notes:
_________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________ _________________________________________________________________________________
65
----------------------------------------------------------------------------------------------------------------------© 2011 Aastra Technologies Limited. All rights reserved. This document contains proprietary information, which is protected by copyright. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, or translated into another language, without the prior written consent of Aastra Technologies Limited, Concord, Ontario, Canada. NOTICE The information in this document is subject to change without notice. AASTRA MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. AASTRA shall not be liable for errors contained herein, neither for incidental nor for consequential damages in connection with the furnishing, performance, or use of these materials. Aastra Technologies Limited Concord, Ontario, Canada
66
