Nortel Meridian 1 format looks different between 2 diff PBX

[ibeintexas]

Hello all,

I am troubleshooting a CDR issue where the customer is telling me they cannot see the CLID for inbound call records via OTM.

I have compaired the problem site (RLS 23.18+) with another site (RLS 23.19) that is showing the CLID properly.

What I have found is that the raw CDR data looks a bit different between the 2 sites, and belive this is causing the issues.

CDR output from problem site - Inbound call to x2202 from 2066649220:

N 016 00 A000006 2202 008.0.00.15 05/26 10:04 00:00:12
& 0000 0000 2066649220XXXXXX

N 017 00 2202 A000015 008.0.00.15 05/26 10:04 00:00:12 A 89001001130
& 0000 0000 2066649220XXXXXX


CDR output from working site - Inbound call to x6406 from 2066649220:

N 064 00 DN6406 A002010 012.0.13.02 05/26 10:54 00:00:18 A 89021130
2066649220XXXXXX

Notice that the CDR format output from problem site is inserting an & 0000 0000 before the inbound CLID. I cannot figure out why this is. The CDR_DATA is setup exactly the same, as well as the RDB and the PARM for both PBX. This is driving me crazy!!

Setup for both PBX are as follows:

TYPE CDR_DATA
CUST 00
CDR YES
IMPH NO
OMPH NO
AXID YES
TRCR YES
CDPR YES
ECDR NO

RDB:

CDR YES
INC YES
LAST NO
QREC NO


PAGE 002

OAL YES
AIA YES
OAN YES
OPD NO
NATL YES
MUS NO

PARM:

FCDR OLD
PCDR NO
TPO NO
TSO NO
CLID YES

Any insight as to what the differences could be would be greatly appreciated!!

Thanks

Rocky

 

[trvlr1]

Are you definitely getting the information from the Telco?

 

[ibeintexas]

How would I know this for sure? I do see the inbound CLID on the CDR records of the site with issue, just in a different format. I believe this formatting difference to be the cause of the issue.

Thanks for you reply!!!

 

[trvlr1]

Do the users see it on their phones correctly?

 

[ibeintexas]

Just verified that customer does see my CLID properly on inbound calls to this PBX on her digital set.

 

[sporty2]

Try looking at the PARM in LD 22 about half way down FCDR old or new is most likely the issue.

sporty2