Table of Contents
Advertisement
8. Keepalive messages. These messages are sent by each telephone to the media controller
at time intervals that are determined by Avaya Communication Manager, and based on the
number of registered sets. On a protocol analyzer, the keepalive message shows up as a
RAS-Registration Request (RRQ) message with the keepalive bit set in the RAS header.
Each request message is answered by the media controller with a RAS-Registration
Confirm (RCF) message.
9. Unregistration messages. If the Avaya Media Server intentionally unregisters a set, or if the
set intentionally unregisters itself, the message sent by either the media controller or the set
is a RAS-Unregistration Request (URQ). The acknowledgment message is
RAS-Unregistration Confirm (UCF). All unregistration requests should be confirmed. Future
releases will include various URQ types, whereas currently there is only one type.
Connecting a personal computer to an IP Telephone
On the back of the IP Telephone, the port with the icon that looks like a terminal is the user port.
(The port with the icon that looks like a network jack is the uplink port, which connects to the
Ethernet switch.) Use discretion when connecting a personal computer to the telephone, and
remember that its primary function is not that of an enterprise network device. For example, do
not connect an enterprise server to the telephone. Such high-traffic servers require their own
separate connections to the enterprise Ethernet switch. Also, do not connect a personal
computer to the telephone at 10 mbps if that computer routinely runs high-volume transactions.
The telephone itself operates well at 10 mbps, and the computer itself may also operate
adequately at 10 mbps. But the two combined can cause the computer to overwhelm the
10-mbps link at the expense of audio quality. Connecting a user computer to the telephone at
100 mbps works very well.
An IP Telephone and an attached PC on different VLANs
The third scenario for attaching a PC to the telephone (the first two were covered in the previous
subsection) is to have the telephone and the PC on separate VLANs. This requires a trunk port,
or some other multi-VLAN port, on the Ethernet switch. One of the VLANs is the port/native
VLAN, and the clear Ethernet frames (ones with no 802.1Q tag) from the PC reside on this
VLAN. The IP Telephone must tag its traffic with the ID of the VLAN to which it belongs. The
Hold QOS# options are exactly the same as described in the previous section, except that now
the VID must not be zero. The Layer 2 and Layer 3 priority options may or may not be
implemented. The IP Telephony Implementation Guide contains more detail about how to
implement this third scenario.
IP terminals deployment
Issue 3.4.1 June 2005
295
Advertisement
Table of Contents
