Avaya CM Concepts & Terminologies Reference

Avaya CM commands format:Action + Object + Parameters.

Action: Add / Delete / Change / List / Display / Remove / busyout / release / enable / disable / reset …

Object: Extension / System-parameter / Media-Module …

  • cabinet:  PN
  • ipserver-interface:  IPSI card
  • configuration:  practically all objects.【list configuration {all | board | carrier | circuit-pack | PN | media-gateway | trunks | station | license | power-supply | software-versions}】
  • node-names:  CLAN / Medpro / VAL / CM / PE
  • ip-interface :  CLAN / Medpro / VAL / CM / PE
  • dialplan analysis:  list of extension / route pattern
    Call Type Description
    ext extension
    attd attendant console
    ars automatic routing selection
    aar automatic alternative routing
    fac feature access code
    dac dial access code
    tac trunk access code
  • data-module:  details about a specific route pattern
  • system-parameters:  system level parameters【License file details check: display system-parameters customer-options】
  • capacity: system capacity consistent with license file

Parameter: specific object subject to this command.

Terminologies & Concepts

Call Routing Overview in CM;

Note that ARS and AAR can share the same trunk groups, route patterns and other routing information. Plus, ARS calls can be converted to AAR calls through ARS Digit Conversions, and vice versa.

Call Routing

Automatic Alternate Routing (AAR): [On-Net call Routing] AAR routes calls within your enterprise through your private network. It allows private network calls to originate or terminate at one or many locations without accessing the Public Network (PSTN).

Automatic Route Selection (ARS): [TEHO Routing] it enables CM to automatically select Carriers / SP and route the calls over Public Network in a most cost-effective (inexpensive) way. In a multi-location system, ASR can be administered in a per-location basis.

Class of Restriction (COR): Enable or Block the calls between specific internal phone station Groups & Limit or Authorize Service Observing service between specific group of phone stations. Calling Permission between stations residing in different COR groups are restricted as desired on a single-direction basis. Likewise, Service Observing (monitoring or listening the in-progress calls to ensure QoS) can also be restricted on that way. Up to 996 COR groups can be configured on Avaya CM. Facility Restriction Levels (FRL) in COR can determine whether phone stations with this COR tag can access specific outgoing trunk group or not.

Facility Restriction Levels (FRL): FRL value, ranging from 0 (low privilege) to 7 (high privilege), can be configured for COR and Outgoing Trunk Group. Those 2 values will be compared, when a phone station places a ASR call, to determine whether this phone station is allowed to access the outgoing trunk group.

Uniform Dial Plan(UDP): it enables sharing of a common dial plan among a group of PBX servers, it is a global dial plan for inter-PBX call routing. When a UDP entry is matched, before routing the call off the local switching system, the dial digits might be subjected to a Extension Conversion, a digit manipulation to change the dialed digits to a Private-Network Number or Public Network Number. Extension Conversions fall into below categories;

  • Automatic Alternate Routing (AAR) conversion: Dialed digits are converted to Private-Network Number, then call is routed to another PBX within the same Private Network.
  • Automatic Route Selection (ARS) Conversion: Dialed digits are converted to Public-Network Number, then call is routed out of Private-Network to Public Network (PSTN for example).
  • Extension number portability (ENP) Conversion: In order  to use ENP conversion, you must specify a node number.
  • Extension (EXT): Unlike AAR conversion or ARS conversion, the system might not change the extension that the user dials before the system routes the call depending on whether UDP Entries or Local Extensions are firstly matched to determine the next hop for routing. You can manually configure that by  “UDP Extension Search Order (local-extensions-first / udp-table-first) ” in Dial Plan Parameters.

Extension to Cellular (E2C): it enables office desk phone and PSTN/Mobile phones to act as one-single phone logically through manual association on Communication Manager. In other words, associated Cell phone will operate as if it were a standard, Caller ID enabled desk phone extension controlled directly by Avaya CM.

  1. Features of E2C include:
    • incoming call to office desk phone will also alert Cell phone simultaneously.
    • Contact Info consistency: when calling desk phone from Cell phone, associated desk phone extension will be displayed as Calling Number. When extending calls to Cell phones, the same calling number presented on desk phone is sent to the cell phone.
    • The Extension to Cellular feature also supports the Fixed Mobile Applications (FMC), Public
      Fixed Mobility (PBFMC) and Private Fixed Mobility (PVFMC). The FMC applications are used
      for wireless endpoints that support a one-X Mobile Client application and have two modes called SMode (Single Mode) and DMode (Dual Mode). The FMC applications (PBFMC, PVFMC, and SPFMC) are the only OPTIM application that supports the CTI Mobility Integration feature.
    • Conditional Call Extending used to administer up to six different independent settings, controls
      which type of calls to extend when EC500 is enabled. These Settings are applied to specific application instead of the station as a whole. Conditional Call Extending feature is used by FMC applications such as PBFMC, PVFMC, and SPFMC.
    • Extension to Cellular users & their associated Cell phone infos can be recognized on another Avaya CM PBX where they are not administered.
    • Basic Supplementary Service such as Incoming call waiting, caller ID, calling number identification, swapping calls between 2 incoming calls, conference calls can be extended to Cell phones by E2C provided that the Cellular Network support those features.
  2. How enable or disable;
    • This feature can be enabled or disabled using Feature Name Extension (FNE).
    • Cellular service providers (CSP) who resell the Extension to Cellular service use the CSP or SPFMC (Service Provider Fixed-Mobile Convergence for dual mode phones) application type. CSP/SPFMC support ISDN, H.323, and SIP trunks. CSP/SPFMC is essentially the same as the Extension to Cellular application. Unlike Extension to Cellular, CSP/SPFMC is always enabled. Under CSP/SPFMC, users cannot disable Extension to Cellular.
  3. Restrictions;
    • EC500 and CSP work only with ISDN-PRI, ISDN-BRI, H.323, Multi Frequency Compelled (MFC), and SIP trunks.
    • Conditional Call Extending feature is not supported for PVFMC application when administered as a dual mode pair (DMX) with a ONE-X application. Conditional Call Extending feature is also not supported for OPS application.
    • You can use shared voice connection option only with the FMC applications such as PBFMC,
      PVFMC, and SPFMC.

Class of Service (COS): used to restrict the telephony features that can be accessed by end users. you can define detailed COS tags (0-15) and assign them to stations.

Advanced Maintenance Tricks:

Advanced search criteria:

list station 1000 to-ext 1010 | list station 1000 count 10 | list station type 4621 | list station port 001V2.

Copy existing station information:

duplicate station 1003 [count 10 start 1060]