V100_PTMC user manual
General Safety Instructions
CAUTION
1. The PxCC that has V100-PTMC card installed must comply with
the country specific safety regulations.
2. Only service personnel should install V100-PTMC card.
3. Before you install V100-PTMC card or remove the cover from your PMC carrier, Unplug the power cord from the computer.
4. For avoiding personal injuries and damage to your computer, and V100-PTMC card, make sure the card’s bezel is secured to the PMC carrier ’s Chassis ground by fastening the card with the screw.
5. Electrical Surges, ESD are very destructive to the equipment.
To avoid it, make sure there is a low impedance discharge path from your computer to Chassis ground.
6. To reduce the risk of damage or injury, follow all steps or procedures as instructed please.
Test Environments
CentOS-5.5
Kernel version: 2.6.18-194.el5
V100-PTMC: opvx_tc_linux_x86-1.0.0
Asterisk: 1.6.2.11
DAHDI: dahdi-linux-complete-2.4.1.2+2.4.1
Hardware: Openvox V100-PTMC
Chapter 1 Overview
1.1 What is Asterisk
The Definition of Asterisk is described as follows:
Asterisk is a complete PBX in software. It runs on Linux, BSD, and Windows (emulated) and provides all of the features you would expect from a PBX and more. Asterisk does voice over IP in four protocols, and can interoperate with almost all standards-based telephony equipment using relatively inexpensive hardware. Asterisk provides Voicemail services with Directory, Call Conferencing, Interactive Voice Response, and Call Queuing. It has support for three-way calling, caller ID services, ADSI, IAX, SIP, H323 (as both client and gateway), MGCP (call manager only) and SCCP/Skinny (voip-info.org).
Figure 1 Topology
1.2 What is V100-PTMC
The V100-PTMC is a high density codec transcoding card. In addition, it is extended to provide voice quality processing features such as voice echo cancellation and adaptive noise reduction. The V100-PTMC is a PTMC, which is compliant with PCIMG2.15/ IEEE1386, IEEE1386.1, and can be integrated into customer’s Compact PCI system. The V100-PTMC also features Ethernet ports and local_CT bus on board. And it can also handle IP TO IP or IP TO TDM transcoding. The V100-PTMC is composed of a core module and a PTMC extender board. The core module contains Vocallo DSP, RAM, Flash, Power Supply, UART, 2 Giga Macs and TDM bus interfaces. The extender PTMC board contains PMC connectors, Giga NIC, Glue, Dip Switch, RJ45 interface of front panel. It connects core module and PCC/PTxCC.
Target Applications
- Hosted VoIP Gateway
- Conferencing Server
- IVR Server
- Distributed Office PBX
- Call Centers
Chapter 2 Hardware Setup
There are some points that should be paid attention to when set up V100-PTMC. In addition, OpenVox design and manufacture V100_PTCCEVB evaluation board to help the customers to evaluate the V100-PTMC on standard PCI bus.
The following is the V100-PTMC image
Figure 2 V100-PTMC
2.1 Hardware Introduction
1. Vocallo DSP and Core Module
The Vocallo DSP, which is used to address transcoding, is located in the core module. The media flow enters and exits through inherent MAC interface and TDM bus interface while the control flow enters and exits just through inherent MAC interface.
2. Giga NIC
The Giga NIC located in extender PMC board bridges the host located in PCC/PTxCC through PCI bus to the vocallo DSP through Eth1.
3. Front Panel RJ45
The front panel RJ45 inextender PMC board supports to provide the packet interface to access the DSP. In some applications, the remote host can communicate with the Vocallo DSP through the front panel RJ45 interface. The interface is always available except PT5MC option is chosen.
4. P4 in PTMC Connectors
The P4 is another packet interface to access the DSP. This interface enables when PT5MC option is chosen.
5. PTMC Connectors
There are four PTMC connectors, which are compliant with PCIMG2.15 (PTMC) electrical specification and IEEE1386, IEEE1386.1 (PMC) mechanical specifications, located in V100-PTMC.
6. Glue
The glue located in extender PMC board bridges the UART and H.110 bus in PMC carrier/PTxCC to the Uart and TDM bus in core module.
2.2 Dip Switch Setup
The Dip switch located at extender PMC board is for configuring the V100-PTMC options.
The following is the Dip Switch Outline.
Figure 3 Dip Switch
Pin 1 is Vocallo DSP Device ID option. If it is ON, the DSP ID is 0x FE. If it is switched to OFF (default), that means the DSP ID is 0x FF. If dual V100-PTMCs are provided on the same PCC/PTCC, one of them should be set to 0x FE, and the other should be set to 0xFF.
Pin 2 is TDM clock of Vocallo DSP enable option. If it is ON, the TDM clock is disabled (default). If it is switched to OFF, the TDM clock is enabled.
Pin3, Pin4 and Pin5 are PTMC configuration options. The V100-PTMC supports 3 PTMC configurations (PT2MC, PT3MC, PT5MC) via Pin3, Pin4, and Pin5. Status “ON” represents binary digital “1”, while “OFF” means 0. For Example, if Pin3-Pin5 is set to 010, PT2MC (default) configuration is enabled. If Pin3-Pin5 is set to 011, PT3MC configuration is enabled. If Pin3-Pin5 is set to 101, PT5MC configuration is enabled.
2.3 LED Indicator
There are 4 LEDs located on the front panel.
Figure 4 Front panel
The T/R flash indicates the front panel RJ45 or P4 in PTMC connectors packet interface is transmitting or receiving data normally.
The LNK light indicates the front panel RJ45 packet interface or P4 in PTMC connectors packet interface is linking up.
The CFG2/3 is PT2MC/PT3MC indicator. If the CFG2/3 is red, which means V100-PTMC is PT2MC option and the PTCC is PT2CC compliant. While if CFG2/3 is green, it means V100-PTMC is PT3MC option and the PTCC is PT3CC compliant.
The CFG5 is PT5MC indicator. Green light means V100-PTMC is PT5MC option and the PTCC is PT5CC compliant.
2.4 Hardware Installation Procedures
- Make sure the V100-PTMC is compatible with your PCC/PTCC. V100-PTMC can be worked together with PCC32, PCC64, PT2CC, PT3CC and PT5CC theoretically. In practice, Electrical compatibility of combinations that include user-defined I/O, whether PMC or PTMC compliant, must be taken into account. The V100-PTMC I/O pins are 5V tolerant for 3.3V. It is recommended that you may consult to our technical support whether the V100-PTMC suits your application.V100_PTCCEVB is a PCI card for evaluating V100-PTMC’s availability.
- Make sure the PCC/PTxCC that has V100-PTMC installed complies with the country specific safety regulations.
- Power off your PCC/PTxCC and unplug it from its AC power source.
- Wear an Anti-static Wrist Strap on your wrist.
- Configure the Dip Switch to the right position.
- Open the cover of the Comppact PCI Platform.
- Remove the filler plate from the front panel of the PCC/PTxCC. (See Figure 5)
- The V100-PTMC must be positioned with care to avoid damaging components against the voltage key post.
- The V100-PTMC bezel enters the front panel of the PCC/PTxCC into alignment with the signal connectors. (See Figure 5)
- Mount the screws. (See Figure 5)
- Replace the cover of the PCC/PTxCC.
- Plug the UTP cable into RJ45 Jack of the V100-PTMC only if the Media/Control Path is the front panel RJ45/UTP.
- Plug the AC power source.
Figure 5 View V100-PTMC Installations
Chapter 3 Software Installation and Configuration
There are three ways to access the DSP, which are Front panel RJ45, P4 inPTMC connectors (Back panel RJ45 on your server) and P1, P2 in PTMC connectors (PCI bus). So you are able to select a type according to the specific environment.
3.1 Download
Download Asterisk package by command below:
#_wget_http://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-1.6.2.11.tar.gz
Download DAHDI package by command below:
Download V100-PTMC package by command below:
#_wget_http://downloads.openvox.cn/pub/drivers/transcoding_cards/opvx_tc_linux_x86-1.0.0.tar.gz
3.2 Installation
Caution: Remember to disable SELinux service. Perform “vim /etc/selinux/config“, change the value of parameter SELINUX to disabled, and then reboot your computer please.
Figure 6 SELinux configuration file
1. Software installation
Some dependencies are crucial. If any of them is absent, the software installation process would not go through successfully. Let’s run “yum install XX“ (XX stands for the dependency’s name) to check the availability of dependencies.
# yum install bison
# yum install bison-devel
# yum install ncurses
# yum install ncurses-devel
# yum install zlib
# yum install zlib-devel
# yum install openssl
# yum install openssl-devel
# yum install gnutls-devel
# yum install gcc
# yum install gcc-c++
# yum install libxml2
# yum install libxml2-devel
If there is no kernel source in the system, users should also install it by running like:
# yum install kernel-devel
If the dependency has been installed, system indicates that nothing to do which means you could go to the next one directly. Otherwise, the system will keep on installing it.
Among DAHDI, Asterisk and V100-PTMC, let’s install DAHDI firstly. Please execute those commands under the directory of /usr/src/ in generally:
# cd /usr/src
# tar –xzvf openvox_dahdi- linux-complete-XX
# cd dahdi-linux-complete-XX
# make
# make install
# make config
Caution: If there is something wrong after “make“, please refer to HERE. In the url link, the moderator introduces you a method how to patch. After patching, save your changes and exit. Then run “make“ again, if successfully done, it is time for you to install Asterisk.
Please operate those commands to install Asterisk.
# cd /usr/src/
# tar –xzvf astersik-XX.tar.gz
# cd asterisk-XX
# ./configure
# make
# make install
# make samples
Please operate those commands to install V100-PTMC
# cd /usr/src
# tar –xzvf opvx_tc_linux_x86-1.0.0.tar.gz
# cd opvx_tc_linux_x86-1.0.0/libopxtc/
# make install
# cd /usr/src/opvx_tc_linux_x86-1.0/codec/asterisk
# make install
2. Configuration
2.1 Modify openvox_codec.conf
# vim /etc/asterisk/openvox_codec.conf
A. If using P1,P2 in PTMC connectors(PCI bus) as communication interface, in this situation, please simultaneously plugging V100-PTMC and asterisk cards to the same server. Sample configuration file openvox_codec.conf is as follows.
If your V100-PTMC is recognized as eth1 by the system, then you need to change the ethX to eth1. One thing you need to note is place V100-PTMC NIC IP and vocalloaddr IP to same network segment, and make these two IPs are different.
B. If using Front panel RJ45 or Back panel RJ45 on your server as communication interface, please directly ignore step 2.2 below. In this case, you will need another PC to provide power to V100-PTMC. Plug V100-PTMC to the PC, and then connect the Asterisk server with the PC over cable or other network devices.Sample of configuration file openvox_codec.conf are as follows.
The X in ethX means the number of the network device that connects with Asterisk server. For example, if your server has two network interface cards, one is eth0, and the other is eth1, and suppose to connect eth1 with V100-PTMC, then you will need to modify X to 1 and modify vocalloaddr to the same network segment as eth1.You can also connect the V100-PTMC through other devices, such as router、switches and so on.
2.2 Setting V100-PTMC NIC IP by running the below command. Right here, let’s take eth1 for an example.
# vim /etc/sysconfig/network-scripts/ifcfg-eth1
Set BOOTPROTO =static
Add two line: IPADDR=10.1.1.80
NETMASK=255.255.255.0
Figure 7 ifcfg-eth1 configurations
After the network settings, remember to perform “service network restart” to restart the network and activate V100-PTMC NIC. See more V100-PTMC details by “ifconfig“.
2.3 Before starting Asterisk, please run “vim /etc/asterisk/modules.conf“, and add a line “noload => res_timing_pthread.so” at the end of modules.conf, it will disable the timing module. Otherwise, it’s going to display many errors from asterisk.
2.4 Enable asterisk by running “asterisk –vvvvvvvgc“, if it has been started before, run “asterisk -r” instead. In the CLI, perform “module load codec_openvox.so” to load V100-PTMC driver.
After entering into CLI, type “op” and press Tab. If it displays openvox, which means installation finished elementarily. Please also perform other commands to check related information, for instance, run “openvox show translators” to show supportive code conversion mode.
It will show license information as below after run “openvox show license“.
3.3 Call Test
Run command below to register two SIP phone, and add configuration at the end of sip.conf.
# vim /etc/asterisk/sip.conf
Figure 8 SIP phone register
Add dial plan at the end of extensions.conf.
# vim /etc/asterisk/extensions.conf
Figure 9 dialplan
Follow the above dialplan to configure two SIP phones, one chooses G711 alaw/ulaw as audio encoding pattern, and the other choose G729. If call normally, it means installation is successful.
Chapter 4 Reference
Tips
Any questions during installation, please consult in our forum or look up for answers from the following websites:
Appendix A Specifications
Dimension
• Compliant with IEEE1386 mechanical specifications
• 149.0×74.0mm(PCB)
Interfaces
•PCI : 32bit 33/66MHz
•Local CT
•10/100/1000 BASE-T RJ45
•UART
•Backplane Gbe
•PMC Connector
Power Requirements
Operating Temperature Range
•0 to 50 °C
Humidity
•10 to 90% NON-CONDENSING
Hardware and Software Requirements
•PCC,PT2CC,PT3CC,PT5CC
•Windows/Linux in Host
Appendix B Transcoding
Codec Support
•G.711 •G.729
•G.722 •GSM
•G.723 •iLBC
•G.726
Transcoding Table
Source code
|
ilbc |
g722 |
g723 |
g726 |
g729 |
alaw |
ulaw |
gsm |
|
ilbc |
|
√ |
√ |
√ |
√ |
√ |
√ |
√ |
|
g722 |
√ |
|
√ |
√ |
√ |
√ |
√ |
√ |
|
g723 |
√ |
√ |
|
√ |
√ |
√ |
√ |
√ |
|
g726 |
√ |
√ |
√ |
|
√ |
√ |
√ |
√ |
|
g729 |
√ |
√ |
√ |
√ |
|
√ |
√ |
√ |
|
alaw |
√ |
√ |
√ |
√ |
√ |
|
√ |
√ |
|
ulaw |
√ |
√ |
√ |
√ |
√ |
√ |
|
√ |
|
gsm |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
|
“√” means the two codes are able to be transcoded.