OpenVox IPC 100 Test Report - cosmocom.gr · OpenVox IPC 100 Test Report ... Test 7 OpenVox IPC100...

OpenVox Test Report

OpenVox Communication Co. Limited URL : http://www.openvox.cn

- 1 -

OpenVox IPC 100 Test Report

OpenVox IPC100 Series

Atom Fan-less CPU Boards

OpenVox Test Report


- 2 -

Contents

Environments ................................................................................................................................- 3 -

Test 1 Tests Based On SIP Calls ................................................................................................- 5 -

Test 1.1 SIP G.711 codec call testing ..................................................................................- 5 -

Test 1.1.1 WinSIP-Playback mode ..............................................................................- 5 -

Test 1.1.2 WinSIP-WinSIP mode ................................................................................- 8 -

Test1.2 SIP G.729 codec call testing................................................................................ - 11 -

Test 2 One OpenVox A400M with 4 analog ports (2FXS, 2FXO – 4 channels) ...................... - 14 -

Test 3 Two OpenVox A400M with 8 analog ports (4FXS, 4FXO – 8 channels) ...................... - 16 -

Test 4 One OpenVox B400M with 4 digital ISDN BRI ports (2 NT modes, 2 TE modes – 8 voice

channels) .................................................................................................................................. - 19 -

Test 5 Two OpenVox B400M with 8 digital ISDN BRI ports (4 NT modes, 4 TE modes – 16 voice

channels) .................................................................................................................................. - 21 -

Test 6 OpenVox IPC100 with Elstix-1.6 ................................................................................. - 24 -

Test 7 OpenVox IPC100 with Elastix-2.0 ............................................................................... - 27 -

Test 8 OpenVox IPC100 with Asterisk-GUI-2.0.4 .................................................................. - 30 -

Test 9 OpenVox IPC100 with Trixbox-2.8 ............................................................................. - 32 -

Test 10 OpenVox IPC100 with soft echo ................................................................................. - 35 -

Test 10.1 Environments ................................................................................................. - 35 -

Test 10.2 Methods ......................................................................................................... - 35 -

Test 10.3 Results ............................................................................................................ - 36 -

OpenVox Test Report


- 3 -

Environments

Hardware：

Using the following hardware to test:

Motherboard Model: IPC100

OpenVox A400M mini-PCI card, 4 analog channels

OpenVox B400M mini-PCI card, 4 ISDN channels

IPC100 Board specifications:

• CPU: Intel Atom Z510P 1.1GHz/Z520P1.3G/Z530P 1.6G

• DRAM: Slot Onboard, up to 2GB DDR2 400/533 SDRM(double side 1GB)

• Chipset: Intel Poulsbo

• South Bridge: Poulsbo integrated

• Storage: CompactFlash socket, 44pin PATA connector 1 SATA slot (only available at

Power in DC 12V)

• Power: DC jack, 7V to 20V, Suggest 12V supply,

Center pin =positive, sleeve = ground, 2.1 mm diameter.

• Three front panel LEDs, for 3 programmable GPO status indicators.

• Pushbutton: for mode setting switch, accessing a programmable GPI, active low means

switch pressed

• Expansion: 2 mini-PCI slot, fixed and individual interrupt (under CentOS 5.3 5.4)

• Connectivity: Up to 3 Ethernet channels (10/100Mbps speed)

2 PCI Ethernet Controller.

1 PCI-E Ethernet controller (can be configured as a Giga-bit LAN at Factory)

Fixed and individual interrupt (under CentOS 5.3 5.4)

Support PXE (for remote boot)

• I/O: DB9 serial port, debug console, RS232

2* USB 2.0 port

• Board size: 6 x 6" (152.4 x 152.4 mm)

• Temperature: 0℃ to 60 ℃ (contact factory for more temp. options)

• Firmware: AMI BIOS

• PCB layer: 8

• Power dissipation: ~6W (Condition: 1GB memory, unattached HDD, unattached miniPCI card,

attached 4GB CF card, under windowsXP)

OpenVox A400M card technical specifications:

• Modular Design: Up to 4 FXS, FXO or mixed FXS/FXO ports per card

• Support mini PCI type Ⅲ

• Designed for low-power systems

• Support both 3.3 V and 12 V

OpenVox Test Report


- 4 -

OpenVox B400M card technical specifications:

• Modular Design: The ports can be configured as 4 digital ISDN BRI ports (NT or TE mode), or

mixed ISDN BRI (NT or TE mode) ports per card

• Support mini PCI type Ⅲ

• Designed for low-power systems

• Support both 3.3 V or 38 V(NT ONLY)

Software:

• CentOS 5.5

• asterisk-1.6.2.10

• dahdi-linux-complete-2.2.0.2+2.2.0

• mISDN-1.1.9.1

• mISDNuser-1.1.9.1

OpenVox Test Report


- 5 -

Test 1 Tests Based On SIP Calls

Test 1.1 SIP G.711 codec call testing

G.711 is a high bit rate (64 Kbps) codec, which gives the best voice quality in

VoIP based telephony systems. Since it uses no compression and it is the same codec

used by the PSTN network and ISDN lines, it sounds just like using a regular or ISDN

phone. It also has the lowest latency (lag) because there is no need for compression,

which costs processing power.

Test 1.1.1 WinSIP-Playback mode

IPC100 with Asterisk

Net

NetWinSip

Playback IVR

Figure 1

OpenVox Test Report


- 6 -

Results of test

OpenVox IPC100 with CPU Z510 1.1GHZ

CPU usage:

Figure 2

RAM usage:

Figure 3

Results of test:

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

9 14 18 23 27 35 51 63

cpu usage asterisk

cpu usage asterisk

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

9 14 18 23 27 35 51 63

asterisk used RAM

asterisk used RAM

Number of calls

CP

U u

sage

%

Number of calls

RA

M u

sed

%

OpenVox Test Report


- 7 -


CPU usage:

Figure 4

RAM usage:

Figure 5

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

10 20 40 60 80 100 120

cpu usage asterisk

cpu usage asterisk

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

3.50%

10 20 40 60 80 100 120

asterisk used RAM

asterisk used RAM

Number of calls

CP

U u

sage

%

Number of calls

RA

M u

sed

%

OpenVox Test Report


- 8 -

Test 1.1.2 WinSIP-WinSIP mode

IPC100 with Asterisk

NetWinSip 1

caller

Net

NetNet

WinSip 2

callee

Figure 6

OpenVox Test Report


- 9 -

Results of test:


CPU usage:

Figure 7

RAM usage:

Figure 8

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

20 40 60 80 100

cpu usage asterisk

cpu usage …

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

20 40 60 80 100

asterisk used RAM

asterisk used RAM

CP

U u

sage

%

RA

M u

sed

%

Number of calls

Number of calls

OpenVox Test Report


- 10 -

Results of test:

OpenVox IPC100 with CPU Z530 1.6GHZ:

CPU usage:

Figure 9

RAM usage:

Figure 10

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

20 40 60 80 100 120 140

cpu usage asterisk

cpu usage …

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

3.50%

20 40 60 80 100 120 140

asterisk used RAM

asterisk used …

CP

U u

sage

%

Number of calls

RA

M u

sed

%

Number of calls

OpenVox Test Report


- 11 -

Test1.2 SIP G.729 codec call testing

G.729 offers toll quality speech at a reasonably low bit rate of 8Kbps. However, it is a rather

"costly" codec in terms of CPU processing time. G.729 codec achieve high level of compression

and that is reason for intensively use of CPU. Test confirming that and as you can see from results.

Results of test:


CPU usage:

Figure 11

RAM usage:

Figure 12

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

9 14 18 23 27

cpu usage asterisk

cpu usage asterisk

1.00%

1.10%

1.20%

1.30%

1.40%

1.50%

1.60%

1.70%

1.80%

1.90%

9 14 18 23 27

asterisk used RAM

asterisk used RAM

Number of calls

CP

U u

sage

%

RA

M u

sed

%

Number of calls

OpenVox Test Report


- 12 -

Results of test:


CPU usage:

Figure 13

RAM usage:

Figure 14

Conclusions:

When analyzing all the acquired data, which is presented as diagrams, we see that with 140

concurrent calls CPU usage is around 77%, and the box is still responsive. All the calls are still

normal, meaning one can hear audio without noise or constant crackle.

From the diagrams we can conclude that OpenVox IPC100 with Z530 1.6GHz can support up

to 140 G.711 codec concurrent calls , CPU usage of asterisk is about 77%, RAM memory of

asterisk is about 3.1%.

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

10 20 30 40 50

cpu usage asterisk

cpu usage asterisk

1.00%

1.05%

1.10%

1.15%

1.20%

1.25%

10 20 30 40 50

asterisk used RAM

asterisk used RAM

CP

U u

sage

%

Number of calls

RA

M u

sed

%

Number of calls

OpenVox Test Report


- 13 -

Testing summary report for test based on SIP calls

Following tables contain summary report of all tests we made which are based on SIP calls.


Type of test Max number of calls

CPU usage of asterisk

at max number of

calls

RAM usage of

asterisk

SIP based calls codec

G.711 63 96% 2.6%


G.729 27 95% 1.8%


Type of test Max number of calls

CPU usage of asterisk

at max number of

calls

RAM usage of

asterisk


G.711 120 98% 3.1%


G.729 50 76% 1.23%

OpenVox Test Report


- 14 -

Test 2 One OpenVox A400M with 4 analog ports

(2FXS, 2FXO – 4 channels)

Following picture is schematic diagram of testing environment. We have two SIP phones

(extensions 100 and 200) and IPC100 board based PC with one OpenVox A400M analog card

with 2 FXO and 2 FXS port. Two FXO ports were configured as trunks and physically connected

to two other FXS ports.

IP Phone

Extension 100

IP Phone

Extension 200

IPC100 with A400M

2 FXS

2 FXO

Analog

ExtensionFXS FXO IVR

Figure 15

Test procedure was made as following:

1. VoIP extension 100 calls to analog extension 1001,

2. Because of analog extensions are physically connected to analog trunk, calls will be going to

FXOs,

3. FXOs answer and play the IVR.

4. VoIP extension 200 is the same as the above 3 steps.

OpenVox Test Report


- 15 -

Results of test

CPU usage:

Figure 16

RAM usage:

Figure 17

0.00%

1.00%

2.00%

3.00%

4.00%

5.00%

6.00%

7.00%

2 4

cpu usage asterisk

cpu usage asterisk

0.00%

0.10%

0.20%

0.30%

0.40%

0.50%

0.60%

0.70%

0.80%

0.90%

2 4

used RAM

used RAM

RA

M u

sed

%

OpenVox Test Report


- 16 -

Test 3 Two OpenVox A400M with 8 analog ports

(4FXS, 4FXO – 8 channels)

Following picture is schematic diagram of testing environment. We have four SIP phones

(extensions 100, 200, 300, 400) and IPC100 board based PC with two OpenVox A400M analog

cards with 4 FXO and 4 FXS ports. Four FXO ports were configured as trunks and physically

connected to Four FXS ports.

IP Phone

Extension 100

IP Phone

Extension 200

IP Phone

Extension 400

IP Phone

Extension 300

IPC100 with A400M

4 FXS

4 FXO

SIP

ExtensionFXS FXO IVR

Figure 18

Test procedure was made as following:

1. VoIP extensions100 calls to then analog extensions 1001.

2. Because of analog extensions are physically connected to analog trunks, calls will be going to

FXO.

3. FXO answers and then plays the IVR.

4. VoIP extensions 200, 300 and 400 are the same.

OpenVox Test Report


- 17 -

At this point we have 8 analog voice channels and 4 SIP channels enabled.

Results of test:

CPU usage:

Figure 19

RAM usage:

Figure 20

Conclusions:


concurrent calls CPU usage is around 14%. All the calls are still normal, meaning one can hear

audio without noise.

8 analog calls statistics:

14 % CPU usage

1.4 % of used RAM memory

0.00%

2.00%

4.00%

6.00%

8.00%

10.00%

12.00%

14.00%

16.00%

2 4 6 8

cpu usage asterisk

cpu usage asterisk

0.00%

0.20%

0.40%

0.60%

0.80%

1.00%

1.20%

1.40%

1.60%

2 4 6 8

used RAM

used RAM

OpenVox Test Report


- 18 -

No problems and clicks in audio

Testing summary report for test based on OpenVox A400M

number of calls CPU usage of asterisk

2 5.6%

4 6.9%

6 10.8%

8 13.8%

OpenVox Test Report


- 19 -

Test 4 One OpenVox B400M with 4 digital ISDN BRI

ports (2 NT modes, 2 TE modes – 8 voice channels)

Following picture is schematic diagram of testing environment. We have two SIP phones

(extensions 100 and 200) and IPC100 board based PC with one OpenVox B400M digital ISDN

BRI card with 2 ISDN BRI ports (NT mode) and 2 ISDN BRI ports (TE mode). Both of these

ISDN BRI ports (TE mode) were configured as trunks and physically connected to other two

ISDN BRI ports (NT mode).

SIP Phone

SIP Phone

IPC 100 with B400M

TE

NT

SIP

extensionNT TE IVR

Figure 21

OpenVox Test Report


- 20 -

Results of test:

CPU usage:

Figure 22

RAM usage:

Figure 23

0.00%

2.00%

4.00%

6.00%

8.00%

10.00%

12.00%

14.00%

2 4

cpu usage asterisk

cpu usage asterisk

0.00%

0.20%

0.40%

0.60%

0.80%

1.00%

1.20%

1.40%

1.60%

1.80%

2.00%

2 4

used RAM

used RAM

RA

M u

sed

%

OpenVox Test Report


- 21 -

Test 5 Two OpenVox B400M with 8 digital ISDN BRI

ports (4 NT modes, 4 TE modes – 16 voice channels)

Following picture is schematic diagram of testing environment. We have four SIP phones

(extensions 100,200,300 and 400) and IPC100 board based PC with two OpenVox B400M digital

ISDN BRI cards with four ISDN BRI ports (NT mode) and four ISDN BRI ports (TE mode). Four

of these ISDN BRI ports (TE mode) were configured as trunks and physically connected to other

four ISDN BRI ports (NT mode).

SIP Phone

Extension 100

SIP Phone

Extension 200

SIP Phone

Extension 400

SIP Phone

Extension 300

IPC100 with B400M

TE

NT

SIP

ExtensionNT TE IVR

Figure 24

OpenVox Test Report


- 22 -

Results of test

CPU usage:

Figure 25

RAM usage:

Figure 26

Conclusions


concurrent calls CPU usage is around 27.19%. All the calls are still normal, meaning one can hear

audio without noise.

8 digital ISDN BRI calls statistics:

27.19 % CPU usage

1.8 % of used RAM memory

No problems and clicks in audio

0.00%

5.00%

10.00%

15.00%

20.00%

25.00%

30.00%

2 4 6 8

cpu usage asterisk

cpu usage asterisk

0.00%

0.50%

1.00%

1.50%

2.00%

2 4 6 8

used RAM

used RAMRA

M u

sed

%

OpenVox Test Report


- 23 -

Testing summary report for test based on OpenVox B400M

number of calls CPU usage of asterisk

2 7.28%

4 11.46%

6 24.06%

8 27.19%

OpenVox Test Report


- 24 -

Test 6 OpenVox IPC100 with Elstix-1.6

Below four figures describe the system information that Elastix installed on OpenVox

IPC 100.

CPU info, Memory usage, Swap usage and so on.

Figure 27

OpenVox Test Report


- 25 -

Utilize diagram to describe the CPU info and Memory usage when some concurrent calls are

working.

Figure 28

OpenVox Test Report


- 26 -

Main Screen:

Figure 29

Flash Operator Panel:

Figure 30

OpenVox Test Report


- 27 -

Test 7 OpenVox IPC100 with Elastix-2.0

OpenVox IPC 100 not only able to run Elastix-1.6, but also of course include the latest

version Elastix-2.0. And below figures are showing the information that Elastix-2.0 is

running on OpenVox IPC100.

Figure 31

OpenVox Test Report


- 28 -

The hardware detector option can detect the existing cards that plugged on the system PCI

slots. And here, apparently detects one BRI card.

Figure 32

Main Screen of Elastix-2.0 PBX Option:

Figure 33

OpenVox Test Report


- 29 -

Operator Panel Window:

Figure 34

OpenVox Test Report


- 30 -

Test 8 OpenVox IPC100 with Asterisk-GUI-2.0.4

OpenVox IPC 100 also owns the ability to run Asterisk-GUI. Here, below these figures are

some interfaces and options for configuration.

Login Window:

Figure 35

Add SIP/IAX Trunk Screen:

Figure 36

OpenVox Test Report


- 31 -

General Preferences Screen:

Figure 37

General Settings:

Figure 38

OpenVox Test Report


- 32 -

Test 9 OpenVox IPC100 with Trixbox-2.8

Below figures are showing the information when Trixbox running on OpenVox IPC100.

System info Panel:

Figure 39

OpenVox Test Report


- 33 -

OS and Network information panel:

Figure 40

Main Screen:

Figure 41

OpenVox Test Report


- 34 -

Conclusion:

OpenVox IPC100 supports currently mainstream PBX which integrated GUI like Elastix,

Trixbox, Asterisk-GUI and so on.

OpenVox Test Report


- 35 -

Test 10 OpenVox IPC100 with soft echo

The following tests are based on OpenVox IPC100 on the purpose of comparing soft echo

causes the influences of CPU and Memory in these three situations: no soft echo, soft echo

oslec and soft echo mg2. Please refer the below table for details.

As we can see, soft echo mg2 needs a little more CPU resource than the other two situations.

Test 10.1 Environments

---------------------------------------------------------------------

Elastix-2.0

Compact Flash Card: 8GB 133X


---------------------------------------------------------------------

Test 10.2 Methods

Step 1: Disable the soft echo.

cd /etc/dahdi/

vi genconf_parameters

Step 2: Reconfigure the channels by these commands:

service dahdi stop

modprobe dahdi

modprobe wctdm

dahdi_genconf

dahdi_cfg

OpenVox Test Report


- 36 -

Step 3: Make some concurrent calls (8,6,4,2) and make sure all the channels are working

well, then, capture the information that you want during the calls running.

Step 4: Change the type of soft echo from oslec to mg2 for another situation.

Repeat the step 2 above and go further the next.

Test 10.3 Results

The following results are based on OpenVox IPC100(1.6G) and OpenVox A400M.

OpenVox IPC 100 Test Report - cosmocom.gr · OpenVox IPC 100 Test Report ... Test 7 OpenVox IPC100...

Documents

Transcript of OpenVox IPC 100 Test Report - cosmocom.gr · OpenVox IPC 100 Test Report ... Test 7 OpenVox IPC100...