OTM Buffering issue

[jheendi]

Good Day All,

We have Meridian CS1000M with SMDR buffer box on the switch.
Just last week I have noticed that we lost all the calls, I tried to repair and compact but no vain.

We have lost all the call database for last month and when I checked the status of Buf under LD 117 I got this
=> stat buf
CDR ENL
TRF ENL
STN DIS
Storage space is empty.
Connected to 192.168.10.6

Is there any way I can recover call database or its too late..

Please help.

 

[allenmac]

From what you have posted above, the CDR records are being dumped to 192.168.10.6 (I assume this is the TM/OTM server), and should be stored in a file on the TM server usually named detail1.dat in the windows folder for that system.

If you also have a Buffer box connected serially to the pbx (and that serial port is configured with user CTY), then it should also receive the call records which you must periodically pull from the box and import into the Telecom Billing Module.

Check to see which device you are actually using to populate your Telecom Billing. If you are using the buffer box, then try changing your collection configuration to reference the 'detail1.dat' file on the TM server - if you have been buffering data to this file for a long time, then the file may be huge, and you could end up with duplicate records in your call database.

 

[DocVic]

Do you have an "external" buffer box, like an MDR2000 or the like? If so, you need to switch the collection to serial and collect that way. Sounds like the CDR records from the PBX to the SMDR box has stopped working. Stat your TTY's. Make sure you can "talk" to your Buffer box.

Regards,
DocVic

 

[jheendi]

Hi Allenmac, I checked under windows directory on the OTM server and could not find file detail1.dat however there is one file named detail1.img and size is 73kb.

We do have Microsoft Access Database file named CDRD001 which is increasing in size all the time and we have to archive call database before it reaches 600 Mb range.

As for DocVic's recomendations, I checked and we can talk to Buffer box and collect data. We do have schedular which run at the end of day to collect and cost all the calls.

Please advise,

 

[allenmac]

Sorry for the confusion, detail1.img is the file that is collecting call records and traffic reports from your pbx.

Check your collection configuration to see which device you are reading the records from. 73KB is a pretty small file, and may not contain many records.

 

[jheendi]

I checked the collection settings and it collect to File detail1.img and use collection script sl1old.coll I am attaching the script for your kind review.

The size of file is increasing and at the end of day we have schecular which run and empty the buffer box.

Do you think the script might have been changed.. cause I see few more in that folder of scrips.

;*******************************************************************************
; Script file for the Data Script Engine to process Meridian SL1 records.
; Created 08-APR-98 by MGR
; Based on MAT SL1.SCR.
;*******************************************************************************
;
;Revision History:
;[1] 15-SEP-00 - RT - Modified to save the value of AuxID in UserDef1$
;[2] 29-JAN-01 Adding MDR2KE_Error.inc to show proper Ethernet message. RT
;[3] 11-MAY-01 Moved the common code to SL1OLD.INC file so it can be used
; in BCM.COL and added "INCLUDE SL1OLD.INC"
;[4] 22-APR-03 -HZ- Adding StoreCIP and RetrieveCIP
;[End of Revision History]

;*******************************************************************************
; INCLUDE LANGUAGE FILES
;*******************************************************************************

Include LNGFILE(COMMON)
Include LNGFILE(SL1)

;*******************************************************************************
; INCLUDE STATUS.INC - Includes constants for sending status information.
;*******************************************************************************

INCLUDE STATUS.INC

;*******************************************************************************
; INCLUDE CONNECT.COM - Includes routines for communications - serial or file.
;*******************************************************************************

INCLUDE CONNECT.CON

;*******************************************************************************
; INCLUDE COLLECT.INC - Includes common CDR handling routines.
;*******************************************************************************

INCLUDE COLLECT.INC

;*******************************************************************************
; INCLUDE MDR2KE_Error.INC - Includes ETHERNET Routine Names and it shows
; that this script does not support Ethernet option
;*******************************************************************************

INCLUDE MDR2KE_Error.inc

;*******************************************************************************
; INCLUDE SL1CDR.INC - Includes common SL1 specific CDR handling routines.
;*******************************************************************************

INCLUDE SL1CDR.INC

;*******************************************************************************
; INCLUDE SL1OLD.INC - Includes common SL1 specific CDR handling routines.
;*******************************************************************************

INCLUDE SL1OLD.INC

;*******************************************************************************
; INCLUDE CIPTABLE.INC - read/write CIP from/to a file
;*******************************************************************************

INCLUDE CIPTABLE.INC ;[4]

;******************************** Main Routine *************************
;*************************************************************************
;*************************************************************************
;
let ConnectionType$ = Upcase(ConnectionType$)
if (ConnectionType$ <> 'FILE') and (not RealTime!) then
begin
println(SL1_OLDRT$)
SendStatus(STAT_OK, SL1_OLDRT$, Result!);
Stop
end
if (ConnectionType$ = 'FILE') and (RealTime!) then
begin
println(SL1_OLDBATCH$)
SendStatus(STAT_OK, SL1_OLDBATCH$, Result!);
Stop
end
println(SL1_START$)
SendStatus(STAT_OK, SL1_START$, Result!);

Do RetrieveCIP ;[4]

Do InitiateConnection

if not ConnectionError! then
if not Cancel_Flag! then
Do ParseMeridian1

Do TerminateConnection

If Not ConnectionError! Then
If Not Cancel_Flag! Then
Do StoreCIP ;[4]

if ConnectionError! then
SendStatus(STAT_ERROR, SCR_ERRDS$, Result!)
if Cancel_Flag! then
SendStatus(STAT_CANCEL, SCR_CANCEL$, Result!)

println(SL1_STOP$)
SendStatus(STAT_OK, SL1_STOP$, Result!);
delay(1000)

_______________________________________________________________--------------------------------------------------------

 

[allenmac]

The script should not have changed.

Unless you changed the format of the records the PBX is sending from 'old' to 'new', you should be ok with this script.

It looks like you are using the data from the detail1.img file to populate your CDR database.

Are you using the records from the buffer box at all, or is it an old piece of equipment that was never removed? I don't understand why you have both.

 

[jheendi]

What happened is we have CDR to monitor call coming in in Real time however buffer box capture data and collect at the end of day to populate Call Database..

 

[jheendi]

Also I noticed that problem started when I got critical error with Data Buffering Access application as below on June 11th..

Here is critical error information pls..

Failed to open local file C:\Nortel\Common Data\Canada Revenue Agency\CSE1000M Multi\DBA\current.trf.dba.

Could this be known issue of OTM 2.20.776 I know its end of Life as of August 4th 2009.

CR ID P Title Impact and Workaround

Q00985507

1 OTM does not clear Pollcat III

Buffer Box memory after collection

Impact: Buffer box space is used up

which may cause lost data if box is

near full; high risk of duplicate data in

the customer's call database which

may cause incorrect reports; may also

cause the collection times to increase

because there are always more

records than what may be new since

last collection.

Workaround: After a collection

customer is required to connect to the

buffer box and manually clear records

by using the ^B 25 command.

Please advise.

 

[allenmac]

I have never found real time call monitoring to be worth the trouble, so I have never used it. It looks like the calls you lost are gone for good, unless you have archived them, and can restore from the archive.