Escolar Documentos
Profissional Documentos
Cultura Documentos
by
Matias Trevino
Pre IP Deployment
Network Assessment
Compatible with voice network readiness
guidelines for Avaya products
Helps with implementation and
troubleshooting
CIR Minimum guaranteed bandwidth
DHCP Dynamic Host configuration Protocol. Provides options and IP-addresses. This Minimizes
maintenance for IP Telephone network by removing the need to individually assign and maintain
addresses and other parameters for each IP telephone on the network.
It is the responsibility of the customer to install and configure the DHCP server correctly.
Subnet mask
When an IP phone is initializing, the "Discovering" message appears when the IP phone begins
looking for the DHCP server. This message remains on the display until the phone successfully
registers with the gatekeeper (the CLAN or S8300 Media Server), at which point the display
shows the date and time.
HTTP Hypertext and transfer file for 1600 or 9600 series phones or TFTP Trivial file and transfer
protocol for 4600 series phones.
You can store the same application software, script file, and settings file on an HTTP server as you
can on a TFTP server. With proper administration, the telephone seeks out the use of this material.
For subsequent software upgrades, the call server provides the capability to remotely reset the
telephone, which then initiates the same process for contacting a file server. The IP Desk phone
then downloads a 46xxsettings.txt file. The settings file contains options you have administered for
any or all of the IP Desk phones in your network. . After the settings file has been downloaded, any
language or certificate files required by the settings will be downloaded. Finally, any new software
files will be downloaded, if necessary. Download the 46xxsettings.txt template file from
support.avaya.com and edit it to add your own custom settings.
Data switches understand MAC addresses and allows data transfer via VLAN with
QoS.
Routers send and receive packets from one network to another network. Routers
understand IP addresses. Host or end points on different VLANs can not
communicate without a router. IP-addresses have to be mapped on a router for 2
different VLANS to communicate. Each VLAN can have only one router interface
with only one IP subnet.
3.
Hardware Problems Phone, RJ45 jack, Cat 5 cable, port on data switch, power supply or
PoE switch, router and CM.
Software Firmware, CM configuration, data switch port configuration 100 duplex, router
configuration, TFTP or HTTP 46xx.txt settings file, DHCP SCOPE 176 for 4600 series phones
and 242 for 1600 and 9600 series phones.
Network Changes in the network that uses bandwidth during peak hours. Packet loss,
Jitter or Latency.
Latency, also referred to as packet delay, is the length of time it takes a packet to travel the
network round-trip. Users will have trouble carrying on a normal conversation when the oneway network delay exceeds 50 milliseconds(ms). Delays in excess of 180 ms can cause the well
known problem of talk over, when each person starts to talk because the delay prevents them
from realizing that the other person has already started talking. Each element of the network
adds to packet delay including switches, routers, distance traveled through the network, and
firewalls.
Copyright 2011 CCC Technologies, Inc. All Rights Reserved.
Resetting phones:
unplug and plug back in
When the message Reset Values? displays, press the * button to continue a restart without
resetting the values.
You would press the # button to reset values to their defaults; however, if you press # and the IP
phone values are statically assigned, you will have to reconfigure the phone.
As described in the phone initialization process, when an IP phone is initializing, the "Discovering"
message appears when the IP phone begins looking for the DHCP server. This message remains
on the display until the phone successfully registers with the gatekeeper (the CLAN or S8300
Media Server), at which point the display shows the date and time.
Copyright 2011 CCC Technologies, Inc. All Rights Reserved.
2.
3.
4.
5.
6.
No power Possible bad power supply if using a power supply, bad port on POE switch,
Bad phone.
PoE switch is always a data switch, but a data switch in not always a PoE switch.
No dial tone IP-Phone is not talking to the call server(S8XX), the problem could be with
the wiring, bad port, connection, configuration in data port or phone.
No audio MEDPRO provides talk path to a non IP device. Connects TDM to IP.
IP phone that stays in DISCOVER mode points to DHCP issue - not seeing DHCP server, port
not programmed for DHCP, IP phone configured with wrong VLAN.
Clipping
Has a network assessment ever been done? Has the network been modified since the
assessment was done?
If no, the network might not be compliant, If the problem cannot be resolved, an
assessment may be required.
Look at the large pattern first. Do other IP telephones on the same VLAN/Sub-network or
floor have the same problem?
Is the a separate VLSN or sub-network used for voice?
Is the number of broadcast messages lower than 1000 messages per second? This is the
number that can be safely handled by the IP Telephone. Check this by using the network
management system.
Is the Ethernet switch connected to the Media Processor set up for auto negotiation?
Check the Media Processor by using ASA. The Media Processor supports auto/auto by
default.
Clipping (continued)
Are 802.1p QoS and IP DiffServ properly and consistently used in switches, routers, the
Media Processor and the TN799 CLAN? Check if the QoS usage is consistent by checking
the following:
At an IP Telephone press the keypad sequence HOLD Q O S # and use the # key to walk
through the menu to verify if the following recommended values are used for voice
priorities:
Run the display or list ip-interface command to find the network region for the CLAN.
Run the display ip-network region command to check the QoS settings for the region.
Clipping
Does the call traverse a WAN link? Does it have sufficient bandwidth and QoS/packet
fragmentation? NOTE: Avaya recommends using G729 which requires 24 Kbps
(uncompressed, excluding Layer 2 overhead). IP packet fragmentation should be turned on
when no DiffServ QoS facilities are available. On Avaya and CISCO router it is possible to
minimize bandwidth for audio usage by using the CRTP (compressed RTP). Are 801.1p QoS
and IP DiffServ properly and consistently used in switches, routers, the Media Processor
and the TN799 CLAN? Check if the QoS usage is consistent by checking the following:
Is the codec set to G729 for calls across the WAN? This can be checked with an active call
in progress by using the status station command. Scroll to Page 3 (Call Control Signaling),
In the Audio Channel section, it should indicate G.729 as the encoder used.
Is the end to end packet loss less than 1%? Packet loss greater than 1% may be perceived
as poor voice quality, IP Telephony packet loss can be measure using:
List trace station ext# or tac
Delay
Step 1: You can use the VOIP Monitor Manger to determine how much delay is on the
network. The levels in the diagram in the next slide show the expected quality.
Step 2: Use the status station command to verify what resources are being used. Use
the trace-route command to verify how many hops are taken to the network. Check
the IP-network-region screen to verify how the network is set up with shuffling, hairpinning, QoS and phb values.
Step 3: Ping the LAN. Check the QoS parameters on the data switch, the rsvp and the
dscp parameters on the layer 3 switch, and if the stp is enabled on the switch. Check
the QoS,rsvp and dscp parameters on the ip-network regions screen.
Step 4: Ping across the WAN. Check the bandwidth constraints. The customer may
have a 10M hub or a 512 WAN link. Check the ports on their layer 2 switch to see
what they are set to. Check the codec set in ip-codec set in the Communication
Manager.
Continuation
Gauges
Acceptable
Warning
Not Acceptable
Jitter (ms)
0-50 ms Conversation
was smooth
50-150 ms Crackling,
static or intermittent delay
could be detected
>150 ms
0180 ms No delay
between each endpoint
>500 ms
Loss
>30 ms