You can use either the Avaya Site Administration (ASA) software
or the System Access Terminal (SAT) application for administering
the host switch. The ASA is a terminal emulator that is part of
the switch console. Unlike the SAT, the ASA software is a desktop
utility that enables you to administer the switch from any terminal.
Use the procedures in this section to administer a C-LAN connection
to the host switch.
Note: The procedures in this section can
be performed using either the ASA or the SAT. The function keys
for both the administration tools might vary. This section describes
the administrative procedures using the ASA. |
This section includes the following topics:
Configuring C-LAN
This section contains descriptions of the forms to be used with
detailed explanations for the required fields. We recommend that
you use the forms in the order shown.
Note: Before you start with the administration
procedures for configuring C-LAN, make sure of the following:
- A dial plan has been administered for the system. To view
the administered dial plan, type the command display
dialplan analysis at the administration command
prompt.
- The switch has been configured to support C-LAN and the
IP server.
|
The following table displays the commands that you must type to
access forms for configuring C-LAN.
Adding node names and IP addresses
- Start the administration tool.
- At the administration command prompt, type change node-names
ip and click send [return], or press
Enter.
The system displays the IP Node Names form. Use this form to
create a node name for C-LAN and to specify its IP address.
With TCP/IP connectivity, node refers to an interface to the
IP network. This form associates a node name with an IP address
for each network node in the network. A node can be an endpoint
such as a C-LAN port in this case, a Call Management System
(CMS) server, or an INTUITY system; it can also be a network
device such as a bridge or router.
- Complete the following fields:
Field Name |
Description |
Name |
Type a logical name for the IP device, which in this
case refers to C-LAN.
For example, you could give the name 'clan' to indicate
that the node is C-LAN.
This node name is also used in the IP Interfaces forms.
Note: Do not use special characters
in the node name. |
IP address |
Type the IP address of the C-LAN node. |
- Click enter [f3], or press
F3 to save the entry.
Tip: Click cancel (esc)
or press Escape to cancel the command and to
type another command at the administration command prompt. |
Back to top
Adding an IP interface
- At the administration command prompt, type change ip-interfaces
and click send [return], or press Enter.
The system displays the IP Interfaces form. Once you have created
a node name for C-LAN, you must enable this C-LAN node name
to identify the interface. You can do this by using the IP Interfaces
form. Also, use the IP Interfaces form to provide details such
as the network gateway and the subnet mask and to associate
the node name with a slot.
- Complete the following fields:
Field Name |
Description |
Enable Eth Pt |
Select y(es) to enable the Ethernet
point for the corresponding node.
The valid entries are n(o) and y(es). Selecting n(o) disables
the Ethernet point.
The default value is n(o). |
Type |
Select C-LAN from the list of valid entries.
This indicates the type of IP interface. |
Slot |
Type the equipment location of the C-LAN circuit pack.
This must be a 5-character board location, where the first
2 digits represent the cabinet number, the third character
represents the carrier, and the last 2 digits represent
the slot number.
The C-LAN board can be physically inserted in this particular
slot on the switch. Tip: Type the
command list configuration all to view
the port numbers for analog line interfaces in the system. |
Code |
This field displays the circuit pack code number.
This is a display-only field. This field is automatically
populated with the value TN799 for C-LAN.
Note: The system automatically populates
this field after you type the slot value. |
Sfx |
This field displays the suffix assigned to this interface
and the hardware version of the circuit pack.
This is a display-only field.
Note: The system automatically populates
this field after you type the slot value. |
Node Name |
Select the node name of the IP interface.
This is the name you have specified for the C-LAN node in
the IP Node Names form. |
Subnet Mask |
Type the subnet mask of the IP interface.
The subnet mask defines the network and host parts of the
IP address. |
Gateway Address |
Type the gateway address of the IP interface. |
Network Region |
Type a number between 1 and 80.
This number indicates the network region to which this interface
belongs. The network region is used for determining the
IP codecs supported. A codec provides encoding of the analog
signals to digital and decoding of the digital signals to
analog. |
- Click enter [f3], or press
F3 to save the entry.
Tip: Click cancel (esc)
or press Escape to cancel the command and
to type another command at the administration command prompt. |
Back to top
Adding an Ethernet data module
- Type add data-module next or add data-module
xxxx at the administration command prompt, where xxxx
stands for the extension number assigned to the Ethernet data
module, as per the administered dial plan. Click send
[return], or press Enter.
The system displays the Data Module form. Use the Data Module
form to assign a link to the node via an Ethernet data module.
This form defines a link and associates the link number with
parameters such as the data module type, C-LAN port location,
and node name for this port on the host switch.
Note: When you use the add data-module
command, the system checks the extension number to make
sure that it is valid and that it does not already exist.
If it exists, the system displays the message "Identifier
previously assigned; please select another." If the
extension number is invalid, the system displays the message
"Extension invalid; please check dialplan" and
then prompts you to enter a new extension.
If you use the word next in the command (add
data-module next), the system will automatically pick
the next lowest-numbered available extension. If no extensions
are available, the system displays the message "No
available extensions in the system." Once the extension
you have entered passes the above criteria, the system
retrieves the translation data and displays the default
values. |
Tip: Type the command list
data-module at the administration command prompt
to view a list of valid data modules and the assigned
extension numbers. |
- Complete the following fields:
Field Name |
Description |
Data Extension |
This field displays the extension number assigned to this
data module.
This is a display-only field. |
Name |
Type a unique identifying name for the data module. The
name can contain alphanumeric characters.
Note: Do not use special characters
in the name field. |
Type |
Type ethernet. This indicates that you
are adding an Ethernet data module. |
Port |
Type the 17th port of the C-LAN board. Use the format
<cabinet><carrier><slot><port> for
the port.
This is the port number that has been reserved for C-LAN
signaling via the Ethernet. Each C-LAN board has 17 ports;
port 17 is used for the LAN interface.
For example, the port could be 01A0317, where 01 is the
cabinet number, A is the carrier, 03 is the slot number,
and 17 is the LAN port. Tip: Type the
command list configuration all to view
the port numbers for analog line interfaces in the system.
|
Link |
Type the communication interface number.
The range is 1 through 99. This number should not have been
assigned on this switch previously. This link number will
later be used in the Processor Channel Assignment form. |
Network uses 1's for Broadcast Addresses? |
Select y(es) or n(o).
This sets the host portion of the IP address to 0s or 1s.
The default is y(es) (all 1s).
Note: Check with the administrator whether
the host switch uses 0s or 1s for broadcast addresses.
|
- Click enter [f3], or press F3
to save the entry.
Tips:
- Click cancel (esc) or
press Escape to cancel the command
and to type another command at the administration command
prompt.
- Use the change data-module xxxx
command to modify data module details.
|
Back to top
Adding the messaging server node name
and IP address
You must inform the switch that the S3400 Message Server exists.
To do this, you must add the messaging server node name and IP address.
- At the administration command prompt, type change node-names
audix-msa and click send [return], or
press Enter.
The system displays the Audix-MSA Node Names form.
- Complete the following fields:
Field Name |
Description |
Audix Names |
Select the name specified for the messaging server node.
This is the name of the Messaging Application Server (MAS).
|
IP Address |
Type the IP address for the messaging server (MAS). |
MSA Names |
Select the Message Servicing Adjunct (MSA) name.
This is an optional field. |
IP Address |
Type the IP address specified for the MSA.
This is an optional field. |
- Click enter [f3], or press
F3 to save the entry.
Tip: Click cancel (esc)
or press Escape to cancel the command and
to type another command at the administration command prompt. |
Back to top
Adding the communication interface processor
channel
- At the administration command prompt, type change communication-interface
processor-channel and click send [return],
or press Enter.
The system displays the Processor Channel Assignment form.
This form assigns a processor channel to the interface link.
It associates a processor channel number with parameters such
as the link number and the interface channel number. The form
also associates these numbers on the local switch with destination
identifiers such as the node name, port number, and the machine
(switch) ID from the dial plan.
- Complete the following fields:
Field Name |
Description |
Enable |
Select y(es) to enable the processor
channel linking.
The default value is n(o). |
Application |
Select or type audix.
This indicates the type of application that connects to
this processor channel. |
Mode |
Select s(erver).
The available options are s(erver) and c(lient). Selecting
the server mode indicates that the host switch will act
as the server and the messaging server as the client. The
messaging server will initiate the TCP session. |
Link |
Type the interface link number.
This must match the link number assigned on the Data Module
form.
For example, if you have assigned link 1 to the interface
in the Data Module form, then you must assign link 1 to
the processor channel in this form. |
Channel |
Type the value of the TCP port.
This is the port on which the switch would accept a connection
from the messaging server.
For example, in the case of DEFINITY switches, the port
value is 5002. |
Destination Node |
Type the name of the messaging server node, which is the
destination node for this channel. |
Destination Port |
Type 0.
Setting this value to 0 ensures that data can be received
from any port of the destination node. |
Local Session |
Type the numerical session identifier of the local
machine.
Tip: Type the command change
dialplan parameters and click send [return],
or press Enter. The system displays the
Dial Plan Parameters form. Note the value in the Local
Node Number field. This is the Local Session value. |
Remote Session |
Type the numerical session identifier of the remote machine.
Note: This number must be the same as
the machine ID of the MAS.
Tip: The Remote Session number will
be used for configuring PBX integration, using the Voice
Mail System Configuration tool. For details, refer to
Configuring the S3400 Message
Server for telephony. |
Machine ID |
Type the identification number of the messaging server.
Note: This number must be the same as
the Remote Session number. |
- Click enter [f3], or press
F3 to save the entry.
Tip: Click cancel (esc)
or press Escape to cancel the command and
to type another command at the administration command prompt. |
Back to top
Adding stations
- To define the S3400 Message Server voice ports as stations,
type add station next or add station
xxx at the administration command prompt. Here,
xxx is a valid extension number. Click send [return],
or press Enter.
The system displays the Station form.
Note: When you use the add station
command, the system checks the extension number to make
sure it is valid and that it does not already exist. If
it exists, the system displays the message "Identifier
previously assigned; please select another." If the
extension number is invalid, the system displays the message
"Extension invalid; please check dialplan" and
then prompts you to enter a new extension.
If you use the word next in the command (add
station next), the system will automatically pick the
next lowest-numbered available extension. If no extensions
are available, the system displays the message "No
available extensions in the system." Once the extension
you have entered passes the above criteria, the system
retrieves the translation data and displays the default
values. |
- Complete the following fields:
Field Name |
Description |
Extension |
This field displays the primary extension number associated
with the station.
This is a display-only field. The system populates this
field with the extension number that you provide when entering
the command.
To change an extension number, remove the station and add
it back with a new extension number, or duplicate the station
with the desired new extension and then remove the station’s
old extension. |
Type |
Type 2500.
This value determines identification of the type of station
set. 2500 represents an analog station set. |
Port |
Type the port address of the station.
This is an optional field denoting the port address ([network
(1-3)]:carrier (A-E):slot (01- 20):circuit (01-24)) of the
station. For example, 1B1207. |
Note: You can leave the default values
in the rest of the fields. |
- Click enter [f3], or press
F3 to save the entry.
Tip:
- Use the duplicate station xxxx
command to enter details for multiple stations with
similar settings. Use the change station xxxx
command to modify station details.
- Click cancel (esc) or
press Escape to cancel the command
and to type another command at the administration command
prompt.
|
Duplicating stations
Use the duplicate station command to enter details of multiple
stations with similar settings. A quick way to add stations using
the ASA software is to copy the information from an existing station
and modify it for each new station.
For example, you can configure one station as a template for an
entire work group. Then, you duplicate the template station form
to add all the other extensions in the group. Note that only telephones
of the same model can be duplicated. The duplicate station command
copies all the feature settings from the template telephone to the
new telephones.
To duplicate an existing station:
- At the administration command prompt, type display
station xxxx, where xxxx is the extension
you want to use as a template.
- Press Enter. The Station form appears, displaying
details of station xxxx. Verify that this extension is
the one you want to duplicate.
- Click cancel (esc) or press Escape
to return to the command prompt.
- Type duplicate station xxxx,
where xxxx is the extension you want to duplicate.
- Press Enter. The system displays a blank Station
form.
- Type in the extension field, port field, and name for each
new station you want to add. The rest of the fields are optional.
You can complete them at any time.
- Click enter [f3], or press
F3 to save the entry.
Back to top
Creating lines for communicating with
the messaging server
For creating lines for communicating with the messaging server,
you must create a hunt group. A hunt group is a group of extensions
that receive calls according to the call distribution method you
choose. When a call is made to a certain telephone number, the system
connects the call to an extension in the group. Use hunt groups
when you want more than one person to be able to answer calls to
the same number.
A hunt group can also be described as a group of extensions that
are assigned the Station Hunting feature so that a call to a busy
extension reroutes to an idle extension in the group.
This section describes the forms to be used with detailed explanations
for the required fields.
Adding a hunt group
Perform the following administrative procedures to add a hunt group:
- Type add hunt group next at the administration
command prompt. Click send [return], or press
Enter.
The system displays the Hunt Group form.
-
On Page 1 of the Hunt Group form, complete the following fields:
Field Name |
Description |
Group Number |
The system automatically displays the next available hunt
group number. This is a display-only field. |
Group Name |
Type the name you want to use to identify the hunt group.
|
Group Extension |
Type the extension number that subscribers should dial
to retrieve their messages from the messaging server. |
Group Type |
Type the code for the call distribution method you choose. |
TN: |
Type the Tenant Number.
A tenant is a subdivision of an organization. A tenant might
be a department of a company, a site location, or a separate
company altogether. In cases where a single application
is partitioned such that it can support multiple tenants,
a tenant number is assigned to each tenant.
The range is 1 through 20. The default value is 1. |
COR: |
Type a number to indicate the Class Of Restriction (COR).
This COR will be assigned to the extension that subscribers
will call to reach the S3400 system.
The range is 0 through 95. The default value is 1. |
Security Code: |
Type the 4-digit security code that group members will
use to retrieve messages. |
ISDN Caller Display: |
Select a value for the ISDN caller display. Valid entries
are grp-name and mbr-name. |
ACD? |
Select y(es) or n(o)
to enable or disable the Automatic Call Distributor (ACD)
feature.
ACD is a feature that answers calls, and then, depending
on administered instructions, delivers messages appropriate
for the caller and routes the call to an agent when one
becomes available.
The default value is n(o). |
Queue? |
Select y(es) or n(o)
to enable or disable the Queue feature. You can tell your
switch how to handle a hunt group call when it cannot be
answered immediately. The call waits in a "queue."
If you select y(es), then three additional
fields are displayed, Queue Length, Calls Warning Threshold,
and Time Warning Threshold. |
Queue Length: |
Type the maximum number of calls that can be in the queue. |
Calls Warning Threshold:
Port: |
Type the maximum number of calls that can be in the queue
before the system flashes a warning.
For example, type 5 in this field if you want the switch
to send a warning when 5 or more calls are waiting in the
queue. |
Time Warning Threshold:
Port: |
Type the maximum number of seconds that a call can be
in the queue for, before the system flashes a warning.
For example, if you type 30 in this field, it tells the
switch that a certain number of calls can wait in the queue,
but that you want to be notified if a call waits for more
than 30 seconds. |
Vector? |
Select y(es) or n(o)
to enable or disable vectors.
A vector is a set of up to 15 vector commands to be performed
for an incoming or internal call. A hunt group may be Vector
controlled if Call Vectoring is a feature on the switch.
If you select y(es), then the Coverage
Path and Night Service Destination fields disappear.
The default value is n(o). |
Coverage Path: |
Type the number you want to use to identify the coverage
path.
A coverage path is the order in which calls are redirected
to alternate answering positions.
See Adding a coverage path for details
on adding a coverage path that covers to the hunt group. |
Night Service Destination: |
Type a hunt group extension, or an attendant, or leave
this field blank.
Use this field to direct hunt group calls to a night service
destination. The destination can be an extension, a recorded
announcement extension, a vector directory number, a hunt
group extension, or an attendant. |
- Click next [7] to access Page 2 of the Hunt
Group form.
- On Page 2 of the Hunt Group form, complete the following fields:
Field Name |
Description |
Message Center |
Right-click to select audix.
This indicates the type of the message center to which the
hunt group connects. Valid entries are: none, audix, and
msa.
Select none if the hunt group does not
serve as a message center hunt group.
Select msa if the hunt group is connected
to a messaging server adjunct. This will cause the Primary
field to appear for switches such as DEFINITY G3r, Avaya
S8300 Media Server, and Avaya S8700 Media Server.
Select audix if the hunt group is connected
to a messaging server. This will cause the Message Center
Audix Name, Calling Party Number to Intuity Audix, and Primary
fields to appear for switches such as DEFINITY G3r, Avaya
S8300 Media Server, and Avaya S8700 Media Server. |
Message Center Audix Name |
Type the name of the message center.
This is the audix name that you have entered in the Audix-MSA
Node Names form.
The message center must be previously administered by you.
If you have not administered any message center names, the
system displays an error message: Must administer ‘change
adjunct-names' form first.
Note: This field appears only for hunt
groups with audix as the message center. This field appears
for switches such as DEFINITY G3r, Avaya S8300 Media Server,
and Avaya S8700 Media Server. |
Primary |
Select y(es) or n(o)
to indicate that the messaging server is the primary adjunct
or not, respectively.
Note: This field appears only for hunt
groups with audix or msa as the message center. This field
appears for switches such as DEFINITY G3r, Avaya S8300
Media Server, and Avaya S8700 Media Server. |
Calling Party Number to Intuity Audix |
Select y(es) to pass the calling party
number to the messaging server. Select n(o)
to prevent the calling party number from being passed to
the messaging server.
This field is used in the case of trunk calls.
Note: This field appears only for hunt
groups with audix as the message center. This field appears
for switches such as DEFINITY G3r, Avaya S8300 Media Server,
and Avaya S8700 Media Server. |
LWC Reception |
Right-click to select none from the
list of valid entries.
Leave Word Calling (LWC) is a feature that allows the
calling party to leave a standard (nonvoice) message for
the called party using a feature button or dial access
code.
Note: C-LAN SWIN does not support LWC
message. |
Audix Name |
Select none.
This field indicates the name of the audix box that would
be used for LWC reception. As C-LAN SWIN does not support
LWC message, you need not specify an audix name here. |
- Click next [7] to access Page 3 of the Hunt
Group form. Use this page of the form to add group members to
the hunt group.
- To add group members, complete the following fields:
Field Name |
Description |
Extension |
Type the extension number of the group member.
This is the extension number that you assign to a station
when you define the S3400 Message Server voice ports as
stations, using the Station form. For details on adding
a station, see Adding stations. |
Name |
The system automatically populates this field when you
save the form. |
- Click enter [f3], or
press F3 to save the entry.
Tip: Click cancel (esc)
or press Escape to cancel the command and
to type another command at the administration command prompt. |
Back to top
Adding a coverage path
A coverage path is the order in which calls are redirected to alternate
answering positions. When a call made to a particular station is
not answered because the called station is busy, or is not answered
within a specific number of rings, then the call is sent to the
coverage path. When you are adding stations for the host switch
subscribers, you will use the coverage path that you create here.
Perform the following administrative procedures to add a coverage
path, covering to the hunt group:
- At the administration command prompt, type add coverage
path next or add coverage path xxx.
Here, xxx is a valid coverage path number. Click send
[return], or press Enter.
The system displays the Coverage Path form.
- Complete the following fields:
Field Name |
Description |
Point1 |
Type the hunt group number.
This is the hunt group to which calls will be directed when
taken up by the coverage path you are creating. |
Rng |
Type an integer between 1 and 99.
This value indicates the number of rings after which a call
is sent to the next point in the coverage path. |
- Click enter [f3], or
press F3 to save the entry.
Tip: Click cancel (esc)
or press Escape to cancel the command and
to type another command at the administration command prompt.
|
Back to top
Administering subscribers on the switch
After you have administered a coverage path with the S3400 Message
Server as a coverage point, you must administer stations of S3400
message server subscribers, on the switch. Administering subscribers
includes adding new subscribers or making changes to the details
of existing subscribers.
Adding subscribers
To add subscribers:
- Type add station next or add station
xxx at the administration command prompt. Here,
xxx is a valid extension number.
Click send [return], or press Enter.
The system displays the Station form.
- Complete the fields on the Station form.
Note: In the Coverage Path 1 field,
type the identification number of the coverage path you
have created earlier (refer to Adding
a coverage path). This is the coverage path that covers
to a hunt group. The group members of this hunt group
are the stations that you have created earlier (refer
to Adding stations). |
- Click enter [f3], or
press F3 to save the entry.
Editing subscribers
To edit subscribers:
- Type change station xxx at the administration
command prompt. Here, xxx is the extension number of
the subscriber.
Click send [return], or press Enter.
The system displays the Station form.
- In the Coverage Path 1 field, type the identification number
of the coverage path you have created earlier (refer to Adding
a coverage path). This is the coverage path that covers to
a hunt group. The group members of this hunt group are the stations
that you have created earlier (refer to Adding
stations).
- Click enter [f3], or
press F3 to save the entry.
Note: Dial the extension number of the
subscriber you have added or edited. If the call is not answered
after a predetermined number of rings, the call is taken up
by the coverage path you created earlier (refer to Adding
a coverage path). The coverage path directs the call to
the subscriber's mailbox on the S3400 Message Server, provided
the administration of mailboxes has been completed on the
Message Storage Server (MSS). For details on administration
of mailboxes for local subscribers, refer to the document
Adding local subscribers. |
Back to top
|