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!

cdr raw data

Status
Not open for further replies.

pbxNewb

MIS
Jan 9, 2008
179
US
Hi,

I'm trying to make sense of some CDR data being polled from my switch into a CDR software package. It is no longer capturing long distance calls made from one of my remote sites across a TIE line. Actually, the raw CDR data shows it captures the calls, but the CDR software is no longer processing them. This all started when they moved from analogue trunks over to a PRI but i'm not sure that would change anything. Anyways, can someone tell me how to interpret this info from the log:

N 055 00 T008010 A001023 04/30 08:33:16 00:00:02.0 A16398111541xxxxxxx <-- ACOD of my LD route + number to be called

&5418817000XXXXXX <--originating site caller 000 000
& 000 01 2



Now before the PRI they did not have caller ID info being outpulsed from the switch. The "originating site" info above was the actual on-net number the call originated from, rather than the main outpulsed number of the facility. Trying to piece this back to gether so i can begin billing them for usage again. Any and all help is appreciated,thanks!

CS1000, RLS4.5
 
I'd talk to the company that made the CDR application, telling them that now you have Caller ID in CDR.

They will tweak it and your issue will be resolved.

[&copy;] GHTROUT.com [&hArr;] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
I'd love to, but since we do not have an ongoing maintenance contract with them, they charge $150/hr with a 2 hour minimum. I was hoping to save this cost by adjusting the software myself. I think I can fix it if I just know how the raw data relates to actual call information.
 
Somewhere in the programming you should have something that relates the trunks to a particular type of call. As your LD has now changed to a new route, you need to make sure it is included. If you can find your old route and put the new trunk(s) in there it may fix your issue.
 
Maybe if you post the name of your CDR package, someone else who has it knows the fix.

[&copy;] GHTROUT.com [&hArr;] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
Is your ACOD the same with the new trunks? If not, that would be the place to start. Did you replace the analog trunks 1 for 1. Most progrrams want to see the channel/trunk members. Since they're outbound, they are starting at the the bottom of the RDB. If you added members in the route, they should be reflected in the CDR program
 
the ACOD is the same, the TIE between our facilities has not changed, just the PRI on the remote site end. They dial 9+1 and it sends it over the TIE to my site and then out my dedicated LD T1. They can make the calls, but when I look at the raw data I see their main outpulsed number as the originating number now that they have the PRI instead of the individual extensions that I saw before when it was working. I've added this main outpulsed DID to my CDR software but it still sees no long distance calls from it.
 
i have small call account DOS version if you want it tell me

Samo
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top