Accessing CMM from CM Shell

Accessing CMM from CM Shell

In this Blog Post Accessing CMM from the CM Shell, I will walk you through how to access the Embedded Communications Manager Messaging A.K.A IA770.

Through out my experience working with Avaya Aura,  I normally get to work in maintaining other components such as patching Dom-0, U-Dom/C-Dom, CM, SAL, and the Utility Servers, not so much voicemail. why? you may ask…

CMM runs the old Audix unix in the background making it rock solid, when once configured correctly rarely crashes or goes down. For these reasons we don’t get to work in the CLI portion as much, only the CMM Web Interface is normally use to maintain Users and Automated Attendants.

I will go over these few steps=

  • Which program or interface to use?
  • Emulation Type
  • How to get into the Communications Manager Messaging or CMM CLI

Which Program or Interface to use?

By now you should feel comfortable using the various ways to connect, when maintaining or implementing CM (Communications Manager). If using a Microsoft Windows Environment Laptop you most likely are using PuTTy (http://www.putty.org); and if using Linux or Mac OS you might use the terminal Console.

Once connected to you system log into CM, then run the command go shell. By typing this command it will put back out of CM where you can manually change the Emulation Type.

Emulation Type

When connecting to CMM (Communication Manager Messaging)/Audix it uses Emulation Type 4410 which will allows the familiar Fs keys that you are well accustom to

For example if you press

  • F1= Aborts the changes made
  • F3= Enters or Saves the changes made
  • F6= Help
  • F7= Next Page
  • F8= Previous Page

Note: If you are using PuTTy, you have to tweak your Keyboard Setting=

  • VT100
  • Control-H

This will allow PuTTy to send the desirable commands back to the Voicemail or CMM Server.

How to get into the Communications Manager Messaging or CMM CLI

Once you type go shell from the CM’s CLI, this will send back out to CM’s Shell, where you can now type the following command to change your default Terminal Emulation Type which is VT100.

First Verify your current Emulation Type by typing the following=

echo $TERM (This command should reply with= VT100)

then type=

export TERM=4410 (This command will change your VT100 to 4410) if you want to verify if your changes were made run the command= echo $TERM (it should reply with= 4410)

Now rung this command=

/VM/bin/Fc

By running the above command it will automatically launch Communications Manager Messaging / Audix’s Command Line Interface – CLI.

That’s it folks. from this terminal you can set your Communication’s Manager Messaging Station Range, Automated Attendants, Enhanced Zero Out Transfer, COS, Incoming Call Routing Tables, and much more…

I hope that this information was valuable to you, please leave a comment below in the comment section with ideas, or better ways to access CMM or Intuity Audix

Please note: I reserve the right to delete comments that are offensive or off-topic.