OTM vs MDR-2000 vs Image Collection vs CDR Collection

[Typeroon]

Hi,

I have to reconfigure my OTM 2.2 server following a hard disk failure. All the configuration was initialy done by Avotus but since we do not want to pay for a "too expensive" service contract that we'll use once a year, I've been told to try to reconfigure it myselft.

All the station admin section was fairly simple but I am struggling with a problem in the telecom billing system.

In fact, all I want to do is to download CDR records that are sent from PBX to MDR-2000, down to the OTM CDR database.

I configured the call collection and on 2 of 3 sites (lets call them sites 2 and 3), the OTM CDR database is being populated correctly. But on 1 of my sites (lets call it site 1), the OTM CDR database is not being populated at all. I can see the records being retreived but instead of being sent to the CDRD001.mdb file, they are sent to TMSIMG.dat file.

I logged into the "Site 1" MDR-2000 box and noticed that the box was configured with CDR COLLECTION = NO and IMAGE COLLECTION = YES On the other sites (2 and 3), the MDR-2000 are configured with CDR COLLECTION = YES and IMAGE COLLECTION = NO

I tried to configure MDR-2000 of "Site 1" the same way it was configured on "Sites 2 and 3" 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 Avotus would have configured this site differently than the 2 others.


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



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


Can someone help me on this issue ?

Thanks in advance.

 

[DocVic]

That "other" site is using DBA (data buffering access) configured along with OTM to collect data to an "image" file. You'll have to un-configure it and use the MDR to collect data. does your OTM have multi sites configured?

DocVic
Dedicated to Nortel Products till the end.
Need help?

http://www.TSS-CO.com

 

[Typeroon]

Yes, my OTM is configured with multi-sites.

I don't know what you mean by using DBA and how to unconfigure it. Can you explain ?

Also, when you say that I will have to use the MDR to collect data. In fact, this is how we are doing. All of our PBX's are sending their CDR records to their respectives MDR-2000 boxes.

But on site #1, for an unknown reason, the records format seems to be different from the 2 others and if the MDR-2000 is not configured with "immage collection=yes" than the MDR box is not accepting the data from the PBX.

I may be wrong but I don't think the problem is with OTM configuration.

Can you give me more details please ?

Thanks a lot for you help.

 

[DocVic]

Image collection should be NO in the PBX. Then records will pass to the MDR. On newer TM-3's, DBA is used to pass all files to an IMG file in the PC, and then process the file for SMDR processing. The TM (or OTM) would be at the site for collection. Once done, you should then be able to collect the call records from the MDR.

DocVic
Dedicated to Nortel Products till the end.
Need help?

http://www.TSS-CO.com

 

[Typeroon]

ok, in wich LD of the PBX should I go to set Image Collection to NO ?

For your information, we have an old release in our PBX. We are running Succession 3.

Also, we are using OTM 2.2 (wich is quite old as well)

Thanks for any more help you can provide to help me resolve this issue.