Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Rolm 9751 CDR output 2

Status
Not open for further replies.

GMala

MIS
Jan 28, 2011
3
US
Greetings!

I have two Rolm 9751 mod 50s at different locations. My CDR dumps to an ip.buffer (Scannex) attached to the breakout box via serial at each location. The ip.buffer then ftp's the data file to my Windows server for call processing.

The two files are formatted differently. One is the standard (correct) format as detailed in the original Siemens manual. The other is slightly different, but enough to mess up my call accounting. I have swapped the boxes just to be sure it is the CDR output and not the buffers causing the problem.

Instead of a regular 0x0d, 0x0a (CR+LF) sequence at the end of each record like the correct site, it is outputting 0x0d, 0x7f, 0x7f, 0x7f, 0x0a, 0x7f, 0x7f, 0x7f, at the problem site.

The questions are: Why is the output different? and, What can I do to change the format of the CDR output?

Thanks in advance!
 
Was the CDR output working fine for both systems, then one of the formats changed recently? Or has this been an ongoing issue?
Just trying to determine if this mismatch could be a switching or database "problem" versus an issue with the way the CDR was originally configured. I suspect that initially these systems worked independently, with CDR intentionally set differently. But now that you have attempted to network the CDR output, you've just discovered the mismatch. There are several 9751 techs that frequent this forum. Unfortunately I have not touched a 9751 since 1993. Perhaps the Realitis/HiPath DX folks can help, since the code is similar.

 
This is from one of my old manuals. The "List CDR_GROUP All" command may tell you what your looking for.


8.14.3 Performing the CDR Test
Because of the numerous recording devices available, a complete test usually
requires third-party vendor assistance.
Test the CDR list output as follows:
b 1. Identify the demarcation point. This point is generally an EIA/TIA-232-E
b connector between the SMIOC and the recording device.
2. Install a tested operating printer on the system side of the demarcation point.
3. Type the following CNFG command:
CREATE SIO_PORT CDR
Set the SMIOC to the baud rate for the test printer.
4. Type LIST CDR in CLI mode. Verify that the fill and drain tasks are running for
each node.
If the drain is not running, type the following:
START CDR DRAIN <node #>
If the fill is not running, type the following:
START CDR FILL <node #>
If the error message CDR DEVICE NOT ON LINE appears, continuity between the
system and the CDR device has been lost.
5. Type the following CNFG command to list the trunk group:
LIST TRUNK_GROUP ALL
6. Type the following CNFG command to list the CDR databases and to identify
the types of calls that the system records:
LIST CDR_GROUP ALL
7. Place test calls for each type of record expected for both incoming and
outgoing calls.
8. Verify that the test calls print out the calling extension, number dialed, trunk
number, and length of the call. Depending on the CDR database, you may
need to make several test calls before the system prints the records.
If this test is unsuccessful, verify the CDR and TRUNK_GROUP databases for
correct entries, then retest.
9. When you successfully complete testing, inform the customer contact that the
system is recording calls and that the third-party recording device can be
installed if necessary.
8-18 9751 CBX Installation Guide
10. When you complete the procedure, enter the time, date, and your initials
next to the correct entry in the Installation Checklist in Appendix B, “Forms.”
Enter any comments
 
Go into CNFG and do a
COMMAND: LI SIO
PORT NAME: CDRL
PHYSICAL NODE NUMBER: 2


PORT CNFG CNFG
NAME NODE PORT PORT TERM
---- -- -- - -
DS CDRL 2 A7 N N


P O R T C H A R A C T E R I S T I C S

BAUD PORT WORD DISABLE STOP
PORT NODE RATE MODE LENGTH PARITY PORT BITS
-- -- ----- -------- - - - -
DS A7 2 9600 PRINTER 7 E N 1


T E R M I N A L C H A R A C T E R I S T I C S

TERM LF CR MAX
PORT NODE TYPE LE_HC ECHO DELAY DELAY CRLFO IFC OFC COL
-- -- ------- -- --- --- --- ---- --- --- ---
DS A7 2 SI700 HC ON ON ON CRLF ON ON 80

O U T P U T F I L T E R C H A R A C T E R S

CURSOR GROUP
LEFT RIGHT UP DOWN FORMFEED HOME SEPARATOR
--- --- --- --- --- --- --- --- --- --- --- --- --- ---
DS ^H NUL BL NUL ! NUL ^J NUL NUL NUL NUL NUL GS NUL

I N P U T F I L T E R C H A R A C T E R S

FUNCTION CHAR CHAR TYPE
------------- --- - -------------------
DS RIGHT ^X <ROLM_STANDARD>
DS LEFT ^Y <ROLM_STANDARD>
DS RUB RUB <ROLM_STANDARD>
DS RUBFORWARD ^F <ROLM_STANDARD>
DS BEGINNING ^B <ROLM_STANDARD>
DS END ^E <ROLM_STANDARD>
DS KILL_TO_END ^K <ROLM_STANDARD>
DS ERASE ^D <ROLM_STANDARD>
DS INSERT ^I <ROLM_STANDARD>
DS FORMFEED ^L <ROLM_STANDARD>
DS FIND_NEXT ^G <ROLM_STANDARD>
DS FIND_PREVIOUS ^V <ROLM_STANDARD>
DS DELETE ^W <ROLM_STANDARD>
DS BEGINNING ^H <ROLM_STANDARD>

and then comparfe the two



OLD ROLMEN WORKING ON NORTELS AND AVAYA
 
Well . . . after trying all kinds of things and performing the suggested tests, I still couldn't get it figured out. I was very fortunate to get the help of the engineer at Scannex to assist me by writing a little code and placing it in the ip buffer to correct the CDR (make it uniform) as it passes through.

Thanks for all the help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top