MDR-2000 vs PBX Meridian Option 11 CDR issue

[Typeroon]

Hi,

First of all, I have to tell you that this thread was already discussed last year but the problem was never really solved because du to an "out of my control" situation, I had to stop the project. But now, I've been asked to jump in the project again so I need some help to finally solve my problem.


I had to reconfigure my OTM 2.2 server following a hard disk failure in may 2010. (I know this is an out-of-date version but the company where I work, does not want to upgrade it). Thanks for your understanding.

I am struggling with a problem downloading CDR records that are sent from PBX to the MDR-2000 buffer box.

We have the same setup at 3 different sites and on 2 of them, everything is working fine. But at one specific site, (lets call it site #1), I am having an issue with the CDR vs MDR-2000 box.

On site #2 and #3 (where it is working fine), we have the following MDR-2000 setup.


*****************************************************************
MDR-2000e Interactive Monitor
Copyright (c) 1986-2000 MDR Technologies Inc.

M2K> Status (Enter)

Date/Time (mm/dd hh:mm): 06/10 13:37 Option Settings: NLN
Number of Records Stored: 000203 Records to be Collected: 000203
Port Config (PBX/Modem): 9600-8-N/ 9600-8-N Minimum Duration: 0
Incoming Calls: Yes Minimum Digits: 0

CDR Collection: Yes Image Collection: No
Meter Pulse Detection: No Multi Tenant Detection: No
Tandem Conversion Option: No Internal Calls (Ext->Ext): No
Last Scan Error Position: 56 Alarm Threshold: 000000
Port Reset Timer: 15 Idle PBX Alarm Threshold: 0

Logical Error Count: 000000 Alarm Enabled: No
Buffer Memory Size: 128K I/O Interrupt Status: Clear
Site Name: Site #:
Primary Alarm Phone No:
Secondary Alarm Phone No:

M2K>
****************************************************************

Here is an example of site 2 and 3 CDR records collected
------------------------------------------------------------------------
X13300T0050006D000581205171635000028000000
X13400D0000363T00510220517163400005800000071525195209939
X13500T0050020D000130705171637000130000000
X13600T0050013D000580805171640000012000000D7806353066
X13700T0050014D000581405171639000130000000D7057287141
X13800T0050019D000130705171639000130000000D5194518083
END
------------------------------------------------------------------------






At site #1 (where I have a problem), the MDR-2000 is configured like this.

*****************************************************************
MDR-2000 Interactive Monitor
Copyright (c) 1986-1994 MDR Telemanagement Ltd.

M2K> Status (Enter)

Date/Time (mm/dd hh:mm): 06/04 00:09 AutoDate: No
Number of Records Stored: 500 Records to be Collected: 500
Access Codes: Yes Leap Year Selection: No
Port Config (PBX/Modem): 1200-8-N/9600-8-N Minimum Duration: 0
Incoming Calls: Yes Minimum Digits: 0

CDR Collection: No Image Collection: Yes
Meter Pulse Detection: No Multi Tenant Detection: No
Tandem Conversion Option: No Internal Calls (Ext->Ext): No
Last Scan Error Position: 52 Alarm Threshold: 0
Port Reset Timer: 15 Idle PBX Alarm Threshold: 0

Logical Error Count: 0 Alarm Enabled: No
Buffer Memory Size: 128K I/O Interrupt Status: Clear
Site Name: Site #:
Primary Alarm Phone No:
Secondary Alarm Phone No:

M2K>
*****************************************************************

Here is an example of site 1 CDR records collected
-----------------------------------------------------------------
X12100IE 100 00 T000006 7507 05/17 15:56 00:02:00
X12200I & 0000 0000 4186662552XXXXXX
X12300IE 101 00 T000004 2454 05/17 15:56 00:03:28
X12400I & 0000 0000 8193508747XXXXXX
X12500IN 102 00 T000020 7026 05/17 15:53 00:02:40
X12600I & 0000 0000 6044373377XXXXXX END
------------------------------------------------------------------

As you can see, they have not the same CDR format.


On site 2 and 3, when OTM retreive the records, it sends it to the CDRD001.mdb file, wich seems to be ok as far as I know.

But at site #1 (where I have trouble), they are sent to TMSIMG.dat file. This is probably because of the CDR COLLECTION = NO and IMAGE COLLECTION = YES in the MDR-2000 so I tried to set it to CDR COLLECTION = YES and IMAGE COLLECTION = NO like the 2 other sites. But since that, CDR records are no longer sent from PBX to MDR-2000.

In the MDR-2000, The "number of records stored" and "records to be collected" are always equal to zero (0). Looks like there is a configuration in the PBX of site 1 that is not the same as on PBX's of sites 2 and 3. I cannot see why MDR-2000 of site #1 would have been set differently than the 2 others. (this setup was initially done before I got hired).

Here is my LD21 CDR_DATA section All 3 PBX are set the same way.

CDR_DATA
CDR YES
IMPH NO
OMPH NO
AXID YES
TRCR YES
CDPR YES
ECDR NO
BDI YES
PORT 2
BCAP NO
CHLN 2
FCAF YES
CHMN 1
FCNC 0


I checked the CDB and RDB of each sites and it seems to be ok (as far as I know). I did not paste them here since it is quite huge. But if it is needed, let me know.

all three sites have FCDR = OLD in the PRT PARM of LD22

I think that at that point, OTM has nothing to do yet so it must be something with the PBX but what ?

Another thing is: Do you know if there is any "image collection" parameter into the PBX, that may be set to YES into our "site 1 pbx" and set to NO into the 2 other sites pbx ?

The last thing I can say is since I think OTM is not related at that point because the problem seems to be between MDR box and PBX, it may be a parameter in the PBX that was changed (accidentally or volontary) by our telco technicien following a maintenance in the "routes" because I can remember them doing changes back to 2010. (quite at the same time/date where we had the OTM crash). So probably they changed something in the routes, related to the CDR that caused all that mess. I checked and everything seems to be ok but I only checked the CDR YES parameter for each route. I don't know if I have to check something else.

I know this is a lot of info for the initial thread but I thought that the more I put initially, better are my chances to have this issue fixed.

Thanks in advance for any help anybody can provide.

 

[trvlr1]

Through regular CLI or OTM, I do not know of any options for changing the format of the CDR, (there may be through higher level access though)
That said, You might want to try connecting a PC directly to the cable, with Hyperterm etc. set up for the appropriate direct connection and see what you get for output., that might prove if it is the feed or the MDR thats causing the issue you are seeing. You should see the CDR come up on the screen.
If you still suspect the MDR 2000 you might want to run "test eprom", "Test Logical", "test NVR" and "Test Ram" to see if the unit can find any issues with itself. You might also want to try a Master Reset (MR) to see if it clears things up.