Avaya IP Telephony User Manual download pdf (Page 29)

KW Avaya IP Telephony Implementation Guide

server and must be activated. An LSP does not accept station registrations or assume call processing

responsibilities until it becomes active, which occurs when a gateway registers to it.

The S8300 SAT interface may be accessed using Avaya SA (ASA) or by telnet-ing to port 5023: telnet

<S8300 address> 5023 or SSH-ing to port 5022.. This could also be done by telnet-ing to the S8300 and

typing sat from the Linux shell. S8300 ICC permits SAT configuration (changes and displays), but

S8300 LSP does not (displays only) because it receives its Avaya Communication Manager translations

from the primary server.

The S8300 connects to the G700/G350/G250 via a backplane 100M Ethernet interface, which is not

configurable.

3.3 G700/G350/G250 Media Gateways

G700 P330/C360 L2 Switch

The P330 L2 switch is the base platform for the G700. All other logical/physical IP components (MGP,

VoIP media modules, LSP) are connected to the P330 L2 switch. The asynchronous port (9600/8/N/1)

marked CONSOLE on the face of the G700 connects the user to the P330 CLI. The IP expansion slot on

the lower left corner of the chassis accepts the same X330 expansion modules used by the P330 switch.

The most common ones are probably the WAN router module and the 16-port Ethernet module. The two

Ethernet ports marked EXT1 and EXT2 are L2 switch ports. There is also an Octaplane® slot on the

back of the chassis, just like the P330. For practical purposes the L2 switching portion of the G700 is

equivalent to a 2-port P330 switch, which has a CLI similar to Cisco’s CatOS and is configured using

various set commands.

Three components of the P330 should be configured: the inband management interface, the default

route, and the switch itself. The inband management interface is displayed and configured using the

commands show interface inband and set interface inband, respectively. The inband interface requires

a VLAN, an IP address, and a mask. The VLAN can be any of the VLANs active on the P330, and the IP

address and mask must correspond to the IP subnet associated with that VLAN.

Once configured, the inband interface should be thought of as a host attached to the P330. This may seem

non-intuitive, because the inband interface is

the P330 and the way to administer the P330 remotely.

However, like most L2 switch management interfaces, the inband interface is associated with a specific

VLAN. As such, it is accessed just like any other host attached to the switch on a given VLAN – either

directly from another host on the same VLAN/subnet, or by routing to it from a host on a different

VLAN/subnet. Many mistakenly think that any host attached to the P330 should be able to access the

inband interface directly, and this is not necessarily true. Hosts on different VLANs/subnets must route

to the inband management interface via a L3 router.

Like any other IP host, the inband interface needs a default route if it is to route off of its VLAN/subnet.

The default route for the inband interface is displayed and configured using the commands show ip route

and set ip route, respectively. If there is more than one router on the inband VLAN/subnet, the inband

interface may have additional routes based on destination subnets or hosts. These are displayed and

configured using the same commands.

Finally, the P330 L2 switch itself has various configuration parameters, such as Spanning Tree, VLANs,

trunking, and speed/duplex. These are configured just like on the P330 switch (see appendix E).

G700 Media Gateway Processor (MGP)

The media gateway processor (MGP) is the media gateway portion of the G700. The MGP manages the

various media modules inserted into the G700. These media modules include analog port modules for

analog phones, DCP port modules for DCP phones, DS1 modules for TDM trunks, and others. The

media module associated specifically with IP telephony is the VoIP module. Each VoIP module is

equivalent to a MedPro board and has 64 audio resources. A single VoIP module is built in to the MGP,

and external VoIP modules can be added as necessary.

1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 80 81

Comments to this Manuals

No comments

Avaya IP Telephony User Manual Page 29

Comments to this Manuals

Related products and manuals for Network switches Avaya IP Telephony