Table of Contents
Advertisement
13-2
Integration Volume
.
In large configurations, there could be delays in message-waiting activation and deactivation under
certain circumstances (for example, broadcast messages). Large configurations can create a high
volume of message-waiting commands within a short period of time. People might notice a delay
in their lamps being turned ON or OFF. Octel advises that this possibility be discussed during
customer training. To address this problem, it is possible to create large system distribution lists
and to send company−wide messages during off hours via future delivery. Alternatively, starting
with Release 5.3.0, message waiting indication can be disabled for broadcast and/or selected
distribution lists.
Direct Calls From External Trunks
If the call comes in on a trunk, the M1 PBX provides the Octel 200/300 with the trunk access code (or the
associated ANI number, if ANI is turned on in the switch and the Central Office) as the source of the call.
Trunks can be directed to message server ports for answering through the M1 auto-terminate feature.
Alternatively, the voice mail server can be called directly using the DID extension assigned to the first
port or to a DID number configured as an ACD pilot. If configured, the message server determines how
to process each call based on the trunk group number. Where no trunk group is configured, or for calls
that involve an ANI display, the system answers with the port-level company greeting. For calls coming
in on a trunk group, the M1 displays the following format on line two of the display module:
Trunk Group xxxx − Trunk Member yyyy
The message server answers with the company greeting appropriate to the trunk or port group.
If the Octel 220/300 has answered a direct call and the caller then dials an extension that is forwarded to
the server for call coverage (secondary answering), the server performs a transfer to ringing, with the
caller immediately hearing ringback until the called party or the Octel 200/300 answers.
If the called extension returns a busy signal, the Octel 200/300 returns to the caller and prompts "(name)
is on the phone. Please leave a message . . ." (If the called extension is programmed to forward to Octel
200/300 on a busy condition, it does not return a busy signal. The Octel 200/300 detects ringing and
completes the transfer.)
A Class of Service (COS) can be assigned to trunk groups, and a company greeting can be configured for
different groups. All Octel 200/300 ports configured for call answering can remain in one hunt group.
This is more efficient than having multiple-port hunt groups to provide different company greetings.
Caution!
Forwarded External Calls
When the M1 forwards a call (RNA, Busy, or Forward All Calls) to the Octel 200/300, the M1 sends the
access code of the incoming trunk group number, referred to as the ACOD, and the called extension
number to the Octel 200/300. The M1 tells the Octel 200/300 the reason the extension was forwarded (no
answer, busy). If the call is forwarded after a certain number of rings, the caller hears rings before the
Octel 200/300 answers. For forwarded external calls, the M1 displays the following format on the second
line of the display:
Trunk Group xx − Trunk Member yy extension number CFNA
Octel 200/300
S.4.1
All trunk groups answered by the Octel 200/300 must
be thoroughly tested to prevent trunks from locking
up ports caused by a wrong configuration, signaling,
or reversed cross connections.
PB60019-01
Advertisement
Chapters
Table of Contents
