Linking an Option 11 to a BCM
Procedure to link an Option 11 to a BCM with transparent co-ordinated dialing (CDP) and centralised voice mail, using the proprietary SL-1 protocol (the BCM requires a keycode to enable SL-1), over a private PRI circuit (E1).
The following are technician notes, and may prove useful to techs attempting a similar installation. There is some good information here, covering a number of concepts on both systems, but it is not intended as a step-by-step installation guide.
Meridian Programming
Add PRI2 Loop (LD 17)
In this case loops 01 and 03 are PRI2's. Clocking must be addressed, but an Option 11 only has one clock source (per cabinet).
CEQU
MPED 8D
SUPL 000 004 008 012
016 032 036 040
044 048 064 068
072
DDCS
DTCS
XCT 000
CONF 029 030 031 062
094 095
PRI2 01 03
APVL
DTI2
MISP
DCH - ADAN - programming (LD 17)
Here the Protocol is set to SL1 (IFC). The PBX must be NET (SIDE). Far end release (RLS) is 25. Remote capabilities (RCAP) include message waiting (MWI), and MCDN Supplementary Services, etc.
ADAN DCH 3
CTYP MSDL
CARD 03
PORT 1
DES annex
USR PRI
DCHL 3
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA NO
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 25
RCAP NCT MSDL MWI ND3
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7
Route Programming (LD 16)
The Private Network Identifier (PNI) identifies the BCM to the Option 11, and must be unique for each (PRI) route. The same number is also entered in the BCM under Private Networking. The ACOD is not too important, because we'll be using CDP for this route.
TYPE RDB
CUST 00
DMOD
ROUT 5
DES ANNEX
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC SL1
PNI 00003
NCNA YES
NCRD YES
TRO YES
CTYP CDP
INAC NO
ISAR NO
DAPC NO
DSEL 3VCE
PTYP DTT
AUTO NO
DNIS NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7333
TCPP NO
TARG
BILN NO
OABS
INST
ANTK
SIGO STD
MFC NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
NBS 2048
NBL 4096
IENB 5
TFD 0
VSS 0
VGD 6
DTD NO
SCDT NO
2 DT NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS NO
PANS YES
EQAR NO
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 7333 5
SGRP 0
AACR NO
Trunk programming (LD 14)
Build 30 of these (if E1 fully provisioned). Note the CLS options:
DES ISDN_TRUNKS
TN 001 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI2
PDCA 1
PCML A
NCOS 0
RTMB 6 1
B-CHANNEL SIGNALING
ATDN 5100
AST NO
IAPG 0
CLS UNR DTN CND WTA LPR APN THFD BARD CLID
P10 VNL
TKID
DATE 2 OCT 2003
CDP programming (LD 87)
We need to use CDP to 'steer' calls to the BCM over the relavant Route. In this case, 24XX steers to RLI 10, which points to Route 5 (in the next step).
PRT CUST 0 FEAT CDP TYPE DSC DSC 24 FLEN 4 DSP DN RRPA NO RLI 10 NPA NXX
RLI programming (LD 86)
Associate RLI 10 with Route 5, in this case.
RLI 10
ENTR 0
LTER NO
ROUT 5
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
Facility Restriction (LD 87)
This would normally already exist.
NCOS 0 EQA NO FRL 0 RWTA NO NSC NO OHQ NO CBQ NO SPRI 0 MPRI 0 PROM 0
That about takes care of the Meridian end!
We have created a PRI loop, built some trunks for it, and have said that all calls to DN
24XX will go over this route.
BCM programming:
You are programming "PRIVATE NETWORKING", over a PRI, using the proprietary SL-1 protocol.
DTM switch settings (E1 PRI):
Bus 6: on on on off on on : Lines 91-120
-or-
Bus 7: on on on off on off : Lines 61-90
If BCM configured with a 3/5 DS30 channel split, DS30 channel 7 is not available.
The Digital Trunk Module (DTM) must be present and enabled in order to continue.
DN Settings:
The BCM must be configured with 4 digit DN's, with a range that 'fits into' (co-ordinates with) the main dialing plan. You may need to run a 'wizzard' to change set DN's, and this can take a long time! After which the BCM must be restarted. You may even find conflicts, even at this early stage, with other BCM access codes. Make sure the DN's are correct before you continue with programming.
Services → Telephony Services → General settings → DN lengths → DN
length: 4
Services → Telephony Services → General settings → DN lengths → Received #
length: 4
PRI programming:
Resources → Media Bay Modules →
Bus → Modules on bus → Module 1 → Module Type: PRI
Bus → Modules on bus → Module 1 → Protocol: SL1 (requires keycode)
Bus → Modules on bus → Module 1 → User (slave)
Bus → Modules on bus → Module 1 → Clock Source: Primary
Bus → Modules on bus → Module 1 → E1 Parameters → CRC4: OFF
Resources → Media Bay Modules →
Bus → Provision Lines: provision as required (all 30)
Line programming:
Services → Lines → All Physical Lines →
Line 061 → Line type: Pool PRI-A
:
continue for number of trunks (start at line 91 if DTM on bus 6)
Access Codes:
Access codes are used for features and Line Pool access. Make sure you don't have any forseeable conflicts here. Delete the Line Pool access codes, as we're going to use Destination Codes:
Services → Telephony Services → General Settings → Access codes → Line Pool Codes
We don't want any carrier codes to interfere with our dialing plan - so, delete these too:
Services → Telephony Services → General Settings → Access codes → Carrier Codes
Routing:
Destination codes are how you route all "off switch" calls.
Services → Telephony Services → Call Routing →
Routes: Click ROUTE 001, select PRI-A as the line pool
Services → Telephony Services → Call Routing → Destination Codes:
Add required destination codes, most will reference ROUTE 001 (unless digits need to be inserted).
The BCM only allows one wildcard in an entry (denoted by A for 'any').
If the Option 11 has DN's in the 22XX range, you will need to build 220A, 221A, 222A, etc.
You'll also need destination codes for '9' (outward), '8' (IVG), '0' (operator), '5555' (voice mail), and possibly more. Pay attention to absorbed digits under 'Schedule'.
Some destination codes will require extra digits inserted, which is done in Route programming. In each case, a new ROUTE must be built to insert digits via 'External #'.
Some problems will crop up, for example: dial zero. The BCM will not allow '0' to call the operator, it will wait for 3 more digits. If none are forth coming, the caller will hear re-order. Solve this by creating a new route, using the PRI-A line pool. Insert '0#' (# signifies end of dialing). Edit the '0' destination code to delete '0'.
Refer to ISDN (PRI) Cause Codes for Call Clearing Cause codes, for an indication if problems occur.
Target Lines:
Target Lines associate the received number with the telephone extension.
Target lines run from Line 241 thru 492.
Services → Telephony Services → Lines →
Target Lines → Trunk Line Data → Recieved Number: for each target line, enter the
received digits.
Every incoming DID number will require a Target Line
DN line access:
Services → System DNs → Active set DNs
FOR EACH DN:
Line Access → Line pool access → Click ADD: add pool PRI-A
Add Target Lines to DN's:
Having defined the Target Lines, they must be added to each extension. An extension can have more than one Target Line associated to it.
Services → System DNs → Active set DNs
FOR EACH DN:
Line access → Line assignment → ADD
Appearance type: Appr&Ring (always choose Appr&Ring for target lines)
Caller ID set: YES (display incoming caller ID information)
Vmsg set: YES (display message waiting from an external voicemail system).
CDP-specific programming:
Private Dialing Plan → Private Access Code <unique code>
Type: CDP
Private DN length: <system DN length> (4)
BCM Network Services:
Trunk Route Optimization:
Network services → MCDN → TRO: YES
Trunk Anti-tromboning:
Network services → TAT →: YES
Centralised VoiceMail:
The BCM will use the Option 11's voice mail, and requires no voice mail setup itself
(no keycode!).
Below, 5555 is the voice mail DN. You will have to program forwarding for each BCM DN, for
example:
DN-Record → Capabilities → Call Forward
Fwd no answer to: 5555
Fwd no answer delay: 4
Fwd on busy to: 5555
Allow redirect must be set to Y (Yes) under set Capabilities.
Thanks to "Trunk Route Optimization", a call from the Option 11 to the BCM, forwarded back to voice mail in the Option 11, will not use any PRI channels. This is a MCDN network feature! Clever!
Remember to build mailbox's for the BCM user DN's that require voice mail, otherwise the caller will hear "user does not subscribe to this service".