Windows Client/Server

T1/E1 Analysis

Transmit/Detect Digits

Overview

T1/E1 cards have the ability to transmit and detect digits on all the TS of 10 ports of HD cards.

Above test was conducted with the response time of 200ms and latency 100ms on a Rack Mount PC having the configuration of Pentium IV 2.8 GHz, 512 MB RAM & 40 GB Hard Disk.

The sample script shown below is Transmitting DTMF, MF, MFR2F AND MFR2B digits and monitoring (capturing) the digits transmitted form card1 for 30 seconds

set latency default;
set response default;
set priority default;

monitor dtmf digits, mf digits, mfr2f digits , mfr2b digits  #2:1 30 sec;
tx dtmf digits("1 2 3 4 5 6 7 8 9 0 * # A B C D ",-10,40,60)#1:1;
wait 5000;
tx mf digits(" 1 2 3 4 5 6 7 8 9 0 KP ST STP ST2P ST3P  ",-10,40,60)#1:1;
wait 5000;
tx mfr2f digits("1 2 3 4 5 6 7 8 9 0 KP ST STP ST2P ST3P  ",-10,40,60)#1:1;
wait 5000;
tx mfr2b digits("1 2 3 4 5 6 7 8 9 0 KP ST STP  ST2P ST3P  ",-10,40,60)#1:1;


  • Digit Detector configuration file option:

    Digit detector configuration file option detects and reports DTMF/MF/MFC-R2 digits on channels as they occur. GL's HD cards have the ability to transmit and detect digits on all the timeslots.

  • Place/Answer Calls in WinkStart
    Click here to download the near and far end termination of MFC-R2 answer call script.
    Click here to download the near and far end termination of MFC-R2 place call script


  • Call capture using WCS

    Simulation of MFC-R2 answer call using Windows Client Server script:

    In this script the near end card initially transmits idle signal and waits for the other end to send line seize signal. After receiving the line seize it will send line seize acknowledge signal to the other end, which is waiting for it. When near end receives MFCR2-F digits, it transmits MFC-R2 backward digits. After finishing the transmission of backward digits, it will send an answer signal to the far end. Call gets established. The near end card transmits a voice file from GL's card for a specified duration (10 sec). The call may be terminated either at near end or at far end. In first script, near end will simply wait for idle signal from the other end and after receiving the idle signal it will transmit the same to far end. Thus terminating the call. In second script, the near end will send a clear back signal and wait for idle signal from the other end. Then it will transmit idle signal to complete the call termination.

    Click here to download the near and far end termination of MFC-R2 answer call script

    Simulation of MFC-R2 place call using Windows Client Server:

    In this script the near end card initially transmits idle signal and waits for the other end to send the same. After receiving the idle signal from far end it transmits line seize signal to far end, and waits for line seize acknowledge signal. Near end now initiates the dialing. After completion of dialing it will wait for answer signal from far end. The near end card transmits a voice file from GL's card for a specified duration (10 sec). The call may be terminated either at near end or at far end. In first script near end will simply wait for clear back signal from the other end and after receiving the same it transmits idle signal to far end, terminating the call. In second script the near end will send idle signal and wait for the same from other end to terminate the call.

    Click here to download the near and far end termination of MFC-R2 place call script



Resources:

Please Note: The XX in the Item No. refers to the hardware platform, listed at the bottom of the Buyer's Guide, which the software will be running on. Therefore, XX can either be ETA or EEA (Octal/Quad Boards), PTA or PEA (tProbe Units), UTA or UEA (USB Units), HUT or HUE (Universal Cards), and HDT or HDE (HD cards) depending upon the hardware.

 Back to Client/Server Scripted Control Software Page