Sunteți pe pagina 1din 162

Consideraciones previas a la

implantación de una solución de


Telefonía IP
Instructor: Alejandro Fernández de la Cueva Pedroche
CCSI: 21221

alejandro.fernandez@avaanza.es

1
Objetivos

• Ofrecer una visión global de una solución integral


de Telefonía IP

A Quien va dirigido:
• Técnicos preventas, técnicos implantadores,
técnicos de Soporte.

Conocimientos previos:
• Básicos de VozIP y conocimientos medios sobre
soluciones TCP/IP

alejandro.fernandez@avaanza.es
Cisco Icons and Symbols

Network
PC Cloud IP Phone

File Web
Server Server
Phones

Database
Cisco
Web
CallManager
Browser

Switches
Multiswitch
Device
Voice-
Enabled
Router
WAN
Softswitch

Bridge Router

alejandro.fernandez@avaanza.es
Sources of Information, URL’s

 IETF/IRTF/IEEE work on QoS


 Integrated Services (intserv)
 http://www.ietf.org/html.charters/intserv-charter.html
 Architecture RFC 1633, controlled load RFC 2211, Guaranteed service RFC 2212
 RSVP signaling protocol.
 http://www.ietf.org/html.charters/rsvp-charter.html
 RFC 2205
 Differentiated Services (diffserv)
 http://www.ietf.org/html.charters/diffserv-charter.html
 Policy for Admission control (rap)
 http://www.ietf.org/html.charters/rap-charter.html

alejandro.fernandez@avaanza.es
Sources of Information, URL’s

MGCP, rfc 2705


SIP, rfc 2543, rfc 2327
RTP, RTCP, rfc 1889

alejandro.fernandez@avaanza.es
Sources of Information, URL’s

alejandro.fernandez@avaanza.es
Diccionario voip

alejandro.fernandez@avaanza.es
Diccionario voip

alejandro.fernandez@avaanza.es
Diccionario voip

alejandro.fernandez@avaanza.es
Diccionario voip

alejandro.fernandez@avaanza.es
Diccionario voip

alejandro.fernandez@avaanza.es
Diccionario voip

alejandro.fernandez@avaanza.es
ANTECEDENTES

13
Separación de Redes

alejandro.fernandez@avaanza.es
Integración de Redes

alejandro.fernandez@avaanza.es
INTRODUCCION
DISEÑO

16
INTRODUCCION DISEÑO IP TELEPHONY

Escenarios que nos podemos encontrar

 Diseño nuevo, diseño desde cero.


 TOP-DOWN

 Diseño de telefonia ip sobre red existente.


 BOTTOM-UP

alejandro.fernandez@avaanza.es
Aplicación: Telefonia IP

 Se incluye dentro de las aplicaciones llamadas


“Enterprise Applications”
 Tipo de diseño: TOP-DOWN
 En realidad son varias aplicaciones
 Señalización, H225, H245, RAS, SIP, MGCP, SKINNY
 RTP
 Dichas aplicaciones requieren tratamiento
QoS distinto, distintas colas
 Los caminos físicos y lógicos son distintos
 Los bandwidth son distintos

alejandro.fernandez@avaanza.es
Aplicación Telefonía IP, Comparativa

 El protocolo IP no esta preparado para transportar Voz

Voz (G729-20ms)
20 bytes
RTP (12 bytes)
UDP (8 bytes)
IP (20 bytes) Voz Voz
Level 2 ?? FR ATM
Level 1 Level 1 Level 1

alejandro.fernandez@avaanza.es
Aplicación Telefonia IP

 Una vez parametrizada la Voz IP, ¿Qué


ocurrirá con los datos.
 ¿Qué datos son los que tiene el cliente?
 ¿Cómo clasificarlos?
 ¿Qué necesidades de QoS necesitan?
 ¿Qué nivel de criticidad coorporativa tiene?
 ¿Qué patrón de flujo tienen estos datos?

Esto nos lleva a pensar que el diseño de telefonia


IP es muy complejo
alejandro.fernandez@avaanza.es
DISEÑO GENERAL DE
REDES IP

21
Flexibilidad de la RED

Description
Functionality Supports the organizational requirements
Scalability Supports constant growth and expansion of
organizational tasks
Availability Provides necessary services reliably anywhere,
anytime
Performance Uses responsiveness, throughput, and utilization as
measures of effective application support
Manageability Provides control, performance monitoring, and fault
detection
Efficiency Provides services with reasonable operational costs
and appropriate capital investment

alejandro.fernandez@avaanza.es
PDIOO Network Life Cycle

alejandro.fernandez@avaanza.es
Design Methodology Steps

A design methodology consists of eight steps:


1. Identify the customer requirements.
2. Characterize the existing network.
3. Design the topology and network solutions.
4. Plan the implementation.
5. Build a pilot or prototype network (optional).
6. Document the design.
7. Implement and verify the design.
8. Monitor and optionally redesign.

alejandro.fernandez@avaanza.es
Identifying Required Information

alejandro.fernandez@avaanza.es
Planned Applications

Application Application Criticality Comments


Type (critical/important/
unimportant)
E-mail

Groupware

Voice networking

Web browsing

Video on demand

Database

Customer support

alejandro.fernandez@avaanza.es
Example: Planned Applications

Application Application Criticality Comments


Type (critical/important/
unimportant)
E-mail Lotus Notes Important

Groupware Lotus Notes Critical

Voice networking IP telephony Critical The company is replacing regular


telephony.
Web browsing MS IE, Opera, Unimportant
Netscape
Video on demand IP/TV Critical

Database Oracle Critical All data storages will be based on


Oracle.
Customer support Specific Critical
applications

alejandro.fernandez@avaanza.es
Example: Planned Intelligent Network
Services

Service Comments

Security Firewall technology to protect internal network;


virus scanning on incoming traffic; intrusion
detection to identify possible outside intrusions
QoS QoS to prioritize important and delay-sensitive
traffic over less important traffic

Network management Centralized network management tools


(HP OpenView with CiscoWorks2000)

High availability Redundant paths with terminated connections on


different network devices

IP multicast IP multicast services to support


videoconferencing, e-learning solutions,
and IP/TV

alejandro.fernandez@avaanza.es
Example: Organizational Goals

Organizational Goal Gathered Data Comments


(Existing Situation)
Increase Corporation Y, • Better products
competitiveness Corporation Z • Reduce costs

Reduce costs Enter data multiple • Single data entry point


times; time-consuming • Easy-to-learn application
tasks
• Simple data exchange
Improve customer Order tracking; technical • Web-based order tracking
support support • Web-based customer
technical support tools

Add new Telephone and fax • Secure web-based ordering


customer orders; telephone and • Secure web-based
services fax confirmation confirmations

alejandro.fernandez@avaanza.es
Example: Organizational Constraints

Organizational Gathered Data Comments


Constraint
Budget $650,000 Budget can be extended by
maximum $78,000

Personnel Engineers with CCNA Plans to hire new engineers in


certificates and CCNP the network department
certificates

Policy Prefers single vendor Current equipment—Cisco;


and standardized prefers to stay with it
protocols

Scheduling Plans to introduce new New applications include


applications in the next videoconferencing, groupware,
nine months and IP telephony

alejandro.fernandez@avaanza.es
Technical Goals

Technical Goals Importance Comments

Performance

Availability

Manageability

Security

Adaptability

Scalability

Total 100

alejandro.fernandez@avaanza.es
Example: Technical Goals

Technical Goals Importance Comments

Performance 20 Important on the central site, less


important in branch offices
Availability 25 Should be 99.9 percent

Manageability 5

Security 15 Security for critical data transactions is


extremely important
Adaptability 10

Scalability 25 Scalability is critical

Total 100

alejandro.fernandez@avaanza.es
Example: Technical Constraints

Technical Gathered Comments


Constraints Data

Existing Coaxial Replace the cabling with


equipment cabling twisted-pair and fiber optics
in the backbone

Bandwidth 64-kbps WAN Select another service provider


availability links with additional links to offer

Application IPX-based Make sure new network


compatibility applications equipment supports IPX

alejandro.fernandez@avaanza.es
Applying a Methodology to Network Design

Characterizing the Existing


Network

alejandro.fernandez@avaanza.es
Network Audit Information Sources

alejandro.fernandez@avaanza.es
Example: Network Audit

alejandro.fernandez@avaanza.es
Network Auditing Tools

• Manual auditing:
– Use monitoring commands on network devices on small
networks
– Use scripting tools to collect information on large
networks
• Use existing management and auditing tools:
– CiscoWorks
– Cisco Secure Scanner
– Third-party tools, such as HP OpenView, Visio Enterprise
Network Tools, NetZoom, IBM Tivoli, WhatsUp Gold,
SNMPc, MRTG, Net Inspector Lite, and so on
• Use other tools to collect relevant information from other
vendor network devices

alejandro.fernandez@avaanza.es
Steps in Analyzing Network Traffic

alejandro.fernandez@avaanza.es
Example: Traffic Analysis

Application #8:
• Description: Accounting software
• Protocol: TCP port 5151
• Servers: 2
• Clients: 50
• Scope: Campus
• Importance: High
• Average rate: 50 kbps with 10-second
bursts to 1 Mbps

alejandro.fernandez@avaanza.es
Requerimientos de las Aplicaciones

 Para determinar el grado de importancia de una


aplicación debemos examinar un minimo de 4
paramentros de la aplicación.

 Retardo de la aplicación para su funcionamiento.


 Jitter máximo que soporta la aplicación.
 Cuanto Ancho de Banda necesita la aplicación.
 Packet loss permitido de la aplicación.

alejandro.fernandez@avaanza.es
Requerimientos de la Aplicación.

Aplicación Retardo Jitter max Ancho de Packet Tipo de Aplicación,


max ms Banda Loss (critica, important ...
Voice

Video

Oracle

SAP

Web

FTP

Aplicación
especifica

alejandro.fernandez@avaanza.es
Requerimientos de la Aplicación.

Aplicación Retardo Jitter max Ancho de Packet Tipo de Aplicación,


max ms Banda Loss (critica, important ...
Voice 150 ms 30 ms 26 kbps 1% critical

Video

Oracle

SAP

Web

FTP

Aplicación
especifica

alejandro.fernandez@avaanza.es
Describing an Existing Network

alejandro.fernandez@avaanza.es
Applying a Methodology to Network Design

Completing the Network


Design

alejandro.fernandez@avaanza.es
Top-Down Design Practices

Start your design here.

Design down the OSI model.

alejandro.fernandez@avaanza.es
Top-Down and Bottom-Up
Approach Comparison

Top-Down Approach Bottom-Up Approach

Benefits • Incorporates • Allows a quick response to


organizational a design request
requirements • Facilitates design based on
• Gives the big picture to previous experience
organization and
designer

Disadvantages • Is more time-consuming • Implements little or no


than bottom-up notion of actual
approach organizational
requirements
• May result in inappropriate
network design

alejandro.fernandez@avaanza.es
Example: Top-Down Voice Design

alejandro.fernandez@avaanza.es
Creating a Network Decision Table

• Decide which network building block requires


decisions.
• Gather possible options for a given situation.
• Create a table that includes possible options and
given requirements.
• Match given requirements with specific properties
of given options.
• Select the option with most matches as the most
appropriate one.

alejandro.fernandez@avaanza.es
Example: Selecting a Routing Protocol

Options OSPF IS-IS IGRP EIGRP RIPv2 Required


Network
Parameters Parameters
Size of Network Large Very Medium Large Medium Large
(Small-Medium- Large
Large-Very Large)
Speed of High High Low Very Medium High
Convergence High
(Very High-High-
Low)
Use of VLSM Yes Yes No Yes Yes Yes
(Yes-No)
Mixed Vendor Yes Yes No No Yes Yes
Devices
(Yes-No)
Network Support Good Poor Good Good Good Good
Staff Knowledge
(Good-Poor)

alejandro.fernandez@avaanza.es
Assessing the Scope of the Network Design
Process

Scope of Design Comments

Entire network All branch office LANs upgraded


to support Fast Ethernet
technology

Campus Redundant equipment and links

WAN Solutions to overcome


bottlenecks

alejandro.fernandez@avaanza.es
Example: Assessing the Scope of the
Network Design Process

• Application—Designing voice
transport
• Network—Designing routing,
addressing
• Physical, data link—Choosing
connection type

alejandro.fernandez@avaanza.es
Structured Design Principles

alejandro.fernandez@avaanza.es
Network Design Tools

alejandro.fernandez@avaanza.es
Example: Planning Design Implementation

Date Description Design Doc. Complete


Time Section
Phase 1 22/04/2005 Install hardware Section 6.2.1 
Step 1 Connect switches Section 6.2.1.1 
Step 1 Install routers Section 6.2.1.2
Step 1 Complete cabling Section 6.2.1.3
Step 1 Verify data link layer Section 6.2.1.4
Phase 2 Configure hardware Section 6.2.2
Step 1 25/04/2005 Configure VLANs Section 6.2.2.1
Step 2 Configure IP addressing Section 6.2.2.2
Step 3 Configure routing Section 6.2.2.3
Phase 2 26/04/2005 Launch into production Section 6.2.3
Step 1 Complete connections Section 6.2.3.1
… …

alejandro.fernandez@avaanza.es
Detailed Structure of a Design Document

alejandro.fernandez@avaanza.es
Structuring and Modularizing the
Network

Designing the Network


Hierarchy

alejandro.fernandez@avaanza.es
Layers in the Hierarchical Model

alejandro.fernandez@avaanza.es
Example: Hierarchical Network

alejandro.fernandez@avaanza.es
Access Layer

• Concentration point at which clients access the


network
• Layer 2 switching in the access layer:
– Defines a single broadcast domain
– Explicitly allows communication between VLANs
• Multilayer switching in the access layer:
– Optimally satisfies the needs of a particular user
through routing, filtering, authentication, security, or
quality of service
– Controls WAN costs using dial-on-demand routing
(DDR) and static routing

alejandro.fernandez@avaanza.es
Distribution Layer

Provides multilayer switching between access and core


layers:
• Provides media transitions
• Aggregates bandwidth by concentrating multiple low-speed access
links into a high-speed core link
• Determines department or workgroup access
• Provides redundant connections for access devices
Implements policy-based decisions:
• Filtering by source or destination address
• Filtering on input or output ports
• Hiding internal network numbers by route filtering
• Static routing
• Security
• Quality of service mechanisms
alejandro.fernandez@avaanza.es
Core Layer

The function of the core layer is to provide


fast and efficent data transport that:
• Forms a high-speed backbone with fast transport
services
• Provides redundancy and fault tolerance
• Offers good manageability
• Avoids slow packet manipulation caused by filters
or other processes

alejandro.fernandez@avaanza.es
Functional Areas of the Enterprise
Composite Network Model

alejandro.fernandez@avaanza.es
Enterprise Composite Network Model
Functional Details

alejandro.fernandez@avaanza.es
Enterprise Campus Functional Area

alejandro.fernandez@avaanza.es
Campus Infrastructure Module

alejandro.fernandez@avaanza.es
Campus Infrastructure: Building Block

alejandro.fernandez@avaanza.es
Campus Infrastructure: Campus Backbone

alejandro.fernandez@avaanza.es
Network Management Module

alejandro.fernandez@avaanza.es
Server Farm Module

alejandro.fernandez@avaanza.es
Edge Distribution Module

alejandro.fernandez@avaanza.es
Network Solution in the Enterprise Campus

alejandro.fernandez@avaanza.es
Network Solution in the Enterprise Campus

alejandro.fernandez@avaanza.es
Network Solution in the Enterprise Campus

alejandro.fernandez@avaanza.es
Network Solution in the Enterprise Campus

alejandro.fernandez@avaanza.es
Network Solution in the Enterprise Campus

alejandro.fernandez@avaanza.es
Enterprise Campus Network
Design Models

Designing Enterprise Campus


requires consideration of:
• Application traffic
• Multicast traffic
• QoS (delay-sensitive traffic)
Campus models
concentrate on:
• Building Access and Building
Distribution
• Campus Backbone
• Server Farm
• Edge Distribution

alejandro.fernandez@avaanza.es
Relative Considerations for the Campus
Design

Campus Infrastructure

Building Building Campus Server Edge


Access Distribution Backbone Farm Distribution
Technology Shared Data Link Data Link Data Link Multilayer Multilayer
Layer Layer/ Layer/ Switched Switched
Switched Multilayer Multilayer
Switched Switched
Scalability High High Medium Low Medium Low
High Low Medium Medium High High Medium
Availability
Performance Low Low Medium High High Medium
Cost/Port Low Low Medium High High Medium

alejandro.fernandez@avaanza.es
Feature and Capability Considerations for
the Campus Design

Campus Infrastructure

Building Building Campus Server Edge


Access Distribution Backbone Farm Distribution
Technology Shared Data Link Data Link Data Link Multilayer Multilayer
Layer Layer/ Layer/ Switched Switched
Switched Multilayer Multilayer
Switched Switched
Traffic Passing Local/ Passing Passing Local/ Passing
Passing Passing
Multicast Limited Limited/ Limited/ Limited/ Limited/
Fully Fully Fully Fully
Supported Supported Supported Supported
QoS Queuing/marking per port
Marking per application

alejandro.fernandez@avaanza.es
Campus Network Traffic Patterns

• Network traffic represents the organizational application


traffic flows.
• Network traffic patterns have changed through the years
in these ways:
– Traditional networks:
• Traditional networks employ the 80/20 rule.
• Servers are located in the workgroup.
• Most of the traffic is local.
– Modern networks:
• Modern networks employ the 20/80 rule.
• Servers are located in a “distant” server farm.
• Most of the traffic is remote.

alejandro.fernandez@avaanza.es
Example: Network Traffic Patterns

alejandro.fernandez@avaanza.es
Patron de Flujos

CCM
1%

4%
38%
30%

22%

5%
62%
alejandro.fernandez@avaanza.es
Multicast Traffic in the Campus Network

• IP multicast delivers a traffic


stream to multiple destinations.
• Considerations on LAN switches:
– Data link layer switches
“flood” a multicast frame
to every port.
– Static entries specify which
ports should receive the
multicast traffic.

alejandro.fernandez@avaanza.es
Relative Network Requirements by
Application Type

Peer-Peer Client- Client- Client-


Distributed Server Farm Enterprise
Servers Edge Servers
Connectivity Shared Switched Switched Switched Switched
Type

Total Required Low Medium Medium High Medium


Throughput

High Low Low Medium High High


Availability

Total Network Low Low Medium High Medium


Costs

alejandro.fernandez@avaanza.es
Example: Client-Server Farm Applications

Typical applications:
• Mail servers
• File servers
• Database servers
Access to applications:
• Fast
• Reliable
• Controlled (security)

alejandro.fernandez@avaanza.es
Example: Client-Distributed
Server Applications

• Servers are located


close to clients.
• Servers and clients
are in the same LAN.
• Request to servers
from nonlocal LANs
is rare.

alejandro.fernandez@avaanza.es
Example: Peer-Peer Applications

• Instant messaging
• File sharing
• Videoconference
systems

alejandro.fernandez@avaanza.es
Example: Client-Enterprise Edge
Applications

Typical applications:
• Internet applications
– Mail servers
– Web servers
– Public Internet servers
• E-commerce
applications

alejandro.fernandez@avaanza.es
Voice Transport

• Two implementations:
– Voice over IP: Transports voice packets over the
IP network using voice-enabled routers
– IP telephony: Implements voice in the network
using Cisco CallManagers and IP Phones
• Both implementations require properly designed
networks.
• All modules of the enterprise network are involved
in the voice network solution.

alejandro.fernandez@avaanza.es
Tráfico de voz sobre ip

 Al menos debemos de pensar que hay dos


tipos de tráfico:
 Señalización por un lado.
 Trafico de importancia media.
 Caminos distintos.
 Varios tipos de aplicaciones, UDP y TCP.
 Trafico de voz sobre ip.
 Trafico de importancia critica.
 Caminos distintos.
 Ancho de banda fijo (variable con VAD).

alejandro.fernandez@avaanza.es
IP Telephony Components

alejandro.fernandez@avaanza.es
Modular Approach in Voice Network Design

alejandro.fernandez@avaanza.es
Example: Voice Network Solution

alejandro.fernandez@avaanza.es
Example: Voice Network Solution

alejandro.fernandez@avaanza.es
Example: Voice Network Solution

alejandro.fernandez@avaanza.es
Example: Voice Network Solution

alejandro.fernandez@avaanza.es
Example: Voice Network Solution

alejandro.fernandez@avaanza.es
Example: Voice Network Solution

alejandro.fernandez@avaanza.es
Evaluating the Existing Data Infrastructure
for Voice Design

Document and evaluate the existing data


infrastructure in each enterprise network
module in terms of:
• New voice performance requirements
• Availability requirements
• Feature requirements
• Potential network capacity or impact

alejandro.fernandez@avaanza.es
Diseño de Voz sobre IP (voz
tradicional)

ESCENARIOS

99
OBTENCION DE VOZ

TRADICIONAL
S1 PPP
VOZ
S0
IP
PPP
Señalización Tradicional
Señalización Analógica.
Señalización Digital.
Señalización IP
Señalización End-to-End
Señalización dependiente de un 3º.
alejandro.fernandez@avaanza.es
Diseño de Voz sobre IP (voz tradicional)

FXS

FXS
VOZ

alejandro.fernandez@avaanza.es
ESCENARIO 2

FXS

FXO FXS
FXS
FXO FXS
FXS VOZ
CENTRALITA
FXS FXO FXO

PSTN

alejandro.fernandez@avaanza.es
ESCENARIO 3

FXS

FXO FXS
FXS
FXO FXS
FXS VOZ
CENTRALITA FXO FXO
FXS

PSTN

alejandro.fernandez@avaanza.es
ESCENARIO 4

FXS

FXS FXO
FXS
FXS FXO
FXS VOZ
CENTRALITA FXO FXO
FXS

PSTN

alejandro.fernandez@avaanza.es
Señalización Analógica

Se entiende que existe una señalización Electrica y


una Lógica

SEÑALIZACIÓN SEÑALIZACIÓN
ELECTRICA LÓGICA
Loop-start
FXS
Ground-start
Loop-start
FXO
Ground-start

alejandro.fernandez@avaanza.es
ESCENARIO 5

FXS

E&M E&M
FXS
E&M E&M
FXS VOZ
CENTRALITA FXO FXO
FXS

PSTN

alejandro.fernandez@avaanza.es
Señalización Analogica E&M

Se entiende que existe


una señalización
Electrica y una Lógica

SEÑALIZACIÓN SEÑALIZACIÓN Nº hilos


ELECTRICA LÓGICA para voz

Tipo 1
Tipo 2 Wink-start 2-hilos
Tipo 3 Delay-dial O
Tipo 4 Inmediate-start 4-hilos
Tipo 5

alejandro.fernandez@avaanza.es
ESCENARIO 6

IP

FXS

FXS E1 E1
FXS SEÑALIZACIÓN CAS VOZ
CENTRALITA E1 E1
FXS

PSTN

alejandro.fernandez@avaanza.es
ESCENARIO 7

FXS

FXS E1 E1
FXS SEÑALIZACIÓN CCS VOZ
CENTRALITA QSIG FXO FXO
FXS

PSTN

alejandro.fernandez@avaanza.es
ESCENARIO 8

S1 PPP
S0
VOZ VOZ
S0 S1

PPP PPP

S1 S0
S0 PPP
S1
VOZ VOZ

alejandro.fernandez@avaanza.es
Señalización en VOIP

 Señalización End-to-End
 H323
H323/SIP
 SIP
S1 PPP S0
VOZ VO
S0 S1
Z

 Señalización dependiente de un Tercero


CCM
 MGCP
MGCP
 SKINNY
SKINNY

alejandro.fernandez@avaanza.es
Clasificación de Tráfico en Telefonía IP

Señalización en IP Telephony
H323 H225 H245 ras

H225 (TCP, 1720) TCP UDP


IP
H245 (TCP, 11000 al 11999)
Level 2
RAS (UDP, 1718 y 1719)
Level 1
SIP
UDP/TCP (5060) SIP
TCP UDP
IP
Level 2
Level 1

alejandro.fernandez@avaanza.es
Señalización en IP Telephony

Señalización dependiente de un
tercero SCCP
 Señalización propietaria TCP
CISCO, SKINNY cliente IP
control protocol, SCCP, Level 2
utiliza puerto 2000 de TCP.
Level 1
 MGCP, Media Gateway
Control Protocol. Utiliza el
protocolo UDP 2427 y TCP
2428 MGCP
TCP UDP
IP
Level 2
Level 1

alejandro.fernandez@avaanza.es
Clasificación tráfico VOIP

Protocolo RTP, real time protocol


 Puertos UDP, 16384-32367 y 49152-65535
Protocolo RTCP, real time control protocol
 Puertos de RTP+1

Voz (20ms)
RTP (12 bytes) RTCP
UDP (8 bytes) UDP
IP (20 bytes) IP
Level 2 ?? Level 2
Level 1 Level 1
alejandro.fernandez@avaanza.es
DSP’s

TRADICIONAL
S1 PPP
VOZ
S0
IP
PPP

DSP’s
procesador de
señal digital
alejandro.fernandez@avaanza.es
Digital signal processor, DSP

 TI 542
 1 conversacion de alta complejidad
 2 conversaciones de media complejidad

 TI 549
 2 conversaciones de alta complejidad
 4 conversaciones de media complejidad

 TI C5510
 TI C5421
alejandro.fernandez@avaanza.es
Tipos de DSP’s

alejandro.fernandez@avaanza.es
Funciones DSP’s

 Decodifica digitos marcados


 Dispara la señalización
 Elimina ruidos
 Activa y desactiva el VAD
 Introduce confort noise y sonido de test
 Elimina ecos
 Realiza la compresion de la voz

alejandro.fernandez@avaanza.es
Diagrama de bloques

? kbps IP

G711 ulaw /PCM

1101010
A/D DSP’s VOZ
64 kbps

Signaling

alejandro.fernandez@avaanza.es
Tipos de compresion

• ADPCM
– Wave form coding scheme
– Adaptive: automatic companding
– Differential: encode changes between
samples only
• ITU standards:
– G.721 rate: 32 kbps = (2 x 4 kHz) x 4 bits/sample
– G.723 rate: 24 kbps = (2 x 4 kHz) x 3 bits/sample
– G.726 rate: 16 kbps = (2 x 4 kHz) x 2 bits/sample

alejandro.fernandez@avaanza.es
Tipos de compresión

• CELP
– Hybrid coding scheme
• High-quality voice at low bit rates, processor
intensive, use of DSPs
• G.728: LD CELP—16 kbps
• G.729: CS-ACELP—8 kbps
– G.729a variant—8 kbps, less processor intensive,
allows two voice channels encoded per DSP

alejandro.fernandez@avaanza.es
Comparativa compresores, G729 / G729a

• Both are ITU standards


• Both are 8 kbps CS-ACELP
• G.729 more complex and processor intensive
• G.729 higher quality than G.729a
• Compression delay the same (10-20 ms)

alejandro.fernandez@avaanza.es
Tipos de codecs

• PCM: pulse code modulation


• G711
• 8000muestras/seg
• 8 bits cuantificación
• Rate = 8000 x 8 = 64 Kbps

alejandro.fernandez@avaanza.es
Tipos de Codecs

• APCM: adaptative pulse code


modulation
• G726
• 8000muestras/seg
• 4 bits cuantificación
• Rate = 8000 x 4 = 32 Kbps

• 2 bits cuantificación
• Rate = 8000 x 2 = 16 kbps
alejandro.fernandez@avaanza.es
Tipos de Codecs

• LD-CELP: predicción lineal con


excitación por codigo bajo retardo
• G728
• Rate = 16 Kbps

• CS-ACELP: predicción lineal con


excitación por codigo algebraico
• G729 ó G729a
• Rate =8 Kbps

alejandro.fernandez@avaanza.es
Tipos de Codecs

• MP-MLQ:
• G723.1
• Rate = 6.3 Kbps

• ACELP
• G723.1
• Rate = 5.3 Kbps

alejandro.fernandez@avaanza.es
Alta o media complejidad

Medium Complexity (4 calls / dsp) High Complexity ( 2 calls / dsp)

G.711 (a-law and m -law) G.728

G.726 (all versions) G.723 (all versions)

G.729a, G.729ab (G.729a AnnexB) G.729, G.729b (G.729-AnnexB)

alejandro.fernandez@avaanza.es
Bandwidth sin cabeceras ip

Standard Bit Rate (Kbps)


G.711, PCM 64
G.726, G.727, ADPCM 16,24,32,40
G.728, LD CELP 16
G.729, CS-ACELP 8
G.729a, CS-ACELP 8

alejandro.fernandez@avaanza.es
Bandwidht con cabeceras

VOZ 20ms ? Bytes, g729 = 20 bytes


RTP 12 bytes
UDP 8 bytes
IP 20 bytes
Level 2 ? bytes
Level 1
20 bytes 8 kbps
20 + 20 + 12 + 8 + L2 bytes X kbps
alejandro.fernandez@avaanza.es
Tabla de decisión según Bandwidth

Codec Information Bandwidth Calculations

Bandwi
Codec Codec
Codec & Mean Voice dth MP Bandwidth
Sample Sample Voice Payload Packets Per Bandwidth
Bit Rate Opinion Payload or w/cRTP MP or
Size Interval Size (Bytes) Second (PPS) Ethernet (Kbps)
(Kbps) Score (MOS) Size (ms) FRF.12 FRF.12 (Kbps)
(Bytes) (ms)
(Kbps)
G.711 (64 82.8
80 Bytes 10 ms 4.1 160 Bytes 20 ms 50 67.6 Kbps 87.2 Kbps
Kbps) Kbps
G.729 (8 26.8
10 Bytes 10 ms 3.92 20 Bytes 20 ms 50 11.6 Kbps 31.2 Kbps
Kbps) Kbps
G.723.1 18.9
24 Bytes 30 ms 3.9 24 Bytes 30 ms 34 8.8 Kbps 21.9 Kbps
(6.3 Kbps) Kbps
G.723.1 17.9
20 Bytes 30 ms 3.8 20 Bytes 30 ms 34 7.7 Kbps 20.8 Kbps
(5.3 Kbps) Kbps
G.726 (32 50.8
20 Bytes 5 ms 3.85 80 Bytes 20 ms 50 35.6 Kbps 55.2 Kbps
Kbps) Kbps

G.726 (24 42.8


15 Bytes 5 ms 60 Bytes 20 ms 50 27.6 Kbps 47.2 Kbps
Kbps) Kbps

G.728 (16 28.5


10 Bytes 5 ms 3.61 60 Bytes 30 ms 34 18.4 Kbps 31.5 Kbps
Kbps) Kbps

alejandro.fernandez@avaanza.es
Retardo Fijo por procesamiento, CODEC

Compression Compression
Bit Rate (kbps) MOS Score
Method Delay (ms)
G.711 PCM 64 4.1 0.75
G.726 ADPCM 32 3.85 1
G.728 LD-CELP 16 3.61 3 to 5
G.729 CS-ACELP 8 3.92 10
G.729 x 2 Encodings 8 3.27 10
G.729 x 3 Encodings 8 2.68 10
G.729a CS-ACELP 8 3.7 10
G.723.1 MP-MLQ 6.3 3.9 30
G.723.1 ACELP 5.3 3.65 30

alejandro.fernandez@avaanza.es
Comparativa Compresores

alejandro.fernandez@avaanza.es
Media Opination Score, MOS

11 22 33 44 55

Rating Speech Quality Level of Distortion


5 Excellent Imperceptible
11 22 33 44 55
4 Good Just perceptible but not annoying
3 Fair Perceptible and slightly annoying
2 Poor Annoying but not objectionable
1 Unsatisfactory Very annoying and objectionable

MOS of 4.0 = Toll Quality


alejandro.fernandez@avaanza.es
Tabla de decision, delay, BW, MOS, etc

Mean
Compress Bit Rate Compress Framing Opinion
Codec Technique (Kbps) MIPS Delay Size Score
G.711 PCM 64 0.34 0.75 0.125 4.1

G.726 ADPCM 32 13 1 0.125 3.85

G.728 LD CELP 16 33 3-5 0.625 3.61

G.729 CS-ACELP 8 20 10 10 3.92

G.729a CS-ACELP 8 10.5 10 10 3.9

G.723.1 MPMLQ 6.3 16 30 30 3.9

G.723.1 ACELP 5.3 16 30 30 3.8

alejandro.fernandez@avaanza.es
Problemas con los ecos

alejandro.fernandez@avaanza.es
Reducir el problema de los ecos

alejandro.fernandez@avaanza.es
Six-Step Design Process

137
Objectives
Upon completion of this lesson, you will be
able to:
• Perform a network audit.
• Set network objectives.
• Review technologies and services.
• Evaluate technical guidelines.
• Perform capacity planning.
• Analyze financial factors.

alejandro.fernandez@avaanza.es
Step 1:
Current Network Audit

• Evaluate the currently network.


• Evaluate the abilities of the IT staff.
• Identify upcoming projects, and determine their
impact on the network.
• If necessary, conduct a traffic study to look at
current traffic patterns.

alejandro.fernandez@avaanza.es
Step 2:
Set Network Objectives

• Determine the dominant traffic type to carry on


the integrated network.
• Set voice quality objectives.
• Consider the expected level of performance from
the integrated network.
• Ask what return on investment or payback period
you are trying to meet.

alejandro.fernandez@avaanza.es
Step 3: Review Technologies
and Services

• Voice over Frame Relay


• Voice over ATM
• Voice over IP

alejandro.fernandez@avaanza.es
Step 4:
Consider Technical Guidelines

• Review the factors that impact voice quality.


• Consider the following components:
– Voice quality, delay, and bandwidth balance
– Acceptable delay and delay variation thresholds
– Delay for the chosen model
– Tandem (or multiple) conversions

alejandro.fernandez@avaanza.es
Voice Compression Types

Codec Type of Coding Data


Type Algorithm Rate Key Features
G.711 Pulse Code 64 Kbps • Supports highest quality voice possible
Modulation (PCM) • Provides no compression
• Provides no bandwidth savings

G.726 Adaptive Differential 32, 24, or • Offers 25 percent cost savings at 32 Kbps over PCM
Pulse Code 16 Kbps • Offers 30 percent cost savings at 24 Kbps over PCM
Modulation (ADPCM) • Offers 35 percent cost savings at 16 Kbps over PCM
• Some fidelity is lost as the compression increases

G.728 Low-Delay 16 Kbps • Models the human voice


CodeExcited Linear- • Offers 35 percent cost savings over PCM
Predictive (LDCELP)

G.729 Conjugate Structure 8 Kbps • Models the human voice


Algebraic Code • Provides eight times the bandwidth savings over PCM
Excited Linear and four times that of 32-Kbps ADPCM
Predictive (CS-ACELP) • Delivers quality comparable to LD CELP and 24-Kbps
ADPCM
• Offers 40 percent cost savings over PCM

alejandro.fernandez@avaanza.es
Voice Quality Guidelines
MOS Values
Score Quality Description of Impairment
5 Excellent Imperceptible
4 Good Just perceptible, not annoying
3 Fair Perceptible and slightly annoying
2 Poor Annoying but not objectionable
1 Bad Very annoying and objectionable

Voice Quality Measurements


Mean Opinion
Codec Type Score Delay (ms)
G.711 4.1 0.75
G.726 3.85 1
G.728 3.61 3-5
G.729 3.92 10
G.729a 3.9 10

alejandro.fernandez@avaanza.es
Delay and Delay Variation

Delay causes two potential impairments to


speech:
• Long delays in conversation cause the receiver to
start to talk before the sender is finished.
• Digital jitter causes gaps in the speech pattern that
cause the quality of voice to sound “jerky.”

alejandro.fernandez@avaanza.es
Voice Delay Guidelines

alejandro.fernandez@avaanza.es
Fixed Delay Components

alejandro.fernandez@avaanza.es
Variable Delay Components

alejandro.fernandez@avaanza.es
Calculating the Delay Budget

Fixed Delay Variable Delay


G.729 coder delay (5 ms look-ahead) 5 ms
G.729 coder delay (10 ms per frame) 20 ms
Packetization delay (included in coder delay)
Queuing delay (64-Kbps trunk) 6 ms
Serialization delay (64-Kbps trunk) 3 ms
Propagation delay (private lines) 32 ms
Network delay
Dejitter buffer 50 ms
Total 110 ms 6 ms

alejandro.fernandez@avaanza.es
Calculating Multiple Conversion Delay
Budgets

Fixed Delay Variable Delay

Delay #1

G.729 coder delay 25 ms

Packetization delay

Queuing delay (64-Kbps trunk) 6 ms

Serialization delay (64-Kbps trunks) 3 ms

Propagation delay (private lines) 32 ms

Dejitter buffer 50 ms

Total Delay #1 110 ms 6 ms

alejandro.fernandez@avaanza.es
Step 5:
Perform Capacity Planning

• Provision line trunks by establishing the


number of trunks from the PBX to the
integrated voice data network.
• Translate the number of trunks to the required
network bandwidth.

alejandro.fernandez@avaanza.es
Provisioning Trunking

Based on:
• Traffic volume and flow
• Selected grade of service
• Company objectives

alejandro.fernandez@avaanza.es
Provisioning Bandwidth

Goal = desired voice quality + grade of


service + cost effectiveness

alejandro.fernandez@avaanza.es
Step 6:
Perform Financial Analysis

Compare benefits against costs:


• Determine if the cost is justified in relation to the
benefits received.
• Calculate the return on the investment.

alejandro.fernandez@avaanza.es
Componentes Telefonía IP

155
Componentes IP Telephony

alejandro.fernandez@avaanza.es
Cisco Call Manager

alejandro.fernandez@avaanza.es
CCM Clustering

alejandro.fernandez@avaanza.es
Gateway de VOIP

Señalización
H323
SIP
MGCP
SKINNY
Intercluster-trunk

alejandro.fernandez@avaanza.es
Servicios

Servicios de MOH
Anunciator
Media termination point, MTP
Transcoder
Conference
Software
Hardware

alejandro.fernandez@avaanza.es
Clientes de Telefonia IP

alejandro.fernandez@avaanza.es

S-ar putea să vă placă și