Professional Documents
Culture Documents
Date: Version:
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. This Application Note is relevant to all Thomson Gateway devices that support video (RTSP and Flexiport) and VoIP (SIP). 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
Applicability:
Updates:
Chapter 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.
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 ...
E-DOC-CTC-20080411-0005 v1.0
Chapter 1
PC
xDSL Modem
Edge Router
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 subscribers device or network through a DSL modem. Next, traffic is sent to the other end of the line, which is located at the telephone companys Central Office (CO). This line consists of the existing copper telephone wires, also called the local loop or last mile.
E-DOC-CTC-20080411-0005 v1.0
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.
E-DOC-CTC-20080411-0005 v1.0
Chapter 2
2 2.1
Network architecture
Following illustration shows the network architecture of the considered Triple-Play scenario:
Video Services
TR-069 ACS
ATM
ATM DSLAM
WWW
Data Services
Voice Network
SIP Server
Voice Services
E-DOC-CTC-20080411-0005 v1.0
Chapter 2
Provided services
The services that are available in the network are: Data services Voice services Video services Remote CPE management
E-DOC-CTC-20080411-0005 v1.0
Chapter 2
2.2
DHCP Relay
DHCP Client
IP Router
IP LocalNetwork
PPP Internet
IP ip_voice
ETH
ETH eth_data
ETH eth_voice
OBC ETH Bridge default (vid=1) internet (vid=2) video (vid=3) voice (vid=4)
FXS1 FXS2
ethif
ATM
atm_Internet
ATM
atm_video
ATM
atm_voice
PVC
pvc_Internet
PVC
v_video
PVC
voice
Data PC
Video STB
E-DOC-CTC-20080411-0005 v1.0
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 2 3 4 5 6 7 8 9 Configure the ATM interfaces. Configure IP QoS. Configure the necessary interface architecture on the Thomson Gateway. Configure the IP addresses. Configure the video services. Configure the data services. Configure the voice services. Configure remote CPE management. 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
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
No IP QoS
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
E-DOC-CTC-20080411-0005 v1.0
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.
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
2.3.4
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 =>:ip =>:ip =>:ip rtadd rtadd rtadd rtadd dst=172.16.10.0/28 intf=ip_voice dst=10.50.2.205/32 intf=ip_voice dst=10.50.2.0/24 intf=ip_voice dst=10.50.7.21/32 intf=ip_voice
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
2.3.5
Configuring IP Addresses
DHCP server
The Thomson Gateway acts as a DHCP 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
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
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.
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.
2.3.8
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.
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 =>:voice =>:voice =>:voice =>:voice =>:voice =>:voice =>:voice =>:voice =>:voice services services services services services services services services services services provision type=hold deactivate type=hold provision type=waiting deactivate type=waiting provision type=clip activate type=clip provision type=clir deactivate type=clir provision type=3pty deactivate type=3pty
The other supplementary services are withdrawn. Withdrawn services are simply not available:
=>:voice =>:voice =>:voice =>:voice =>:voice =>:voice =>:voice =>:voice services services services services services services services services withdraw withdraw withdraw withdraw withdraw withdraw withdraw withdraw type=transfer type=mwi type=forcedFXO type=cfu type=cfnr type=cfbs type=callreturn 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
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
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
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
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:
Thomson Gateway
ATM
ATM DSLAM
ATM Multiplexing
ATM
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:
www.thomson-broadband.com
Coordinates:
Thomson Telecom Prins Boudewijnlaan 47 B-2650 Edegem Belgium
Copyright
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.