advanced training

THOMSON™ Triple Play

Author: Thomson Presales

Date: April 2023

Version: v1.0

Abstract: This document provides a technical overview on the triple play scenario presented on the Customer Training of November 2008. The goal of the training is to build up a complete triple play scenario based on the requirements defined by a fictive ISP.

Applicability: This document applies to all Thomson Gateway devices having both Ethernet and DSL as a physical WAN connection. It can be used as a reference for similar scenarios.


2 v1.0


Contents

1 Before we start......................................................................................3

2 TGlite.....................................................................................................4

2.1 Requirements................................................................................................................................. 4

2.2 Configuration Guidelines..............................................................................................................4

2.2.1 DSL Connectivity......................................................................................................................... 4

2.2.2 ETH Connectivity......................................................................................................................... 7

2.2.3 CWMP Configuration................................................................................................................... 8

3 TGvideo.................................................................................................9

3.1 Video Requirements...................................................................................................................... 9

3.2 STS file explained.......................................................................................................................... 9

4 TGplus.................................................................................................13

4.1 Basic requirements..................................................................................................................... 13

4.2 Advanced requirements..............................................................................................................14

4.3 Configuration Guidelines............................................................................................................15

4.3.1 Connection Part......................................................................................................................... 15

4.3.2 Basic Requirements Guidelines.................................................................................................17

4.3.3 Advanced requirements Guidelines...........................................................................................18

v1.0 3


1 BEFORE WE START

1 Make sure you are using R8.2.1.2

2 Reset to factory defaults

:system reset factory=yes proceed=yes

3 Flush the default connection

:ppp relay flush:ppp flush:eth flush:atm flush:atm phonebook flush

4 Some more to get started

:env set var=SESSIONTIMEOUT value=0:ip ipdelete addr=10.0.0.138:wireless ifconfig state=disabled

4 v1.0


2 TGLITE

In this chapter we set up the initial base configuration proposed by the ISP. This configuration will serve basic internet and remote management capabilities.

2.1 Requirements

* All requirements stated below have to be functional on both the ETH and DSL interface.

> 1 IPoE interface for Internet (dsl: pvc=8/40, eth: untagged)

> 1 IPoE interface for Management (dsl: pvc=8/37, eth: vlan=14)

> Ensure the traffic flow over the correct interface

> Preconfigure the ACS server

▪ Host: http://acs.tg.com:7547

▪ No authentication is required on connection request

▪ Periodic Inform Interval: 120 seconds

2.2 Configuration Guidelines

2.2.1 DSL Connectivity

1 Add the PVC Phonebook entries

:atm phonebook add name=pvc_data addr=8*40:atm phonebook add name=pvc_mgmt addr=8*37

2 Add the ATM interfaces

:atm ifadd intf=atm_data:atm ifconfig intf=atm_data dest=pvc_data:atm ifattach intf=atm_data

:atm ifadd intf=atm_mgmt:atm ifconfig intf=atm_mgmt dest=pvc_mgmt:atm ifattach intf=atm_mgmt

v1.0 5

http://acs.tg.com:7547/


3 Add the ETH interfaces

:eth ifadd intf=eth_internet:eth ifconfig intf=eth_internet dest=atm_data wan=enabled:eth ifattach intf=eth_internet

:eth ifadd intf=eth_mgmt:eth ifconfig intf=eth_mgmt dest=atm_mgmt wan=enabled:eth ifattach intf=eth_mgmt

4 Add the IP interfaces

:ip ifadd intf=ip_internet dest=eth_internet:ip ifattach intf=ip_internet

:ip ifadd intf=ip_mgmt dest=eth_mgmt:ip ifattach intf=ip_mgmt

5 Enable DHCP on the IP interfaces

:dhcp client ifadd intf=ip_internet:dhcp client ifadd intf=ip_mgmt

6 Configuring the options for the DHCP Clients

:dhcp client rqoptions add intf=ip_internet option=51:dhcp client rqoptions add intf=ip_internet option=58:dhcp client rqoptions add intf=ip_internet option=59:dhcp client rqoptions add intf=ip_internet option=1:dhcp client rqoptions add intf=ip_internet option=3:dhcp client rqoptions add intf=ip_internet option=6 :dhcp client rqoptions add intf=ip_mgmt option=51:dhcp client rqoptions add intf=ip_mgmt option=58:dhcp client rqoptions add intf=ip_mgmt option=59:dhcp client rqoptions add intf=ip_mgmt option=1:dhcp client rqoptions add intf=ip_mgmt option=3:dhcp client rqoptions add intf=ip_mgmt option=6

7 Create a rule which classifies traffic being management based on the destination address.

:label rule add chain=rt_user_labels srcintf=!wan name=mgmt_routing dstip=172.30.104.0/24 log=disabled state=enabled label=Management

8 Add the label to the Management DHCP Client. This will add a label to the default route created by the DHCP client. This label will ensure that only management traffic will be able to use this route.

:dhcp client ifconfig intf= ip_mgmt label=Management

6 v1.0


9 Attach the DHCP Clients and retrieve an IP address.

:dhcp client ifattach intf=ip_internet:dhcp client ifattach intf=ip_mgmt

10 Enable NAT on both interfaces

:nat ifconfig intf=ip_internet translation=enabled:nat ifconfig intf=ip_mgmt translation=enabled

v1.0 7


2.2.2 ETH Connectivity

1 Create a vlan for Management

:eth vlan add name=vlan_mgmt vid=14

Create an ETH interface on top of the physical "ethif5" interface

:eth ifadd intf=eth_wan:eth ifconfig intf=eth_wan dest=ethif5 wan=enabled:eth ifattach intf eth_wan

2 Add the ETH interfaces for Management and Internet, associated with their VLAN

:eth ifadd intf=eth_mgmt_5:eth ifconfig intf=eth_mgmt_5 dest=eth_wan vlan=vlan_mgmt wan=enabled:eth ifattach intf eth_mgmt_5

3 Add the IP interfaces for Management and Internet

:ip ifadd intf=ip_internet_5 dest=eth_wan:ip ifattach intf ip_internet_5

:ip ifadd intf=ip_mgmt_5 dest=eth_mgmt_5:ip ifattach intf ip_mgmt_5

4 Add DHCP client on the IP interfaces

:dhcp client ifadd intf=ip_internet_5:dhcp client ifadd intf=ip_mgmt_5


:dhcp client rqoptions add intf=ip_internet_5 option=51:dhcp client rqoptions add intf=ip_internet_5 option=58:dhcp client rqoptions add intf=ip_internet_5 option=59:dhcp client rqoptions add intf=ip_internet_5 option=1:dhcp client rqoptions add intf=ip_internet_5 option=3:dhcp client rqoptions add intf=ip_internet_5 option=6

:dhcp client rqoptions add intf=ip_mgmt_5 option=51:dhcp client rqoptions add intf=ip_mgmt_5 option=58:dhcp client rqoptions add intf=ip_mgmt_5 option=59:dhcp client rqoptions add intf=ip_mgmt_5 option=1:dhcp client rqoptions add intf=ip_mgmt_5 option=3

8 v1.0


:dhcp client rqoptions add intf=ip_mgmt_5 option=6

6 Add the label to the Management DHCP Client. This will add a label to the default route created by the DHCP client. This label will ensure that only management traffic will be able to use this route.

:dhcp client ifconfig intf= ip_mgmt_5 label=Management


:dhcp client ifattach intf=ip_internet_5:dhcp client ifattach intf=ip_mgmt_5


:nat ifconfig intf=ip_internet_5 translation=enabled:nat ifconfig intf=ip_mgmt_5 translation=enabled

2.2.3 CWMP Configuration

1 Configure CWMP (TR069) to address the correct ACS server each 120 seconds

:cwmp config periodicInfInt=120 connectionRequest=enabled connectionReqAuth=none:cwmp server config url=http://acs.tg.com/:service system modify name=CWMP-C state=enabled routelabel=Management

v1.0 9


3 TGVIDEO

In the last chapter we ended by configuring the ACS server. This will make the gateway contacting the ACS server allowing it to be managed. In this chapter we will upgrade our TGlite service with the TGvideo service, offering fully routed video on all ethernet ports using IGMP proxying and snooping.

In order to provision the gateway with the video configuration we will create an .sts file. This is a script file containing CLI commands which will be sequentially executed on the gateway.

When you have this script you need to upload it to the BBNM server and create an extra action.

3.1 Video Requirements

> Create an STS file to provision the gateway enabling the TGvideo Service.

> 1 IPoE interface for Video (dsl: pvc=8/38, eth: vlan13)

> Ensure the traffic flow over the correct interface

> Configure maximally optimised routed Video using IGMP

3.2 STS file explained

1 The header of an STS file, which is mandatory to run.

TPVERSION=2.0.0 BOARD_NAME=CANT-Y

2 Create a rule which classifies traffic being video based on the destination address.

:label rule add chain=rt_user_labels name=video_routing dstip=172.16.13.0/24 log=disabled state=enabled label=Video srcintf=!wan

3 Add the PVC Phonebook entry

:atm phonebook add name=pvc_video addr=8*38

4 Add the ATM interface

:atm ifadd intf=atm_video:atm ifconfig intf=atm_video dest=pvc_video:atm ifattach intf=atm_video

5 Add the ETH interface

10 v1.0


:eth ifadd intf=eth_video:eth ifconfig intf=eth_video dest=atm_video wan=enabled:eth ifattach intf=eth_video

6 Add the IP interface

:ip ifadd intf=ip_video dest=eth_video:ip ifattach intf=ip_video

7 Enable DHCP on the IP interface

:dhcp client ifadd intf=ip_video


:dhcp client rqoptions add intf=ip_video option=51:dhcp client rqoptions add intf=ip_video option=58:dhcp client rqoptions add intf=ip_video option=59:dhcp client rqoptions add intf=ip_video option=1:dhcp client rqoptions add intf=ip_video option=3:dhcp client rqoptions add intf=ip_video option=6

9 Add the label to the Video DHCP Client. This will add a label to the default route created by the DHCP client. This label will ensure that only video traffic will be able to use this route.

:dhcp client ifconfig intf=ip_video label=Video

10 Attach the DHCP Client and retrieve an IP address.

:dhcp client ifattach intf=ip_video

11 Create a vlan for Video

:eth vlan add name=vlan_video vid=13

12 Add the ETH interface for Video, associated with the proper VLAN.

:eth ifadd intf=eth_video_5:eth ifconfig intf=eth_video_5 dest=eth_wan vlan=vlan_video wan=enabled:eth ifattach intf eth_video_5

v1.0 11


13 Add the IP interfaces

:ip ifadd intf=ip_video_5 dest=eth_video_5:ip ifattach intf ip_video_5

14 Enable DHCP on the IP interface

:dhcp client ifadd intf=ip_video_5


:dhcp client rqoptions add intf=ip_video_5 option=51:dhcp client rqoptions add intf=ip_video_5 option=58:dhcp client rqoptions add intf=ip_video_5 option=59:dhcp client rqoptions add intf=ip_video_5 option=1:dhcp client rqoptions add intf=ip_video_5 option=3:dhcp client rqoptions add intf=ip_video_5 option=6

16 Add the label to the Video DHCP Client. This will add a label to the default route created by the DHCP client. This label will ensure that only video traffic will be able to use this route.

:dhcp client ifconfig intf=ip_video_5 label=Video

17 Attach the DHCP Client and retrieve an IP address.

:dhcp client ifattach intf=ip_video_5


:nat ifconfig intf=ip_video translation=enabled:nat ifconfig intf=ip_video_5 translation=enabled

19 Enable IGMP snooping on all physical ethernet interfaces which could host a STB.

:eth bridge ifconfig intf=ethport1 igmpsnooping=enabled :eth bridge ifconfig intf=ethport2 igmpsnooping=enabled :eth bridge ifconfig intf=ethport3 igmpsnooping=enabled :eth bridge ifconfig intf=ethport4 igmpsnooping=enabled

20 Enable IGMP snooping on the bridge

:eth bridge igmpsnooping config state=enabled

12 v1.0


21 Configure "fastleave" and "explicit host tracking" on all IGMP enabled ports.

:eth bridge igmpsnooping ifconfig intf=ethport1 fastleave=enabled exptrack=enabled:eth bridge igmpsnooping ifconfig intf=ethport2 fastleave=enabled exptrack=enabled:eth bridge igmpsnooping ifconfig intf=ethport3 fastleave=enabled exptrack=enabled:eth bridge igmpsnooping ifconfig intf=ethport4 fastleave=enabled exptrack=enabled

22 Since we are creating a routed scenario, we will need to use the IGMP proxy. The IGMP proxy will help getting IGMP (multicast) through the router and act as a querier towards the LocalNetwork.

:igmp proxy config state=enabled

23 Configure the proxy to be listening on the LocalNetwork and transmitting on the Video interfaces

:igmp proxy ifconfig intf=LocalNetwork state=downstream fastleave=enabled exptrack=enabled :igmp proxy ifconfig intf=ip_video_5 state=upstream:igmp proxy ifconfig intf=ip_video state=upstream

24 Conclude the STS file with a blank line (else the last line will not be executed)

v1.0 13


4 TGPLUS

In this chapter we set up the VoIP configuration proposed by the ISP. This service comes on top of previously configured services (Internet, Management and Video).

There are two lists of requirements. Basic requirements have to be fulfilled to gain the VoIP contract.

Advanced requirements are added value for the ISP, they will grant higher customer satisfaction.

4.1 Basic requirements

All requirements stated below have to be functional on both the eth and dsl interface.

> 1 IPoE interface for VoIP (dsl: pvc=8/36, eth: vlan 12)

> Ensure the VoIP traffic (SIP and RTP) flow over the correct interface

> Preconfigure the SIP proxy and registrar:Proxy: sip.tg.comRegistrar: sip.tg.com

> Configure a SIP account to register on the mentioned registrar.

▪ The SIP account should map to an analog phone plugged on FXS1

▪ A list of SIP URI is provided has followed : each group of TSSM will have its own account

SIP URI Username / Password

10XX 10XX / 10XX

Where X maps to the group ID

▪ For instance Group 14 should use :

> SIP URI :1014

> Username / Password : 1014

SIP Specific Settings

> The Register should expire after 2 minutes.

> Caller ID presentation has to be displayed on the Phone

> The subscriber can enable Caller ID restriction dialling *31, or do it on a one specific call dialling:

14 v1.0


*31*<number>

> If there is an incoming call while already on the phone, a tone should alert the subscriber, and dialing Hookflash + 2, he should be able to switch between pending and active call.

> The priority of the codec should be G729 - G711a

▪ no other codec should appear in SIP the negotiation

> The digit from the phone should be sent according to RFC2833 the dynamic Payload type announced in a SDP for rfc2833 should be 101

Dial Plan Settings

> The numbering plan of VoIP call is as follow:

o 1xxx

o 2xxx[xx]

4.2 Advanced requirements

> VoIP Traffic need be tagged in the network with DSCP:

Here are DSCP values which are to be used

▪ Signaling = af32

▪ RTP = ef

> Specific InterDigit Timeout

If we call a number which have a closed dialling plan (min number of digit = max number of digit) the timeout between each digit should be 10s, else it should be 4s.

> Tones played on the analog phone are etsi definition.

One exeption is for the ringback tone:

▪ Description of the Tone:

Off for 4000 ms

On for 1500 ms with a frequency of 500 Hz

▪ Official Cadence definition Scheme:

500: 1500/0:4000/L

v1.0 15


> Add an interactive answer which should be played by the CPE when the end user dial too slowly

i.e: if the user takes too much time between 2 digit, the interdigit timer will expire before the end user has finished to dial the full number, an explicit message should explain him what happened.

Voice message encoded with G711a is provided.

4.3 Configuration Guidelines

4.3.1 Connection Part

DSL Configuration

1 Add the PVC Phonebook entry

:atm phonebook add name=pvc_voip addr=8*36

2 Add the ATM interfaces

:atm ifadd intf=atm_voip:atm ifconfig intf=atm_voip dest=pvc_voip:atm ifattach intf=atm_voip

3 Add the ETH interfaces

:eth ifadd intf=eth_voip:eth ifconfig intf=eth_voip dest=atm_voip wan=enabled:eth ifattach intf=eth_voip

4 Add the IP interfaces, and define a different MAC address for this interface

:ip ifadd intf=ip_voip dest=eth_voip:ip ifconfig intf=ip_voip mtu=1500 hwaddr $_LMACADDR:ip ifattach intf=ip_voip


:dhcp client ifadd intf=ip_voip


16 v1.0


:dhcp client rqoptions add intf=ip_voip option=51:dhcp client rqoptions add intf=ip_voip option=58:dhcp client rqoptions add intf=ip_voip option=59:dhcp client rqoptions add intf=ip_voip option=1:dhcp client rqoptions add intf=ip_voip option=3:dhcp client rqoptions add intf=ip_voip option=6

7 Create label and a rule which classifies traffic being VoIP (SIP and RTP) based on the destination address and port.

:label add name=voice_routing:label modify name=voice_routing defclass=default inheritance=enabled:label rule add chain=rt_user_labels index=1 name=sip srcintf=local dstip=172.30.102.0/24 serv=sip log=disabled state=enabled label=voice_routing

8 Add the label to the VoIP DHCP Client. This will add a label to the default route created by the DHCP client. This label will ensure that only management traffic will be able to use this route.

:dhcp client ifconfig intf=ip_voip label=voice_routing


:dhcp client ifattach intf=ip_voip

ETH Configuration

1 Create a vlan for VoIP

:eth vlan add name=vlan_voip vid=12

2 Add the ETH interfaces for VoIP associated with its VLAN.

:eth ifadd intf=eth_voip_5:eth ifconfig intf=eth_voip_5 dest=eth_wan vlan=vlan_voip wan=enabled:eth ifattach intf eth_voip_5

3 Add the IP interfaces, and define a different MAC address for this interface

:ip ifadd intf=ip_voip_5 dest=eth_voip_5:ip ifconfig intf=ip_voip_5 mtu=1500 hwaddr $_LMACADDR:ip ifattach intf ip_voip_5

v1.0 17



:dhcp client ifadd intf=ip_voip_5


:dhcp client rqoptions add intf=ip_voip_5 option=51:dhcp client rqoptions add intf=ip_voip_5 option=58:dhcp client rqoptions add intf=ip_voip_5 option=59:dhcp client rqoptions add intf=ip_voip_5 option=1:dhcp client rqoptions add intf=ip_voip_5 option=3:dhcp client rqoptions add intf=ip_voip_5 option=6

6 Add the label to the VoIP DHCP Client. This will add a label to the default route created by the DHCP client. This label will ensure that only VoIP traffic will be able to use this route.

:dhcp client ifconfig intf=ip_voip_5 label=voice_routing


:dhcp client ifattach intf=ip_voip_5

4.3.2 Basic Requirements Guidelines

1 Configure the SIP proxy and registrar. Make sure to assign both ip_voip interface to the Voice application. The application will use it to find which source IP to use.

:voice sip config primproxyaddr=sip.tg.com primregaddr=sip.tg.com:voice config static_intf=enabled intf=ip_voip secondintf=ip_voip_5

2 Configure a SIP account to register on the mentioned registrar. Your URI, username, password and displayname should be in the format 10{your two digit groupID here}. Please do not copy paste immediately.

:voice profile add SIP_URI=1001 username=1001 password=1001 displayname=1001 voiceport=FXS1:service system modify name VOIP_SIP state enabled

3 Configure Register expire to 2 minutes.

:voice sip config regexpire 120

18 v1.0


4 Caller ID presentation and Call Waiting are provisioned by default, but not Caller ID restriction

:voice services provision type=clir

5 Configure codec priority as requested : G729 - G711a

:voice codec config type=g729 priority=1 status enabled:voice codec config type=g711a priority=2 status enabled:voice codec config type=g711u status disabled:voice codec config type=g723_1 status disabled

6 Configure DTMF relay in order to be sent according to RFC2833 and to have the dynamic Payload type 101

:voice config digitrelay=rfc2833:voice codec dynamic config type=g726_40 payloadtype=102:voice codec dynamic config type=rfc2833 payloadtype=101

7 Configure the 2 requested dialplan entries

▪ 1xxx

▪ 2xxx[xx]

:voice dialplan add prefix=1 defaultport=VoIP fallbackport=NA priority=NA fallback=disabled minimumdigits=4 maximumdigits=4 posofmodify=0 remnumdigits=0 rescan=no data=no action=ROUTE_excl_eon:voice dialplan add prefix=2 defaultport=VoIP fallbackport=NA priority=NA fallback=disabled minimumdigits=4 maximumdigits=6 posofmodify=0 remnumdigits=0 rescan=no data=no action=ROUTE_excl_eon

4.3.3 Advanced requirements Guidelines

1 Configure DSCP for signalling in af32

:voice qos config type=Signaling qosfield=DSCP dscp=af32

2 Configure InterDigit Timeout

Closed dialling plan should be 10s, else it should be 4s.

:voice fxsport config interdigit=10000 interdigitOpen=4000

3 Tones played on the analog phone are etsi definition.

v1.0 19


▪ Official Cadence definition Scheme:

500: 1500/0:4000/L

:voice tone patterntable modify id=111 freq1=500 duration=1500

> Add an interactive answer should be played by the CPE when the end user dial too slowly

The ID mapping with this Event is 101. The voice message encoded with G711a is provided, it has to be put in the DL directory of the CPE.

:voice tone descrtable add tone=EventID101 status=enabled delay=1000 patternentryid=0 file=dl/EventID101 filerepeat=1 text=Too_slow nexttone=none repeatafter=0:voice tone eventtable modify eventid=101 tone=EventID101

20 v1.0

Visit us at:

www.thomson-broadband.com

Acknowledgements

All Colleagues for sharing their knowledge.

Coordinates

THOMSON Telecom

Prins Boudewijnlaan 47

B-2650 EdegemBelgium

Email: [email protected]

Copyright

©2023 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.

http://www.thomson-broadband.com/

advanced training

Documents