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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. RichardLynch

    CDR serial cable tNetTask: restarting receive

    Not sure which setting it was, but we got it working with minicomm, and then just copied the settings over into the shell script, and it's working flawlessly. I suspect the settings are configuration dependent, so I won't cloudy the waters posting ours. Use something like minicomm and tweak it...
  2. RichardLynch

    CDR serial cable tNetTask: restarting receive

    I'm trying to get CDR data to an external CentOS computer for analysis by an application I am writing. The hardware guy has hooked up a cable, and told me to use 9600 7-N-1, no flow control, no handshakes. I have set up /dev/ttyS0 as follows: speed 9600 baud; rows 0; columns 0; line = 0; intr...
  3. RichardLynch

    Hide CLID on Attendant Console

    Train the directory to hit *9 or whatever it is that blocks caller ID before they call in?... [shrug] Sure sounds like somebody has an "issue"...
  4. RichardLynch

    Nortel CDR D records

    Aha! Some D records are the whole call sequence, according to the text in the EXAMPLES section of the docs! Apparently, some routings never generate anything but the D record. Even more fun, it turns out that there are E (END) records which have no corresponding S (START) records, in direct...
  5. RichardLynch

    Nortel CDR D records

    I get the part that a DMCA device has connected to the trunk... I'm just not clear on the actual sequence of events that leads to the D record. For example, there are a lot of N records followed by a corresponding D record. I'm interpreting that to mean that a call came in, and the D device...
  6. RichardLynch

    Nortel CDR D records

    I am successfully parsing individual CDR records. I am now "matching up" records for a single "call sequence". E.g., An N record might be tied to a D record, if they have the same ORIGNO and TERMNO, as a "near" timestamp. I seem to have a lot of D records in isolation, however. What exactly...
  7. RichardLynch

    Sample CDR logs

    Anybody have a good source of sample CDR logs for QA purposes? Our logs have very limited subset of Record Types, so my generalized parser isn't getting a real QA workout. If no, would anybody be interested in collaborating on collecting something like that? We'd need a "sanitizer" script...
  8. RichardLynch

    Call Detail Record Parsing Line 2

    Okay, so what happens to a 7-digit tenant system in line 1, record type 'L', columns 71-77? There simply isn't room there to cram in 7 digits... Do I get the number modulo 10000? Or does the record actually extend and the TERTENO doesn't actually start at 75, but wherever is convenient? PS I...
  9. RichardLynch

    Call Detail Record Parsing Line 2

    Thanks! Up to 7 digits, eh? Okay, I'll code it for {3,7} digits. I appreciate it!
  10. RichardLynch

    Call Detail Record Parsing Line 2

    Aha! My 'L' records also have 4-digit Tenant numbers in columns 70-73 and 75-78 rather than the 3-digits documented. I am now 99.9999% certain these are 4-digit Tenant numbers, expanding left and right. Is there kit out there that uses 5-digit Tenant numbers?
  11. RichardLynch

    Call Detail Record Parsing Line 2

    I'm parsing the output from a Nortel CS1000 Call Detail Recording stream. In my sample data, I have a line 2 like this: & 0000 0000 ##########XXXXXX Digits obscured by # to protect the guilty. In the documentation (Release 5.0 Doc Rev 1.04) on pages 167-169, I can find nothing...

Part and Inventory Search

Back
Top