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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Pulling Traffic
- Thread starter nortel24
- Start date
- Thread starter
- #3
acewarlock
Technical User
You can get Volume of calls on 1 TN in LD 2, you would use CDR to get the Number called or calling the DN. Do you hhave NTP's to lookup the commands?
- Thread starter
- #5
acewarlock
Technical User
Read the prompts in LD 2, I havn't done this in years and I don't have NTP's Available.
CDR is NOT friendly in the Nortel system. You can turn it on or you can turn it off. That's about it. It will give you information on all calls in a very raw format.
From there you will need to wire up a TTY port so you can collect this information to a seperate application, or you can parse the information out to a spreadsheet. There are some on the NET if you look.
If you have a lot of call traffic, the capture file you collect in one day could be a 5-6 MB file. That doesn't seem like much these days, but when was the last time you tried to open a 5MB text file. It will lock up your computer.
CDR is not just punch in a few line code changes and you have what you need. It doesn't store historical data without a buffer box and you telling it to do so.
Still if you want to turn this on.....
In LD 15 you need to make a change to the CDR_Data
Req: chg
Type: CDR
CDR: YES
PORT: whatever tty port will collect the data
---
LD 16 - you need to turn on CDR on each incoming and outgoing route you want to track. check your ntps to make sure you collect what you want.
---
LD 17
Add CTY to the USER prompt on the TTY you are using to collect CDR information
Be careful what you promise someone when it comes to CDR. CDR applications can be very expensive, and if you use a macro enabled spreadsheet, it can be very time consuming for you to keep up with it.
Hope all this helps.
From there you will need to wire up a TTY port so you can collect this information to a seperate application, or you can parse the information out to a spreadsheet. There are some on the NET if you look.
If you have a lot of call traffic, the capture file you collect in one day could be a 5-6 MB file. That doesn't seem like much these days, but when was the last time you tried to open a 5MB text file. It will lock up your computer.
CDR is not just punch in a few line code changes and you have what you need. It doesn't store historical data without a buffer box and you telling it to do so.
Still if you want to turn this on.....
In LD 15 you need to make a change to the CDR_Data
Req: chg
Type: CDR
CDR: YES
PORT: whatever tty port will collect the data
---
LD 16 - you need to turn on CDR on each incoming and outgoing route you want to track. check your ntps to make sure you collect what you want.
---
LD 17
Add CTY to the USER prompt on the TTY you are using to collect CDR information
Be careful what you promise someone when it comes to CDR. CDR applications can be very expensive, and if you use a macro enabled spreadsheet, it can be very time consuming for you to keep up with it.
Hope all this helps.
Assuming “Nortel24” has all the CDR Packages he need, and has a Spare I/O port to use as a CDR port, after he sets up the System, LD-15 LD-17 if he was to hook up a old PC with the data being saved to a file, and ONLY turn on the stations CLS CDMA (external station activity records allowed) and ICDA (internal CDR Allowed) the only data that would be sent to the CDR port would be the one DN’s activity, so file size would not be a issue and simple spreadsheet should be able to provide enough info.
- Status
Similar threads
- Locked
- Question
- Locked
- Question