Versions Compared

Old Version 12

changes.mady.by.user Editor

Saved on

compared with

New Version 13

changes.mady.by.user Editor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Configuring your SMDR output

Determine the path you want to create a local DB of the call logging info. The default path is: ReferencemacroLabelThe MX-One phone system saves the call logging information into a local database, located by default in:

Code Block
/var/opt/eri_sn/call_logging

Screenshotmacro
Borderfalse
URL/download/attachments/16712035/MX-One+logging+DB.png

To edit thisthe default path, SSH into each MX-One and use the

Keywordmacro
Labelmc
command. You can use the
Keywordmacro
Labelmkdir (key 7)
 to configure the directory structure as required.

Enter Next, you need to enter the following commands for the primary MX-One (the one that will send the data via IP to TIM Plus):

Code Block
callinfo_output_set  -output 0  -lim 1  -type file  -subtype general  -local    -dbname /var/opt/eri_sn/call_logging/log0  -format ": {stoptime md110date L 4 4}{stoptime md110time L 4 4}{stoptime second 0R 2 2} {duration md110duration L 5 5}; [taxpulses != 0]: {taxpulses R 4 4}; [taxpulses == 0]:     ; {conditionCodeUserDefined L 3 3} {accesscode1 R 5 5}{accesscode2 R 5 5}; [conditionCodePos == 17]: {chargedNumber R 20 20}; [conditionCodePos != 17]: {dialednumber R 20 20}; {callingnumber L 20 20} {accountcode L 15 15} {cilcode L 6 6} {queueTimeCounter 0R 3 3} {ringTimeCounter 0R 3 3} {ogTrnkId R 10 10} {incTrnkId R 10 10} {connectedNumber R 16 16}{return}{newline};"  -eol NL  -record call  -localtime
Code Block


callinfo_output_set  -output 1  -lim 1  -type tcp  -subtype general  -server 10.194.129.37  -port 9000  -format ": {stoptime md110date L 4 4}{stoptime md110time L 4 4}{stoptime second 0R 2 2} {duration md110duration L 5 5}; [taxpulses != 0]: {taxpulses R 4 4}; [taxpulses == 0]:     ; {conditionCodeUserDefined L 3 3} {accesscode1 R 5 5}{accesscode2 R 5 5}; [conditionCodePos == 17]: {chargedNumber R 20 20}; [conditionCodePos != 17]: {dialednumber R 20 20}; {callingnumber L 20 20} {accountcode L 15 15} {cilcode L 6 6} {queueTimeCounter 0R 3 3} {ringTimeCounter 0R 3 3} {ogTrnkId R 10 10} {incTrnkId R 10 10} {connectedNumber R 16 16}{return}{newline};"  -eol NL  -record call  -localtime
Code Block


callinfo_output_set  -output 2  -lim 1  -type file  -subtype none  -record call  -utc
callinfo_output_set  -output 3  -lim 1  -type file  -subtype none  -record call  -utc  
callinfo_output_set  -output 4  -lim 1  -type file  -subtype none  -record call  -utc  
callinfo_output_set  -output 5  -lim 1  -type file  -subtype none  -record call  -utc  
callinfo_output_set  -output 6  -lim 1  -type file  -subtype none  -record call  -utc  
callinfo_output_set  -output 7  -lim 1  -type file  -subtype none  -record call  -utc  
callinfo_output_set  -output 8  -lim 1  -type file  -subtype none  -record call  -utc  
callinfo_output_set  -output 9  -lim 1  -type file  -subtype none  -record call  -utc

 

Then, for the primary MX-One, add the following two commands to send the data:

...

For each additional MX-One in the cluster, the following commands need to be entered:

...