nemo server installation guide 7feb07

8/13/2019 Nemo Server Installation Guide 7Feb07

1/9

Nemo Server

Installation Guide


2/9

Sepnkatu 20 | FI-90100 Oulu | Finland | tel. +358 50 395 7700 | fax +358 8 551 6182 | www .anite.com/nemo

Installing the Server

Please refer to the enclosed IBM server installation documents how to setup the power, keyboard,mouse, and display.

Do not connect the server to the Internet at this t imethe firewall of the server is active but the root(that is the superuseraccount on Linux) password is weak by default, which makes the server

vulnerable to intrusions.

Change the root password first:

1. Boot the server. Wait until the logon prompt appears.

2. Log on as root.

Username: root

Password: nemonemo

After the logon has completed, the Fedora Core 2 desktop appears.

3. Select the Terminal / Command L ineicon from the bottom row (second from left).

The following prompt refers to console commands from now on:

[root@nemoserver root]#

4. Password can be changed with command passwd:

[root@nemoserver root]# passwd

Changing password for user root.

New UNIX password:

Retype new UNIX password:

passwd: all authentication tokens updated successfully.

Create a new password according to the following guidelines:

- Do not use common words or names

- 8 characters long

- Has upper and lower case characters, numbers, and special characters

- Following is an example of such password (do not use this): 6yV-1pSc

After the rootpassword has been changed to a stronger one, it is safer to connect to the Internet.

Please note that Anite Finland Ltd cannot guarantee absolute safety when the server is connected tothe Internet, especially if the data test option is installed. This is because the data test option has active,

public services like FTP, WWW, POP3, and SMTP that can be (or become) vulnerable.

However, the server has a precisely configured firewall that should prevent all common intrusions.


3/9


Audio Test Installation

This chapter is needed only if the server has one or more Audio Test options.

The server has 4 to 12 analogue Loop Start (FXO) RJ11 ports for connecting with POTS (PSTN) lines.

1. Connect the lines to the RJ11 connectors that are located at the rear side of the server. There is noneed to configure the number of each line.

2. Switch on the server and wait until the Login prompt appears. The server is then operational.

There is no need to log on unless one wants, for example, to configure network settings asdescribed in chapter Configuring the Server.

Data Test Installation

This chapter is needed only if the server has one or more Data Test options.

The server has 4 to 8 Ethernet RJ45 ports for connecting to the Internet and one network interface for

local remote maintenance, such as, connecting with sshor vncthrough a local area network.

1. Connect the network lines to the RJ45 connectors that are located at the rear side of the server. TheLAN connector is located nearby the display connector and is away from the other networkconnectors.

2. Switch on the server and wait until the Login prompt appears. The server is then operational if theInternet Service Provider (ISP) has a DCHP service.

The server fetches IP addresses during the boot process by using the DHCP protocol. In case theDCHP service is not available and IP addresses should be configured manually, please refer to

chapter Configuring the Server.


4/9


Configuring the Server

These settings are optional.

Changing Network Settings

1. Log on as root.

Username: root

Password: nemonemo

Note: At this time the root password should be different than shown here as it has beenchanged in the first chapter.

After the logon has completed, the Fedora Core 2 desktop appears.

2. Select the Terminal / Command L ineicon from the bottom row (second from left).

In Fedora Core 2, or Linux generally, network interfaces are named as eth0, eth1, etc. so that the

last number is different for each interface. The following interfaces are installed in each data testoption:

Data test options Available network interfaces

NONE lo, eth01 Data test option lo, eth0, eth1, eth2, eth3, eth4

2 Data test options lo, eth0, eth1, eth2, eth3, eth4, eth5, eth6, eth7, eth8

Note: A special i nterface lo is the local loop-back interface that is used by the operating system for localcommunications.

Each of these interfaces has a separate start-up script and these scripts are located in the folder/etc/sysconfig/network-scripts/and are named as follows: script for eth0 is ifcfg-eth0, script foreth1 is ifcfg-eth1, and so on.

By editing these scripts it is possible to switch between DCHP and manually assigned IP addresses.

3. Change the interface eth0 settings with the following command (replace eth0 with other interfaceif needed):

[root@nemoserver root]# cd /etc/sysconfig/network-scripts

[root@nemoserver root]# vi ifcfg-eth0

Now the vi-editor opens. By default the configuration uses DHCP and shows:

DEVICE=ETH0

ONBOOT=yes

BOOTPROTO=dhcp


5/9


Set the vi-editor to insert-mode by pressing sequence Esc i

Note that all vi-editor commands are case-sensitive.

Change the configuration to static IP:

DEVICE=ETH0

ONBOOT=yes

BOOTPROTO=static

BROADCAST=192.168.10.255

IPADDR=192.168.10.1

NETMASK=255.255.255.0

TYPE=Ethernet

Note that parameters IPADDR, NETMASK, and BROADCAST are supplied by ISP, andBROADCAST is optional.

Save the script and close the vi-editor by pressing the sequence Esc : x

Repeat the procedure for each network interface that should have a static IP address.

Changing Audio-Test Settings

1. Log on as rootand select the Terminal / Command Lineicon from the bottom row.

2. Audio-test service settings can be changed by editing the file /usr/vqd/voiceqd.conf

[root@nemoserver root]# vi /usr/vqd/voiceqd.conf

Instructions for using the vi-editor can be found from the previous chapter.

This is the default configuration:

# Ani te Fi nl and Ltd voi ce qual i t y conf i gur at i on# Not e: Thi s conf i g i s case sensi t i ve, do not change paramet er names

# Di r ect or y f r om where ref erence sampl es are aut o- l oaded ( max 8 sampl es! )Sampl eDi r . / t est _sampl es

# Di r ector y where t est r esul t s wi l l be stored ( each cal l - > new f i l e)Resul t sDi r / home/ nemot est / r esul t s

# St art - and re- sync sampl es ( do not change)St ar t SyncSampl e . / sync_sampl es/ st ar t _sync. wavReSyncSampl e . / sync_sampl es/ r e_sync. wav

# Sof t war e and hardwar e gai n set t i ngs# I f t he audi o si gnal i s t oo sat ur ated or t oo weak i t can cause qual i t y l oss# I n t hese cases t r y t o decr ease ( sat ur ated) or i ncr ease (t oo weak) hwgai n 1db at a t i meSwTxGai n 10. 0HwTxGai n 10. 0

# Enabl es/ di sabl es consol e out putEnabl eConsol e 1

# Enabl es/ di sabl es socket ser ver ( do not enabl e!)Enabl eSocket 0


6/9


The most important settings are SW and HW Gain settings. Because the actual analogous PSTN

line levels may vary greatly on different places, it might be necessary that gain settings should beadjusted.

Maximum values for both are 12.0. Do not exceed this limit! If the test sample speech soundsdistorted when heard from the mobile end, lower both values by 1.0 and try again until the best scoreis achieved. If the speech sounds too weak and scores are lower than expected, increase both gainsby 1.0 until the best score is achieved.

3. After the configuration has been modified, the voiceqd service has to be restarted. Thiscommand stops the process:

[root@nemoserver root]# /usr/vqd/vqd-run stop

Service is automatically restarted by the system after a maximum of 1 minute.

Changing Audio-Test Samples

Requirements for test samples are:

- 8kHz sampling rate

- 16-bit linear PCM

- signal scaled to 80% of the full scale

- band-pass filtered with corner frequencies at 250Hz and 3500Hz

- minimum duration of each sample: 2 seconds

- maximum duration of each sample: 6 seconds

Server-side limitations, that do not affect mobile-to-mobile testing, are:

- max 6 samples total in server test-sample folder

- the first 1.5 seconds have to be different in each sample

By default, reference samples are located in the folder /usr/vqd/test_samples

This folder can be changed for example to /home/nemotest/samplesif one wants to upload new

test samples via FTP. However, new samples will be loaded by the vqd service only when it starts.Therefore, after new samples are in place, reboot the server or use the method described inprevious chapter to restart the service.

Note that there should be a maximum of 6 samples total in the samples folder. If there are more, theserver may not have enough time to identify the sample during the first receiving from the field end.

The speakers language, gender, or age is irrelevant but it is essential that the test sample containsnothing but speech because the mobile codecs are highly optimized for that. Any clear speechsample will work fine.

Running Voiceqd Service Manually


7/9


In case one wants to observe the voiceqd service operation in real-time, the service can be runmanually on the terminal.

Crontab is a system where certain tasks can be run at given intervals. In this case a script that

checks whether the voiceqd service process is up and running runs once every minute.1. Log on as rootand select the Terminal / Command Lineicon from the bottom row.

2. Crontab settings can be changed by editing the file /etc/crontab

[root@nemoserver root]# vi /etc/crontab

Instructions for using the vi-editor can be found from the previous chapter.

Enter insert-mode (Esc i) and find the line that reads:

* * * * * r oot / usr/ vqd/ vqd- r un. sh > / dev/ nul l

That line should be commented out, and comments begin with character #:

# * * * * * root / usr/ vqd/ vqd- run. sh > / dev/ nul l

After the change, save and close (Esc : x) and the service will not be automatically restarted

anymore.

After the Crontab has been modified, the voiceqd service has to be stopped:

[root@nemoserver root]# cd /usr/vqd

[root@nemoserver root]# ./vqd-run stop

Now the service can be run manually and it writes the log output - in addition to log file - to the

terminal where it runs:

[root@nemoserver root]# ./voiceqd

If you want to re-enable the automatic restart ing, just repeat the previous procedure and uncommentthe above-mentioned line.

Measurement Guidelines

1. Server measurement files

The server generates one measurement f ile for each test call and each line. Files have the same fileformat as the Nemo Outdoor measurement files.

Measurement files are located in the folder /home/nemotest/results

Each file is named by using this naming convention:

aaBbbcc ddeeff.dtnwhere aais year, Bbb is 3-letter month abbreviation, cc is day of month, ddis hourin 24-hour format, eeis minutes, ffis seconds, and nis the called line number.

For example, 05Apr21 173345.dt1. This file was generated on April 21st2005 at 17:33:45 from line 1.


8/9


Measurement files can be fetched from the server by using FTP with username: nemotest andpassword: nemonemo

After login, change to folder results and download measurement files. Do not try to delete files that arecurrently active, that is, test call(s) is still on.

2. Nokia Terminal Configurat ion

a. Make a test call and adjust the terminal headset volume to minimum.

b. Switch off alert and warning tones. Beeping during measurement will lower the score.

3. Nemo Outdoor Configuration

a. Set Nemo Outdoor Voice Quality test mode to Half Duplex Start TX.

b. Select one of the default test samples: 3s.wav, 4s.wav, 5s.wav, 6s_m.wav , 6s_f.wav.

When Nemo Outdoor calls the fixed line connected to the server, the server answers the call and records1.5 seconds of incoming audio. It then compares the recorded snapshot and chooses the best matchingsample from default samples.

After the identification, the server sends the identified, non-degraded sample to Nemo Outdoor thatrecords it and calculates the PESQ score.

Along with test samples, one can hear short pseudo-noise bursts between samples: those are used forsynchronization purposes and do not affect the PESQ score because they are eliminated before thecalculation.

And the receiving, Nemo Outdoor sends the same sample to the server and because this time the serveralready knows the sample, it records for the duration of the identified sample and calculates the score,opens a measurement file and stores the result there. The file is closed when the line is dropped.

This testing goes on alternating until Nemo Outdoor drops the call or the pseudo-noise sync burst is notdetected for 4 consecutive times by either end.

As the dropped line sound varies greatly in different countries, it might be that the server does not detectthe sound. It can detect up to 3 pre-programmed dropped-line sounds.

In case the server does not detect the line drop, it takes up to 30 seconds for the server to automaticallyhang-up the line as it drops the call after 4 consecutive pseudo-noise bursts are missing.

Therefore,

c. Set the time between calls parameter to one minute in Nemo Outdoor.

Note that sometimes the first pseudo-noise sync burst that is longer than a mid-call burst can be lost dueto an initial handover. In such a case, the server and Nemo Outdoor cannot synchronize. In this case,what happens next depends on the side where it was missing: server hangs up in 30 seconds and NemoOutdoor in 15 seconds so the worst case is 45 seconds. Set one minute between calls to be sure that

the server is ready before the next call comes.


9/9


Log Instructions

The logs of the vqd-service are located in the /usr/vqdfolder and they look like this:20050421_2035_log.txt

The easiest way to retrieve logs is to put them into the tar archive and to send by e-mail.

Log in and open a console as described earlier. Go to the /usr/vqdfolder.

[root@nemoserver root]# cd /usr/vqd/

Make a new archive named logs.tarand put all logs in it

[root@nemoserver root]# tar cf logs.tar *log.txt

Compress the archive

[root@nemoserver root]# gzip logs.tar

Finally, move it to folder /home/nemotestand download it by FTP and send by e-mail as an attachment.

[root@nemoserver root]# mv logs.tar.gz /home/nemotest

nemo server installation guide 7feb07

Documents