Tandem/Toll Replacement

SCPs

LNP

800#

SS7/C7
EO Toll Tan EO Toll Toll Softswitch EO

EO
Tan EO

Toll

Packet
GW GW
1

Nguyen Tai Hung - VTC October, 2003

PRI Offload for Internet Access

ISP 1
SS7 IMTs

RAS

EO

EO EO Tan
Scalable Solution PRIs

TDM

RAS ISP 2

MUX

RAS

ISP 3

Nguyen Tai Hung - VTC October, 2003

PRI Offload for Internet Access

ISP 1
RAS
SS7 IMTs High-Speed Packet Interface

EO

Packet
EO
EO Tan

RAS ISP 2

Distributed Solution
RAS

PRIs

ISP 3

Nguyen Tai Hung - VTC October, 2003

PBX Access

ILEC
IMTs PBX PRI

SS7

ILEC
SS7 Gateway PBX

Packet IP
CAS Gateway Switch PBX Softswitch Gateway Switch PBX

Nguyen Tai Hung - VTC October, 2003

Business Phone Feature Server

Softswitch SS7 Gateway Feature Server SIP DSL/T1 IP Gateway Switch

SS7

Packet

PSTN

IP Phones

Adapter

Analog/Digital Phones

Nguyen Tai Hung - VTC October, 2003

Integrated Access
Softswitch

SS7/C7

xDSL

Circuit
Gateway Switch

Packet
Cable IP Phone

Integrated Access Device PBX

Nguyen Tai Hung - VTC October, 2003

Comparing MGCP and MEGACO

MGCP comes from the IETF
Initial efforts at getting carrier signaling into/across IP networks RFC2705: MGCP 1.0, 10/1999

But you cant get this to work without the big boys (e.g., the Telcos), who meet via the ITU MEGACO is a cooperative effort between the IETF and the ITU
Future efforts will be/are being focused here
Nguyen Tai Hung - VTC October, 2003 7

More on MEGACO
MEGACO (MEdia GAteway COntrol) is the IETF name
In the ITU, its H.248 RFC3015: MEGACO 1.0, 11/2000
a little more recent

MEGACO supports broader range of network types (including ATM)

Good summary article:

http://www.networkmagazine.com/article/NMG20001004S0013

MEGACO Working Group Charter:

http://www.ietf.org/html.charters/megaco-charter.html
Nguyen Tai Hung - VTC October, 2003 8

The MGCP Model

Controllers (call agents) control media gateways
Gateway does what Call Agent says; masterslave E.g., Call Agent tells Gateway to make a connection from a PSTN connection to an RTP port

MGCP doesnt address gateway-to-gateway communications

Generally assumes SIP will do this
Nguyen Tai Hung - VTC October, 2003 9

The MGCP Model (2)

Two major components in the MGCP architecture:
Endpoints: Sources/sinks of traffic within a gateway
e.g., an interface to the PSTN a single call, or a collection of calls (a trunk) many different types of endpoints exist (see pp. 241242)

Connections: The IP resources allocated to an endpoint to allow communication between the IP and PSTN networks
Nguyen Tai Hung - VTC October, 2003 10

MGCP Connection Establishment

Nguyen Tai Hung - VTC October, 2003

11

MGCP Call Establishment details

Nguyen Tai Hung - VTC October, 2003

12

MGCP Gateway Interaction

Nguyen Tai Hung - VTC October, 2003

13

MGCP with SIP

Nguyen Tai Hung - VTC October, 2003

14

MEGACO Concepts
Very similar to MGCP Constructs
Termination like an MGCP Endpoint Context like an MGCP Connection, but more than that
more than two Contexts can be associated

Transactions commands and responses

Dual text/binary encoding

binary to accommodate the bellheads

MEGACO is more peer-to-peer than MGCP

Nguyen Tai Hung - VTC October, 2003 15

MEGACO Call Setup Details

Nguyen Tai Hung - VTC October, 2003

16

Sigtran
Sigtran is an IETF working group that addresses:
signaling performance in IP networks interworking signaling between the PSTN and VoIP protocols

IETF Working Group:

http://www.ietf.org/html.charters/sigtran-charter.html

Recent work:
Security considerations draft, 10/2002 RFC3331: SS7 MTP2 User Adaptation Layer, 9/2002 RFC3332: SS7 MTP3 User Adaptation Layer, 9/2002
Nguyen Tai Hung - VTC October, 2003 17

Interworking: SIP/MGCP/ISUP

Nguyen Tai Hung - VTC October, 2003

18

Interworking via Sigtran

Nguyen Tai Hung - VTC October, 2003

19

SIP/H.323 vs Megaco Summary

Fully compatible at system level Real question is whats more appropriate for what application Thick vs Thin tradeoff

Peer (SIP or H.323) end user devices:

Thick client, functional/peer control model Higher complexity client Feature poor (generic SIP or H.323 relative to current systems) Appropriate for high-end & special purpose devices, soft clients

Megaco end user devices:

Thin client (stimulus-like) control model, low complexity client Shortest path to feature rich system Highly appropriate for mass deployment devices, horizontal features Excellent fit to i2000 goals
Nguyen Tai Hung - VTC October, 2003 20

Miscellaneous References
http://www.networkmagazine.com/article/NMG2000100 4S0013 http://www.vovida.org/pipermail/mgcp/ ftp://ftp.rfc-editor.org/in-notes/rfc2705.txt ftp://ftp.rfc-editor.org/in-notes/rfc2897.txt http://www.ietf.org/html.charters/megacocharter.html ftp://ftp.rfc-editor.org/in-notes/rfc3015.txt ftp://ftp.rfc-editor.org/in-notes/rfc3054.txt http://www.protocols.com/pbook/ss7.htm

Nguyen Tai Hung - VTC October, 2003

21