Opt 81C ISDN-BRI internal, Polycom video conf 2

[NortelGuy1979]

I posted this to the comp.dcom.sys.nortel; thought I'd cross-post here too. Any help would be appreciated!
========
Hi All,
I have scoured these groups for info on BRI setup in the M1 for Polycom video conferencing, to no avail. I have the basics down; but I don't know the details of the programming.

We have an 81C w/ Succession R3 software; two MISP's, and 5 UILC's. I am having trouble getting a Polycom to work; I know it is good because it works on the BRI's from SBC. However, on the 81C, the Polycom will not detect SPIDS; and won't make calls if I enter the info manually, etc.

Here's my setup (one port...) Can someone tell me what I'm doing wrong? The rest of my ports are like this too.
============================================
(MISP)
LOOP 104
APPL BRIL
DPSD NO
CARD1 108 0 5
CARD2 108 0 6
CARD3 108 0 7
CARD4

(UILC)
TN 108 0 5
MISP 104
CTYP UILC

(LAPD)
PGPN 0
LAPD
T200 2
T203 20
N200 3
N201 260
K 1
N2X4 10
#DSL 40
#ROUTES 0

(DSL)
TN 108 0 5 0
DES HH
CUST 0
CTYP UILC
OPT BRIL
MISP 104
B1CT VCE DTA
B2CT VCE DTA
LDN NO
XLST 0
MTEI 8
MCAL 16
MTSP 8
LAPD 0
PRID 6
PDCA 1
FDN
EFD
HUNT
EHT
TGAR 1
NCOS 7
SCPW
SGRP 0
CLS CTD ICDD CDMD MRD ABDD PGND BRTD
DATE 8 NOV 2004

(TSP)
TYPE TSP
DSL 108 0 5 0
OPT

USID 1
MPHC NO
SPID 81640447850101

DN 44785 0
CT VCE DTA
MCAL 4
CLIP YES
PRES YES
COLP NO
TRANS NO
FEAT HTD FND SFD CFTD MWD FBD CFXD DNO3 DNDY
SSRV_NI

DFDN 44785


USID 2
MPHC NO
SPID 81640447860101

DN 44786 0
CT VCE DTA
MCAL 4
CLIP YES
PRES YES
COLP NO
TRANS NO
FEAT HTD FND SFD CFTD MWD FBD CFXD DNO3 DNDY
SSRV_NI

DFDN 44786
============================================
I've also tried, on the TSP, only having USID 1 and putting two DN's and two SPID's on that one USID. Doesn't work either. I've also tried changing protocals from NI-1 to DMS, and that doesn't work. My vendor is clueless; and Polycom says it's not their problem since the unit works on the PSTN.

Any help is MUCH appreciated! My hospital is trying to save money on ISDN from SBC; and utilize our existing trunking.

Thanks,
Matt

 

[cmawbey]

I havent set one of these up in a long time but i found my old notes. they may help...

UK setup. UILC's are not supported in the UK.

You need software packages 203 216 235

You need a MISP and at least 1 SILC at each end

SILC has 8 4-wire ports numbered 0-7
Sockets used are RJ45 type
Even port connected to pins 5 and 4
Odd port connected to pins 3 and 6
Ports are polarity aware

SETUP FOR BRI EXTENSIONS:

All programming done in LD 27. Configuration has four parts.

Part 1 LAPD (Link Access Protocol Datablock)

REQ new
TYPE lapd
PGPN x (try 0)

LAPD yes
T200 2
T203 20
N200 3
N201 260
K 1
N2X4 10

PGPN <cr>

Part 2 MISP installation

For Option 11 MISP needs to be in slots 1-3 of main cab
For big switch MISP goes in a free slot of a network shelf. The card uses the EVEN loop of that slot. The odd
loop can not be used for any purpose.

REQ new

TYPE misp

LOOP x
(card number if Option 11 or the even loop from the slot in the network shelf of a big switch)

APPL bril (BRI line)
<cr> .....

MISP is brought up in LD 32:
ENLC x FDL for OP11
ENLL x FDL for big switch
(FDL is needed the first time to download the application 'bril')



Part 3 DSL (Digital Subscriber Loop)
This is configured 1 per BRI extension.

REQ new
TYPE dsl
TN c u or l s c u
DES BRI
CUST 0
CTYP SILC (UILC not used in the UK)
OPT BRIL
MISP x (Loop set up in part 2)
MODE NTAS



LAPD 0 (as set up in part 1)

PRID y (protocol ID)
This is dependant on terminal equipment but 'y' can be:
1=ANSI
2=ETSI (used here)
3=DMS
4=NET64
5=NUMERIS
6=NI-1

TGAR 0

CLS unr

<cr>

Part 4 TSP (Terminal Service Profile)
This is configured 1 per BRI extn.

REQ new

TYPE tsp

DSL c u or l s c u (of the DSL set up in part 3)

USID 0 (used here) or
SPID aaaa..aa (Service profile ID, I think used in US)


DN xxxx

CT vce dta

DFDN xxxx (as above)


You should now have a working BRI line.




Colin



Colin

 

[NortelGuy1979]

Thanks Colin for your help. Your setup tips and a few calls to ATAC helped. Also turns out the Polycom was detecting the protocol type wrong or something, too.
Thanks again,
Matt