Telrad Digital Emagen Unified Messaging System Manual

							76-110-0887/0, Issue 1
9-18
No answer
The caller will be sent directly to the message-taking menu for the 
mailbox which 
emaGEN attempted a transfer to but received a no-
answer condition.
Take msg.
The caller will be sent directly to the message-taking menu for the 
mailbox which 
emaGEN attempted a transfer to, but received a re-
fusal such as a do-not-disturb signal.
Enter M.B.
The caller will be sent directly to get password prompt. This condition 
occurs when there is a MSG button set up on the subscribers tele-
phone set which may be pressed in order to immediately access 
emaGEN. This action will direct the subscriber immediately into the 
subscribers menu.
Monitor
This action tells 
emaGEN to record whatever audio is currently 
present on the port as a new message in the designated mailbox.
Hang up
This action tells 
emaGEN to immediately hang up and release the 
port for new calls.
Hand shake
This action tells 
emaGEN that it has a valid connection with a given 
PBX. This string consists of two parts; the received string, comma 
and the return string.
Ignore
This action tells 
emaGEN to ignore the related series of digits if they 
are received.
Transfer
This action tells 
emaGEN to transfer the caller to the received ex-
tension, as if he entered through the caller menu.
Line
This action tells 
emaGEN to check in the trunk integration table 
which department corresponds with the received trunk, and prompt 
the caller according to this department’s protocol.
Announce
This action tells 
emaGEN to play a message with the number re-
ceived from the PBX and then hang up.
Getuser#
The user will be prompted to enter their mailbox number, as if dialing 
# from the main menu. 
						

							Section 9:  PBX
9-19
9.12 CONFERENCE SEQUENCE
The conference sequence is used to connect a caller to a subscriber 
in a remote location. The Automated attendant allows transfer of a 
call to a remote location instead of an external extension, defined in 
the Mailbox --> Properties --> Follow me field; see Section 11.5. 
The conference sequence, using the following parameters, puts the 
caller on hold, grabs another line, dials the remote telephone number 
and conferences the calls (normally the calls are conferenced within 
emaGEN, because most PBXs do not allow CO line to CO line con-
ferencing without having at least one internal extension on the line 
-- this parameter is set in Mode). If the remote destination returns as 
busy or no answer, 
emaGEN uses the reconnect parameters to re-
connect the caller back to the system.
Put first on hold
This field contains the sequence of digits that 
emaGEN must use to 
put the first caller on hold in the PBX in order to start the conference 
connection.
Dial second line
This field contains the sequence of digits that 
emaGEN m u s t  d i a l  i n  
order to access a second dial tone while making a conference con-
nection.
Conference
This field contains the sequence of digits that 
emaGEN must dial to 
connect the held party with the second party that was just dialed. 
Reconnect if busy
This field contains the sequence of digits that 
emaGEN must dial to 
Legal values:0, 1, 2..9, * #, & / use , for pause
Default:Blank
Action:Enter the required digits.
Legal values:0, 1, 2..9, * #, & / use , for pause
Default:Blank
Action:Enter the required digits.
Legal values:0, 1, 2..9, * #, &, use , for pause
Default:Blank
Action:Enter the required digits. 
						

							76-110-0887/0, Issue 1
9-20
reconnect the caller if a busy is received from the remote location.
Reconnect if no answer
This field contains the sequence of digits that 
emaGEN must dial to 
reconnect the caller if a no answer is received from the remote loca-
tion.
Mode
The mode determines whether 
emaGEN will:
a. stay on the line as a third party making a conference (Super-
vised).
b. disconnect after connecting the two parties from within the PBX- 
CO line to CO line (Non Supervised)
.
Legal values:0, 1, 2..9, * #, & / use , for pause
Default:Blank
Action:Enter the required digits.
Legal values:0, 1, 2..9, * #, & / use , for pause
Default:Blank
Action:Enter the required digits.
Legal values:Supervised/Non-Supervised
Default:Non-Supervised
Action:Select Supervised or Non-Supervised mode. 
						

							Section 9:  PBX
9-21
9.13 TRUNK INTEGRATION TABLE
Figure 9-3    PBX --> Trunk Integration screen
emaGEN has the ability to identify up to 64 different incoming trunk 
codes and use them to direct incoming calls to a specific department 
for processing. If the PBX has the capacity to send a code in the 
DTMF sequence, 
emaGEN will use this code to identify what de-
partment a given call is to be sent to. This functionality allows all 
ports to be non-dedicated, providing the most efficient use of the 
emaGEN system.
Trunk
This field is where the PBX code for a given trunk line is identified.
Legal values:001-999
Default:Blank
Action:Enter the PBX trunk code for each incoming 
trunk.
  
						

							76-110-0887/0, Issue 1
9-22
Department
This field tells 
emaGEN what department to use when the related 
trunk code is received by 
emaGEN.
9.14 RS232 INTEGRATION TABLE
Figure 9-4     PBX --> Serial Integration screen
emaGEN supports four different com ports, which can be set inde-
pendently. The com port default is com1. Each of the following fields 
is applicable in all four com ports.
Active
This field determines if the port is available for data send and receive 
or it is idle.
Protocol
This field determines the protocol in which data  will be received and 
should be sent.
The legal values of the options for different protocols are listed be-
low.
Legal values:1-9
Default:Blank
Action:Select from the drop list.
Legal values:Checked/Unchecked
Default:Unchecked
Action:Click the field to check/uncheck.
  
						

							Section 9:  PBX
9-23
Channels
This field determines for which channels this com port is receiving 
data. 
emaGEN can be set to receive data from different devices, 
each device corresponding to different channels (voice ports). 
NOTE
It is necessary to assign 10 more channels
than actual voice channels, as the system
also uses virtual channels for some opera-
tions.
Baud rate
This field determines the baud rate in which the signaling occurs.
Parity
This field determines the parity of the data interchange. It can be 
None, Even or Odd.
Legal values:InternalFor Integration with 
Telrad Systems.
ANIANI protocol -- not used for 
emaGEN. 
This should always be internal.
SMDI1SMDI protocol -- data without ring.
SMDI2SMDI protocol -- data before ring.
SMDI3SMDI protocol -- data after ring.
Default:None
Action:Select from the drop list
Legal values:0 - Maximum number of channels
Default:0 - 0
Action:Enter channel numbers
Legal values:above 300
Default:9600
Action:Select the baud rate from the drop list.
Legal values:N / O / E
Default:N
Action:Click the button. 
						

							76-110-0887/0, Issue 1
9-24
Stop bit
This field determines the stop bit for the data interchange.
Word length
This field determines the word length (in bits) for the data inter-
change.
Xon / Xoff
This field determines transmission type.
Rx / Tx size
This field determines transmission capacity.
DTR / RTS
This field determines the signaling method
.
Legal values:1 / 2
Default:1
Action:Click the button.
Legal values:7 / 8
Default:8
Action:Select 7 or 8.
Legal values:Xon / Xoff
Default:70/30
Action:Use default unless specified otherwise by 
communication method.
Legal values:1024 / 1024
Default:1024 / 1024
Action:Use default unless specified otherwise by 
communication method.
Legal values:1 / 1
Default:1 / 1
Action:Use default unless specified otherwise by 
communication method. 
						

							10-1
Section 10 
DEPARTMENTS
10.1 DEPARTMENT DEFINITION
Figure 10-1   Department --> Properties screen
The Department definition is used to configure the automated atten-
dant aspect of each department. In most cases you will use only one 
department, which will be the site’s automated attendant. 
						

							76-110-0887/0, Issue 1
10-2
The department activated for each port:
 is defined in the PBX --> Port Definition (“Department” Column 
on PBX --> Port Definition screen, see Section 7) 
or 
 can be dynamically set using a PBX Integration Line command 
(on the PBX --> Trunk Integration screen, see Section 8.11).
NOTE
If a call comes in and integration informa-
tion sent by the PBX routes the call to a
specific mailbox, the main automated atten-
dant will not be activated.
The automated attendant greetings and routing are time sensitive. 
The operation mode determines which greeting to use and which op-
erator and no response mailbox to use at any given time. The oper-
ation mode can be set automatically – using the working hours table 
or can be fixed at any given mode.
When setting up a system, you will need to record the automated at-
tendant greetings. These greetings are not mailbox numbers – rather 
they are simple prompts, recorded through the system administrator 
mailbox. 
10.1.1 Recording system greetings
1. Enter the administrator mailbox designated in Site --> Settings. 
2. Press # for administrator menu. 
3. Select option 2 – record a prompt. 
4. Enter the greeting number to be recorded and follow the instruc-
tions.
The greetings to be recorded are:
 100 – good morning
 101 – good afternoon
 102 – good evening
 111 – Company greeting (“Thank you for calling …”)
 121 – Instructions (“With a touch tone phone… Press 1 for…”)
For a full description of the prompts refer to Section 16, below.
For system administrator instructions refer to Section 15, below.
10.1.2 Conversion table
After recording the system prompts, you will want to create a corre-
sponding routing scheme.  
						

							Section 10:  DEPARTMENTS
10-3
While the user is listening to the automated attendant greeting, you 
want to provide them with one-touch dialing in addition to the ability 
to dial a mailbox number or press 0 to reach the operator.
The one-touch dialing is defined in the conversion table.
For each digit option you want to use as a one-touch number, assign 
a mailbox number -- in the Department --> Properties --> Conver-
sion Table. 
The automated attendant will execute the routing to this mailbox.
NOTE
You can use any number in the conversion
table, regardless of the mailboxes number-
ing scheme. For example, if you have mail-
boxes starting with the digit 3 -- you may
also use the digit 3 in the conversion table.
The system will wait for the maximum num-
ber of digits allowed for a mailbox (defined
in Mailbox length field, under the Security
heading of the Site --> Settings ).
If it receives all digits -- it will try to open a
mailbox. Otherwise, it will try to convert the
entered digit according to the conversion
table.
10.1.3 Using a script instead of the standard automated attendant
In some cases when a more sophisticated automated attendant tree 
is required, you can override the standard  automated attendant that 
uses the conversion table and the external prompts and use a script. 
Set the Department --> Properties --> Start with script field to the 
designated script. 
The system will automatically start with the script without playing any 
of the external prompts.
10.2 DEPARTMENT --> PROPERTIES GENERAL SETTINGS
Department Number
This is the field that determines which Company, tenant or depart-
ment is going to be defined.
Legal values:1,..9
Default:1