tdmoip

49
v.1.0 v.1.0 1 1 Contents Contents TDMoIP: Introduction Clock Recovery & Measurement

Upload: mofasser-ahmed-tamal

Post on 13-Nov-2014

130 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: TDMoIP

v.1.0v.1.0 11

1

ContentsContents

• TDMoIP: Introduction• Clock Recovery & Measurement

Page 2: TDMoIP

v.1.0v.1.0 22

2

1. TDMoIP: 1. TDMoIP: IntroductionIntroduction

Page 3: TDMoIP

v.1.0v.1.0 33

3

PseudowiresPseudowires

Pseudowire (PW): Pseudowire (PW): A mechanism that emulates the A mechanism that emulates the essential attributes of a native service while transporting essential attributes of a native service while transporting over a packet switched network (PSN)over a packet switched network (PSN)

Page 4: TDMoIP

v.1.0v.1.0 44

4

Tunneling - interworkingTunneling - interworkingMating different network protocols is Mating different network protocols is

called called interworkinginterworking

The protocol converter goes by The protocol converter goes by

various names :various names :interworking function (IWF)interworking function (IWF)gateway (GW)gateway (GW)

Simplest case is Simplest case is network interworkingnetwork interworkingEasily provided by Easily provided by tunnelingtunneling

networkNativeService

NativeService

Page 5: TDMoIP

v.1.0v.1.0 55

5

Emulating TDMEmulating TDM

From PSTN to PSNFrom PSTN to PSN

Page 6: TDMoIP

v.1.0v.1.0 66

6

Classic TelephonyClassic Telephony

Circuit switched ensures signal integrityCircuit switched ensures signal integrity Very High Reliability (“Very High Reliability (“five ninesfive nines”)”) Low Delay and no noticeable echo Low Delay and no noticeable echo    Timing information transported over the Timing information transported over the

networknetwork Mature Signaling Protocols Mature Signaling Protocols (over 3000 features)(over 3000 features)

T1/E1

COSWITCH

analog lines

SONET/SDHNETWORK

PBX

extensions

Access Network

T1/E1

PBX

Core (Backbone) Network

SynchronousNon-packet network

COSWITCH

Page 7: TDMoIP

v.1.0v.1.0 77

7

TDMoPSNTDMoPSN

The TDMoIP approach replaces the The TDMoIP approach replaces the NetworkNetwork with a packet (IP or MPLS) networkwith a packet (IP or MPLS) networkThe access networks and their protocols remain !The access networks and their protocols remain !TDM PseudowireTDM PseudowireCan G.xxx compliance be maintained?Can G.xxx compliance be maintained?

T1/E1/T3/E3

analog lines

PBX

extensions

Access Network

PBX

T1/E1

Packet Switched Network

Asynchronous networkNo timing information transfer

Page 8: TDMoIP

v.1.0v.1.0 88

8

A few G.XXX sayings …A few G.XXX sayings …

G.114 (One-way transmission time)G.114 (One-way transmission time) delay < 150 msdelay < 150 ms acceptable acceptable 150 ms < delay < 400 ms conditionally acceptable150 ms < delay < 400 ms conditionally acceptable delay > 400 ms unacceptabledelay > 400 ms unacceptable G.126/G.131 echo control may be neededG.126/G.131 echo control may be needed

G.823/G.824 (timing)G.823/G.824 (timing) Primary vs. secondary clocksPrimary vs. secondary clocks jitter masksjitter masks wander maskswander masks

G.826 (error performance)G.826 (error performance) BER better than 2 BER better than 2 ** 10 10-4-4

Page 9: TDMoIP

v.1.0v.1.0 99

9

TDMoIP vs. VoIPTDMoIP vs. VoIP

Two ways to integrate TDM services into PSNsTwo ways to integrate TDM services into PSNs

VoIPVoIPVoice centric!Voice centric! Revolution - complete Revolution - complete (forklift)(forklift) CPE replacement CPE replacement New signaling protocols (translation needed)New signaling protocols (translation needed) New functionality New functionality (e.g. video-phone, presence)(e.g. video-phone, presence)

TDMoIPTDMoIPClear channel/ leased line serviceClear channel/ leased line service Evolution - CPE unchanged, IWF added at edgeEvolution - CPE unchanged, IWF added at edge No change to signaling protocols (network IW)No change to signaling protocols (network IW) No new functionalityNo new functionality Migration pathMigration path

Page 10: TDMoIP

v.1.0v.1.0 1010

10

TDMoIP as a Migration PathTDMoIP as a Migration Path

VoIP has promising futureVoIP has promising futurebut today’s installed base is still legacy TDM but today’s installed base is still legacy TDM

PSTN is not going to be replaced overnight PSTN is not going to be replaced overnight

Voice quality concerns Voice quality concerns (delay, compression, packet (delay, compression, packet loss)loss)

TDMoIP can use new infrastructure with TDMoIP can use new infrastructure with legacy CPElegacy CPE

Maintains functionality of all PBX and Centrex Maintains functionality of all PBX and Centrex featuresfeatures

Page 11: TDMoIP

v.1.0v.1.0 1111

11

TDMoIP Protocol ProcessingTDMoIP Protocol Processing

Steps in TDMoIPSteps in TDMoIPThe synchronous bit stream is segmentedThe synchronous bit stream is segmentedThe TDM segments are The TDM segments are adaptedadaptedTDMoIP control word is prependedTDMoIP control word is prependedPSN (IP/MPLS) headers are prependedPSN (IP/MPLS) headers are prependedPackets are transported over PSN to destinationPackets are transported over PSN to destinationPSN headers are utilized and strippedPSN headers are utilized and strippedControl word is checked, utilized and strippedControl word is checked, utilized and strippedTDM stream is reconstituted and played outTDM stream is reconstituted and played out

TDMframes

TDMframes

IP Packets

PSN

IP Packets

Page 12: TDMoIP

v.1.0v.1.0 1212

12

TDMoIP Protocol ProcessingTDMoIP Protocol Processing

Traffic Types:Traffic Types:

Structured (framed)Structured (framed)

Unstructured (unframed)Unstructured (unframed)

TDMframes

TDMframes

IP Packets

PSN

IP Packets

Page 13: TDMoIP

v.1.0v.1.0 1313

13

TDMoIP encap formatsTDMoIP encap formats- For - For StructuredStructured Traffic Traffic(TDMoIP: IETF draft-Anavi-(TDMoIP: IETF draft-Anavi-tdmoip-06)tdmoip-06)

encapsulation encapsulation (encap)(encap) : : process of process of adding protocol control information adding protocol control information to data in order to build a packet to data in order to build a packet for transport across an PSNfor transport across an PSN

Page 14: TDMoIP

v.1.0v.1.0 1414

14

FunctionalityFunctionalityWhat needs to be transported from end to end?What needs to be transported from end to end?Voice Voice (telephony quality, low delay, echo-less)(telephony quality, low delay, echo-less)Tones Tones (for dialing, PIN, etc.)(for dialing, PIN, etc.)Fax and modem transmissionsFax and modem transmissionsSignaling Signaling (there are 1000s of PSTN features!)(there are 1000s of PSTN features!)

CCS (comon Channel Signaling), CAS (Channel Associated Signaling)CCS (comon Channel Signaling), CAS (Channel Associated Signaling)

Timing Timing

T1/E1frame

SYNC TS1 TS2 TS3CAS

signalingbits

… … TSn

(1 byte)

“timeslots”

Page 15: TDMoIP

v.1.0v.1.0 1515

15

Why isn’t it easyWhy isn’t it easyWhy don’t we simply encapsulate the T1/E1 frame?Why don’t we simply encapsulate the T1/E1 frame?

IP T1/E1 frame

24 or 32 bytes

UDP RTP?

Because a single lost packet would cause service interruption CAS signaling uses a superframe (16/24 frames) Superframe integrity must be respected

Because we want to efficiently handle fractional T1/E1

Because we want a latency vs. efficiency trade-off

Page 16: TDMoIP

v.1.0v.1.0 1616

16

The basic ideaThe basic ideaThose problems can be solved by:Those problems can be solved by: adding a packet sequence numberadding a packet sequence number adding a pointer to the next superframe boundaryadding a pointer to the next superframe boundary only sending timeslots in useonly sending timeslots in use allowing multiple TDM frames per packetallowing multiple TDM frames per packet

Good idea! This is precisely AAL1 !

for example

UDP/IP T1/E1 frames (only timeslots in use)seqnum(with CRC)

ptr

TS1 TS2 TS5 TS7 TS1 TS2 TS5 TS77 @

Page 17: TDMoIP

v.1.0v.1.0 1717

17

why AAL1 – For Static why AAL1 – For Static Structured TrafficStructured Traffic

““ AAL1” is the AAL1” is the simplestsimplest method to method to transport structured TDM traffic transport structured TDM traffic (voice, (voice,

sync, signaling)sync, signaling)

ATM community has done the debugging for ATM community has done the debugging for

us!us!

Any alternative will eitherAny alternative will either fall apart upon packet loss fall apart upon packet loss or or be less efficient be less efficient or or mandate high latency (e.g. multiframe per packet) ormandate high latency (e.g. multiframe per packet) or be essentially equivalent (I.e. contain a structure pointer)be essentially equivalent (I.e. contain a structure pointer)

Page 18: TDMoIP

v.1.0v.1.0 1818

18

Isn’t that enough?Isn’t that enough?AAL1 is inefficient if the timeslots are not always in AAL1 is inefficient if the timeslots are not always in

useuse

Although we can configure which timeslots are usedAlthough we can configure which timeslots are usedwe can not change this configuration in real-time!we can not change this configuration in real-time!

To allow dynamic allocation of timeslotsTo allow dynamic allocation of timeslotswe can use we can use AAL2AAL2

AAL2 AAL2 buffers each timeslot and encapsulates in a buffers each timeslot and encapsulates in a

“minicell”“minicell”

Bandwidth conservation comes at a priceBandwidth conservation comes at a price more computationmore computation less robustless robust

Page 19: TDMoIP

v.1.0v.1.0 1919

19

AAL2 for Dynamic BW AAL2 for Dynamic BW TrafficTraffic

AAL1 is BW inefficient when AAL1 is BW inefficient when timeslots are dynamictimeslots are dynamic

Even with GB rates we should consider efficiency considerations Even with GB rates we should consider efficiency considerations

““AAL2” is the AAL2” is the simplestsimplest method to method to transport dynamic structured TDMtransport dynamic structured TDM

Any alternative will eitherAny alternative will either fall apart upon packet loss orfall apart upon packet loss or be less efficient (e.g. require renegotiation) be less efficient (e.g. require renegotiation) or or be essentially equivalentbe essentially equivalent

Page 20: TDMoIP

v.1.0v.1.0 2020

20

Isn’t this just ATM?Isn’t this just ATM?

AAL1 and AAL2 are AAL1 and AAL2 are adaptation protocolsadaptation protocolsoriginally designed to massage data into a format originally designed to massage data into a format that can be readily usedthat can be readily used

As we have shown, they are natural candidates forAs we have shown, they are natural candidates forany application which needs to multiplex timeslotsany application which needs to multiplex timeslots

For TDMoIP we do not put the AAL1/2 into ATM cells For TDMoIP we do not put the AAL1/2 into ATM cells (no 5 byte (no 5 byte

header)header)

Rather we put the AAL1/2 directly into a UDP/IP or MPLS packetRather we put the AAL1/2 directly into a UDP/IP or MPLS packet

So, So, NONO, this is , this is NOTNOT ATM ATM

But it can easily interwork with ATM access networks!But it can easily interwork with ATM access networks!

Page 21: TDMoIP

v.1.0v.1.0 2121

21

Service Inter-workingService Inter-working

TDMoIP is not the first TDM emulation technologyWe should also provide service interworking, existing ATM circuit emulation services (AAL1, AAL2)

PSN

E1/T1E3/T3

E1/T1E3/T3 TDMoMPLS GW

ATM-MPLS IWF

ATM/AAL1

ATM-CES GW

ATM layer

AAL1 AAL2 AAL5

CBR VBR n-rt

Page 22: TDMoIP

v.1.0v.1.0 2222

22

One More Payload type: HDLCOne More Payload type: HDLCEfficiently transfer CCS traffic (such as Efficiently transfer CCS traffic (such as

SS7 embeded in TDM traffic)SS7 embeded in TDM traffic)

Assume messages shorter than the MTU Assume messages shorter than the MTU (no (no fragmentation)fragmentation) monitor flags until frame detectedmonitor flags until frame detected test FCStest FCS if incorrect - discardedif incorrect - discarded if correct - if correct -

perform unstuffingperform unstuffing flags and FCS removedflags and FCS removed send framesend frame

Page 23: TDMoIP

v.1.0v.1.0 2323

23

TDMoIP layering structure – TDMoIP layering structure – Structured TrafficStructured Traffic

AAL1 used for static (and transparent) allocation: NxAAL1 (N=1..31)

AAL2 used for dynamic bandwidth: NxAAL2 (N=1..31)

HDLC used for CCS signaling and data (e.g frame relay)

PSN / multiplexing

Optional RTP header

TDMoIP Encapsulation

AAL1 AAL2 HDLC

higher layers

Page 24: TDMoIP

v.1.0v.1.0 2424

24

TDMoIP Control WordTDMoIP Control Word

For Structured Traffic:For Structured Traffic:FORMID (4 b)FORMID (4 b)

indicates TDMoIP mode (AAL1, AAL1 - CAS, AAL2, HDLC)indicates TDMoIP mode (AAL1, AAL1 - CAS, AAL2, HDLC) ensures differentiation between IP and MPLS PSNsensures differentiation between IP and MPLS PSNs

Flags (2 b)Flags (2 b) L bit (Local failure)L bit (Local failure) R bit (Remote failure)R bit (Remote failure)

Res (4 b):Res (4 b):

Length (6 b) Length (6 b) used when packet may be padded used when packet may be padded

Sequence Number (16 b) Sequence Number (16 b) used to detect packet loss / miss-orderingused to detect packet loss / miss-ordering

For UnStructured Traffic:For UnStructured Traffic:FORMID (4 b): 0000FORMID (4 b): 0000

Res: Res:

FORMID flags Res   Length            Sequence Number  

Page 25: TDMoIP

v.1.0v.1.0 2525

25

TDMoIP encap formatsTDMoIP encap formats- For - For UnStructuredUnStructured TrafficTraffic(SATOP: Draft-ietf-pwe3-satop)(SATOP: Draft-ietf-pwe3-satop)

SATOP: Structue-agnostic TDM over SATOP: Structue-agnostic TDM over Packet)Packet)

Page 26: TDMoIP

v.1.0v.1.0 2626

26

Payload Type of UnStructured Payload Type of UnStructured TrafficTraffic

TDM traffic is treated as RAW dataTDM traffic is treated as RAW data TDM bit stream is put into payload fieldTDM bit stream is put into payload field

The payload size is defined during setupThe payload size is defined during setup

Payload size remains the samePayload size remains the same

It should support the payload size:It should support the payload size: T1: 192 bytesT1: 192 bytes E1: 256 bytesE1: 256 bytes T3 and E3: 1024 bytesT3 and E3: 1024 bytes

If RTP is used:If RTP is used: Clock used for time stamp must be an integer of Clock used for time stamp must be an integer of

multiple 8Kzmultiple 8Kz

Page 27: TDMoIP

v.1.0v.1.0 2727

27

TDMoIP encap formatsTDMoIP encap formatsSummarySummary

Page 28: TDMoIP

v.1.0v.1.0 2828

28

TDMoIP layering structureTDMoIP layering structurePSN / multiplexing

Optional RTP header

TDMoIP Encapsulation

TDM Over IP Payload

higher layers

Page 29: TDMoIP

v.1.0v.1.0 2929

29

TDMoIP Control WordTDMoIP Control Word

For Structured Traffic:For Structured Traffic:FORMID (4 b)FORMID (4 b)

indicates TDMoIP mode (AAL1 w/o CAS, AAL1 w/CAS, AAL2, HDLC)indicates TDMoIP mode (AAL1 w/o CAS, AAL1 w/CAS, AAL2, HDLC) ensures differentiation between IP and MPLS PSNsensures differentiation between IP and MPLS PSNs

Flags (2 b)Flags (2 b) L bit (Local failure)L bit (Local failure) R bit (Remote failure)R bit (Remote failure)

Res (4 b):Res (4 b):

Length (6 b) Length (6 b) used when packet may be padded used when packet may be padded

Sequence Number (16 b) Sequence Number (16 b) used to detect packet loss / miss-orderingused to detect packet loss / miss-ordering

For UnStructured Traffic:For UnStructured Traffic:FORMID (4 b): 0000FORMID (4 b): 0000

Res: Res:

FORMID flags Res   Length            Sequence Number  

Page 30: TDMoIP

v.1.0v.1.0 3030

30

TDMoIP packet formatTDMoIP packet formatIP header (5*4bytes)

UDP header * (2*4bytes)

Optional RTP header (3*4bytes)

TDMoIP header (4bytes)

TDMoIP payload

* The UDP source port number is used as a bundle identifierNotes

Page 31: TDMoIP

v.1.0v.1.0 3131

31

IPVER IHL IP TOS Total Length

Identification Flags Fragment Offset

Time to Live Protocol IP Header Checksum

Source IP address

Destination IP address

VER Circuit Bundle Number Destination Port Number

UDP Length UDP Checksum

RTV P X CC M PT RTP Sequence Number

Timestamp

SSRC Identifier

FORMID L R Z Length Sequence Number

TDMoIP Payload

IP Header

UDP Header

RTP Header

Control Word

32 Bit

Payload

0x 085E or 2142

Eth

ern

et IP

HeaderTOS

Src adrDst adr

UDPHeader

Src Bundle#

Dst= 0x085E

TDMoIP

Control

Word

Adapated

Payload

(AAL1,AAL2,

HDLC, RAW)

CR

C-3

2

UDP Source Port Number is used as the bundle number designator , UDP Destination port number set to hex 085E (2142) assigned by IANA for TDMoIP.

CBID

20 Bytes

8 Bytes

IP/UDP/RTP EncapsulationIP/UDP/RTP Encapsulation

Page 32: TDMoIP

v.1.0v.1.0 3232

32

TDMoMPLS packet formatTDMoMPLS packet format

outer label

inner label

controlword

TDMPayload

• Inner and outer labels specify TDM routing and multiplexing• Inner Label contains TDMoMPLS circuit bundle number

• The control word• enables detection of out-of-order and lost packets• indicates critical alarm conditions

• The TDM payload may be adapted• to assist in timing recovery and recovery from packet loss• to ensure proper transfer of TDM signaling• to provide an efficiency vs latency trade-off

Page 33: TDMoIP

v.1.0v.1.0 3333

33

FORMID L R Z Length Sequence Number

TDMoIP Payload

Outer Label EXP S TTL

Inner Label = CBID EXP S TTL

MPLS Header

Control Word

Payload

• Example of MPLS Header :

Eth

ern

et

MPLSOuterLabels

MPLSInnerLabel

TDMoIPControlWord

Adapated

Payload

(AAL1,AAL2,

HDLC, RAW)

CR

C-3

2

8 Bytes

MPLS EncapsulationMPLS Encapsulation

Page 34: TDMoIP

v.1.0v.1.0 3434

34

TDM o L2TPv3TDM o L2TPv3

IP header (5*4 B)

Session ID (4 B)

Optional cookie (4 or 8 B)

TDMoIP header (4 B)

TDMoIP payload

Note : No UDP header

higher layers

Page 35: TDMoIP

v.1.0v.1.0 3535

35

• Structured TDM Payload

• Multiple AAL1: NxAAL1

• Multiple AAL2: NxAAL2

• HDLC

• UnStructured TDM Payload:

• Bit stream, fixed bytes

TDMoIP Frame

ControlWord

IP/UDP orMPLS header

EhterNetHeader

TDMoIP in Ethernet FrameTDMoIP in Ethernet Frame

FCSTDM Payload

Page 36: TDMoIP

v.1.0v.1.0 3636

36

TDMoIP Frame w QoS SupportTDMoIP Frame w QoS Support

MAC Layer IP Layer UDP TDM AAL1 Payload CRC

VLAN Tagging

Priority Labeling

IEEE 802.1p&Q

TOS -Type of ServiceField (Diffserv) Priority

UDP Source & DestinationPorts

2142 (Given by IANA)Level 4 priority

TDMoIPControl Word

Typical 48 Octet Payload AAL1/AAL21 Octet Header 47 Octet payloadUp to 30 AALn Frames in Payload Field

• Header Compression can be used to decrease the header down to a few bytes

• Ethernet Packet Min 64 bytes Max 1536 bytes

Page 37: TDMoIP

v.1.0v.1.0 3737

37

TDM Timing RecoveryTDM Timing Recovery

Page 38: TDMoIP

v.1.0v.1.0 3838

38

IntroductionIntroduction PSN (e.g. IP) have no clock distribution mechanismPSN (e.g. IP) have no clock distribution mechanism

For TDM over PSN receiver must recover clockFor TDM over PSN receiver must recover clock In Band: timing information is transferred over PSN, (e.g., In Band: timing information is transferred over PSN, (e.g.,

RTP)RTP) Required high quality reference clock Required high quality reference clock

Timing information is provided in some means Timing information is provided in some means independend of PSN, (e.g., adaptive clock mechanism)independend of PSN, (e.g., adaptive clock mechanism)

Recovered clock quality:Recovered clock quality: Can not guarantee “Quality traffic” if the recovered clock Can not guarantee “Quality traffic” if the recovered clock

is not accurate enoughis not accurate enough E1: G.823E1: G.823 T1: G.824T1: G.824

Page 39: TDMoIP

v.1.0v.1.0 3939

39

Introduction cont.Introduction cont. Result of RTP can not meet the G.823, G.824Result of RTP can not meet the G.823, G.824

Due to time stamp quantization error, packet loss, ..Due to time stamp quantization error, packet loss, .. Use 12 bytes for RTPUse 12 bytes for RTP Require reference clock in both side (expensive for high Require reference clock in both side (expensive for high

accurate reference clock)accurate reference clock)

Conventional adaptive clock slaves local clock to jitter Conventional adaptive clock slaves local clock to jitter buffer levelbuffer level initial frequency discrepancy is eventually compensatedinitial frequency discrepancy is eventually compensated jitter buffer level corresponds to frequency offsetjitter buffer level corresponds to frequency offset

Although highly robust, there are several faultsAlthough highly robust, there are several faults entire network jitter transferred to local clockentire network jitter transferred to local clock unstable and vulnerable to packet lossunstable and vulnerable to packet loss jitter buffer level may settle far from buffer centerjitter buffer level may settle far from buffer center long convergence timeslong convergence times

Page 40: TDMoIP

v.1.0v.1.0 4040

40

Introduction cont.Introduction cont.

TXC PacketTrunk-4 chip's innovative clock TXC PacketTrunk-4 chip's innovative clock recovery scheme recovery scheme

retains robustness of conventional schemeretains robustness of conventional scheme improved capabilitiesimproved capabilities Two phasesTwo phases

acquisitionacquisition phase phase rapid rapid frequency lock frequency lock is attained. is attained.

trackingtracking phase phase the achieved frequency lock is sustained the achieved frequency lock is sustained jitter buffer centeringjitter buffer centering (according to configuration value)(according to configuration value) jitter attenuation standards conformance for large PDVjitter attenuation standards conformance for large PDV packet loss immunity improved.packet loss immunity improved.

Page 41: TDMoIP

v.1.0v.1.0 4141

41

Frequency Hold-overFrequency Hold-over

Rx buffer starvation (under-run) can be caused by:Rx buffer starvation (under-run) can be caused by: Network congestion Network congestion packet losspacket loss In dynamic application when there is no activityIn dynamic application when there is no activity While shifting to an alternate bundle, in redundancy modeWhile shifting to an alternate bundle, in redundancy mode

- Last frequency is frozen, until data flow is resumed.Last frequency is frozen, until data flow is resumed.- No need for re-acquisition!No need for re-acquisition!

Long-term recovered clock accuracy:Long-term recovered clock accuracy:E1/T1: better than 0.02 ppmE1/T1: better than 0.02 ppm

Page 42: TDMoIP

v.1.0v.1.0 4242

42

Why TDMoIP?Why TDMoIP?

Complementary to VoIP.

Provides high voice quality with low latency.

Can support all applications that run over E1/T1 circuits, not just voice.

Can be made transparent to protocols and signaling.

An evolutionary – not revolutionary – approach, so investment protection is maximized.

Page 43: TDMoIP

v.1.0v.1.0 4343

43

Voice EvolutionVoice Evolution

Circuit Circuit SwitchingSwitching

Packet SwitchingPacket Switching

PSTNPSTN ATMATM IP/MPLSIP/MPLS

Leased-Line Leased-Line ServiceService

Circuit Circuit Emulation Emulation

ServiceService

TDMoIP/MPLS TDMoIP/MPLS (CBR)(CBR)

Switched Switched Voice Voice

ServiceService

VoATM (ATM VoATM (ATM LES)LES)

TDMoIP/MPLS TDMoIP/MPLS (VBR)(VBR)VoIPVoIP

Page 44: TDMoIP

v.1.0v.1.0 4444

44

TDM over GbE MANTDM over GbE MAN

PublicINTERNET

100 Mbps

TDMoIP GW

CustomerPremise

PBX CustomerPremise

GbE

TDMoIP GW

100 Mbps

PBX

CLASSSwitch

CentralOffice

GbE

TDMoIPGW

TDMoIP GW

POP

IP

TDM LeasedLines

PSTN

Page 45: TDMoIP

v.1.0v.1.0 4545

45

Features: TDM concentration (grooming multiple T1/E1 into OC-3/STM-1 trunks) E3/T3 Carrier Trunking

With:GbE Network I/FOC-3/STM-1 TDM interface

TDM ConcentrationTDM Concentration

SDH/SONETCLASS

Switch

PBX

PBX

IP

TDMoIPGW

PSTN

SS7

TDMoIPGW

TDMoIPGW

TDMoIPGW

SDH/SONET

PBX

PBX

IP

ADM

PBX

ADM

Page 46: TDMoIP

v.1.0v.1.0 4646

46

Metro MTU Application Metro MTU Application

POTS

PBX

Switch

TDMoIP GW

TDMoIP GW

SwitchTDMoIPGW

PBX

PBX

PBX

Building LevelIntegration

Office LevelIntegration

PBX

SwitchPBX

TDMoIPGW

PSTN

Corporate Site A

TDMoIP GW

Switch/Router

Corporate Site B

IP/MPLSNetwork

Page 47: TDMoIP

v.1.0v.1.0 4747

47

Metro(GbE, IP, RPR,

HFC, EoS)

Cellular Backhaul over Cellular Backhaul over IP/EthernetIP/Ethernet

Fixed Wireless, Coax, or Fixed Wireless, Coax, or Fiber AccessFiber Access

FixedWireless

FT1/T1/n*T1

CMTS

FT1/T1/n*T1

Coax

Cell sites w/TDMoIP

blade retrofits

FT1/T1/n*T1Fiber

Switch site w/TDMoIP GW

T1/ T3/ E1100 Mbps

GW GW

Page 48: TDMoIP

v.1.0v.1.0 4848

48

GbESwitch

IP Network

SS7 over IPSS7 over IP

VoIP GW

User’s needs:

• Transparent SS7 forwarding over IP• Voice transferred as VoIP• Cross Connect functionality

Potential customers:

• Voice carriers• Satellite providers• Cellular operators• MAN providers

PSTN

PublicVoice

Switch

PublicVoice

Switch

GbESwitch

TDMoIP-basedsignaling GW

VoIP GW

SS#7Server

IntelligentNetwork

TDMoIP-basedsignaling GW

TDMoIP-basedsignaling GW

Page 49: TDMoIP

v.1.0v.1.0 4949

49

TDMoIP SummaryTDMoIP Summary

IP and Ethernet network technologies will be dominant in the IP and Ethernet network technologies will be dominant in the future. future.

Revolutionary VoIP may take more time to mature. Evolutionary Revolutionary VoIP may take more time to mature. Evolutionary solutions that offer a careful migration path are now preferred. solutions that offer a careful migration path are now preferred.

TDMoIP provides simplicity, transparency, and affordable cost, TDMoIP provides simplicity, transparency, and affordable cost, and that’s actually what the market is looking for. and that’s actually what the market is looking for.

PacketTrunk-4 allows the implementation of multi-T1/E1 TDMoIP PacketTrunk-4 allows the implementation of multi-T1/E1 TDMoIP gateways with enhanced cost/performance for a variety of carrier gateways with enhanced cost/performance for a variety of carrier and enterprise applications across the network.and enterprise applications across the network.