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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CS 1000E CDR ISSUES 1

Status
Not open for further replies.

nasa123

Technical User
Mar 5, 2009
30
0
0
NG
Dear forum,

i cant get cdr to output from a cs1000e system, below is what i have done. can someone please tell me what i have left undone or why i cant get it to work.

Any help on this will be appreciated.




>ld 22

PT2000

REQ prt

TYPE adan tty 9


ADAN TTY 9
CTYP MGC
IPMG 0 0
DNUM 9
PORT 1
DES CDR
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC CTY
XSM NO
TTYLOG 0
BANR YES



REQ prt

TYPE parm


PARM
LPIB 3500
HPIB 3500
500B 2000
SL1B 255
DTIB 35
DTOB 4
NCR 50000
MGCR 25
CSQI 255
CSQO 255
TUBO NO
NCPU 1
CFWS YES
PCML A
ALRM YES
ERRM ERR BUG AUD
DTRB 100
ABCD NO
TMRK 128
FCDR NEW
PCDR YES
TPO NO
TSO NO
CLID YES
DUR5 NO
MLDN NO
MARP YES
IPIE YES
FRPT NEFR
DCUS 5
DTDT NO
MSCL 100
PMSI
MANU PMS1
PMCR 0
PORT NONE
NDIS 20
OCAC NO
MTRO MR
SBA_ADM_INS 000
SBA_USER 512
BCAP SPEECH
IDLE_SET_DISPLAY NORTEL
ICON NO
MSEC ON
MSSD MSNV
NKEY 31
TKEY 24







>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 1
CNI DGTS
BCAP NO
CHLN 1
FCAF NO

REQ: end





>ld 21

PT1000

REQ: prt

TYPE: rdb

CUST 0

ROUT 10


TYPE RDB
CUST 00
ROUT 10
DES PSTN_L_11
TKTP DID
NPID_TBL_NUM 0
SAT NO
IDEF NET
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC EURO
CNTY ETSI
SBN NO
PNI 00000
NCNA NO
NCRD NO
ISAR NO
CPFXS YES
SDID NO
DAPC NO
INTC NO
MBXR NO
DSEL VOD
PTYP DCO
AUTO NO
DNIS YES
NDGT 4
DDLY NO
DCDR YES
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
STEP
ACOD 76
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 2
NDNO 2 *
DNAM YES
MFC NO
ICIS YES
OGIS YES
TIMR ICF 256
OGF 512
EOD 7936
LCT 256
NRD 10112
DDL 70
ODT 4096
RGV 128
FLH 510


PAGE 002

GTO 896
GTI 0
SFB 3
NBS 2048
NBL 4096
DTD NO
SCDT NO
2 DT NO
DDO NO
DRNG NO
CDR YES
INC NO
LAST YES
QREC YES
OAL YES
AIA YES
OAN YES
OPD YES
NDP EXC 0
CDRX YES
NATL YES
SSL
CFWR NO
IDOP NO
MUS YES
MRT 21
MR NO
PANS YES
EQAR NO
FRL 0 0
FRL 1 1
FRL 2 2
FRL 3 3
FRL 4 4
FRL 5 5
FRL 6 6
FRL 7 7
TTBL 0
ATAN NO
PLEV 2
OPR NO
PRDL YES
EOS NO
DNSZ 0
RCAL NO
MCTS NO
ALRM NO
BTT 30
ACKW NO
ART 0
PECL NO
DCTI 0
TIDY 1010 10
SGRP 0
ARDN NO
AACR NO





>ld 20


PT0000
REQ: prt

TYPE: tnb

TN 11 1

DATE

PAGE

DES


DES PSTN_L_11
TN 011 01 VIRTUAL
TYPE DID
CDEN SD
CUST 0
TRK PRI2
PDCA 1
PCML A
NCOS 7
RTMB 10 1
B-CHANNEL SIGNALING
NITE
AST NO
IAPG 0
CLS UNR DTN CND ECD WTA LPR APN THFD SPCD
P10 VNL
TKID
DTCR NO
AACR NO
DATE 24 DEC 2008
 
thanks for ur very fast response

That was the first config i did and it didnt work
 
In that case, have you tested the port without having CTY programmed just to make sure the port is good? In either case the port number has to match the TTY number.
 
i get a connection to the pabx thru the same port but i can't seems to work much with it because it outputs some jargons (like u will get if the baud rate doesnt match)
 
any change to the CDR info in the PARM section of the configuration record require a system ini to activate.

If you are getting garbage output from your CDR TTY port, then you need to adjust your terminal settings. Your TTY Port is set to 9600-8-n-1. Try adding MTC to that port, and then try logging into the PBX from it.
 
make these changes

1 - ld 15 cdr_dat
say no to BDI
port should be 9

2 - ld 17 parm
say no to PCDR (prioroty to CDR could really mess you up)

3 - ld 17 adan tty 9
user xmtc sch <-- you do not want maint messages on CDR port and adding SCH allows you to see data with 8/n/1 other wise you need 7/m/1 or 7/s/1 or 7/e/1

4 - ld 16 rdb
QREC say no - unless you realy want it but can create duplicate call records


Also, no need to INI to change PCDR in parms

 
Thanks guys,

it's after-hours now, i'm gonna make these changes first thing tommorrow morning and give the house a feedback.

I really appreciate you all.
 
sorry guys for the late response, i was tied down by something more urgent.

reusser, i tried out the changes you suggested but nothing changed
 
have a Null Modem in between that MGC cable on your cdr connection?

Mato' Was'aka
 
i have just cty only and yes, i have a null modem on my connection.
 
I'd be trying to get the TTY to work for SCH to prove you can log into it and have a valid and usable TTY session. Only then should you try to change it back to CDR/CTY.

The best way to set up CDR is to get the TTY port to work as a TTY port - then you know the port at least works.

So if you never got the TTY port to work as a TTY, CDR/CTY will also never work.

[&copy;] GHTROUT.com [&hArr;] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators
 
If you're using Hyperterm to collect your CDR records, try using 9600/8/N/2 (or whatever baud rate you use) instead of 8/N/1. That program is weird but I got it to work by changing the stop bits to 2.
 
Hi all,

i changed to port 2 and surprisingly i got cdr outputs, it doesnt make any sense to me but it's working.

i appreciate all of you that have given me one hint or another, you guys are great.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top