CS1000 CDR Set-UP

[ableseaman]

Good Afternoon

We have a CS1000E with Call Servers (MGC 0-0 & MGC 0-1) split between 2 locations - both of which are on the same Campus LAN.

Our Call Logging system is connected to MGC 0-0 on port 2. We want to move our call logger to MGC 0-1. I have printed off the ADAN settings as thought it could just simply be unplugged at one end and plugged in at the other. Howver from the ADAN print off I can't see anything listed against MGC 0-1.

Does something need to be set-up on MGC 0-1 to allow CDR - if so what is required?

I have printed off the ADAN list below.

ADAN HIST
SIZE 50000
USER MTC SCH BUG OSN
ADAN TTY 0
CTYP CPSI
DNUM 0
PORT 0
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 1
CTYP MGC
IPMG 0 0
DNUM 1
PORT 1
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR NO


ADAN TTY 2
CTYP MGC
IPMG 0 0
DNUM 2
PORT 2
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER CTY


ADAN TTY 3
CTYP PTY
DNUM 3
PORT 0
DES PTY_1
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 4
CTYP PTY
DNUM 4
PORT 1
DES PTY_2
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES



PAGE 001

ADAN TTY 5
CTYP PTY
DNUM 5
PORT 2
DES PTY_3
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 6
CTYP PTY
DNUM 6
PORT 3
DES PTY_4
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 7
CTYP CPSI
DNUM 7
PORT 1
DES ONSITE
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 8
CTYP MGC
IPMG 4 0
DNUM 8
PORT 1
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR NO
ADAN TTY 9
CTYP MGC
IPMG 8 0
DNUM 9
PORT 1
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR NO
ADAN TTY 10
CTYP XSM



PAGE 002

IPMG 16 1
DNUM 10
DES xsm
ADAN ELAN 16
CTYP ELAN
DES
N1 512
ADAN ELAN 17
CTYP ELAN
DES
N1 512
ADAN ELAN 24
CTYP ELAN
DES
N1 512
ADAN DCH 50
CTYP MSDL
MG_CARD 008 1 02
PORT 1
DES
USR PRI
DCHL 50
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA YES
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 5
RCAP ND2 NCT RVQ MSDL TAT
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DPNSS DCH 52
CTYP DCHI
MG_CARD 004 0 01
PORT 1
DES USR DPNSS
ADAN DPNSS DCH 53
CTYP DCHI
MG_CARD 008 0 02
PORT 1
DES USR DPNSS
ADAN DPNSS DCH 54
CTYP DCHI
MG_CARD 008 1 01
PORT 1
DES DASS_100_101_110
USR DPNSS
ADAN DPNSS DCH 55
CTYP DCHI



PAGE 003

MG_CARD 012 0 01
PORT 1
DES
USR DPNSS
ADAN DPNSS DCH 56
CTYP DCHI
MG_CARD 016 0 01
PORT 1
DES
USR DPNSS
ADAN DPNSS DCH 57
CTYP DCHI
MG_CARD 016 0 02
PORT 1
DES DPNSS_R125
USR DPNSS
ADAN DCH 58
CTYP MSDL
MG_CARD 012 1 01
PORT 1
DES
USR PRI
DCHL 58
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA YES
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 6
RCAP ND2 NCT RVQ MSDL TAT
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DPNSS DCH 59
CTYP DCHI
MG_CARD 012 1 02
PORT 1
DES DPNSS_R127
USR DPNSS
ADAN DCH 99
CTYP DCIP
DES V_DCH_R99
USR ISLD
ISLM 4000
SSRC 1800
OTBF 32
NASA YES
IFC SL1
CNEG 1
RLS ID 6
RCAP ND2 TAT
MBGA NO

 

[Firebird Scrambler]

Have you printed off the CDR settings in LD 21?. You might need to change the port allocated for CDR.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[ableseaman]

Cheers Firebird

CDR printed off below.

It doesn't mention anything specifically about MGCs within here just that it uses port 2. Does this mean that port 2 on both Cores MGC 0-0 & MGC 0-1 will cover CDR or does it need to be specifically setup for MGC 0-1 port 2?

TYPE CDR_DATA
CUST 00
CDR YES
IMPH NO
OMPH NO
AXID YES
TRCR YES
CDPR YES
ECDR YES
BDI NO
OTCR YES
PORT 2
CNI DGTS
BCAP NO
CHLN 4
FCAF YES
CHMN 0
FCNC 0

 

[minicompbx]

Might be a dummy answer but just make sure that tty are enable and configure to use CDR
Go to load 37 ld 37
Make stat tty
To enable a tty: tty enl x
To disable a tty: tty dis x

where x is tty port.

 

[ableseaman]

Minicompbx

Print out of TTY shows;

TTY 0 : ENBL
TTY 1 : DSBL ( MGC 0 0 )
TTY 2 : DSBL ( MGC 0 0 )
TTY 3 : DSBL DES: PTY_1
TTY 4 : DSBL DES: PTY_2
TTY 5 : DSBL DES: PTY_3
TTY 6 : ENBL DES: PTY_4
TTY 7 : ENBL DES: ONSITE
TTY 8 : ENBL ( MGC 4 0 )
TTY 9 : ENBL ( MGC 8 0 )
TTY 10 : ENBL ( XSM 16 1 ) DES: xsm

If I try to enable TTY 2 (enl tty 2) I get the OK prompt but the TTY stays disabled.........

Nothing should have changed on the CS1000. The reason for moving the call logger was due to UPS issues serving the call logger system. I have checked the call logger and there doesn't appear to be any raw call data being provided by teh CS1000.

 

[Firebird Scrambler]

As the TTY 2 is configured on your MGC 0 0 card and it's showing as disabled, then you might have to reboot the MGC 0 0.
The reason for my query is that TTY 1 is also showing disabled!.

Print out of TTY shows;

TTY 0 : ENBL
TTY 1 : DSBL ( MGC 0 0 )
TTY 2 : DSBL ( MGC 0 0 )

I've found a report below that shows problems at 7.5. Patch mplr31426 for rls 7.50 was issued to fix it. I'd give the MGC a reset first!.

MGC TTYs using low baud rates can cause multiple TTYs to disable during long printouts.

Various scenarios are possible but, the scenario described below easily demonstrates the problem using the simultaneous output of Traffic reports and ACD (ACDC) reports.


SETUP
=====
VoIP enabled solution using TTYs deployed across various MGCs.
Call Server uses ACDC with many (30+) ACD and CDN queues.
ACD reports (ACDC) are output to the ACD printer.
Lots of traffic reports are enabled and output.

ADAN TTY 1
CTYP MGC
IPMG 160 1
DNUM 1
PORT 1
DES Port_1
BPS 1200 <- low baud rate
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG <- Is used for TRF
TTYLOG 0
BANR YES

ADAN TTY 5
CTYP CPSI
DNUM 5
PORT 0
DES cpsi_0
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN <- not used for TRF
TTYLOG 0
BANR YES

ADAN TTY 6
CTYP CPSI
DNUM 6
PORT 1
DES cpsi_1
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG OSN <- Is used for TRF
TTYLOG 0
BANR YES

ADAN TTY 10
CTYP MGC
IPMG 160 0
DNUM 10
PORT 0
DES Port_0
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG <- Is used for TRF
TTYLOG 0
BANR NO

ADAN TTY 11
CTYP MGC
IPMG 160 0
DNUM 11
PORT 1
DES Port_1
BPS 1200 <- low baud rate
BITL 8
STOP 1
PARY NONE
FLOW NO
USER ACD <- ACDC report printer
CUST 00
SSUP NO
APRT YES

ADAN TTY 12
CTYP MGC
IPMG 160 0
DNUM 12
PORT 2
DES Port_2
BPS 19200
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH <- Is used for TRF
TTYLOG 0
BANR NO

All traffic reports are activated
----------------------------------
.tshs 01 01 31 12
00 23 1
1 2 3 4 5 6 7
.tops 1 2 3 4 5 6 7 8 9 10 11 12 13 14
.tshc 0 01 01 31 12
00 23 1
1 2 3 4 5 6 7
.topc 0 1 2 3 4 5 6 7 8 9

ACDC reports are setup
----------------------
TYPE SCB
CUST 0
CPRD 01 01 12 31
SHR 0
EHR 10
DOW 1 2 3 4 5 6 7
RFRQ 1
SFRQ 1
ROPT 1 2 3 4
PRIO 11
PAGE NO
AID YES
IDLB 0001
IDUB 9999
LOG 40
SRPT YES
TOT4 YES

EXPECTED RESPONSE
=================
Remote MGC TTYs should not be disabled unless there is a genuine device or IP infrastructure response problem.


ACTUAL RESPONSE
===============
All remote IP TTY devices that output at low baud rate will become disabled.
Also, any high baud rate remote IP device that outputs the same information as the low baud rate device(s) will become disabled.

.stat

TTY 0 : ENBL ( MGC 160 1 ) DES: FW_Modem <- Not for TRF or ACD
TTY 1 : ENBL ( MGC 160 1 ) DES: Port_1
TTY 2 : ENBL ( MGC 160 1 ) DES: Test <- Not for TRF or ACD
TTY 4 : DSBL DES: PTY
TTY 5 : ENBL DES: cpsi_0 <- Not for TRF or ACD
TTY 6 : ENBL DES: cpsi_1
TTY 8 : DSBL DES: PTY
TTY 9 : ENBL DES: PTY
TTY 10 : ENBL ( MGC 160 0 ) DES: Port_0
TTY 11 : ENBL ( MGC 160 0 ) DES: Port_1
TTY 12 : ENBL ( MGC 160 0 ) DES: Port_2
TTY 13 : DSBL DES: PTY
.
IOD040 10

IOD040 01
stat

TTY 0 : ENBL ( MGC 160 1 ) DES: FW_Modem
TTY 1 : ENBL ( MGC 160 1 ) DES: samwin_bkp
TTY 2 : ENBL ( MGC 160 1 ) DES: Test
TTY 4 : DSBL DES: PTY
TTY 5 : ENBL DES: cpsi_0
TTY 6 : ENBL DES: cpsi_1
TTY 8 : DSBL DES: Pty_Samwin
TTY 9 : ENBL DES: pty_samwin
TTY 10 : DSBL ( MGC 160 0 ) DES: Port_0
TTY 11 : DSBL ( MGC 160 0 ) DES: Port_1
TTY 12 : DSBL ( MGC 160 0 ) DES: Port_2
TTY 13 : DSBL DES: samwin
.


If the TTYs had, in fact, been disabled due to lack of response (IOD040) then associated TTY007 should be recorded in the RPT log.
pdt> rdtail 10
[307] 19/09/2011 10:01:13 TTY0007 (cont'd)
[306] 19/09/2011 10:01:13 TTY0007 SDI tty with dev num 1, fd 45 timeout twice
[305] 19/09/2011 10:00:56 TTY0007 (cont'd)
[304] 19/09/2011 10:00:56 TTY0007 SDI tty with dev num 10, fd 49 timeout twice
[303] 19/09/2011 10:00:51 TTY0007 (cont'd)
[302] 19/09/2011 10:00:51 TTY0007 SDI tty with dev num 12, fd 51 timeout twice
[301] 19/09/2011 10:00:45 TTY0007 (cont'd)
[300] 19/09/2011 10:00:45 TTY0007 (cont'd)
[299] 19/09/2011 10:00:45 TTY0007 SDI tty with dev num 11, fd 50 timeout twice
[298] Restricted Access!


IOD0040 n
TTY or printer n is not emptying the output buffer. Output circuitry on
pack is faulty. The device is disabled. Probable fault is on pack in
question. This information is also displayed on the maintenance
display. If fault persists after pack is replaced, suspect:

1. Miscellaneous pack on active CPU

2. Other serial data interface




KEYWORDS
--------
TTY MGC IOD0040 IOD040 DISABLE DISABLED











All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[minicompbx]

This link might help you :

http://pbxbook.com/meridian/cdr.html

 

[ableseaman]

Thanks both

I have reported to our maintainer..........