![Asentria Teleboss 850 Скачать руководство пользователя страница 145](http://html.mh-extra.com/html/asentria/teleboss-850/teleboss-850_user-manual_2981745145.webp)
TeleBoss 850 2.06.280_STD User Manual
Page 139
Call Type, Start Date Time, End Date Time, Effective Call Duration (converted from seconds to HH:MM:SS format),
Acting Extension Number, Trunk 1 and the user wants to specify the record using TICKET FIELD NUMBERS, the
setup would look like this:
alcatel.ip=22.23.212.12
alcatel.port = 2533
alcatel.timeout = 30
alcatel.field[1]=10,2,L // Call Type
alcatel.field[2]=40,17,L // Start Date Time
alcatel.field[3]=12,17,L // End Date Time
alcatel.field[4]=38,10,L,STOHMS // Effective Call Duration
alcatel.field[5]=41,25,R // Acting Extension Number
alcatel.field[6]=16,5,5,L // Trunk Identity
alcatel.field[7]=9,30,L // Calling Number
alcatel.field[8]=2,30,L,0D0A // Called Number
In the above, the field definition arguments are:
<field>=<ticket field # , length of that field to take, justification[,end of line chars][,conversion]>
The 0D0A terminator on field 8 tells the unit to store all assembled output fields up to and including that output field
(in ascending order of field definition number) as 1 record. Note that the 0D0A optional value places the end-of-line
characters on the last field, but you could include the EOL characters at other fields also so as to make multiple
records. If the final field definition does not have any EOL characters, then the unit stores whatever it has assembled
so far as 1 record, appended with either:
1. the first EOL character set found in any other field definition starting with the first field, or
2. CRLF, if no other field definitions have EOL characters.
If we wanted to use explicit character position values, the setup would look like this:
alcatel.ip=22.23.212.12
alcatel.port = 2533
alcatel.timeout = 30
alcatel.field[1]=166,2,2,R // Call Type
alcatel.field[2]=441,17,17,L // Start Date Time
alcatel.field[3]=169,17,17,L // End Date Time
alcatel.field[4]=430,10,10,R,STOHMS // Effective Call Duration
alcatel.field[5]=458,30,20,L // Acting Extension Number
alcatel.field[6]=211,5,5,R // Trunk Identity
alcatel.field[7]=136,30,30,L // Calling Number
alcatel.field[8]=5,30,30,L,0D0A // Called Number
In the above, the field definition arguments are:
<field>=<start pos, how long the field is, length of that field to take, justification[,end of line chars][,conversion]>
Once a configuration file is uploaded to the unit, the T850 indicates that it is processing the data. It returns
"COMPLETE" when all settings are processed. The unit gives no other progress or status feedback to the user while
it is processing the file. Instead, it logs feedback to a file that the user can view after processing is complete. If there
were any problems, the unit will display an error message after processing is complete.
To view the log, enter the
SK LOG
command. This will display which settings, if any, it failed to process because of
bad value, key name, or syntax. Bear in mind, this upload process does not attempt to error check the output field
definitions, it only stores them. Instead, the real time client verifies these field definitions when it is started. If the
client is idle (you can tell the client's state by entering the
IPRC STATUS
command), you must start the client in order
to tell it to compile the settings (
IPRC START
command).
Содержание Teleboss 850
Страница 6: ......