LD 15, NEW DEFAULT

 

One of the things that I didn’t want my website to become was a Nortel support portal, but I finally gave in.  I need a place to keep a bunch of handy links while working between multiple computers and frankly, this portal makes the most sense.  So, today, I started adding a bunch of links to the portal that are relevant to providing Nortel support.

 

Resetting a Nortel IP phone just became a lot easier.  Nortel has announced in their Unistim 3.0 documentation the ability to reset a Nortel IP phone to factory default settings.  The following code is required to reset to factory default:

  • **RENEW[mac]#

Where [mac] is replaced by your MAC address.  Example: If your MAC address is 00:11:22:33:44:55, then your reset code would be:

  • **73639001122334455#

For more information on what the factory default settings are, refer to the Unistim 3.0 Revision 1 product bulletin located on Nortel’s Partner Information Center webpage.

NOTE
You must have valid Nortel Partner credentials to access this bulletin.

 

For August, I plan on trying to do a Overlay review for each Nortel SL1 Overlay (used in routine maintenance).  The purpose of the review is to highlight some key information about routine maintenance.  I’d like to do at least 3 overlays a week.  I’d like to include core tasks only, perhaps I can spend a couple of weeks later this year talking about routine maintenance on some other applications.

 

If you telnet to your signaling server, you can use cslogin to access your SL1 interface for your PBX.  To return to the oam prompt of your signaling server, enter tilde period (~.) from the SL1 interface.

  • telnet <ip address>
  • login <username>
  • password <password>
  • oam> cslogin
  • OVL111
    >~.
  • oam>

 

I’ve got a whole article I’m writing on how to secure a CS1000 (although, not for public distribution), but the fact of the matter is that there are some very simple things that people can do to keep a better watch on what is done in their system.  One of the things that can be done is implementing the Audit log.

>ld 22
PT2000

REQ  prt
TYPE pwd
PWD2

PWD
.

.

.

  AUDT YES
  SIZE 50
.

.

.

 This combined with the MULTI_USER prompt in LD 17 OVLY data gives you a lot of data about users who enter your system and perform tasks;

REQ  prt
TYPE ovly

OVLY
.

.

.

  MULTI_USER ON

The audit log is located in the LD 17 PWD datablock and provides a way of tracking which user account logs in, which interface they connect with and what management overlays they use while logged in.

REQ  prt
TYPE audt
LOG TTY #00  11:08  ADMIN2 PWD2  022

You can also modify the TTYLOG prompt on LD 17 ADAN HST and LD 17 ADAN TTY to capture other kinds of information.

The MULTI_USER prompt is very important because setting all users up with individual accounts allows you to perform auditing of what each user does.  Restricting all users except the super users (your engineer level users) from accessing LD 17 will also prevent them from modifying your logging settings.  A standard Telecom Analyst has no need to access LD 17, although you might give them LD 22 to be able to print any of the configuration information from LD 17.

 

One of the things that I’m occassionally asked (but never personally implemented) is:

“How do I forward my desk number at work to some other location when I’m not ask my desk?”

Enter Kris Guntzelman (who originally gave me the answer)

The feature you are looking for is indeed Remote Call Forwarding.  The FFC
(in LD 57) is RCFA (for activate) and RCFD (for deactivate).

HOWEVER, the set you are attempting to activate/deactivate the feature on
MUST have a Station Control Password (SCPW) programmed or else the system
won’t let you do it.

What I’ve got set up here is a DISA line that has an NCOS of 0 and is TLD
(that way the DISA can’t be exploited).  Once you dial in and you enter your
DISA password, you enter the FFC for RCFA, then the SCPW of the station you
wish to program, then the PRIME DN of that same phone.  You should now get
hit with stutter dialtone.  If you hit # now, the phone will be forwarded to
its last destination, otherwise enter the number (9 first if necessary) then
# when finished.

RCF follows all the same rules as regular CFW.  If your phone doesn’t have a
high enough NCOS to make the call w/o an acct code, it won’t work.

Of course, this is a toll fraud risk if not properly monitored and policed.  DISA as a whole is dangerous.  DISA (in this case) stands for Direct Inward System Access and is a means of providing remote users the ability to call in to your phone system and receive dial tone, which permits them to call another number (or an internal number) freely as if they were on your system.  The security you set on your DISA feature (TLD and NCOS 0 suggested above) determines what off-net dialing capabilities the DISA user will have.

Some companies provide a toll free number and a DISA access code to their remote/traveling users to permit them to use the company’s phone system to make long distance calls rather than acquiring calling cards or paying for cellphone roaming charges.  This was much more common in the last decade (or decade before that) when long distance costs were higher on cell or calling cards than it was to purchase a toll free number and pay for both the toll free and long distance charges from a central location.

Still, a worthwhile memorandum for the archives.

 

Got to love the “business made simple” marketing strategy of Nortel, but what lurks behind that marketing strategy?  Decades of excellent architecture with one of the most consistant (some might say archaic) command line interfaces known to man.

With the recent (as in last few years) renaming of the traditional “Meridian-1 Option” line of enterprise phone systems to Communication Server 1000, there comes a few new, confusing names to the Nortel playground.  Half group, Single group, Multi group, Cabinet, Chassis.

Making sense of this is what I do, so I whipped up this handy cheat sheet on all of the versions I know of or could find in the documentation, and a quick tutorial on how to identify system hardware with a few quick commands in the CLI.

 Voila! My Nortel CS1000 Hardware Version bulletin.

  •   Meridian-1 / CS1000 Hardware Version Lookup Table [DRN08061701] (33.7 KiB, 586 hits)
    You need to be a registered user to download this file.

 

The password reset procedure on a CS1000 4.0 system indicates that you are required to provide the original install floppy disk. Attempting the password reset procedure without the original diskette will result in the system prompting you for the current PDT2 password. If you don’t have it, you’ll be forced to reload the software on all CPUs.

 

In the Nortel CS1000, the ability to short hunt is tied to the last hunt key (LHK) which is only prompted if the class of service is hunting allowed (CLS HTA).  However, if you want it to short hunt to other keys on the same phone but not off phone, you must put 000 in the HUNT prompt.

I have to make a note of this because I have forgotten this more times than I care to admit over the last few years.  This way, I’ll have a record to look back on.

Keywords: Nortel, CS1000, LHK, CLS HTA, HUNT 000, Short Hunt

Favorite Books

Favorite Music

© 2011 Undecided Suffusion theme by Sayontan Sinha