New 3904
Copyright ©2003-2008, John Williams, DATARAVE. All Rights Reserved.
Original article located at: http://www.datarave.net/zfh/meridian-1/tutorials/cs1000-routine-administration-tasks/new-3904new-3904/
Disclaimer: The information provided herein and any software accessed or obtained by any party from this library are provided by DATARAVE.NET “AS IS”, and are without warranty of any kind, either express or implied. DATARAVE.NET or its principals shall not be liable for any damages arising out of the use of such information or software.
Overview:
The thought behind the order in which things is done comes from my time spent as a CPE Vendor field technician. The following steps are the entirety of programming the average Taurus set (e.g., 3902, 3903, 3904).
WARNING: If you are programming ACD sets, do not make any changes to any ACD sets. OUT and NEW only. The reason for this is as follows: Because ACD information is contained in a separate database than the set information, and links are created or deleted during the NEW or OUT procedure, when a CHG is made, occasionally there will be insufficient memory to complete the CHG procedure and the database information will not be properly created, deleted or changed (depending on the attempted chg). This results in information from either set and/or ACD database that is not properly linked to the other database. This is commonly called “Database corruption,” and may require billable assistance from Nortel Networks GNTS group (often called “E-TAS”).
Step 1: Cable the set, and plug it in
This may seem out of order, don’t worry, read on and you’ll soon learn why I do things this way.
When you cable the set to the PBX and plug it in, even if it is not programmed, the set should allow you to go in to Diagnostic mode (Hold RLS while plugging the set in, this works on all Aries and Taurus sets. Press RLS to exit Diagnostic mode.)
Since cabling usually takes the longest (i.e., at sites with poor cable management), I like to get this out of the way first.
Step 2: Find an unused DNB for your would be digital set.
>LD 20 REQ: PRT TYPE: LUDN CUST 0 DN 66 CUSTOMER 00 - UNUSED DNS: 660 661 662 663 664 665 6660 6661 6662 6666 6667 6668 667 668 669
Step 3: Find an unused voice TNB for your digital set in the making.
>LD 20 REQ: LUVU TYPE: 3904 TN 12 0 0 TYPE 3000 TN 012 0 0 00 8D VCE TYPE 3000 TN 012 0 0 02 8D VCE TYPE 3000 TN 012 0 0 03 8D VCE TYPE 3000 TN 012 0 0 04 8D VCE TYPE 3000 TN 012 0 0 05 8D VCE
Step 4: Program the set.
You need to know a lot of information about how you want to build your set before starting. This tutorial does not cover the the wide variety of information already available within the Nortel Technical Publications on the following prompts or programmable features. A later tutorial will cover the various classes of service commonly used.
>LD 20 REQ: NEW TYPE: 2616 TN 12 0 0 0 DES XMPL CUST 0 FDN 5555 TGAR LDN NCOS 7 RNPG SSU SGRP CLS HTA FNA IRA OLA LNA DNDA CNDA TDD MWA HUNT 5555 LHK 1 SCI LPK 1 PLEV FCAR AST IAPG MLWU_LANG DNDR KEY 0 SCR 6666 MARP CPND VMB KEY 1 SCR 7666 KEY 2 TRN KEY 3 AO6 KEY 4 CFW 4 KEY 5 MWK 5555 KEY 6 ADL 16 KEY 8 ADL 16 . . . KEY 15 ADL 16 MEM AVAIL: (U/P): 1223835 USED U P: 96880 55540 TOT: 1376255 DISK RECS AVAIL: 473 TNS AVAIL: 165 USED: 35 TOT: 200 ACD AGENTS AVAIL: 300 USED: 0 TOT: 300 AST AVAIL: 100 USED: 0 TOT: 100 DATA PORTS AVAIL: 2500 USED: 0 TOT: 2500 DIGITAL TELEPHONES AVAIL: 2497 USED: 3 TOT: 2500 INTERNET TELEPHONES AVAIL: 0 USED: 0 TOT: 0 REQ:
Step 5: Identify unit.
>LD 32 .IDU 12 0 0 0 M2616 TN 012 0 00 00 TN ID CODE: M2616 NT CODE: NT2K16GH COLOR CODE: 03 RLS CODE: 01 SER NUM: 12345AThe reason I identify the unit as the first step to testing the phone is, who wants to walk all the way to the set only to find out that it’s not wired properly? Using the identify unit command, you can remotely check for the set type and serial number if the set is wired properly.
Step 6: Test set
Visit the set and test it.
Copyright ©2003-2008, John Williams, DATARAVE. All Rights Reserved.

Follow me on Twitter