Span Loop-Back Test - Avaya Media Processing Server 500 Hardware Installation And Maintenance

Configuration (Part II)

Span Loop-Back Test

Background
The span loopback test verifies the operation of any two spans (or up to four span pairs) on the
same DCC. The test also helps verify most of the system configuration parameters (other than those
that must be modified for the test). For the purpose of this test, any two spans on the DCC can be
paired, one inbound and one outbound. Generally, you want to use two spans that are already
configured as such; however, you can redirect a particular span if necessary (for example, for fault
isolation). All lines on both spans must have DTMF receivers allocated to them. If the DTMF
receiver resource does not exist (or if there are not enough), you must create them.
For this test, two MPS Developer test applications are provided in the /home/peri/testapps/ directory:
IntwTTSA.ppr and OutwTTSA.ppr. The corresponding executable files (IntwTTSA.vex and
OutwTTSA.vex) can already exist in that directory. If the .vex files are not in the directory, generate
them from the .ppr files using MPS Developer. IntwTTSA.vex and OutwTTSA.vex are assigned to,
and started on, lines of the inbound and outbound spans, respectively.
The spans are looped back through the TCCP using a crossover cable. For more information, see
Telephony Interfaces
device, you need to devise some method of making the loop-back connections to run this test.
During the test, the outbound lines or applications dial into the inbound lines or applications over the
looping cables, exchange touchtones, disconnect, and repeat indefinitely. Status messages are
displayed in a command tool window. The examples shown in the following procedure depict TMS1,
span 2 (outbound) looped back to TMS1, span 1 (inbound) using the T1 standard (24 lines/span).
Span Loop-Back Test Procedure
1. Ensure the DCC containing the spans to be tested are connected to the back of the TCCP.
2. Loop the spans to be tested by connecting a crossover cable between the two spans on front
of the TCCP. If the TCCP has RJ48M connectors, a breakout adapter (octopus) cable.
3. Log on to the system as (or change the user to) root: su Password: <root password>
4. Edit the $MPSHOME/common/etc/tms/tms.cfg file to configure resources and lines for the
test. If the tms.cfg file is already configured with the required resources and lines,
modifications are not necessary.
a. Under the [SYSTEM] section, ensure there are RSET profiles defined (and
uncommented) for inbound and outbound lines with DTMF receivers:
[SYSTEM]
...
RSET_PROFILE = InLine
RSET_PROFILE = OutLine isdn:1 dtmf:1
...
b. Under the TMS resource definition [CLASS] section, ensure there are (at least) enough
DTMF receivers for all lines on both spans to be tested (that is, 48 for T1, 60 for E1):
[CLASS]
COUNT
CLASS_NAME = dtmf ; this field is optional to override class in CDF
CDF
Avaya Media Processing Server 500 Hardware Installation and Maintenance
132
on page 195. If your system is not equipped with a TCCP or a span breakout
isdn:1 dtmf:1
= 48 ; number of resources of this class to load
= dtmf.cdf
Comments? infodev@avaya.com
; Inbound rset profile
; Outbound rset profile
October 2014