Você está na página 1de 20
Triple-Play Using IPoE for Voice, PPPoE for Data and Bridged Video on Multiple PVCs (with

Triple-Play Using IPoE for Voice, PPPoE for Data and Bridged Video on Multiple PVCs (with VLANs)

Date:

April 2008

Version:

v1.0

Abstract:

This Application Note provides technical information on the support of a Triple-Play scenario by Thomson Gateway products. First, a brief introduction to the basic concepts of Triple-Play is presented. Next, a tested and proven scenario shows how the Thomson Gateway can be integrated in a Triple-Play network. The presented scenario uses multiple PVCs, with an IPoE connection for voice traffic, a PPPoE connection for data traffic and a bridged connection for video traffic. RTSP and IGMP are used to support video and SIP is the selected VoIP signalling protocol. This document describes the mechanisms that are used to set up the scenario, the configuration of the Thomson Gateway using CLI commands and an illustration of the resulting configuration.

Applicability:

This Application Note is relevant to all Thomson Gateway devices that support video (RTSP and Flexiport) and VoIP (SIP).

Updates:

Thomson continuously develops new solutions, but is also committed to improving its existing products.

For more information on Thomson's latest technological innovations, documents and software releases, visit us at http://www.thomson-broadband.com

Chapter 1

1 Introduction to Triple-Play

Introduction

In this chapter, we give some background information on Triple-Play. Today, both telecom operators and cable operators are developing their networks to offer the Triple-Play service to the customer. In this introduction, we mainly focus on the delivery of the Triple-Play service by telecom operators using the DSL broadband access technology.

Delivery of multiple services

The term Multi-Play is a general term, used to refer to the delivery of multiple telecommunication services.

Following more specific terms are also used:

Dual-Play: the Dual-Play service refers to the delivery of two services. These services are:

 

Voice and data services in the case of telecom operators.

Video and data services in the case of cable operators.

Triple-Play: the Triple-Play service refers to the delivery of voice, video and data services over a common network infrastructure, with one subscription. To this end, operators add an additional service to their Dual-Play service:

 

Cable operators already provide video and data services and compete with telecom operators to provide voice services.

Telecom operators already provide voice and data services and compete with cable operators to provide video services.

Quadruple-Play: the Quadruple-Play service combines the Triple-Play service with the delivery of wireless services.

Triple-Play services

The term “Triple-Play service” covers a large collection of voice, video and data services, including:

Video telephony

IPTV, which is multicast video

Video on Demand (VoD), which is unicast video

Voice over IP (VoIP)

Gaming

Internet access (HTTP traffic)

E-mail

2

E-DOC-CTC-20080411-0005 v1.0

Chapter 1

Triple-Play DSL network infrastructure

Following illustration shows the typical DSL network infrastructure:

Subscriber’s Premises Local Loop Telephone Ethernet Company’s or Internet Service Provider’s Network Central
Subscriber’s Premises
Local Loop
Telephone
Ethernet
Company’s
or
Internet Service Provider’s
Network
Central Office
ATM Switches
PC
xDSL Modem
DSLAM
PC
xDSL Modem
Access Network
Internet
Edge
BRAS
Router
PC
xDSL Modem
DSLAM
PC
xDSL Modem

This DSL network infrastructure consists of the following key elements:

DSL modem

Digital Subscriber Line Access Multiplexer (DSLAM)

Broadband Remote Access Server (BRAS)

DSL modem

Traffic is sent from the subscriber’s device or network through a DSL modem. Next, traffic is sent to the other end of the line, which is located at the telephone company’s Central Office (CO). This line consists of the existing copper telephone wires, also called the “local loop” or “last mile”.

Digital Subscriber Line Access Multiplexer (DSLAM)

At the CO, the traffic is received by the DSLAM. The DSLAM aggregates the digital data streams coming from numerous DSL modems onto a single high-capacity uplink (ATM or Gigabit Ethernet) towards the Internet Service Provider (ISP). The DSLAM uses multiplexing techniques.

Different DSLAM types exist:

ATM DSLAMs: these DSLAMs have an ATM uplink port.

The first generation ATM DSLAMs are designed as simple Layer 2 ATM multiplexers. They provide a seamless transition from the last mile ATM Permanent Virtual Circuits (PVCs) to a single PVC in the ATM access network. This single PVC is used for all services.

The second generation ATM DSLAMs also have ATM switching capabilities. As a result, they support ATM Switched Virtual Circuits (SVCs) and all of the class of service, traffic shaping and traffic prioritization capabilities inherent with ATM. Different services can use different SVCs.

E-DOC-CTC-20080411-0005 v1.0

3

Chapter 1

Ethernet or IP DSLAM: these DSLAMs have an Ethernet uplink port.

In its simplest implementation, IP DSLAMs function as Layer 2 switches with a limited Layer 3 capability. They support Ethernet VLANs in combination with Ethernet multicast capability (IGMP snooping or proxy support).

The industry trend is definitely towards more advanced Layer 3 functionality on the IP DSLAMs.

Broadband Remote Access Server (BRAS)

The BRAS sits at the core of an ISP’s network, which is a business or organization that provides to customers access to the Internet and related services.

The specific tasks of a BRAS include:

Aggregation point: the BRAS aggregates the output from multiple DSLAMs in the access network.

Router: the BRAS routes traffic into an ISP’s backbone network.

Session termination: the BRAS provides the logical termination of PPP sessions. These may be PPP over Ethernet (PPPoE) or PPP over ATM (PPPoA) encapsulated sessions.

Subscriber management functions: the BRAS provides the interface to authentication, authorization and accounting (AAA) systems. The BRAS is also responsible for assigning session parameters such as IP addresses to the clients. The BRAS is the first IP hop from the client to the Internet.

Policy management and QoS: at the BRAS, an ISP can insert policy management and IP Quality of Service (QoS).

4

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

2

Triple-Play Scenario

2.1

Scenario Overview

Network architecture

Following illustration shows the network architecture of the considered Triple-Play scenario: Video Services DHCP Server
Following illustration shows the network architecture of the considered Triple-Play scenario:
Video Services
DHCP Server
Video Server
TR-069 ACS
for Video
- Unicast
- Multicast
BRAS
Triple-Play - multiple PVCs - ATM DSLAM
& Router
Video Service
FTP, HTTP Servers
Router
Data Service
ATM
Router
DNS and SNTP Server
RADIUS
ATM
Voice Service
Router
DSLAM
WWW
Data Services
Voice Network
DHCP Server
SIP Server
for Voice
Voice Services

Digital Subscriber Line Access Multiplexer (DSLAM)

In the network, an ATM DSLAM is used. The ATM DSLAM uses ATM multiplexing and multiplexes all received PVCs into a single PVC on its uplink. This PVC is terminated in the BRAS.

E-DOC-CTC-20080411-0005 v1.0

5

Chapter 2

Broadband Remote Access Server (BRAS)

The BRAS also serves as a Router. Three virtual routers have been configured in the BRAS:

Video Service Router for video traffic

Data Service Router for data traffic

Voice Service Router for voice traffic

These virtual routers are totally isolated from each other. This isolation provides security and non- interference between the three types of services (data, voice and video).

The BRAS and its three virtual routers provide access to the different services via different service VLANs. For example, one VLAN is used between the Video Service Router and the Video Server, another VLAN is used between the Data Service Router and the FTP Server, and so on.

Provided services

The services that are available in the network are:

Data services

Voice services

Video services

Remote CPE management

6

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

2.2 Thomson Gateway Configuration

Target configuration scheme

In order to set up the scenario, we configure the Thomson Gateway as shown in following illustration. The illustration also explains how the data, voice and video streams are handled by the Thomson Gateway.

DHCP Server LAN_private 192.168.1.[64-253] DHCP Relay DHCP Client IP Router IP LocalNetwork PPP Internet IP
DHCP Server
LAN_private
192.168.1.[64-253]
DHCP Relay
DHCP Client
IP Router
IP LocalNetwork
PPP Internet
IP ip_voice
PPP
Relay
VoIP
Module
ETH
ETH eth_data
ETH eth_voice
OBC
ETH Bridge
default (vid=1)
internet (vid=2)
video (vid=3)
voice (vid=4)
1234
ethport
Data
Voice
FXS1
FXS2
1234
ethif
Video
ATM
ATM
ATM
atm_Internet
atm_video
atm_voice
PVC
PVC
PVC
pvc_Internet
v_video
voice
Voice
Data
Video
Analogue
PC
STB
br_Internet
br_video
br_voice

Phone

E-DOC-CTC-20080411-0005 v1.0

7

Chapter 2

2.3 Practical Realization

Mechanisms

To set up this scenario, we use following mechanisms:

Use of three extra VLANs for data, video and voice traffic

DHCP server for the data PC

DHCP client on behalf of the analogue phone

SNTP and DNS

SIP as VoIP signalling protocol

CWMP for remote CPE management

Configuration overview

Following configuration steps have to be performed to configure the Thomson Gateway for this scenario:

1 Configure the ATM interfaces.

2 Configure IP QoS.

3 Configure the necessary interface architecture on the Thomson Gateway.

4 Configure the IP addresses.

5 Configure the video services.

6 Configure the data services.

7 Configure the voice services.

8 Configure remote CPE management.

9 Save the configuration.

These steps are described in following subsections, explaining the used Command Line Interface (CLI) commands. To test this scenario, the Thomson TG716v5 Release 6.2.17.5 was used.

2.3.1 ATM Interfaces

ATM phone book

Three PVCs (ATM connections) are used. Following three entries are added to the ATM phone book (the VPI/ VCI values are indicative):

=>:atm phonebook add name=pvc_Internet addr=8.35 =>:atm phonebook add name=voice addr=0.65 =>:atm phonebook add name=v_video addr=0.48

8

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

ATM interfaces

Three ATM interfaces are created on top of the phone book entries, one for each PVC. The upper layer protocol for the ATM interfaces is set to MAC (Ethernet), as these ATM interfaces will be connected to the bridge:

=>:atm ifadd intf=atm_Internet =>:atm ifconfig intf=atm_Internet dest=pvc_Internet ulp=mac =>:atm ifattach intf=atm_Internet

=>:atm ifadd intf=atm_voice =>:atm ifconfig intf=atm_voice dest=voice ulp=mac =>:atm ifattach intf=atm_voice

=>:atm ifadd intf=atm_video =>:atm ifconfig intf=atm_video dest=v_video ulp=mac =>:atm ifattach intf=atm_video

2.3.2 IP QoS

No IP QoS

In contrast to a network setup with a single PVC, the classification of IP packets and IP QoS support are not required as different traffic streams (data, voice, video) are sent over different PVCs. IP QoS is not enabled for the three created PVCs. As a result, all data packets forwarded to a PVC are sent to a single queue for that PVC.

2.3.3 Configuring Ethernet Interfaces

Ethernet interfaces on the bridge

The configuration of the Ethernet bridge and the Ethernet (LAN and WAN) interfaces includes following steps:

Configuration of the bridge: the use of a filter on the Ethernet WAN interfaces is disabled. As a result, all broadcasts are allowed to the WAN interfaces. An example of these broadcasts are the DHCP requests sent by the DHCP client on the Thomson Gateway.

The use of VLANs on the bridge is enabled. Later on, we will define additional VLANs on the bridge.

=>:eth bridge config filter=none vlan=enabled

E-DOC-CTC-20080411-0005 v1.0

9

Chapter 2

Ethernet WAN interfaces on the bridge: three Ethernet WAN interfaces are created on the bridge. Each interface is connected to the corresponding ATM interface.

=>:eth bridge ifadd intf=br_Internet =>:eth bridge ifconfig intf=br_Internet dest=atm_Internet =>:eth bridge ifattach intf=br_Internet

=>:eth bridge ifadd intf=br_voice =>:eth bridge ifconfig intf=br_voice dest=atm_voice =>:eth bridge ifattach intf=br_voice

=>:eth bridge ifadd intf=br_video =>:eth bridge ifconfig intf=br_video dest=atm_video =>:eth bridge ifattach intf=br_video

Ethernet LAN interfaces on the bridge: by default, four Ethernet LAN interfaces already exist on the bridge, namely ethport1, ethport2, ethport3 and ethport4. Each of these interfaces is connected to a physical interface, ethif1, ethif2, ethif3 and ethif4 respectively.

Virtual Local Area Networks (VLANs)

The configuration of VLANs is organized as follows:

Three new VLANs are created. The default VLAN learning constraint is not added. This means that independent VLAN learning is used for each VLAN.

=>:eth vlan add name=internet vid=2 addrule=disabled =>:eth vlan add name=video vid=3 addrule=disabled =>:eth vlan add name=voice vid=4 addrule=disabled

Each Ethernet WAN interface is added to its corresponding VLAN and explicitly deleted from the default VLAN. The internal OBC interface is added to the three new VLANs as tagged member.

=>:eth bridge vlan ifadd name=internet intf=br_Internet =>:eth bridge vlan ifadd name=voice intf=br_voice =>:eth bridge vlan ifadd name=video intf=br_video

=>:eth bridge vlan ifdelete name=default intf=br_Internet =>:eth bridge vlan ifdelete name=default intf=br_voice =>:eth bridge vlan ifdelete name=default intf=br_video

=>:eth bridge vlan ifadd name=internet intf=OBC untagged=disabled =>:eth bridge vlan ifadd name=video intf=OBC untagged=disabled =>:eth bridge vlan ifadd name=voice intf=OBC untagged=disabled

No Flexiport mechanism

We could use the Flexiport mechanism to recognize on-the-fly to which Ethernet LAN interface the STB is connected and to map this interface to the video VLAN. However, we describe here a solution without the Flexiport mechanism.

The Ethernet LAN interface ethport2 is added to the video VLAN and is explicitly deleted from the default VLAN. This means that the STB must be connected to ethport2.

=>:eth bridge vlan ifadd name=video intf=ethport2 =>:eth bridge vlan ifdelete name=default intf=ethport2

10

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

Logical Ethernet interfaces

Two new logical Ethernet interfaces are created. Both interfaces have the bridge as destination. One interface is assigned to the data VLAN, the other one to the voice VLAN.

=>:eth ifadd intf=eth_data =>:eth ifconfig intf=eth_data dest=bridge vlan=internet =>:eth ifattach intf=eth_data

=>:eth ifadd intf=eth_voice =>:eth ifconfig intf=eth_voice dest=bridge vlan=voice =>:eth ifattach intf=eth_voice

2.3.4 Configuring IP and PPP Interfaces

IP interfaces

The default IP interface LocalNetwork is used and a new IP interface ip_voice is created. An appropriate MAC address is assigned to this interface:

=>:ip ifadd intf=ip_voice dest=eth_voice =>:ip ifconfig intf=ip_voice hwaddr=02:14:7f:00:00:5e =>:ip ifattach intf=ip_voice

Several static entries are added to the IP forwarding table for the Voice Network:

=>:ip rtadd dst=172.16.10.0/28 intf=ip_voice =>:ip rtadd dst=10.50.2.205/32 intf=ip_voice =>:ip rtadd dst=10.50.2.0/24 intf=ip_voice =>:ip rtadd dst=10.50.7.21/32 intf=ip_voice

In addition, an entry is added to the ARP (Address Resolution Protocol) cache:

=>:ip arpadd intf=LocalNetwork ip=192.168.1.72 hwaddr=00:00:00:00:00:04

PPPoE interface

The logical data Ethernet interface is added to the PPP relay list. An appropriate MAC address, which differs from the MAC address of the IP interface ip_voice, is assigned to this interface.

=>:ppp relay ifadd intf=eth_data =>:ppp relay ifconfig intf=eth_data hwaddr=00:14:7f:00:00:5e

Next, a new PPP interface is created and connected to the PPP relay. The username and the password for PAP/CHAP authentication are also specified:

=>:ppp ifadd intf=Internet =>:ppp ifconfig intf=Internet dest=RELAY user=user@inet password=pwdinet

E-DOC-CTC-20080411-0005 v1.0

11

Chapter 2

A default route to the PPP interface will be added to the IP forwarding table as soon as the PPPoE session is

established. Also, Network Address Translation (NAT) is enabled on the PPP interface.

=>:ppp rtadd intf=Internet dst=0.0.0.0/0 src=0.0.0.0/0 metric=1 =>:nat ifconfig intf=Internet translation=enabled

In addition, the following address mapping template is created:

=>:nat tmpladd intf=Internet outside_addr=0.0.0.1 inside_addr=192.168.1.72 weight=10

Now, the PPP interface can be attached:

=>:ppp ifattach intf=Internet

2.3.5 Configuring IP Addresses

DHCP selection rules

No DHCP selection rules are defined.

DHCP server

The Thomson Gateway acts as a DH CP server for the data PC. To this end, the default DHCP pool LAN_private is used, which requires no extra configuration. This DHCP pool only leases IP addresses in response to DHCP requests received on the IP interface LocalNetwork.

DHCP relay

By default, the DHCP relay is already enabled for the IP interface LocalNetwork. This means that the DHCP relay handles DHCP requests that are received on this interface.

When the DHCP relay receives a DHCP request, it looks in its DHCP relay forward list for an appropriate entry. By default, the entry LocalNetwork_to_127.0.0.1 is already created. If this entry is hit, the DHCP request is forwarded to the local DHCP server.

DHCP client

In order to access the Voice Network, the Thomson Gateway uses a DHCP client to obtain an IP address from

the DHCP server in the Voice Service Router. Following configuration steps are necessary:

DHCP client: the DHCP client is configured to request an IP address for the IP interface ip_voice. When the DHCP client receives an IP address, entries are added to the IP forwarding table.

=>:dhcp client ifadd intf=ip_voice =>:dhcp client ifconfig intf=ip_voice metric=1 dnsmetric=0 =>:dhcp client ifattach intf=ip_voice

12

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

Options to be transmitted: the DHCP client can send DHCP options to the DHCP server, indicating desired configuration values. The options are limited to a single option to be transmitted: the DHCP client requests a specific IP address:

=>:dhcp client txoptions add intf=ip_voice option=dhcp-requested-address value=(addr)172.16.10.19 index=1

2.3.6 Configuring Video Services

Introduction

All video streams (both multicast and unicast) are obtained from the same Video Server.

Multicast video: the Internet Group Management Protocol (IGMP) is used to support multicast video.

Unicast video: the Real Time Streaming Protocol (RTSP) is used to support unicast video. The support of unicast video requires no extra configuration of the Thomson Gateway.

No IGMP configuration

The Thomson Gateway uses the bridged scenario for the video services. Hence, the IGMP proxy mechanism

is not used in this scenario.

Only the Ethernet LAN interface to which the STB is connected is part of the video VLAN. The other Ethernet LAN interfaces are part of the default VLAN. As a result, the use of IGMP snooping is also not required.

2.3.7 Configuring Data Services

Introduction

A Point-to-Point Protocol over Ethernet (PPPoE) session is used to access the data services. This PPPoE

session is initiated by the PPPoE client in the Thomson Gateway and is terminated in the BRAS. The PPPoE server is located in the BRAS itself. The PPP request is authenticated in the external RADIUS server, by the use of either PAP or CHAP. Once the PPP request is authenticated, the BRAS gives an IP address from its PPPoE pool to the Thomson Gateway.

Simple Network Time Protocol (SNTP)

The Simple Network Time Protocol (SNTP) is a simplified form of the Network Time Protocol (NTP), used to synchronize computer clocks in the Internet. The internal Thomson Gateway real time clock (SNTP client) will be synchronized with an NTP server.

Enable the SNTP service:

=>:service system modify name=SNTP state=enabled

E-DOC-CTC-20080411-0005 v1.0

13

Chapter 2

NTP server : two NTP servers are added to the NTP server list. To this end, the IP address of each NTP server is specified, as well as the SNTP version of the NTP server.

=>:sntp add addr=10.50.2.20 version=3 =>:sntp add addr=11.0.0.138 version=3

SNTP client: the SNTP client on the Thomson Gateway is enabled by default.

Domain Name System (DNS)

The most basic use of the Domain Name System (DNS) is to translate user-friendly domain names and host names to computer-friendly IP addresses.

The DNS service is enabled by default

DNS client: the DNS client sends DNS requests to the internal DNS server (or DNS resolver). By default, the internal DNS server is defined.

DNS server: the internal DNS server either translates a host name to the correct IP address or forwards the DNS request to an external DNS server. The host name “isp” is added to the list of host names. Three remote DNS server errors are suppressed.

=>:dns server host add name=isp addr=0.0.0.0 ttl=1200 =>:dns server config suppress=3

2.3.8 Configuring Voice Services

Introduction

In this scenario, the selected Voice over IP (VoIP) signalling protocol is the Session Initiation Protocol (SIP). SIP is an application-layer signalling protocol that can establish, modify, and terminate multimedia sessions such as Internet telephony calls.

Voice over IP (VoIP)

An analogue telephone is connected to the Thomson Gateway via an FXS port. In order to use VoIP, the Thomson Gateway must act as a SIP User Agent on behalf of the FXS port. To do so, the VoIP service must be enabled:

=>:service system modify name=VOIP_SIP state=enabled

SIP user agent

In order to support VoIP and SIP, the following parameters must be configured:

VoIP:

Dual-Tone Multi-Frequency (DTMF) information: DTMF information is sent according to RFC 2833.

Port range: the port range that can be used by the RTP/RTCP protocol is set from 10 000 through 12 000.

14

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

Interface: the voice application is configured with the voice-if interface as static interface. This means that the IP address of this interface is used as the source IP address of voice messages.

=>:voice config digitrelay=rfc2833 rtp_portrange=10000-12000 static_intf=enabled intf=voice-if

SIP proxy server and registrar:

The primary proxy address identifies the outbound proxy server. In addition, the proxy port defines the outbound proxy port.

In a similar way, a primary registrar address and registrar port are configured.

 

=>:voice sip config primproxyaddr=10.50.7.21 proxyport=sip =>:voice sip config primregaddr=10.50.7.21 regport=sip

Session keep-alive mechanism: SIP does not define a keep-alive mechanism for the sessions it establishes. RFC 4028 defines an extension to SIP. This extension allows a periodic refresh of SIP sessions through session refresh requests. The extension defines two important timers:

Session interval: the maximum amount of time that can occur between session refresh requests before the session will be considered timed out. The value of this timer is set to 120 s.

Minimum timer: as a lot of session refresh requests results in a lot of processing load, all elements (Proxy, UAC, UAS) can have a configured minimum value for the session interval that they are willing to accept.

 

=>:voice sip config min-se=90 session-expires=120

Voice profile: voice profiles are used to assign specific phone numbers to local voice ports (FXS 1 or FXS 2) or to define a common number. In this scenario, only a common number is configured. The string entered as SIP-URI is used as user name in the Address of Record (AoR).

=>:voice profile add SIP_URI=1234 voiceport=COMMON

Voice codecs

By default, the codec capability of the Thomson Gateway is configured to support codecs G.711 µ-law (North America and Japan) and G.711 A-law (Europe and the rest of the world).

The codec G.711 A-law is configured with the highest priority.

=>:voice codec config type=g711a priority=1 status=enabled =>:voice codec config type=g711u priority=2 status=enabled

Supplementary services

Following supplementary services are provisioned in this scenario. A provisioned service can be activated or deactivated:

Call hold service

Call waiting service

CLIP service: this service includes both the Calling Line Identification Presentation (CLIP) and the Calling Name Identification Presentation (CNIP).

CLIR service: this service includes both the Calling Line Identification Restriction (CLIR) and the Calling Name Identification Restriction (CNIR).

Three party service

E-DOC-CTC-20080411-0005 v1.0

15

Chapter 2

CLIR on call service: the CLIR on call service is automatically provisioned AND activated when the CLIR service is provisioned. It is also assigned the same service code.

Call waiting on call service: the Call waiting on call service is automatically provisioned AND activated when the Call waiting service is provisioned. It is also assigned the same service code.

=>:voice services provision type=hold =>:voice services deactivate type=hold =>:voice services provision type=waiting =>:voice services deactivate type=waiting =>:voice services provision type=clip =>:voice services activate type=clip =>:voice services provision type=clir =>:voice services deactivate type=clir =>:voice services provision type=3pty =>:voice services deactivate type=3pty

The other supplementary services are withdrawn. Withdrawn services are simply not available:

=>:voice services withdraw type=transfer =>:voice services withdraw type=mwi =>:voice services withdraw type=forcedFXO =>:voice services withdraw type=cfu =>:voice services withdraw type=cfnr =>:voice services withdraw type=cfbs =>:voice services withdraw type=callreturn =>:voice services withdraw type=ccbs

By default, a prefix service code is assigned to an action on a supplementary service. For example, the service code 94 is assigned to the call hold service. Automatically the prefix service code *94/#94 is used to activate/ deactivate the service.

Following parameters are configured:

CWreply: if the call waiting service is provisioned and activated, the served user is informed of the incoming call. In addition, the calling user receives an 180 response, which indicates the ring tone.

The CLIR format is set to non-standard. This means that the following address appears in the From:

anonymous<SIP:user name@domain name>. This format might be required for billing reasons.

=>:voice sip config CWreply=180 =>:voice sip config clirformat=nonstandard

FXS port configuration

The Foreign eXchange Station ports (FXS1 and FXS2) support an analogue line end point.

Dialling of a number is considered ended when the interdigit timer (IDT) expires. Two interdigit timers are configured:

The interdigit timer, i.e. the maximum allowable time between the dialling of digits, is set to 4 s.

The interdigit timer for open numbering is set to 5 s. An entry of the dial plan belongs to an open numbering scheme if the minimum number of digits differs from the maximum number of digits. Once the minimum number of digits has been reached and an open numbering scheme is used, the interdigit timer is set to this value.

=>:voice fxsport config interdigit=4000 interdigitOpen=5000

16

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

Dial plan

To obtain an overview of the dial plan on the Thomson Gateway, use following command:

=>:voice dialplan list

The dial plan is mainly used for outgoing calls. These entries must be explicitly created. An entry is created by configuration of following parameters:

The prefix: for example 01.

The default outgoing port: this parameter is set to VoIP.

The fallback mechanism: as the FXO port is not used in this scenario, the fall-back mechanism is disabled and no fall-back outgoing port is configured.

The priority: the main reason to add entries to the dial plan is to give the corresponding calls a high priority.

The minimum and maximum number of digits: for example, these parameters are set to 10. As the minimum number of digits equals the maximum number of digits, the entry belongs to a closed numbering scheme. This means that the called number must have the correct prefix and have exactly 10 digits to hit the entry.

The action: if the collected digits contain an end-of-number indication (#) and the action is ROUTE_excl_eon, the end-of-number indication is not sent out.

Other parameters: when an entry is hit, the outgoing call is set up (routed). It can be configured that the dialled numbers are modified. In this example, the dialled numbers are not modified.

For example, following entry is created:

=>:voice dialplan add prefix=01 defaultport=VoIP fallbackport=NA priority=High fallback=disabled minimumdigits=10 maximumdigits=10 posofmodify=0 remnumdigits=0 insert="" rescan=no data=no action=ROUTE_excl_eon

Country settings

Several voice related configuration parameters, for example tones for tone generation, are specified for multiple countries in a binary file. A country must be selected from the country list.

=>:voice country config country=france1

2.3.9 Remote CPE Management

Introduction

TR-069 (Technical Report 069), which is specified by the DSL-Forum, defines the CPE WAN Management Protocol (CWMP). CWMP is used for remote management of the Thomson Gateway.

CWMP supports the communication between the following network elements:

Customer Premises Equipment (CPE), which is the Thomson Gateway in this scenario

Auto Configuration Server(s) (ACS), which is the TR-069 ACS in this scenario

The TR-069 ACS can be accessed over PPP. To this end, the PPPoE session that is set up for the data services is reused. The PPPoE session is initiated by the PPPoE client in the Thomson Gateway and is terminated in the BRAS.

E-DOC-CTC-20080411-0005 v1.0

17

Chapter 2

Enabling CWMP

In order to allow remote management of the Thomson Gateway by the TR-069 ACS, the use of CWMP on the Thomson Gateway is enabled.

=>:cwmp config state=enabled

HTTP session set up

The Thomson Gateway must be configured with the HTTP URL of the TR-069 ACS. This URL contains an IP address. The username and password can also be configured to enable authentication of the Thomson Gateway by the TR-069 ACS:

=>:cwmp server config url=http://10.50.2.75:8085/ACS username="" password=""

Connection set up

The initiative to establish a connection can be taken by the CPE or the ACS. To enable ACS connection initiation, the path to reach the Thomson Gateway can be specified, as well as the username and the password the TR-069 ACS must use to log in:

=>:cwmp config connectionRequest=enabled connectionReqPath="" connectionReqUserName="" connectionReqPsswd="" connectionReqAuth=none

2.3.10 Save the Configuration

Save the configuration

To make your changes pe rmanent, save the configuarion as follows:

=>:saveall

18

E-DOC-CTC-20080411-0005 v1.0

Chapter 2

2.4 Expected Results

Overview

An overview of the scenario is shown in following illustration:

Video Service Router Data Service 8/35 Router pvc_Internet 0/65 voice Voice Service Router 0/48 v_video
Video Service
Router
Data Service
8/35
Router
pvc_Internet
0/65 voice
Voice Service
Router
0/48 v_video
Thomson
ATM
BRAS
Gateway
DSLAM
& Router
ATM
ATM
ATM
MAC Address
Multiplexing
Classification

ATM layer

Traffic is sent over different PVCs, which are initiated in the Thomson Gateway and terminated in the ATM DSLAM. Following PVCs are used:

PVC pvc_Internet for data (PPP signalling and data traffic)

PVC voice for VoIP (DHCP signalling and voice traffic)

PVC video for video (DHCP signalling, bidirectional unicast traffic, multicast traffic and STB management)

The ATM DSLAM uses ATM multiplexing to multiplex the three received PVCs into a single PVC on its uplink. This PVC is terminated in the BRAS.

MAC addresses

The BRAS uses MAC Address Classification to classify the different streams. Next, the BRAS routes the different streams over different service VLANs in the backbone network.

Following MAC addresses are used:

Data streams: the packets of the data streams are sent over the PPP relay interface towards the backbone network. As a result, they will use the MAC address of this interface as their MAC address.

Voice streams: all voice related traffic uses a local USB MAC address, that is the MAC address of the DHCP client in the Thomson Gateway.

Video streams use the MAC address of the STB itself.

E-DOC-CTC-20080411-0005 v1.0

19

Visit us at:

Coordinates:

Thomson Telecom

Prins Boudewijnlaan 47 B-2650 Edegem Belgium

Copyright

Prins Boudewijnlaan 47 B-2650 Edegem Belgium Copyright ©2008 Thomson. All rights reserved. The content of this

©2008 Thomson. All rights reserved. The content of this document is furnished for informational use only, may be subject to change without notice, and should not be construed as a commitment by Thomson. Thomson assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. The information contained in this document represents the current view of Thomson on the issues discussed as of the date of publication. Because Thomson must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Thomson, and Thomson cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. Thomson MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.