Aastra MX-ONE (Aastra 700) - IP connection

Hi Sabs,

Here is the info for settings up an MX-One:

Determine the path you want to create a local DB of the call logging info.  Default is:

...

These instructions help you configure your Aastra MX-ONE (Aastra 700) phone system to work with TIM Plus. Contact your system maintainer if you are not familiar with the configuration of your PBX.

<a id="Configure the SMDR output"></a>

Configuring your SMDR output

The Aastra MX-One phone system saves the call logging information into a local database, located by default in:

/var/opt/eri_sn/call_logging

...

...

...

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):

...

...

callinfo_output_set

...

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

##SEE callinfo_status_set.txt "-lim 1" file##

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

##SEE callinfo_output_set.txt "-lim 2" file##

##SEE callinfo_status_set.txt "-lim 2" file##

Lime 2, 3, 4, n depending on which server you are applying the commands for.

The IP address portion needs to be highlighted in the docs as it will have to be changed.

The guys said at Weston said they would review the doc before it goes live (Andy Smith, Paul Blackwell and Rob Tate).

Let me know if you have any questions.

Thanks,

Andy

Staffline OSP - Weston (screenshots - Andy Smith?!)

HMRC

East Riding District Council - through Weston

speak with Andy Smith from Weston for connection method and screenshots

client for which the IP connection was configured: Staffline OSP

Example 2

This example shows a UK logging format with output over TCP to the

server at 192.168.0.1 on port 9876.

5.2 Fixed Output Format

The fixed output format is a predefined output format that cannot be

altered. The fixed output formats can only be used for CIL data, not for

VoIP QoS logging. For further information, see the command description

for CALL INFORMATION LOGGING, CL .

callinfo_output_set -type file -subtype general \?

-dbname /var/log/smdr/ex_2 -output 1 -lim all \?

-format “{callingNumber L 2 10} connected to {connectedNumber L 2

10} ; \?

[dialedNumber ==connectedNumber] : {newline} {exit} ; \?

but dialed {dialedNumber L 2 10} ; \?

[duration <= 10] : {newline} {exit} ; duration {duration L 2 20} ;

{newline} ;”

callinfo_status_set -state on -lim all -output 1

callinfo_output_set -lim all -output 0 -type tcp -subtype general \?

-server 192.168.0.1 -port 9876 -local -utc -eol CRNL \?

-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} \?

{dialednumber R 20 20} {callingnumber L 20 20} {accountcode L 15

15} \?

{cilcode L 6 6} {queueTimeCounter 0R 2 2} {ringTimeCounter 0R 2 2}

\?

{ogTrnkId R 9 9} {incTrnkId R 9 9} {connectedNumber R 16 16}

Fixed Output Format

The fixed output format is a predefined output format that cannot be

altered. The fixed output formats can only be used for CIL data, not for

VoIP QoS logging. For further information, see the command description

for CALL INFORMATION LOGGING, CL

Execution

• Key the command callinfo_output_set -format to choose a fixed

output format .

• Key the command callinfo_status_print to check the result .

TEsting the TCP output

How can the data, sent on TCP to the central storage, be tested?

The command callinfo_tcp_print is creating a passive server that

will listen to the incoming datastream and present it on the screen.

To see the output, make a copy of the output data and paste it

directly into the server where the program is running. For example,

enter command:

>callinfo_tcp_print -server localhost -port 1023

  -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  

callinfo_output_set  -output 1  -lim 1  -type tcp  -subtype general  -server 192.168.0.1  -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

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  

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

callinfo_status_set  -lim 1  -output 0  -state on
callinfo_status_set  -lim 1  -output 1  -state on

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

callinfo_output_set  -output 0  -lim 2  -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  

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

callinfo_status_set  -lim 2  -forward 1  -state on

<a id="Configure TIM Plus"></a>

Configuring TIM Plus

Follow the steps below to configure TIM Plus to listen for SMDR data from your MX-One:

1. Click on the Directory tab.
2. Choose the site you want to configure and click Properties.
   

   Screenshotmacro
   Border false URL /download/attachments/16712035/MX-One_1.png

3. In the Site Properties window, select Aastra MX-ONE - BC13 from the PBX model drop-down list.
4. In the Connection method field, select Listen for connections from PBX from the drop-down list.
5. Leave the Host field blank.
6. In the Port field, enter the port number you have configured in the phone system.
7. Click on the Save button to apply the settings.