Connecting a paging system to a Communication Manager gateway as a station is significantly less complex than connecting it as a CO trunk. Compare this post to my immediately previous post about paging via trunks.
Branch offices often have overhead paging systems, and it can be incredibly convenient for the overhead paging system to be connected to your Communication Manager gateway, so that users can operate the paging system from their deskphones (or anywhere, depending on your configuration).
This particular document notes how to connect a Communication Manager gateway (in this case, a G430 with an MM714B analog FXS/FXO line card) to a Valcom V-2006A using CO trunking facilities.
Most users understand that “to get an outside line”, they have to dial some number first – most commonly the digit 9, but sometimes other digits are used. When the user does that, they’re triggering Automatic Route Selection (ARS) functionality, which tells the phone system to automatically figure out how to route the digits that follow the access code.
Communication Manager (CM) is able to supply music to callers. This is primarily useful when callers are placed on hold, but can also be needed by vectors queueing callers for a specific skill/hunt-group.
With the appropriate equipment, Avaya Aura CM sites can “survive” an outage. An outage, in this context, means that the site lost IP (or TDM shudder) connectivity to both its primary controller and its enterprise survivable server (if there is one). The necessary equipment includes (generally) a media gateway with a local survivable processor, and some form of trunking (if you want calls to be able to leave the gateway).
