Hi,
I was wondering if anyone had information on interpreting CDR records from a Meridian Option 11 (rel 24.25)
Basically, we currently have output spew across the terminal (via tty 2) - which is okay (although a little annoying!). I would prefer to collate this information to a file somewhere - is this possible? This would allow me to capture some details (even a snapshot) and write a script to gather it into readable format.
Screen ouput currently looks similar to:
N 029 00 8124 A110027 06/06 11:47:18 00:03:04.0 A9161007717478715
N 030 00 A110003 ATTN01 06/06 11:43:52 00:08:22.0
&
I would like to be able to interpret this to show the the trunk used to make/recieve the call? Most of the other info is fairly self explanatory - however, I'm not conviced the output matches what I have set-up in CDR_DATA :
>ld 21
PT1000
REQ: prt
TYPE: cdr
TYPE CDR_DATA
CUST 0
TYPE CDR_DATA
CUST 00
CDR YES
IMPH NO
OMPH NO
AXID YES
TRCR YES
CDPR YES
ECDR YES
BDI YES
OTCR YES
PORT 2
CNI DGTS
BCAP YES
CHLN 4
FCAF NO
Does this seem to reflect the output above ????
There are two routes we use - one which has CDR=yes in LD16, however, the other will not accept this change and remains the default CDR=no. Is there a way of forcing this to accept CDR=yes ? Some details on the RDB are below:
REQ: prt
TYPE: rdb
CUST 0
ROUT 109
TYPE RDB
CUST 00
DMOD
ROUT 109
DES EURO2
<----snip---->
DDO NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
<----snip---->
Also, CDR port seems to be set-up fine, but do I need to enable/disable, etc to accept changes? (if I want the messages to stop scrolling off screen, etc)
REQ prt
TYPE adan tty 2
ADAN TTY 2
TTY_TYPE SDI
CAB 00
CARD 00
PORT 2
DES Call_Detail_Rec
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER CTY
Any info greatly appreciated, thanks a lot for your time
Regards,
Paul
I was wondering if anyone had information on interpreting CDR records from a Meridian Option 11 (rel 24.25)
Basically, we currently have output spew across the terminal (via tty 2) - which is okay (although a little annoying!). I would prefer to collate this information to a file somewhere - is this possible? This would allow me to capture some details (even a snapshot) and write a script to gather it into readable format.
Screen ouput currently looks similar to:
N 029 00 8124 A110027 06/06 11:47:18 00:03:04.0 A9161007717478715
N 030 00 A110003 ATTN01 06/06 11:43:52 00:08:22.0
&
I would like to be able to interpret this to show the the trunk used to make/recieve the call? Most of the other info is fairly self explanatory - however, I'm not conviced the output matches what I have set-up in CDR_DATA :
>ld 21
PT1000
REQ: prt
TYPE: cdr
TYPE CDR_DATA
CUST 0
TYPE CDR_DATA
CUST 00
CDR YES
IMPH NO
OMPH NO
AXID YES
TRCR YES
CDPR YES
ECDR YES
BDI YES
OTCR YES
PORT 2
CNI DGTS
BCAP YES
CHLN 4
FCAF NO
Does this seem to reflect the output above ????
There are two routes we use - one which has CDR=yes in LD16, however, the other will not accept this change and remains the default CDR=no. Is there a way of forcing this to accept CDR=yes ? Some details on the RDB are below:
REQ: prt
TYPE: rdb
CUST 0
ROUT 109
TYPE RDB
CUST 00
DMOD
ROUT 109
DES EURO2
<----snip---->
DDO NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
<----snip---->
Also, CDR port seems to be set-up fine, but do I need to enable/disable, etc to accept changes? (if I want the messages to stop scrolling off screen, etc)
REQ prt
TYPE adan tty 2
ADAN TTY 2
TTY_TYPE SDI
CAB 00
CARD 00
PORT 2
DES Call_Detail_Rec
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER CTY
Any info greatly appreciated, thanks a lot for your time
Regards,
Paul
