There are two methods available, depending on the model/software version of the IP Office
(1) Via IP
(2) Via reading of a CSV file created by IP Office Delta Server utility.
Connecting Via IP
This method has only recently been released for IPOffice.
As at 3rd May 2010 there appeared to be no significant problems with connection apart for Externally Diverted Calls from Virtual Extension numbers.. At the moment, it appears the IP Office software does not report on the outbound leg of an externally diverted call.
To connect via IP the IPOffice system needs to be set up in 'Listen Mode'. This is the default setting.
On the SMDR tab in IP Office programming software, leave the IP Address fields at 0.0.0.0 and enter an available TCP port number (e.g. 1150). Enter 500 (or more if you wish) in the Records to buffer field and tick the 'Call Splitting For Diverts' option. Upload.
In PABXSoft, the set up in Reports>Setup>Site is simply a matter of (1) Selecting IP Office (via IP) in Reports Setup>Site and also entering the IP address of the IP Office system and the TCP Port number. Username and Password should be left blank.
Connecting via CSV
This is a tried and trusted method and very reliable, but we understand is no longer supported on the newer IP Office systems.
Avaya IP Office needs to be set up so that a file called SMDR.csv is created
It does not matter where this file is located as when PABXSoft Call Collector is launched a message box will appear asking you to browse to the location of the SMDR.CSV file.
PABXSoft polls this text file every three seconds.
Although data collection from IPOffice is not done via IP address or Serial port
we recommend that you setup PABXSoft in Reports/Setup/Site to connect to a
unused serial port. (e.g. Com 1, Com 2, Com 3 etc)
In the event that the Avaya SMDR program is shut down all call records during this
time will not be recorded.
If the Call Collector is shut down then when it is restarted it will gather all call records
that are in the Avaya SMDR.csv file and process them.
Conflict with Avaya Voice Mail
It has been brought to our attention that the Avaya VoiceMail Pro product appears
to create some conflicts with Microsoft Access databases. A message can appear
asking for a ".msi" file to be installed from the VoiceMail Pro CD. PABXSoft uses an
Access database so if this problem is encountered then PABXSoft and VoiceMail Pro
will need to be installed on different PCs.
Call Collector not processing data?
There are normally two possible causes for this.
1. The location of the IP Office SMDR.csv file is not located where PABXSoft is looking for it.
If the SMDR.CSV file is relocated then the normal Call Collector (not our Windows service version) has a 'Locate SMDR.CSV file) function to allow you to browse to the new location.
2. The Registry entry
If you have previously run PABXSoft or used the import function then PABXSoft has created two values in the computer registry. These values are reset to zero by the Call Collector at midnight but if the Call Collector was not running at that time then the previous day's values will still be located in the registry.
The Call Collector will not process any calls until the current days SMDR.csv file size is greater than the value saved to the registry. The solution is to manually reset the registry values to zero. This can be done as follows
START>RUN>REGEDIT
HKEY_CURRENT_USER>SOFTWARE>VB and VBA PROGRAM SETTINGS
PABX>AVAYA then move to the right window and double click the AB symbol next to Last Line Number and set the value to zero, and then do the same for File Size. Exit the registry and the Call Collector should then process all the calls in the SMDR.csv file for the day.
Note if you are running the Call Collector as a Windows Service then instead of the registry values open the PABX.INI file in C:\Program Files\PABXSoft\Call Collector Service and change the Last Line number there.