Ss 7 Fun 04

Aculab digital network access cards
Call, switch, and speech, telephony software installation guide
MAN1761 Version 6.4.7

Proprietary Information
Aculab Plc makes every effort to ensure that the information in this document is correct at the
time of publication. Aculab does not, however, accept responsibility for any errors or omissions.
Aculab has a policy of continuous product introduction and improvement. Please check
documentation and product versions to ensure accuracy of information.
IBM and PC/AT are registered trademarks of International Business Machines Corporation.
MVIP is a trademark of GO MVIP Inc.
All other trademarks are recognised and acknowledged. Aculab Plc reserves the right to change
or amend specification without notice.
© Copyright Aculab Plc 2004:All rights reserved
RECORD OF REVISION
Rev Date By Detail
6.0 06.12.02 CJL Interim release
6.1.0A 19.06.03 DJL Controlled release of initial revision 6 software
6.1.0 15.01.04 DJL updated installation and configuration tools
6.1.1 18.06.04 DJL Review updates
6.2.2 07.09.04 DJL Beta release
6.2.2 15.09.04 DJL Full release
6.2.3 28.10.04 DJL Updates for Linux
6.2.4 12.11.04 DJL Addition of SS7 signalling link and ISUP bearer ACT info.
6.3.0 24.12.04 DJL Various updates including support for new hardware
6.3.1 26.01.05 DJL Corrections to appendix B
6.3.2 10.02.05 DJL Removal of Solaris restrictions
6.3.3 22.02.05 DJL Addition of Linux/Solaris configuration notes
6.3.4 19.04.05 DJL Correction of typological errors
6.3.5 26.05.05 DJL Review of ACT functions
6.4.0 03.11.05 DJL Updates for V6.4 release
6.4.1 18.01.06 DJL Correction of ACT images/definitions
6.4.2 10.04.06 DJL Review updates — small changes
6.4.3 06.07.06 DJL Update to document cross reference descriptions
6.4.4 15.08.06 DJL Update to Prosody X information
6.4.5 21.08.06 DJL New example added - installing a Prosody X card.
6.4.6 05.10.06 DJL Updates to Linux installation example
6.4.7 14.12.06 DJL Updates to include Solaris specific information
2
Contents
1 Getting started.................................................................................................................................................... 5
1.1 Introduction ...................................................................................................................... 5
2 Installation process overview................................................................................................................... 6
2.1 Install the Aculab hardware .............................................................................................. 6
2.2 Host system startup. .......................................................................................................... 6
2.2.1 E1/T1 trunk and Prosody PCI and cPCI cards ........................................................ 6
2.2.2 E1/T1 16 trunk cPCI card ...................................................................................... 6
2.2.3 IP telephony PCI and Prosody X PCI, cPCI and PCIe cards .................................... 6
2.2.3.1 Pre Prosody X (IP Telephony PCI) ............................................................... 7
2.2.3.2 Prosody X ................................................................................................... 7
2.3 Dowloading and installing the V6 telephony software ...................................................... 9
2.4 Configuring the Aculab Telephony Software ..................................................................... 9
2.5 Aculab example code ....................................................................................................... 9
3 Example card installation and configuration for a windows environment............. 10
3.1 Installing the Prosody X card hardware. .......................................................................... 10
3.2 Starting the Prosody X card host system. ......................................................................... 10
3.3 Download and install of the Aculab telephony-software. ................................................ 11
3.4 Adding the card to the Aculab card list (Prosody X only)................................................. 15
3.4.1 Setting up the Ethernet TCP/IP card address ........................................................ 15
3.4.2 Updating the Aculab card list.............................................................................. 15
3.5 Configuring the Aculab telephony-software. ................................................................... 18
3.5.1 Special consideration - using CAS and SS7 ISUP protocols on PMXC modules ... 18
3.5.2 Card Details ........................................................................................................ 18
3.5.3 Clocking settings ................................................................................................. 21
3.5.4 IP Settings............................................................................................................ 22
3.5.5 TiNG Settings ...................................................................................................... 23
3.5.6 Applying the configuration.................................................................................. 24
4 Example installation and configuration for a non-windows environment. ............ 26
4.1 Telephony-software download and installation............................................................... 26
4.2 Linux/Solaris drivers ........................................................................................................ 27
4.2.1 Pre-requisites....................................................................................................... 27
4.2.2 Making Libraries and Supporting Utilities............................................................ 27
4.2.3 Building, and Configuring, the Driver.................................................................. 27
4.2.4 Creating the Driver.............................................................................................. 28
4.2.5 Creating the Prosody X NIC Driver on Linux ....................................................... 28
4.2.6 Installing the Prosody X NIC Driver on Solaris .................................................... 28
4.2.7 Configuring the Driver......................................................................................... 28
4.2.8 Loading and Unloading the Driver ...................................................................... 28
4.2.9 Automatic Loading of the Driver ......................................................................... 29
4.2.10 Removing the Driver ........................................................................................... 29
4.2.11 Setting up Prosody X Card IP Address on Linux................................................... 29
4.2.12 Setting up Prosody X Card IP Address on Solaris ................................................. 29
4.3 Managing Prosody X cards.............................................................................................. 30
4.3.1 Distinguishing Prosody X cards on Linux ............................................................ 30
4.3.1.1 How it works............................................................................................ 30
4.3.1.2 Simple use................................................................................................ 30
4.3.1.3 Speeding up the process........................................................................... 30
4.3.2 Adding a Remote Prosody X card ........................................................................ 31
4.3.3 Adding a Local Prosody X Card........................................................................... 32
4.3.4 Listing installed Prosody X cards ......................................................................... 32
4.3.5 Obtaining information for an installed Prosody X card ........................................ 32
4.3.6 Removing a Prosody X card ................................................................................ 32
4.4 Card configuration files ................................................................................................... 33
4.4.1 Creating configuration files ................................................................................. 33
4.4.2 Per-card configuration file description................................................................. 35
4.4.3 Example configuration files ................................................................................. 39
4.4.4 Configuration file updates ................................................................................... 41
3
4.5 Signalling Software Installation........................................................................................ 42

4.5.1 Firmware files and extensions.............................................................................. 42
4.5.2 Firmware and DSP download (FWDSPLDR) ........................................................ 42
Appendix A: Aculab PCI & Compact PCI cards...............................................................................43
A.1 Device driver installation — common parameters............................................................. 43
A.2 E1/T1 PCI Primary Rate Trunk card ................................................................................. 43
A.3 Serial Number location ................................................................................................... 43
Appendix B: Call Driver Installation Options ....................................................................................44
B.1 Table of Signalling System Options ................................................................................. 44
B.2 System Specific Option definitions .................................................................................. 45
B.2.1 -cA/B and X/Y bits configuration (DPNSS only).................................................... 45
B.2.2 —cBBY Backbusy control (CAS only) ................................................................... 45
B.2.3 -cCA connect acknowledgement (ETS300 only) .................................................. 45
B.2.4 —cCICnnnn circuit identification codes (ISUP only) ........................................... 45
B.2.5 -cCn number of CLI digits (CAS only) .................................................................. 45
B.2.6 —cDn number of DDI digits (CAS only)................................................................ 46
B.2.7 -cDPCnnnnn signalling point code (ISUP only) ................................................... 46
B.2.8 -cEn Call Charging Switch (ETS300 only)............................................................ 46
B.2.9 —cEX Primary Rate Call Charging (ETS300 only) .................................................. 47
B.2.10 -cFD Diversion (QSIG, ETS300, AT&T T1, and NI-2)........................................... 47
B.2.11 -cFF facility (QSIG, ETS300, and NI2).................................................................. 47
B.2.12 -cFP MLPP activation (ETS300 only) .................................................................... 47
B.2.13 -cFR Raw Data (ETS300 and QSIG) ..................................................................... 47
B.2.14 -cFU user to user (QSIG and ETS300) .................................................................. 47
B.2.15 -cIMP75............................................................................................................... 47
B.2.16 —cME ................................................................................................................... 47
B.2.17 -cNA1 release link trunk (NI-2 only) .................................................................... 48
B.2.18 -cNCRC disable CRC4 (ISUP only) ...................................................................... 48
B.2.19 —cNE network end configuration (DASS, ETS300, FETEX, AT&T, and NI2) .......... 48
B.2.20 -cOPCnnnnn[,i] (ISUP only) ................................................................................ 48
B.2.21 -cQM/S-A/B master/slave priority (QSIG only) ..................................................... 48
B.2.22 -cRn Default clearing cause (all versions) ............................................................ 48
B.2.23 -cSLCnn signalling link code (ISUP only)............................................................. 48
B.2.24 -cSO disable service message (AT&T and NI2) .................................................... 49
B.2.25 -cSP stop call proceeding (ETS300 only).............................................................. 49
B.2.26 -cSU stop setup acknowledge (ETS300 only) ....................................................... 49
B.2.27 —cSW configuration (ETS300 only) ...................................................................... 49
B.2.28 -cTS[I]nn (ISUP only) ........................................................................................ 49
Appendix C: Troubleshooting ......................................................................................................................50
C.1 Call Driver and Signalling Firmware Problems ................................................................ 50
Device Driver Error Message ........................................................................................... 50
C.1.1 Firmware Download Errors.................................................................................. 50
4
1 Getting started
1.1 Introduction
This document is a guide to the installation procedure for the Aculab telephony software
components; as required by Aculab digital access & Prosody PCI, cPCI, and PCIe format cards.
It provides an overview of the download, installation, and configuration of the call, switch, and
speech drivers, the signalling protocol firmware, and rich media speech processing firmware,
(Aculab telephony software).
It does not cover the regulatory requirements and hardware installation of the cards. Please refer
to the appropriate hardware installation guides for further details.
Aculab supports many popular operating systems and numerous signalling systems for use with
the E1/T1 primary rate modules (PM/PMX/PMXC). Precise details of the installation of the Aculab
telephony software are dependent on the operating system and signalling system(s) being used.
ASCII text files are used to configure clocking, protocol firmware, DSP firmware, and Prosody
firmware as appropriate for each card. These text files can be created/edited either by using a
text editor or by running the Aculab configuration tool (ACT).
The V6 telephony software Aculab configuration tool (ACT) supports the following operating
systems:
Windows 2000 with service pack 2 or later
Windows XP with service pack 1 or later
Linux/Solaris (Please check with Aculab for confirmation of the supported distributions)
CAUTION All earlier versions of the Aculab Configuration Tool should be un-installed before loading a new version. As a precaution, double
check that all earlier versions of library and configuration files have also been deleted before proceeding.
5
2 Installation process overview

Installing and configuring Aculab hardware and any associated telephony software involves a
number of key steps:
1. Install the Aculab hardware.
2. Start the Aculab hardware host system.
3. Download the required Aculab telephony-software distribution package.
4. Configure the Aculab telephony-software.
Once you have completed these steps, you will be able to utilise the Aculab card telephony
software and hardware resources through the various Aculab application programming interfaces
(APIs).
2.1 Install the Aculab hardware

Install the Aculab hardware in accordance with the appropriate hardware installation guide.
2.2 Host system startup.

2.2.1 E1/T1 trunk and Prosody PCI and cPCI cards
If you install the Aculab cards before you have installed the V6 telephony software, you will
need to cancel hardware auto detection on start-up. For example, for Windows 2000:
1. Install the cards into the required system as detailed in the appropriate hardware
manuals.
2. Power up the system
3. Once Windows has started, the system will attempt to auto-detect the new hardware. As
the card drivers are Aculab specific drivers, they will not be available until you have
downloaded the Aculab telephony software, in this instance select Cancel.
2.2.2 E1/T1 16 trunk cPCI card
This card uses an X type primary-rate module, called a PMX, or PMXC if it also contains
signalling DSP resources. Communication with the PMX requires an Ethernet IP address to be
assigned to the base card at start-up. This is achieved by using an IP Addresses co-installer
application. For Windows:
manuals.
Once Windows has started, the system will auto-detect the new hardware and start the IP
Addresses co-installer application. For details on using the IP Addresses co-installer application,
please refer to the E1/T1 16 trunk cPCI card hardware installation guide.
2.2.3 IP telephony PCI and Prosody X PCI, cPCI and PCIe cards
Unlike earlier Aculab cards, which used bespoke communication between the base card, DSPs,
PM, and PCI/cPCI (host system), communication between the base card, rich media DSPs,
PMX/PMXC resources, and the host system, now uses TCP/IP Ethernet protocols managed
through an Ethernet switch on the base card.
Note Please refer to the ‘card boot & discovery’ section of the ‘Prosody X administration guide’ for further guidance on Prosody X boot-up
and network configuration considerations.
manuals.
4. Once Windows has started, the system will auto-detect the new hardware as an Ethernet
card. As the card’s driver is an Aculab specific driver, it will not be available until you
have downloaded the Aculab telephony software, in this instance select Cancel.
6
2.2.3.1 Pre Prosody X (IP Telephony PCI)
Primry rate module Proprietary connection

(PM)
IP Telephony PCI card

Card resources
DSP resources
NIC B
TCP/IP network
PCI/cPCI connection
NIC A Host system
The Aculab IP telephony PCI card resources are managed through the standard PCI/cPCI bus
interface, however management of IP Telephony on early cards required a communication path
from NIC B to the host system via NIC A. Since V6.4, and the introduction of the cross bus
driver, this communication path is no longer required.
Configuration of NIC A is via the host system; for example, using Microsoft Windows network
connections.
Configuration of NIC B is via either the ACT for windows or the prosody_ip_card_mgr
command.
2.2.3.2 Prosody X
PMX/PMXC Proprietary connection

resources
Prosody X PCI card Prosody X resources
Ethernet
NIC B
Switch
Ethernet DSP resources

port
NIC C
TCP/IP network
PCI/cPCI connection
NIC A Host system
The Prosody X card is detected by the host system as a network interface card (shown as NIC C).
Communication with the Prosody X card media DSP and PMX/PMXC card resources is also via
an Ethernet connection (shown as NIC B).
Configuration of NIC C is via the host system; for example, using Microsoft Windows network
connections.
7
Configuration of NIC B is via either the ACT for windows or the prosody_ip_card_mgr
command.
The Prosody X card contains an Ethernet switch, which connects NIC B with both the local host
system via NIC C, and a TCP/IP network via the cards Ethernet port. Management of the Prosody
X card resources can therefore be carried out either by the local host via NIC C, or by a remote
host via the TCP/IP network Ethernet port.
Note As Windows recognises the Prosody X card as a network adapter (NIC) and not an Aculab Computer Telephony device, it will not
appear automatically in the ACT card list. It must be manually added to the list before it can be configured.
To achieve this, a new option has been added to the ACT card list dialog called Prosody X cards…
This option will open a dialog that allows you to enter the serial numbers of Prosody X cards,
and to assign IP address (NIC B) to each card for communication with the DSP and PMX/PMXC
resources. A command line option is also available.
8
2.3 Dowloading and installing the V6 telephony software

The required V6 telephony software is available for download from the Aculab company web
site at www.aculab.com. To assist you with downloading and installation, Aculab provide a
windows tool called the Aculab install tool (AIT). How to use the AIT application, is detailed in
the Aculab install tool - FTP downloads utility guide. The non-windows command line tool, instcmd, is
detailed in section 4.1 of this document.
The AIT application can be run on most systems, however Internet access would normally be
required to enable you to select and download the individual V6 telephony software
components required for your particular system configuration. Should you require to run the
Aculab installer on a stand alone system, the Aculab installer tool has an option to create a zip
file, either manual or self extracting, that can be exported and run on a stand alone system. The
zip file contains a copy of the Aculab installer tool along with any files you have downloaded for
that configuration.
AIT application installation options
AculabInstaller.exe - running this version will install a copy of the AIT application only
onto your system. The default location being C:/Program Files/aculab/installer
Package*.zip — If you are using an AIT application created zip file version, you can select to
extract the files to a specified directory, Aculab recommend that you use C:/Program
Files/aculab/installer
Package*.exe — If you are using an AIT application created self-extracting version, the files will
extract to the *.exe file location. Aculab recommend that this is C:/Program
Files/aculab/installer
An example of the use of the AIT is detailed in section 3.3 of this document
Note AIT telephony-software packages contain some utilities and applications that are included either for use by the Aculab tools or for
Aculab diagnostic and test purposes. for example, cl_config, mam_tool. Documented for them is not supplied because it is
intended that they be used only as instructed by Aculab Support.
Detecting the Aculab Aculab E1/T1 trunk and Prosody PCI and cPCI hardware
Upon completion of the download and installation of the required telephony software, the AIT
application should automatically install the Aculab device drivers for any detected Aculab
hardware. If it does not, you can either restart the system, which will check for new hardware as
part of the start-up process, or you can use the Windows Device Manager to detect new
hardware.
2.4 Configuring the Aculab Telephony Software

Details on the configuration of firmware required to utilise the Aculab card resources is detailed
in the Aculab configuration tool (ACT) user guide.
Sections 3 and 4 of this document provide examples of a typical Aculab card installation and
configuration.
2.5 Aculab example code

The AIT includes a package called ‘example code’. This package contains generic examples of
applications developed for test purposes only. These examples may be of assistance when
getting started with the Aculab APIs. For further information, please see the Aculab SDK
documentation that accompanies the example code files.
9
3 Example card installation and configuration for a windows environment.

For this example, we will demonstrate the installation of a Prosody X PCI card into a chassis
containing a Windows 2000/XP operating system. Similar processes will apply to Linux or
Solaris X-windows environments.
3.1 Installing the Prosody X card hardware.

CAUTION Do not proceed to install or connect the Prosody X PCI card to the 2.048/1.554 Mbit/s digital service or Primary Rate ISDN network
termination port until you have read in full and understood the appropriate Aculab card installation guide, in particular the sections
marked 'Installation and Safety'.
Proper electrostatic discharge (ESD) procedures should be maintained throughout.
1. MAKE A NOTE OF THE CARD SERIAL NUMBER
2. Remove the power from the host system and disconnect any mains leads
3. Remove the host computer covers.
4. Locate a vacant full-length PCI slot and, if required, remove the blanking plate.
5. Fit the card to the PCI slot and screw the bracket to the chassis.
6. Ensure that adjacent devices/cards do not foul the Prosody X card or PMX/PMXC module.
7. If required, fit H.100/110 CTBus ribbon cables.
8. Replace the covers on the host computer.
9. Attach the mains leads ready to apply power.
CAUTION In order to retain a good earth connection to the card, it is important that you ensure that the card retaining screw, as detailed in step
5 above, is securely fitted.
3.2 Starting the Prosody X card host system.

10. Turn on the host system, once Windows has started it will automatically detect the new
hardware:
and present a Found New Hardware Wizard dialog:
11. As the Aculab cards driver is Aculab specific, it will not be available until you have
downloaded the Aculab telephony software, therefore select Cancel.
For further guidance, please refer to the boot & discovery section of the Prosody X
administration guide.
10
3.3 Download and install of the Aculab telephony-software.

Before you proceed with the download of the Aculab telephony software, you will first need to
install the Aculab installer tool (AIT) - FTP download application. This can be obtained from the
Aculab web site at http://www.aculab.com/support/ait_telephony_software.asp. For our example, select the
Windows ( XP/2000; Server 2003) option.
You will be presented with the options to; download the Aculab installation tool - FTP downloads utility
guide.pdf,read the release note, and download the AculabInstaller.msi application. Along with
Instructions regarding the AIT application’s password requirements.
12. As required, using standard Windows process, download and run the AculabInstaller.msi
application.
Providing you accept the defaults, the Aculab installer tool (AIT) application will have been
installed in C:/Program Files/Aculab/Installer, and an Aculab – AIT entry will have
been added to your Windows Start - programs shortcut menu.
13. Either from the Windows Start menu, or by double clicking on the file, run the
installer.exe
If the AIT can not see the Internet, for example, access is via a secure proxy server, you will
presented with the following message:
Please refer to the AIT user guide Connection options – server settings section for details of how to
set up any required proxy settings.
Providing the AIT can connect to the Internet, you will be presented with a Login dialog:
14. Enter valid Username and Password details then select OK to continue.
The login details will be either the unique customer details provided to you by Aculab
support, or the generic login details obtained from the Aculab web site.
Once you have logged in successfully, you will be presented with the New Package dialog.
15. Select the required distribution from the pull down menu, in our example we have chosen
the Windows distribution.
16. Enter a unique distribution package local name, for example, we have used Test
installation, then select Ok to continue.
11
You will now be presented with the AIT primary dialog displaying your selected distribution
package. Select the distribution tree + symbol to see the distribution package key
components.
Note Components such as Switch, Resource_Management, Call_Control, and V6_Base are common
requirements (interdependencies) and will be downloaded and installed automatically when you install one of the key components
such as TiNG.
In our example, we will not be using the SS7, 3rd_Party, and Prosody S Software
components. These can be removed from the distribution.
17. Right click on any non-required components in turn and select Remove from ‘Test installation’
package.
18. Right click on the New or Updated Components on… entry and then select Install, this will start the
download and installation process for the remaining distribution components.
12
During the process, should you receive a licence agreement dialog prompt:
19. Select I Agree to continue.

You can monitor the progress of the installation by viewing the AIT primary dialog log.
During the process, after all the hardware drivers have been installed, the AIT will check for
any new hardware, detect, and then install the drivers for the new Prosody X PCI card. An
entry will then be added to the Windows Network and Dial-up Connections dialog (default - DHCP).
13
Once the AIT has successfully downloaded and installed the selected distribution
components, you will be prompted to re-boot the host system.
20. Select OK to continue.
The primary AIT dialog will now show the Installed components.
21. Select the File – Exit menu option to close the AIT.
22. Re-boot (Restart) the host system.
14
3.4 Adding the card to the Aculab card list (Prosody X only).
As previously mentioned, the Prosody X card is recognised by the host system as a network
interface card (NIC) and not an Aculab resource card. Before you can configure the Prosody X
card resources, you must first make it known to the Aculab card list, which is referenced by the
Aculab configuration tool (ACT). The ACT has an option to add Prosody X cards to the card list
using the cards IP address and card serial number.
For further guidance, please refer to the boot & discovery section of the Prosody X card
Administration guide for the booting and discovery of cards.
3.4.1 Setting up the Ethernet TCP/IP card address
For guidance on choosing an IP address, plus clarification on other issues such as network
connectivity, network bandwidth, and fragmentation, please refer to the network setup
considerations section of the Prosody X card Administration guide.
For this example, we will assume that we are not using DHCP, and that a range of IP addresses
(192.168.1.40 to 49) within a network have been reserved for use by IP gateways, such as our
Prosody X card. We will use the first of these addresses, (192.168.1.40) for the NIC and the next
address (192.168.1.41) for the Prosody X card resources.
23. To set the static IP address, use the standard Windows Network and Dial-up Connection properties
dialogs:
3.4.2 Updating the Aculab card list

For this example, we will update the card list using the Aculab configuration tool (ACT). For
command line options, please refer to section 4.3.2. For further information on using the ACT,
please refer to the Aculab configuration tool (ACT) user guide.
24. To open the ACT, select Start – programs – Aculab – V6 – ACT, or run the C:/Program
Files/Aculab/V6/ACT.exe application, then select the Card List view.
The card list view will not show the Prosody X card until it has been added to the Aculab
card list using the Prosody X view functions.
15
25. To add the Prosody X card to the Card List, first select the Prosody X view.
Note Under certain conditions, the Prosody X cards may appear in the list but will not show an IP Address or active Status. In these
instances you should select the card entry followed by Edit. Otherwise:
26. Select Add
If the card is to be configured from another system, you only need to add the Serial Number and IP
Address. If the card is to be booted and configured by the local host, you must select Boot Card to
enable entry of the required parameter.
16
27. Select Boot Card then enter the appropriate Serial Number, IP Address and Netmask parameters.
28. Enter a unique Security Key, or select Generate Key, to create a key for the card. This key is used
to restrict access to the card from approved hosts. For further details, please see the ACT and
Prosody X card administration guides.
29. Select Add followed by OK for the Register Remote Card dialog prompt. The card will go through
various Diagnostics and Status changes prior to being added to the Prosody X page list.
30. Selecting the Card List view dialog should now shoe the Prosody X card.
Note It can take some time for the card to appear in the card list. If the card fails to appear, try closing down and restarting the ACT
Note The DSPs on a PMXC are used for CAS and SS7 only and are automatically configured when CAS or SS7 protocols are selected for a
port. Unlike earlier PMs, these DSPs will not appear as available resources in the Card List, (DSPs column shows 0).
17
3.5 Configuring the Aculab telephony-software.

We will now configure:
Card Details - Set up the E1/T1 port protocols
Clock Settings - Set the clock master
IP Settings - Set up for SIP & H.323
TiNG Settings - Set up various speech processing features
3.5.1 Special consideration - using CAS and SS7 ISUP protocols on PMXC modules
A PMXC module may contain either one or two Signalling DSPs (DSP0 and DSP1)
• A single DSP can support up to 8 tone based CAS ports
• Running one or more SS7 signalling channel on a PMXC requires DSP0
• Running both SS7 signalling channels and tone based CAS on a PMXC requires DSP0 and
DSP1, DSP0 for SS7 and DSP1 for a maximum of 8 ports of tone based CAS
3.5.2 Card Details
For our example, we are going to set half of the ports for R2 (CAS), and the other half of the ports
for ETS 300.
31. In the Card List View, select the Prosody X card entry followed by Card Details, or double
click on the Prosody X card entry, to open the card Details Page dialog.
32. In the Port Protocols field, select the first port entry followed by Port Details, or double
click on the first port entry, to open the Port * Protocol Selections dialog.
18
33. In the Protocol Selection List, select R2T1 PMX. Then select Protocol Options to open the
R2T1 PMX Switch Options dialog.
The Available Switches pull down menu details the available options for the selected protocol.
The Switch Description field displays details for a selected switch. To browse the options, select
options as you scroll up or down the list.
34. Select a required option from the Available Switches field followed by Add Switch.
35. Repeat for all required options
36. For configurable switches, select the required Selected Switches entry then use the Switch
Configuration tab to set the required value.
37. Once you have completed the setting up of your required switch options, Select Ok to close
the Switch Options dialog and return to the Protocol Selection dialog. Then select OK to implement
your Protocol Selections and return to the Card Details Page dialog.
38. You will be presented with an option to set ‘All ports on the card set the same as this one’, Ignore this
option and select ‘Just set the current port to this protocol’ followed by Continue.
19
39. Repeat steps 31 to 37 for each port. In the following example, we have set the first four ports
for R2T1 and the second four ports for ETS300, both network and user end types.
40. Select OK to close the Card Details Page dialog and return to the Card List primary dialog.
20
3.5.3 Clocking settings

As this example is for a single card, and will not be using the H.100 bus (CTBus), we only need
to set the Clock master source; this will be set to be derived from Port 0. Details of setting up
clocking for more that one card, including bus termination, is detailed in the
Aculab_configuration_tool.pdf, which is available from the support area of the company web
site at www.aculab.com.
41. Select the Clocking Settings view, and then double click on the Prosody X card entry, or
select the Prosody X card entry followed by Clocking Details, to open the Clocking Details dialog.
42. From the Clock Source pull down menu, set the source to Port 0.
43. Now select Bus Master followed by Ok to complete the clocking settings and return to the
Clocking Settings primary dialog.
21
3.5.4 IP Settings
This option allows you to set specific SIP and H.323 port parameters as well as generic card
details. For further details on setting these parameters, please refer to the
Aculab_configuration_tool (ACT) user guide, available from the support area of the company
web site at www.aculab.com. For our example, we will accept the default values.
Other than when using enhanced SIP, using SIP or H.323 on a Prosody X card requires the use
of the TiNG resource manager (TRM). Please see the TiNG resource API guide for further details.
44. Select the IP Settings view.
45. Select the Prosody X card entry, then check the Enable H.323 and Enable SIP options. The Use
Aculab supplied ONCRPC portmapper should have been selected by default.
22
3.5.5 TiNG Settings

The TiNG firmwares to be loaded onto the Prosody Modules will depend on what functionality
you plan to support. For our example, we will assume that we are going to be providing some
form of IVR and voicemail solution to users accessing the system from any of the R2, ETS, or IP
ports.
Prosody X normally requires the Datafeed module. Additional modules may include inchan,
outchan, some form of play and record for playing prompts and recording messages, vmprx
and vmptx for the transmitting and receiving of voice media over IP, etc.
There is additional documentation available, such as the TiNG Resource Manager and Channel
Capacity Calculator, which may be of assistance in deciding on which modules may be
required. For further details, please see Ting (Prosody speech API guides) documentation.
Information on using the use TRM file option is detailed in the ACT user guide.
For our example, we will ignore the TRM option and select the firmware modules individually.
46. Select the TiNG Settings view.
47. Select the Prosody X card entry, then select Card Details to open the TiNG Firmware Selection
dialog. By default, Module 0 will be selected.
48. Scroll down the Available Firmware list, selecting and adding the required firmwares, for
example, select datafeed followed by Add Firmware to add datafeed to the Added Firmwares
list.
23
49. Once you have made all the required selections, select Add to All Modules. You will then be
asked to confirm your selection.
50. Select Yes to close the prompt, then select OK to close the TiNG Firmware Selection dialog and
return to the primary TiNG Settings dialog.
3.5.6 Applying the configuration

51. Once you have completed all your required configurations, select Apply Settings to implement
the configuration. You will then receive a confirmation dialog.
52. Select Yes to continue

The Firmware Download dialog will display the progress status.
Once completed, you will receive a confirmation dialog.
53. Select OK. You will now be presented with a Close option
24
54. Select Close to close the dialog and exit the ACT.
Note You should now be ready to use the Application Programming Interface (API) functions to interface between your application and the
Prosody X card resources. If you are unfamiliar with the Aculab APIs, the AIT packages contain some code examples that may be of
assistance.
25
4 Example installation and configuration for a non-windows environment.

The following sections describe how to install Aculab software on a system using only command
line tools. Although this example is mainly of interest to users running Linux or Solaris without
the X-Windows system installed, most of the tools are generic, and may be used on Windows
command prompts. As indicated, some tools are specific to Linux and/or Solaris.
Note It is assumed that the Aculab card has already been installed.
Three basic areas are covered:
1. Installing the Aculab software on a machine
2. Loading the drivers
3. Configuring the cards in the system.
4.1 Telephony-software download and installation

The text mode install command (instcmd) may be used instead of using the Aculab install tool
(AIT) graphical user interface (GUI), using the format:
instcmd [arg] [package name]
Where arg can be:

-install installs the components described by [package name]
-uninstall uninstalls the components described by [package name]
-download downloads the components described by [package name]
-list lists new/updated components described by [package name]
-delete deletes the cached components described by [package name]
-new creates a new package
-setup *sets up network settings
-packages *shows all packages that have been created by the -new argument
* These do not need the [package name] argument:
Most of these have very little interaction/output. The only ones that need much instruction are: -
-setup
–new
-setup:
This will ask you for the username and password, which are as used by the AIT GUI. Unlike the
AIT, instcmd does not use proxy server settings. Apart from these settings, it behaves the same
as the Connection->Login and Connection->Server Settings options in the AIT GUI.
-new
You will be asked which distribution you want to base your package on. This will first behave
like the File->New package GUI AIT option. You will then be asked which components you are
interested in. Select Y or N for each as appropriate.
Example use:
Downloading/installing a package
4. Run instcmd –setup
5. Enter username and password
6. Run instcmd –new my_package
You will be presented with a list of distributions (EG, V6 Windows, V6 Linux, etc).
7. Select the distribution you are interested in.
8. You will now be presented with the list of components, one at a time, and asked if you want
to add it to your package. Select as appropriate.
9. Run instcmd –download [package name](to download the packages you require)
10. Run instcmd –install [package name] (to install the packages you have downloaded)
Note As with the AIT GUI, you don’t need to run instcmd –download followed by instcmd –install, you can just run
instcmd –install.
26
11. Wait for installation to complete.
Checking for updates:

12. instcmd –list, see if there are any updated components. If there are any updated
components you are interested in, then:
13. instcmd –download/instcmd –install, to download/install the recent additions as
required.
4.2 Linux/Solaris drivers

4.2.1 Pre-requisites
Before using Aculab tools on Linux, there are a few pre-requisites that must be installed.
If Prosody X or 16 port trunk cards are being used, IP and ethtool must be installed. These are
usually supplied with the distribution, but ethtool is not always installed by default.
Under Linux, the Kernel sources need to be installed and configured. Your Linux distribution
documentation will explain how to do this.
If a Prosody X card is being used on a 2.6 based Linux kernel, then ebtables must be installed.
Source and pre-built packages can be found at http://ebtables.sourceforge.net. The binaries must be
placed into /sbin. Binaries installed from the .rpm package will be installed into
/usr/local/sbin, these must be copied into /sbin before use.
Note See $ACULAB_ROOT/driver/readme.install for distribution-specific information before building the Aculab drivers on Linux.
Note Many of the scripts listed in this section appear in $ACULAB_ROOT/driver/install on Solaris instead of $ACULAB_ROOT/driver
Note Aculab currently supply only 64 bit Solaris kernel drivers with 32 and 64 bit userspace libraries
Note Linux installation scripts are kept in $ACULAB_ROOT/driver, Solaris scripts are kept in $ACULAB_ROOT/driver/install
4.2.2 Making Libraries and Supporting Utilities
Newer TiNG distributions are supplied with a pre-built shared object as well as the source code.
This section is applicable only if you would like to link your applications against a static TiNG
library.
If a static TiNG library is needed, then the $ACULAB_ROOT/driver/makelibs script file must be run
before building the driver. This creates the appropriate supporting utilities to build and run the
Prosody 2 (TiNG) driver component. makelibs libonly may be run to build only libTiNG.a and
not the assorted test tools that are not needed for every-day operation. This will greatly reduce
the time taken to build TiNG.
4.2.3 Building, and Configuring, the Driver
If Prosody X or 16-port trunk cards are being used in the system, then the distribution’s kernel
source package must be installed. Consult the distribution’s documentation for information on
this.
ACULAB_ROOT must be set to the root directory of the Aculab distribution (e.g.,
/usr/local/aculab/v6). setV6.sh is a script that will set the all of the environment variables
correctly. To run:
source setV6.sh
This file may also be modified and copied into /etc/profile.d to ensure settings are loaded
for each bash shell.
Before the driver can be loaded, it has to be fully built. Due to the many variations of Linux and
Solaris distributions, there cannot be a "one binary for all" situation. To cope with this, the driver
kit contains precompiled objects with the final compilation of the kernel-specific code and the
linking together of the loadable module, completed on the host machine. The script files
dacpinst for Linux and solinst.pl for solaris, are used to automate this process and
configure the driver to your needs.
To avoid compilation errors, Please ensure that the sources for the intended kernel have been
installed, prior to building the driver. For most distributions, this required package would be
called kernel-source.
27
The commands for dacpinst are as follows:

./dacpinst build - builds, then configures, the driver.
./dacpinst config - configures an existing driver.
./dacpinst clean - removes the objects, allowing a clean rebuild.
./dacpinst version - gives the version of dacpinst.
At each prompt, dacpinst will often give options (i.e., "yes/no") in brackets "(....)", and the
default actions in square brackets "[....]". The default actions will predict the desired input
according to a typical build. If you'd like the default input, hit return, or else type in what you'd
like, instead.
The commands for solinst.pl are as for dacpinst. Simply replace any instance, in the above
example, of dacpinst with solinst.pl.
4.2.4 Creating the Driver
Running "./dacpinst build" or "./solinst.pl build", asks you what components you
would like to include. Select the Call, Switch, and Speech components as necessary. If an
invalid combination is selected, you will be asked to enter an alternative combination.
Please follow the on-screen instructions.
4.2.5 Creating the Prosody X NIC Driver on Linux
Prosody X cards running under Linux use a slightly modified E1000 driver from the distribution’s
standard kernel source. This driver will be built if Prosody X card support is requested. If the
E1000 driver is already running on the system, dacpinst will instruct the user to reboot before
using Prosody X cards.
4.2.6 Installing the Prosody X NIC Driver on Solaris
A pre-built NIC driver for Prosody X cards is available from the AIT. Run nicinst in
$ACULAB_ROOT/driver/install to install the NIC driver. Running nicinst –check will report
whether the NIC driver needs installing or updating.
Once the NIC driver has been installed, an IP address should be assigned to each Prosody X
card. This can be achieved by creating an appropriate /etc/hostname.acupx file for each
Prosody X card. These interfaced should be brought up before running aculab_v6 start.
4.2.7 Configuring the Driver
If you have successfully completed the previous part there should be a loadable module created
that represents the driver for your system.
If you are configuring the driver through "./dacpinst config" or "./solinst.pl config",
you will be asked how many Aculab cards there are in total. If you are continuing from
"./dacpinst build" or "./solinst.pl build", then some of these questions have already be
answered and you won't be asked to enter the details at these prompts again.
You will be asked which switch mode you want to be in: H100, SCBus or MVIP. The switch
driver will be in this mode and cannot change while the driver is running.
You will also be asked for a non-privileged user to run the Aculab tools. The Aculab Resource
Manager (acuresmgr) will be run as root, but will spawn any tools as this user minimizing the
amount of root access required for the Aculab tools.
4.2.8 Loading and Unloading the Driver
After successfully configuring the driver, you will be given a new script file called aculab_dacp
for Linux or aculab_v6 for solaris. This script file is compatible with those in /etc/init.d and
/etc/rc*.d or /etc/rc.d/rc?.d (as used in most distributions of Linux or Solaris) and can be
used to automatically load the driver at boot-up.
The commands for Linux aculab_dacp are as follows:
./aculab_dacp start - loads, then starts, the driver.
./aculab_dacp stop - stops, then unloads, the driver.
./aculab_dacp restart - restarts the driver.
28
aculab_dacp also creates the device nodes (in /dev) required for correct operation.
The command for Solaris aculab_v6 are as for aculab_dacp. Simply replace any instance, in
the above example, of aculab_dacp with aculab_v6.
4.2.9 Automatic Loading of the Driver
The aculab_dacp and aculab_v6 script files can be used to automatically load the driver at the
boot-up sequence of Linux. For example, if you are defaulting to using Linux runlevel 5 (usually
boots up to X-Windows in Redhat), then you can symbolically link aculab_dacp into
/etc/rc.d/rc5.d using similar superuser commands to:
cd /etc/rc.d/rc5.d
ln -s /usr/local/aculab/v6/install/aculab_dacp ./S91aculab_dacp
Note For Solaris, replace aculab_dacp with aculab_v6

Note The location and style of your boot-up scripts may differ on your system.
4.2.10 Removing the Driver
To unload the driver, ensure that no other process is using it, and then enter:
./aculap_dacp stop for Linux, or ./aculap_v6 stop for Solaris
4.2.11 Setting up Prosody X Card IP Address on Linux

Like any other NIC card in the system, Prosody X cards need to have their host NIC interface
assigned an IP address. Consult the distribution’s documentation for information on how to do
this.
Further details can be found in the card boot & discovery section of the Prosody X administration
guide.
Note Further O/S specific information can be found in $ACULAB_ROOT/driver/readme.install

Note Ensure $ACULAB_ROOT/log is writable by any users (including root) that are likely to generate trace before using trace_mode
to generate trace.
4.2.12 Setting up Prosody X Card IP Address on Solaris
Like any other NIC card in the system, Prosody X cards need to have their host NIC interface
assigned an IP address. These addresses are set up in the same way as other NIC interfaces in
the system by modifying /etc/hostname.acunic?.
Further details can be found in the card boot & discovery section of the Prosody X administration
guide.
29
4.3 Managing Prosody X cards

Both Windows and Linux recognise the Prosody X card as a network adapter (NIC) and not an
Aculab Computer Telephony device. It will not appear automatically in the ACT card list and
must be manually added to the list. This can be achieved either through the ACT using the
Prosody X cards… option, or by using the command line tool prosody_ip_card_mgr (section 4.3.2).
4.3.1 Distinguishing Prosody X cards on Linux

When you add multiple Prosody X cards to a Linux system, they will have been assigned names,
for example eth2, eth3, and eth4. This does not tell you which is which, which is essential if
you want to plug an external network connection into any of them. A utility is supplied to help
you tell which is which. It is a Perl script, findprosodyx.pl, which is located in the v6/bin
directory.
This script is entirely self-contained, does not require any other configuration files or programs
from Aculab, nor does it require any components to be built. The only prerequisites are that you
must have perl(1), ifconfig(8), and tcpdump(8) installed on your system.
4.3.1.1 How it works
The Linux version of ifconfig(8) tells you the Ethernet (MAC) address built into each network
interface card. When a Prosody X card has not yet been configured, it periodically sends a
broadcast to initiate configuration. These broadcasts contain its serial number, so that anything
receiving it can tell which configuration (if any) to use. They also contain the Ethernet (MAC)
address, which is used by the network interface portion of the card. By listening for them, we
can discover the mapping between serial number and Ethernet (MAC) address of a Prosody X
card, and by combining this with the information from ifconfig we can work out which name
Linux has assigned to which card.
4.3.1.2 Simple use
The simplest way to use this utility is to run it before aculab_dacp start has been run, giving
only the name of the interface chosen by Linux. For example:
perl findprosodyx.pl eth2
After a while (about six minutes - see the next section, speeding up the process), if this interface
is a Prosody X card, the serial number of the card will be printed out (on stdout), for example:
123456 is the serial number of Prosody X card eth2
In normal use you will see more output, because there is some sent to standard error by the
utility tcpdump, which the script uses to listen for Ethernet traffic, for example:
tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size 1500
bytes
101 packets captured
101 packets received by filter
0 packets dropped by kernel
If there is a network cable connected to the card, and there are other Prosody X cards on the
same segment, the script may receive broadcasts from them, for example:
# Saw other card: 654321 (00:02:1f:00:0a:9d) while looking for
00:02:1f:00:05:aa
Note If eth2 is not a Prosody X card, or if the Prosody X card is not waiting to be configured, the script will wait forever.
4.3.1.3 Speeding up the process
The simplest way to use this script results in a long delay while it listens for Ethernet traffic. This
is caused by the way in which tcpdump passes on the traffic. It buffers it into blocks, and the
script gets nothing until a whole block is available. Since the periodic broadcasts are only sent
about every four seconds and are quite short, this causes a long delay.
There are two ways of speeding this up, which are mutually incompatible.
30
Speeding it up by adding traffic

If you cause more traffic to be seen by tcpdump, then it will pass on the traffic faster and the
script will see the Prosody X broadcasts faster. One way of doing this is to connect a network
cable to the Prosody X card and let in whatever traffic happens to be present. Most networks
have enough broadcasts to make this a considerable improvement.
Another way to add traffic is to use a tool such as ping to send packets to the IP address
associated with the interface you are interested in. Such packets are captured by tcpdump, so it
passes on a buffer full more frequently. This is probably the best method to use if you want to
use this script in some automated manner (for example, to verify at boot time that the Prosody X
cards are still in the same order).
Speeding it up by counting packets
You can tell the script to only let tcpdump capture a specific number. This makes tcpdump flush
its buffer as soon as the limit is reached. The limit is specified with the -p option, like this:
perl findprosodyx.pl -p 10 eth2
However, if there is other traffic, tcmpdump may stop before the broadcast from the Prosody X
card has been seen. This makes it fail, for example, like this:
perl findprosodyx.pl -p 10 eth2
tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size
1500 bytes
10 packets captured
10 packets received by filter
0 packets dropped by kernel
Error: EOF from tcpdump
If there is a lot of traffic on the Ethernet, then you can tell the script to make tcpdump ignore
anything which could not be the broadcast from a Prosody X card. This is done using the -x
option, for example:
perl findprosodyx.pl -p 10 -x eth2
The disadvantage of this option is that tcpdump does not pass on packet capture data as often,
since there is less of it. In particular, it means that the trick of using ping to add traffic, as
described above, no longer works.
4.3.2 Adding a Remote Prosody X card
If the Prosody X card is installed in a machine other than the machine on which the Aculab
software is running, or is installed in the same machine but the host NIC has not been assigned
an IP address, as in sections 4.2.9 or 3.4, then the card is a remote card. To add a card use one
of the following commands:
prosody_ip_card_mgr add <serial_no> <card_key> <ip_address_of_card> <netmask>
<gateway_address>
to provide an explicit configuration or:

prosody_ip_card_mgr add <serial_no> <card_key> dhcp
to configure using DHCP.

The card_key is a password which ensures security of the system and which must be specified.
More than one system may use resources on a Prosody X card, but they must all use the same
card_key to talk to the card.
For example, If you want to give your Prosody X card (serial number 179779, card key theKey),
an IP address of 192.168.1.42 and there's no gateway, you would use:
prosody_ip_card_mgr add 179119 theKey 192.168.1.42 255.255.255.0
31
4.3.3 Adding a Local Prosody X Card

If the Prosody X card is installed in the machine on which the Aculab software is running, and
the host NIC interface has been assigned an IP address as in sections 4.2.9 or 3.4, then the card
is a local card. Use the same commands as in section 4.3.1 but with “prosody_ip_card_mgr
configure persistent” instead of “prosody_ip_card_mgr add”. For example:
prosody_ip_card_mgr configure persistent 179119 theKey dhcp
Note The IP address supplied to the prosody_ip_card_mgr tool must be different to the IP address assigned to the host NIC.
Note Should you receive an error message ERR_CARD_NOT_FOUND, check that your Prosody X card is running the latest flash revision. See the
‘Flash upgrade process’ section of the ‘Prosody X administration guide’ for further details.
Note To see if your card has been detected, run ‘swcmd –e’. It may take a few seconds to show up so you may need to try a few of times.
4.3.4 Listing installed Prosody X cards
To list all Prosody X cards currently installed in the system use the following command:
prosody_ip_card_mgr list
This will return the serial number and IP address of any cards, (this example is for a single card):
1 Prosody IP cards registered on this system:
179779 (192.168.1.42)
4.3.5 Obtaining information for an installed Prosody X card

To obtain card details for a specific card, use the following command:
prosody_ip_card_mgr info <serial_no>
For example, to obtain information for card serial number 179779, use the following:
prosody_ip_card_mgr info 179779
This will return the following information:

Device 0:
Model: AC5200 Prosody X
Serial number: 179779
Version: 1.2
Bootloader: Prosody-X-U-Boot 0.4.0-Oct 18 2005
Firmware: Aculab Prosody IP Firmware 0.0.20
3.3V: 3.266V
5V: 4.766V
Temperature 0: 19C
Temperature 1: 45C
Device 1:
Model: AC5400 PMX
Serial number: 180227
Version: 1.1
Bootloader: Prosody-X-U-Boot 0.4.0-Oct 18 2005
Firmware: Aculab Prosody IP Firmware 0.0.20
3.3V: 3.266V
5V: 4.766V
Temperature 0: 71C
Temperature 1: 57C
4.3.6 Removing a Prosody X card

To remove a card use the following command:
prosody_ip_card_mgr remove <serial_no>
32
4.4 Card configuration files

The default configuration of Aculab cards is determined using a series of configuration files.
The Aculab Resource Manager looks for *.cfg files in the ACULAB_ROOT/Cfg directory, where
ACULAB_ROOT is the directory in which the Aculab package is installed. These files must be
generated either automatically by the Aculab Configuration Tool (ACT), via the command line
using CFGTemplates.exe (on Windows) or cfgtemplates (on Linux/Solaris), or manually
using an ASCII text editor.
Note The default location of “ACULAB_ROOT” for Windows is “C:/Program Files/Aculab/V6/”
All *.cfg files are in the form <serial_no>.cfg. For example, a card with the serial number
12345 would have a corresponding cfg file of 12345.cfg.
4.4.1 Creating configuration files

CFGTemplates.exe is a command line application that will create a cfg template file for a
given Aculab card. It is found in the bin directory of in the ACULAB_ROOT folder. To run this
application the user must pass a serial number into the application, for example,
cfgtemplates 131865
The above example will create a file with the file name 131865.cfg
This will not be a fully configured file; certain fields have been left blank for the user to edit
using a standard ASCII text editor. For example, the call section will have no firmware selected
for either the call ports or the DSP 32/65s. Also the Speech section will not have any TiNG
firmware specified.
Example of running the application
The following is an example run on a Windows system. There are no differences in executing
the tool on Windows, Linux or Solaris.
Run cfgtemplates 131865
If the card is already in the system, you will be asked if you wish to automatically detect the card
type.
You will then be asked to specify the bus mode; MVIP, SCBus or H100 (for cPCI select H100).
Next you will be asked if the card is a "Bus Master" i.e. is this card to supply the clock source.
If yes, then the clock source will be requested. If No, the card will take the CTBus Mode as the
clock source.
Now you will be asked to confirm if the card is to be bus terminated (at either end of the CTBus).
If the card is not in the system, you will be asked to specify the card type. This will be followed
by a series of questions relating to the number of ports, SHARCs and so on as appropriate.
Note If you are configuring an IP Telephony card, you will also be asked if you wish to use the IP Telephony services. If you select yes, an
additional configuration file called voip_rm.cfg, containing your selections, will be created. This file must also be copied into
ACULAB_ROOT/cfg
Once all the questions have been answered, the file will be written to the directory that the
application was executed in. You can now manually add any firmwares to the file as required
and copy the file into ACULAB_ROOT/cfg.
33
Example of prompts if the card is NOT in the system:

C:/>cfgtemplates 131865
Aculab's V6 configuration template file generator
-------------------------------------------------
The file 131865.cfg will be created for you now
Which bus mode do you wish to use (M)vip, (S)cbus or (H)100 [m/s/h] : h
Is this card a "Bus Master" [y/n] : n
Is this card to terminate the bus [y/n] : n
What Type of Card are you create this CFG file for (P)rosody, E1/T1 (T)runk or (V)oip
[p/t/v] : t
How many call control ports does the card have [0/1/2/4/8]: 0
File Created successful - please configure the blank fields and copy the file to the
cfg folder in the V6 installation directory
Example of prompts if the card is in the system:

C:/>cfgtemplates 131865
Aculab's V6 configuration template file generator
-------------------------------------------------
The file 131865.cfg will be created for you now
Do you wish automatically detected the cards attributes [y/n] : y
Which bus mode do you wish to use (M)vip, (S)cbus or (H)100 [m/s/h] : h
Is this card a "Bus Master" [y/n]: n
Is this card to terminate the bus [y/n]: n
File Created successful - please configure the blank fields and copy the file to the
cfg folder in the V6 installation directory
Example of resulting configuration file:

[General]
CardName=<name>
[EndGeneral]
[Switch]
CtBusTermination=FALSE
CtBus=SWMODE_CTBUS_H100
H100Mode=H100_SLAVE
Network=0
Source=H100_SOURCE_H100_A
AutoFallBack=H100_FALLBACK_DISABLED
NetRefClockSpeed=H100_NETREF_8KHZ
[EndSwitch]
34
4.4.2 Per-card configuration file description

File layout
The .cfg files are split into a number of blocks corresponding to the switch, call, and speech
components a card may have. [<component_name>] and [End<component_name>] delimit
each of the components. The components are:
[General]
……
[EndGeneral]
[Call]
……
[EndCall]
[Switch]
……
[EndSwitch]
[Speech]
……
[EndSpeech]
[VoIP]
……
[EndVoIP]
Note Only the general, call and switch options are common to all cards, speech and VoIP are optional.
The general component fields
This component contains a single field, CardName. The field value should contain the serial
number of the card.
[General]
CardName=Card<128483>
[EndGeneral]
The switch component fields

There are 7 fields in the switch component. These fields map directly to the fields in the
"h100_config_board_clock_parms" structure, and are populated with exactly the same values
(see the Switch API guide for further details).
Example switch component:
[Switch]
CtBusTermination=TRUE
CtBus=SWMode_CTBus_H100
Network=0
H100Mode=H100_SLAVE
[EndSwitch]
Each line in the section consists of a field name followed by equals and then the value assigned
to that field.
Note The fields in this section are case sensitive
H.100 configuration
CtBusTermination: This card should terminate the bus. Possible values:
TRUE - the card should terminate the H.100 bus
FALSE - the card should not terminate the H.100 bus
CtBus: This setting controls the bus that the card will use. For H.100use:
SWMODE_CTBUS_H100 - H.100 mode (the default)
Note Changing this setting requires a restart of the drivers for the card. This will only occur the first time this setting is applied to a card -
upon subsequent reboots the card will start in the correct mode."
35
Source - controls the source of the card's clock. This can be one of the following:
H100_SOURCE_INTERNAL - generate a clock on board and provide it to the CT bus
H100_SOURCE_NETWORK - use the port specified in the network field as the clock
H100_SOURCE_H100_A - take the clock from the H.100 clock master A
H100_SOURCE_H100_B - take the clock from the H.100 clock master B
Network - controls the network port that is used as a clock reference if Source is set to
H100_SOURCE_NETWORK. The network port index is the physical index of the port on the card.
Remember that for the Switch API, ports are numbered from 1.
H100Mode - controls whether the card is an H.100 primary or secondary master or a clock slave.
The possible values for this field are:
H100_SLAVE - card will be a slave on the H.100 bus (Source must be one of
H100_SOURCE_H100_A or H100_SOURCE_H100_B)
H100_MASTER_A - card will drive the A clock on the H.100 bus (Source must be one of
H100_SOURCE_INTERNAL or H100_SOURCE_NETWORK).
H100_MASTER_B - card will drive the B clock on the H.100 bus (Source must be one of
H100_SOURCE_INTERNAL or H100_SOURCE_NETWORK).
AutoFallBack - This field determines the card's behavior when an H.100 clock failure occurs.
This field can contain one of the following values:
H100_FALLBACK_DISABLED
H100_FALLBACK_ENABLED
H100_AUTO_RETURN
H100_CHANGEOVER_TO_NETWORK
See the description of the auto_fall_back field in the documentation for the
sw_h100_config_board_clock() function for an explanation of how these fields apply.
NetRefClockSpeed - This field is used to tell the card the speed of the CT_NETREF fallback
clock. See the description of the netref_clock_speed field in the documentation for the
sw_h100_config_board_clock() function for further details.
Legacy configuration (MVIP or SC-Bus)

It is possible to put the following Aculab cards into legacy modes that support SC-BUS or MVIP:
Aculab Prosody PCI
Aculab E1/T1 Trunk PCI
To connect to cards that have SC-BUS or MVIP connectors it is necessary to use an Aculab
Legacy Adapter.
The configuration settings for legacy bus modes are controlled by the following entries in the
config file for a card:
CtBus: This setting controls the bus that the card will use. The possible legacy values are:
SWMODE_CTBUS_MVIP - MVIP mode
SWMODE_CTBUS_SCBUS - SC-BUS mode
Mode: Used in legacy mode only, this setting controls the clocking behaviour of the card. It can
take one of the following values:
CLOCK_REF_NET1 - drive bus, take clock from network port 0
CLOCK_REF_MVIP - take clock from MVIP bus
CLOCK_REF_LOCAL - drive bus, generate clock locally
CLOCK_REF_SCBUS - take clock from SC-BUS
Note When using Linux or Solaris, the CT bus mode must match the CT bus mode selected when building/configuring the drivers.
Note Changing bus mode will trigger a restart of the driver for this card. This will only happen the first time the card is put into legacy
mode - upon subsequent reboots it will start in the correct mode.
36
CtLimitOverride: When in MVIP or SCBUS mode, Aculab PCI cards restrict their switching
capacity in order to better operate with substandard competitor’s cards. There is a method to
enable the card’s full capacity for when you know that the cards it is interfacing with can cope
with it.
The possible values for this entry can be:
TRUE
FALSE
Note Changing this setting requires a restart of the drivers for the card. This will only occur the first time this setting is applied to a card -
upon subsequent reboots the card will start in the correct mode.
Note This setting only applies to SCBUS and MVIP modes.
The call component fields
The following fields are requires in the call section for each port.
Port=
PortName=
Firmware=
Config=
DSPA=
DSPB=
PortInit=
The following definitions apply:
Port
Is the port number starting at 0, if you have four ports then they are numbered 0-3.
PortName
Is a user defined 16 character text string, for example:
Portname=London Port1.
Firmware
The location from ACULAB_ROOT of the call firmware file, for example:
Firmware=/firmware/ETS_SUPN.upr
Config
The firmware switch to applied at download time, for example:
-CNE (ETS300 network side).
For details of available/valid firmware switches, please read the associated
$ACULAB_ROOT/firmware/*_switches.txt file. For example, for ETS this would be the
ets_switches.txt file.
DSPA & DSPB

The firmware location from ACULAB_ROOT of the DSP firmware, for example:
DSPA=/dsp/swap16.bin
DSPB=/dsp/swap16.bin
PortInit
Can be either TRUE to perform PortInit, or FALSE to not perform PortInit. For example:
PortInit=TRUE
A typical configuration for a revision 2 PM4 would be as follows:
[Call]
Port=0
PortName=Port 0
Firmware=/Firmware/ETS_SUPN.upr
Config=-cNE
DSPA=/DSP/cpdtmf.bin
DSPB=
PortInit=TRUE
Port=1
PortName=Port 1
Firmware=/Firmware/ETS_SUPU.upr
37
Config=
DSPA=/DSP/ddtmf.bin
DSPB=
PortInit=TRUE
Port=2
PortName=Port 2
Firmware=/Firmware/ETS_SUPN.upr
Config=-cNE
DSPA=
DSPB=
PortInit=TRUE
Port=3
PortName=Port 3
Firmware=/Firmware/ETS_SUPU.upr
Config=
DSPA=
DSPB=
PortInit=TRUE
[EndCall]
The speech component fields

The speech component is split into "blocks" in a similar fashion to the call component, however
in this case the "blocks" are delimited by the "Module" field.
The "Firmwares" field takes the full path from the ACULAB_ROOT of the Prosody firmware to be
downloaded.
The Prosody2 (TiNG) firmware modules are assumed to be in the following directory:
ACULAB_ROOT/TiNG/Share/Gen
Where ACULAB_ROOT is the directory in which the Aculab drivers are installed.
Example speech component:
[Speech]
Module=0
Firmware=<first_firmware> <second_firmware>…
Module=1
Firmware=inchan.elf outchan.elf
[EndSpeech]
module — the module number, starting with module 0
Firmware — the firmware to be downloaded to that module.
For further information of the available firmwares, please see the TiNG browser documentation
at either:
$ACULAB_ROOT/TiNG/pubdocs/softmodindex.html
or
http://www.aculab.com/support/ting/softmodindex.html
Note In addition to any other firmwares chosen, Prosody X will require the datafeed.elf firmware.
IP telephony
Each IP Telephony card should contain a card specific voip section detailing the settings for that
card.
[VoIP]
IPAddress=192.168.20.14
SubnetMask=255.255.255.0
Gateway=0.0.0.0
EncodeGain=8192
DecodeGain=8192
RTP_TOS=0x0
RTCP_TOS=0x0
Def_Jitter=30
Max_Jitter=150
Max_Jitter_Buffer=250
TDMEncoding=TDM_ULAW
38
EchoCancel=EC_G165
EchoSpan=16
EchoSuppression=ES_OFF
DTMFDetect=0
[EndVoIP]
Note Prosody X cards do not use the IPAddress, SubnetMask or Gateway fields. These should be set to 0.0.0.0 to allow the config tool to
parse the files correctly.
Another .cfg file (voip_rm.cfg) is generated for the configuration of the shared IP Telephony
services, for example:
[H323Service]
USE=TRUE
H245_Tunneling=IPT_ENABLED
FastStart=IPT_ENABLED
EARLYMEDIA=IPT_ENABLED
[EndH323Service]
[SIPService]
USE=TRUE
AddressHold=IPT_ENABLED
EarlyMedia=IPT_ENABLED
[EndSIPService]
[PortmapService]
USE=TRUE
[EndPortmapService]
4.4.3 Example configuration files

E1/T1 configuration file example
The following example configuration file is for an E1/T1 PCI card with a 4 port E1 LIM and a
DSP fitted to position A.
[General]
CardName=Card<128483>
[EndGeneral]
[Switch]
CtBusTermination=FALSE
Network=0
H100Mode=H100_SLAVE
[EndSwitch]
[Call]
Port=0
PortName=Port 0
Firmware=/Firmware/ETS_SUPN.p4r
Config=-cNE
DSPA=swap16.bin
DSPB=
PortInit=TRUE
Port=1
PortName=Port 1
Firmware=/Firmware/ETS_SUPU.p4r
Config=
DSPA=swap.bin
DSPB=
PortInit=TRUE
Port=2
PortName=Port 2
Config=-cNE
DSPA=conbeep.bin
DSPB=
39
PortInit=TRUE
Port=3
PortName=Port 3
Config=
DSPA=conbeepu.bin
DSPB=
PortInit=TRUE
[EndCall]
[Speech]
[EndSpeech]
Note Although the E1/T1 card does not contain and speech (Prosody) modules, for consistency, the configuration file still shows a blank
speech component.
Prosody configuration file example
The following example configuration file is for a Prosody PCI card with a 4 port E1 LIM, two
prosody modules (0 and 1) and a DSP.
[General]
CardName=Card<193>
[EndGeneral]
[Switch]
CtBusTermination=TRUE
Source=H100_SOURCE_INTERNAL
Network=0
H100Mode=H100_SLAVE
[EndSwitch]
[Call]
Port=0
PortName=Port 0
Config=-cNE
DSPA=ddtmf.bin
DSPB=
PortInit=TRUE
Port=1
PortName=Port 1
Config=
DSPA=dconf2u.bin
DSPB=
PortInit=TRUE
Port=2
PortName=Port 2
Config=-cNE
DSPA=ddtmf.bin
DSPB=
PortInit=TRUE
Port=3
PortName=Port 3
Config=
DSPA=cngdet.bin
DSPB=
PortInit=TRUE
[EndCall]
[Speech]
Module=0
Firmwares=inchan.elf recmu.elf
Module=1
Firmwares=inchan.elf recmu.elf
40
[EndSpeech]
V5 compatibility file example

Assuming that the system contains the two previous examples, the V5 compatibility file for such
a system would be:
;V5 Setup file
;Configure card ordering, clocking, and protocol info
;-y <serial no> -sw(<clock switches>) -cl(*[<s type>])
-y 128483 -sw(-hA) -cl(S_ETSNET S_ETS300 S_ETSNET S_ETS300 )
-y 193 -sw(-hL) -cl(S_ETSNET S_ETS300 S_ETSNET S_ETS300 )
4.4.4 Configuration file updates

Should you need to update a configuration, for example, following changes to a .cfg file, you
can use the config command as follows:
Config <serial number> <switches>
Where:
<serial number> is the serial number of the card, for example, 248 for file 248.cfg
<switches> are the following:
-v verbose displays what it is doing while running, e.g Config 248 -v

-m module. To use this you have to specify a module number, this will only download
prosody firmware to that module, e.g. Config 248 -m 0
-p port. As for -m except for ports, e.g. Config 248 -p 0 -p 1
-s reloads the clocking setting for the card, e.g Config 248 -s
All of these switch can be use together, for example:
Config 248 -p 0 -p 1 -p 2 -p 3 -m 0 -m 1 -s –v
This example will download firmware to ports 0 — 3 & modules 0 —1, reset clocking, and run
verbose.
41
4.5 Signalling Software Installation

4.5.1 Firmware files and extensions
PCI and cPCI module Firmware
Cards fitted with Lucent/AT&T DSP32s use file names ending with suffix .bin
Cards fitted with ADSP21065 DSP65s use file names ending with suffix .b65
Cards fitted with pre revision 2 PMs use file names ending with .p4r
Cards fitted with revision 2 PMs use file names ending with suffix .upr
Cards fitted with PMX moduless use file names ending with suffix .pmx
Note If you are configuring a PMX module, and plan to use CAS or SS7 protocols, please ensure you are aware of section 3.5.1; Using CAS
and SS7 ISUP protocols on PMX modules.
4.5.2 Firmware and DSP download (FWDSPLDR)
fwdspldr is a firmware download utility for PCI and cPCI Aculab cards. It is used to download
the signalling protocol and DSP firmware, and to specify configuration switches simultaneously.
The fwdspldr utility uses standard Aculab API calls, the source of which can be made available
on request.
Note On most cards, the DSP firmware refers to the optional Lucent/AT&T DSP or SHARC ADSP 21065 modules. cPCI E1/T1 cards and DSP65
modules have ADSP 21065 DSPs fitted, and should not be confused with the Prosody ADSP 21065 DSP firmware.
Usage for fwdspldr is as follows:
fwdspldr [-dspa <filename>] <serial_no> <portnum> <filename> <config>
Where:
-dspa Is used to specify which Lucent/AT&T or SHARC ADSP 21065 DSP to
download firmware to. (not applicable to BR4/8 cards).
<serial_no> Is the serial number of the card to download firmware to.
<portnumber> Is the port on the card to download the firmware to.
<filename> Is the DSP or signalling protocol firmware file to download.
<config> Is used to specify any configuration switches to be passed to the signalling
protocol firmware.
Note The filename suffix is subject to the type or revision of the primary rate module (PM). A pre revision 2 PM has a file suffix of .P4R, a
revision 2 PM has a file suffix of .UPR, and a PMX has a file suffix of .PMX
Download Examples
The following example downloads firmware to the first port of a pre revision 2 PM4 module on a
PCI/cPCI Prosody card fitted with a Lucent/AT&T DSP32 module.
fwdspldr -dspa cpdtmf.bin 12345 0 qsig_sup.p4r -cQMA
The following example downloads firmware to the first port of a pre revision 2 PM4 module on
an E1/T1 cPCI card fitted with a ADSP 21065 DSP65 module.
fwdspldr -dspa cpdtmf.b65 145678 0 ets_supn.p4r -s99,255 -cne
The following example downloads firmware to the first two ports of a revision 2 PM4 module on
an E1/T1 PCI card fitted with a ADSP 21065 DSP65 module. The first line downloads a DTMF
tone generation firmware to DSP65 position A, the second line doesn't download any DSP
firmware.
fwdspldr -dspa cpdtmf.b65 12345 0 ets_supn.upr -s99,255 -cne
fwdspldr 12345 1 ets_supu.upr
For more information on the configuration switches available for a specific signalling firmware,
see the release note text files associated with that firmware.
42
Appendix A: Aculab PCI & Compact PCI cards

A.1 Device driver installation – common parameters
The fwdspldr utility or the call_restart_fmw API call is used to download firmware to the
PM modules used on Aculab PCI & Compact PCI cards. Users upgrading from ISA to PCI &
Compact PCI cards may need to change their applications to reflect this change.
A.2 E1/T1 PCI Primary Rate Trunk card

The E1/T1 PCI Primary Rate Trunk card can occupy any position in a ‘chain’ of CTBus devices. If
the E1/T1 PCI Primary Rate Trunk card is the first or last device, at either end of a ‘chain’ then
the card must be configured to terminate the bus, (see the ACT application section for further
details).
If the E1/T1 PCI Primary Rate Trunk card is in the middle of a ‘chain’ of CTBus devices, then the
termination function is not used. See the ‘E1/T1 PCI Primary Rate Trunk card Installation Guide’ for
the position of the CTBus termination indicator LED. This LED can be used to identify the
terminated cards in a system.
A.3 Serial Number location

Please refer to the appropriate card hardware installation manuals for locations of the serial
number labels.
43
Appendix B: Call Driver Installation Options

This section describes the options that can be used to configure call control on an Aculab card
or module. These options are applied by supplying a configuration switch when installing a
driver, or by supplying a switch when downloading firmware to the card using ‘restart’. More
details on how to install drivers on a particular operating system are detailed earlier in this
manual. For further details of protocol firmware switches, (-s switches) please refer to the
documentation (*.txt file) that accompanies each protocol firmware file.
Following is a description of each of the configuration switches and where they may be used.
B.1 Table of Signalling System Options

Here is a check box to indicate which configuration switches are supported by which signalling
systems:
CAS DASS DPNSS ETS300 FETEX QSIG AT&T N12 ISUP
-cAX X
-cAY X
-cBBY X
-cBX X
-cBY X
-cCA X
-cCIC X
-cCn X
-cDn X
-cDPC X
-cEN X
-cEX X
-cFD X X
-cFF X X X
-cFP X
-cFR X X
-cFU X X
-cIMP75 X
-cME X X
-cNA1 X
-cNCRC X
-cNE X X X X X
-cOPC X
-cQM/s A/B X
-CRn X
-cSLC X
-cSO X X
-cSP X
-cSU X
-cSW X
-cTS X
Only the key switches are listed, this is especially the case for ISUP, which has an extensive list.
For further details, check the associated text file for the firmware, which are available from the
Aculab web site download area.
44
B.2 System Specific Option definitions

The following list details some of the configuration options that can be used to configure a
signalling port on an Aculab Digital Access card. This list should be used in conjunction with
the latest release note for each protocol. The release notes are shipped with the firmware files
and provide a more in depth description of available options.
B.2.1 -cA/B and X/Y bits configuration (DPNSS only)
Default setting: A/X
This option allows the dpnss A/B X/Y bits to be configured for layers 2 and 3 to enable DPNSS to
DPNSS configuration
-cAX
-cAY
-cBX
-cBY
Incorrect setting of the A/B bits will result in an inactive DPNSS layer 2.
B.2.2 –cBBY Backbusy control (CAS only)
Instructs the CAS driver (and signalling system) to use ‘backbusy’:
-cBBY configure all timeslots all ports
-cBBY, xxxxxxxx configure all timeslots indicated in the mask xxxxxxxx
The mask is an 8 digit hexadecimal representation of a 32bit value where each bit indicates the
busy mode. A bit set to 1 will enable backbusy. A bit reset to 0 will disable backbusy. Bit 0 of
the 32bit value controls timeslot 0 and bit 31 controls timeslot 31.
B.2.3 -cCA connect acknowledgement (ETS300 only)
Some equipment require a CONNECT_ACKNOWLEDGE from the user end of the protocol after
receipt of a CONNECT message. This configuration switch provides for this behaviour.
B.2.4 –cCICnnnn circuit identification codes (ISUP only)
-cCICnnnn
-cCICnnnn,aaaaaaaa
-cCICnnnn,aaaaaaaa,bbbbbbbb
Where nnnn is a decimal number of 1 to 4 digits that will be the CIC assigned to the first bearer
timeslot, with subsequent CICs allocated sequentially (including any timeslot used for signalling,
although this CIC will never be used). The OPC and DPC assigned to the ISUP circuits will be
the most recent values preceding the –cSLC parameter itself.
If specified, aaaaaaaa is a CIC MAP, which allows the user to define which timeslots have CICs
assigned to them. It is specified as a 32bit number expressed in hexadecimal, where bit zero
corresponds to timeslot zero etc. If not specified, a value of fffffffe is assumed.
If specified, bbbbbbbb is a Circuit MAP, which allows the user to define which timeslots have
may be used for ISUP call control. It is specified as a 32bit number expressed in hexadecimal,
where bit zero corresponds to timeslot zero etc. If not specified, a value of fffffffe is
assumed Any timeslots which are in use for signalling are automatically excluded from ISUP call
setup, regardless of whether this is explicitly shown in the circuit map.
If –cCICnnnn is not specified, ISUP will not be available for call setup on the timeslots of that
port.
B.2.5 -cCn number of CLI digits (CAS only)
It is necessary for the device driver and signalling system firmware to know the number CLI
digits supported by the trunk. The driver configuration switch available for this purpose is –cCn,
where n is a one or two digit decimal value of the number of digits required.
The -cCn option specifies the number of CLI digits expected by the system, for example, -cC4
instructs the driver/signalling system to expect 4 CLI digits
It is important that this initial configuration is correct or unexpected behaviour may result.
45
B.2.6 –cDn number of DDI digits (CAS only)

It is necessary for the device driver and signalling system firmware to know the number of DDI
digits supported by the trunk. The driver configuration switch available for this purpose is –cDn,
where n is a one or two digit decimal value of the number of digits required.
The -cDn option specifies the number of DDI digits expected by the signalling system, for
example, -cD3 instructs the driver/signalling system to expect 3 DDI digits
It is important that this initial configuration is correct or unexpected behaviour may result.
B.2.7 -cDPCnnnnn signalling point code (ISUP only)
-cDPCnnnnn
Where nnnnn is a decimal number equating to the signalling pointcode of the adjacent network
component to which the link connects. The network component may be a Signalling Transfer
Point, or, if using fully associated signalling, a Signalling End Point. nnnnn must coincide with
the pointcode of an STP (AdjacentPC), or of an SP (RemotePC) in the stack configuration file as
described in the SS7 installation and administration guide.
This parameter may be repeated to specify that signalling link(s) and ISUP bearer timeslots have
different DPC values. See –cSLC and –cCIC.
B.2.8 -cEn Call Charging Switch (ETS300 only)
This switch allows the application to send or receive call charging information depending on the
country or exchange being used at the time. For further information on the call_put_charge()
and call_get_charge() functions it is advisable to consult the 'Receiving Call Charge
Information' and 'Sending Call Charge Information' sections in the Call Control Driver API
Guide. The value transmitted will be one of two categories of charging for EuroISDN.
1. UNITS - One method is to transmit the value as UNITS. When charging uses the UNITS format
a value representing the number of units accrued up to that point during the call will be
transmitted. This value is initially one and is incremented by one each time the
call_put_charge() function is used. The driver does not require any parameters in the call to
call_put_charge() by the application.
2. CURRENCY - The second method is CURRENCY. When this type of information is used by the
protocol the transmitted value is the accumulated cost of the call up to that point. This
information is passed to the driver in the "charge" field of put_charge_xparms. The format of
this string is an ASCII representation of the numeric value. Example : To send the value of 100
the three ASCII characters necessary to encode 100 as a string would be used. Printing this string
to the screen should show '100' (without quotes).
Codes For Different Countries (n)
n=1 Switzerland/CURRENCY Charging will use Facility information elements based on ETS300
182. A charging string in put_charge_xparms() is required.
n=2 Germany/UNITS Charging will use Facility information elements based on ETS300 182. The
charging string in put_charge_xparms() is ignored.
n=3 Holland/UNITS Charging will use Display information elements based on a country Specific
specification. The charging string in put_charge_xparms() should be left blank.
n=4 Switzerland/CURRENCY Charging will use Display information elements based
on a country Specific specification. A charging string in put_charge_xparms()
is required.
n=5 Austria/CURRENCY Charging will use Facility information elements based on
ETS300 182. A charging string in put_charge_xparms() is required.
n=6 Norway/CURRENCY Charging will use Facility information elements based on
n=7 Sweden/CURRENCY Charging will use Facility information elements based on
n=99 Disable Charging
46
B.2.9 –cEX Primary Rate Call Charging (ETS300 only)

This configuration switch is for use with ETS300 Advice of Charging where there may well be
some national/network dependent differences in the way the charging information is presented.
X is a one or two digit decimal country code:

0 is the default
1 for Switzerland (type I)
2 for Germany
3 for Holland
4 for Switzerland (type II old style)
5 for Austria
6 for Norway
7 for Sweden
99 for disable charging
Consult the release notes supplied with the latest revision of firmware for further details.
B.2.10 -cFD Diversion (QSIG, ETS300, AT&T T1, and NI-2)

This configuration switch activates the diversion feature in the driver.
If the switch for this service is not set, any attempt to use this service through the API will fail.
Example:
If Diversion and Facility features are required for QSIG on port zero then the switches can be
supplied as follows using fwdspldr.
Fwdspldr 12345 0 qsig_sup.upr -cFF –cFD
B.2.11 -cFF facility (QSIG, ETS300, and NI2)

This configuration switch activates the facility feature in the driver.
Example:
If Diversion and Facility features are required for QSIG on port zero then the switches can be
supplied as follows using fwdspldr.
Fwdspldr 12345 0 qsig_sup.upr -cFF –cFD
B.2.12 -cFP MLPP activation (ETS300 only)

Activates Multi-Level Precedence and Pre-emption (MLPP Q.955) in the firmware and driver.
B.2.13 -cFR Raw Data (ETS300 and QSIG)

Activates firmware to use Raw Data information. See Appendix J of the Call
Control Driver API guide.
B.2.14 -cFU user to user (QSIG and ETS300)

This configuration switch activates the user-to-user feature in the driver.
User to User : -cFU
User to User : -cFUN (no negotiation)
B.2.15 -cIMP75
Sets line impedance to 75 ohms (default is 120 ohms).
B.2.16 –cME
If an outbound DASS/DPNSS call is made with the sending complete flag set, then an ISRMC is
used, otherwise an ISRMI will be sent. If the -cMC switch is applied an ISRMC will be used for
all outbound calls, regardless of whether the sending complete flag is set.
47
B.2.17 -cNA1 release link trunk (NI-2 only)

Enables RLT (release link trunk) call transfer with NI-1 signalling. Without the switch NI-2
signalling is used for call transfers.
B.2.18 -cNCRC disable CRC4 (ISUP only)

This instructs the firmware not to use CRC4 framing at L1.
B.2.19 –cNE network end configuration (DASS, ETS300, FETEX, AT&T, and NI2)
Default setting: User end
Network end configuration, sets up the device driver for network end working
-cNE configure port for network end
This switch applies to signalling systems with the exception of CAS, DPNSS, QSIG and ISUP.
Note For correct network end operation, you will require the network end firmware for that signalling system.
B.2.20 -cOPCnnnnn[,i] (ISUP only)

Where nnnnn is a decimal number equating to the signalling pointcode, and optional instance,
of your application. This must coincide with the pointcode (LocalPC) of an SS7 signalling point
in the stack configuration file, as described in the SS7 installation and administration guide.
B.2.21 -cQM/S-A/B master/slave priority (QSIG only)

This configuration switch enables the QSIG Master and Slave bits, M for master and S for slave,
and also the ‘priority if call clash’ bits A/B. Valid options are:
-cQSB
-cQMA
-cQSA
-cQMB
One end must be set to be master and the other end must be set to be slave. Incorrect setting of
these bits will result in an inactive QSIG layer 2. The default configuration for QSIG is –cQSB.
B.2.22 -cRn Default clearing cause (all versions)

Default setting: BUSY
This option allows the default clearing cause to be configured, where n is a one or two digit
hexadecimal value of the required clearing cause and must be a correct value supported by the
signalling system.
-cR3E configure ‘Call Rejected’ on all ports

-cR3En0 configure ‘Call Rejected’ on port 0 only
The above example shows the CALL_REJECTED cause for 1TR6.
B.2.23 -cSLCnn signalling link code (ISUP only)

Where nn is a decimal number equating to the MTP3 Signalling Link Code for the signalling link.
The signalling link is created when the -cSLCnn parameter is processed, the parameters for the
link must appear in this option. If -cSLCnn is specified more than once, multiple signalling links
will be created. The OPC and DPC assigned to the signalling link will be the most recent values
preceding the —cSLC parameter itself.
48
B.2.24 -cSO disable service message (AT&T and NI2)

This configuration switch disables the transmission of the ‘service message’ by the protocol
stack. The service message brings the timeslot into service and may cause problems with some
manufacturers equipment, for example,
1110 0110 0000 0010 0000 0000 0100 0000 will enable backbusy on timeslots: 31, 30, 29,
26, 25, 17, 6 and would be represented by the value: E6020040 and would therefore be
configured by: -cBBY, E6020040
Note On E1 systems timeslots 0 and 16 are reserved and will be ignored.
B.2.25 -cSP stop call proceeding (ETS300 only)

-cSP switch stops a CALL_PROCEEDING message from being sent automatically after a SETUP
message has been received. It is useful if extra information is required to be included in the
message by the use of the call_proceeding function.
- cSP configure for all ports
B.2.26 -cSU stop setup acknowledge (ETS300 only)

Stops a SETUP_ACKNOWLEDGE message from being sent automatically after a SETUP message has
been received. It is useful if extra information is required to be included in the message by the
use of the call_setup_ack function.
B.2.27 –cSW configuration (ETS300 only)

This configuration swtch modifies the driver for use in Sweden where a call_proceeding
message is required instead of a setup_acknowledge message.
B.2.28 -cTS[I]nn (ISUP only)

Where nn is a decimal number equating to the timeslot that will be used for the signalling link
on the E1 line connected to the network port. For E1 cards that support the function, if I is
specified, then the signalling link will face inwards (that is towards the switch matrix and H.110
bus), it can then be switched out on a different E1 using the Aculab switch API. Refer to Aculab
software for digital access cards - Switch API guide, for further details of the Aculab switch API.
49
Appendix C: Troubleshooting
C.1 Call Driver and Signalling Firmware Problems
Device Driver Error Message
C.1.1 Firmware Download Errors
The restart or FWDSPLDR utility is used to download the signalling system firmware to a Digital
Access card. This may produce many errors. This section covers the more common errors.
Bad Systat from Downloaded Signalling System
This is an indication that the download signalling system has detected an error or cannot start.
This may occur for example if a ‘tone based’ signalling system could not find the DSP daughter
card, or the clock is not set correctly for that card.
Device driver does not support the download Signalling system
Ensure that you are specifying the correct firmware file (.UPR .P4R) file for the device driver
that you have installed. If you are trying to download ‘network end’ firmware ensure that you
have set the -cNE configuration switch on the call driver or on the command line when using
restart.
Downloaded signalling system failed to start
The downloaded firmware is not executing. Ensure that you have specified the correct firmware
file for the installed device driver.
Note Ensure that the firmware file is the latest available from Aculab.
50

Ss 7 Fun 04

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ss 7 Fun 04

Hochgeladen von

Copyright:

Verfügbare Formate

Aculab digital network access cards

Call, switch, and speech, telephony software installation guide

MAN1761 Version 6.4.7

4.5 Signalling Software Installation........................................................................................ 42

2 Installation process overview

2.1 Install the Aculab hardware

2.2 Host system startup.

2.2.3.1 Pre Prosody X (IP Telephony PCI)

Primry rate module Proprietary connection

IP Telephony PCI card

NIC A Host system

PMX/PMXC Proprietary connection

Prosody X PCI card Prosody X resources

Ethernet DSP resources

NIC A Host system

2.3 Dowloading and installing the V6 telephony software

2.4 Configuring the Aculab Telephony Software

2.5 Aculab example code

3 Example card installation and configuration for a windows environment.

3.1 Installing the Prosody X card hardware.

3.2 Starting the Prosody X card host system.

and present a Found New Hardware Wizard dialog:

3.3 Download and install of the Aculab telephony-software.

19. Select I Agree to continue.

20. Select OK to continue.

22. Re-boot (Restart) the host system.

3.4.2 Updating the Aculab card list

3.5 Configuring the Aculab telephony-software.

3.5.3 Clocking settings

3.5.5 TiNG Settings

3.5.6 Applying the configuration

52. Select Yes to continue

Once completed, you will receive a confirmation dialog.

4 Example installation and configuration for a non-windows environment.

4.1 Telephony-software download and installation

Where arg can be:

11. Wait for installation to complete.

Checking for updates:

4.2 Linux/Solaris drivers

The commands for dacpinst are as follows:

Note For Solaris, replace aculab_dacp with aculab_v6

4.2.11 Setting up Prosody X Card IP Address on Linux

Note Further O/S specific information can be found in $ACULAB_ROOT/driver/readme.install

4.3 Managing Prosody X cards

4.3.1 Distinguishing Prosody X cards on Linux

Speeding it up by adding traffic

to provide an explicit configuration or:

to configure using DHCP.

4.3.3 Adding a Local Prosody X Card

4.3.5 Obtaining information for an installed Prosody X card

This will return the following information:

4.3.6 Removing a Prosody X card

4.4 Card configuration files

4.4.1 Creating configuration files

Example of prompts if the card is NOT in the system:

Example of prompts if the card is in the system:

Example of resulting configuration file:

4.4.2 Per-card configuration file description

The switch component fields

Legacy configuration (MVIP or SC-Bus)

DSPA & DSPB

The speech component fields

Firmware — the firmware to be downloaded to that module.