User manual OPTICOM HDV-550 DATASHEET

[. . . ] Before you start reading this documentation, you should have studied the OPERATM User Manual thoroughly, since the basic operation of components of the OPERATM system is assumed to be known in the following. OPTICOM's E1/T1 interface option provides you with a large variety of protocols. In the current version the following protocol types are available: E1 Euro ISDN, E1 MFC-R2 CAS protocol including many country-specific variants, E1 CAS-R2 protocol including R2D and R2D modified variants, T1 CAS/Robbed Bit protocols including E&M wink start, E&M immediate start, E&M delay dial/start, loop start and ground start, and T1 National ISDN-2 PRI protocol. T1 ISDN implementations for particular switches are supported as T1 ISDN PRI protocol for the Lucent®/AT&T® 4ESS switch, T1 ISDN PRI protocol for the Lucent®/AT&T® 5ESS-9 switch, T1 ISDN PRI protocol for the Lucent®/AT&T® 5ESS-10, and T1 ISDN PRI protocol for the Nortel® DMS100 switch. [. . . ] As shown in Figure 6. 3, select the loop mode button in the OptiCallTM dialog. Enter the desired phone number which has to comprise five digits according to the protocol subversion chosen. Figure 6. 3: Settings in the OptiCallTM dialog. Select the file that contains a speech sample that will be sent through the network, in the field Reference. In this example we use the WAVE file that is located in the installation directory of your OPERATM system, "DefaultRefFile. wav". Finally, enter the destination directory where the test files shall be saved to. Also enter the root file name for your test files after the character #, e. g. In the "Origin" list box, select the entry "4: E1_MFCR2 Port 0 BCh 0". Select "34: E1_MFCR2 Port 1 BCh 0" as the terminating device. Please note, that depending on the hardware configuration of the selected OPERA host computer, the index numeration in the list boxes of OptiCallTM may be different than stated in this example. The OPERATM host computer is selected in the Network Node entry field of the OptiCallTM dialog. After having pressed the start button, the connection will be established. The speech sample will be sent and the test samples will be saved to the location we have defined above. First Signal Off Time [10 msec] - "Signal Off" period (in 10 msec units) for the first cadence on-off cycle. Second Signal On Time [10 msec] - "Signal On" period (in 10 msec units) for the second cadence on-off cycle. Second Signal Off Time [10 msec] - "Signal Off" period (in 10 msec units) for the second cadence on-off cycle. · · · · Using this configuration file, the user can create up to 16 different call progress tones using up to 15 different frequencies. Each one of the call progress tones is specified by the following parameters: the tone frequency (either single or dual frequencies are supported) and the tone cadence. This is specified by 2 sets of ON/OFF periods, but you may discard the use of the second On/Off cycle by setting the relevant parameters to zero. When the tone is made up of single frequency, the second frequency field should be set to zero. [AUDI01] 7. 2 Editing a CAS Protocol Table 7. 2. 1 Overview CAS/Robbed Bit protocols implement the specific state machine. The user can change the protocol's parameters and even the entire state machine via two related files: the Protocol Table Text File and the User-defined Parameters Header File. The Protocol Table Text File is describing the protocol state machine and various initialization parameters for tuning to a specific switch or PBX. The Protocol Table Text File is named xxx. txt. The User-defined Parameters Header File maps the text-named parameters defined in the above Protocol Table Text File to their User-defined numerical values. The User-defined Parameters Header File is named UserProt_defines_xxx. h. [. . . ] When the event source is DSP or User, the value will be as NO_STATE. When the event 45 CHAPTER 7: OPTIONS FOR ADVANCED USERS Parameter, #1, #2, #3 Trunk Bchannel ConId comes from DSP or from User, the value will be as NONE. The table's function parameters as in the protocol table. The trunk number the event is associated with. [. . . ]