SignaIIing and ControI

In IP Networks
- H.248, H.323 and SIP
For APRCOT, Feb 27, 2001 - 2
SignaIing Standards
Media Gateway ControI SignaIIing
H.248/Megaco
CaII SignaIIing
SP and SP-T
H.323
For APRCOT, Feb 27, 2001 - 3
Network View
SG
MG
MGC
SG
MG
MGC
SP
User Agent
H.323
Endpoint
PSTN
PSTN
Call signalling
Media gateway control signalling
Media flows
SIP-T
SIP
H.323 call
signalling
H.248
Megaco
H.248
Megaco
For APRCOT, Feb 27, 2001 - 4
H.248/MEGACO Overview
MEdia GAteway ControI ProtocoI [RFC3015]
H.248 is TU-T reference for the same protocol
Protocol for controlling telephony gateway and
terminals (P Phones)
Basis for Vendor ndependent Network
deployment
For APRCOT, Feb 27, 2001 - 5
H.248/Megaco evoIution
8C6P 8C6P HC6P HC6P
Hegaco|h.248 Hegaco|h.248
l-RFC 2Z05 l-RFC 2Z05
HC6P re|eased as
|nformat|ona| RF6
(0ct 99}
V0CP proposa| oy rerg|rg
lP0C ard 30CP
(Te|cord|a & Leve| 3)
Corsersus oelWeer lETF ard lTu or
Vegaco Proloco|
(Varcr 99)
Lucerl suor|ls V0CP
lo lTu-T 301
(Nov 1999)
lE7F
RFC 3015
H06P
(proposa|}
H06P
(proposa|}
|P06 |P06
For APRCOT, Feb 27, 2001 - 6
Megaco architecture
Hed|a Cateway Layer (HC}
W lrp|ererls correcl|ors
W lrp|ererls or corlro|s erd dev|ce lealures (|rc|ud|rg
ul)
W No know|edge of ca|| |eve| features
Hed|a Cateway 6ontro| Protoco|
W Vasler / s|ave corlro| ol V0s oy V0Cs
- Correcl|or corlro|
- 0ev|ce corlro| ard corl|gural|or
- Everls ard s|gra|s
W 0rthogona| to ca|| contro| protoco|s
Hed|a Cateway 6ontro| Layer (HC6}
W 6onta|ns a|| ca|| contro| |nte|||gence
6a|| contro| (eg. h.323, 8|P.}
|P Phone
Hed|a Cateway
P8TN,
ATH,
etc
Ana|og
Hed|a Cateway
P8TN ||ne
Hed|a Cateway
||res
6a|| Agent
Hed|a Cateway 6ontro||er
P8TN trunk|ng
Hed|a Cateway
lrur|s
For APRCOT, Feb 27, 2001 - 7
Megaco connection modeI
ased on 3 concepts:
Term|nat|on
- lderl|l|es ar erd po|rl lor red|a l|oWs
- lrp|ererls 3|gra|s, ard gererales Everls
- Car appear |r al rosl ore corlexl.
- Perrarerl (prov|s|ored) lerr|ral|ors car ex|sl ouls|de a
corlexl
6ontext
- 0el|res corrur|cal|or oelWeer Terr|ral|ors, acls as a
r|x|rg or|dge
- Corla|rs 1 or rore Terr|ral|ors
- 3upporls ru|l|p|e slrears
8tream
- A corlexl car rave ru|l|p|e slrears, eacr lyp|ca||y lor a
red|ur, e.g. aud|o, v|deo, elc
- Tre V0C spec|l|es Wr|cr slrears a g|ver lerr|ral|or
supporls
V0 V0
T
a
T
o
C
r
T
c
T
d
l2
02=l1l3
l1
l3
03=l1l2
01=l2l3
8|mp|e, powerfu| connect|on|resource mode|
For APRCOT, Feb 27, 2001 - 8
Provides control for manipulating terminations and contexts.
Current Command Set:
Megaco/H.248: Commands
Command Initiator Description
Add MGC Adds a termination to a context.
ModiIy MGC ModiIies a termination`s properties, events, and
signals.
Move MGC Moves a termination Irom one context to another.
Subtract MGC Removes a termination Irom its context.
AuditValue MGC Returns current state oI properties, events, signals,
and statistics.
AuditCapabilities MGC Returns all possible values Ior termination
properties, events, and signals allowed by an MG.
NotiIy MG InIorms MGC oI event occurrence(s).
ServiceChange MGC Takes or places a termination(s) out oI or in service.
MG For registration and restart; notiIies MGC
termination(s) will be taken out oI or returned to
service.
For APRCOT, Feb 27, 2001 - 9
Packages and profiIes
Packages:
Extension mechanism to define new termination and MG
behavior
Adds detailed application semantics to the protocol, e.g. a
package can define the events for DTMF signaling
Profiles:
Define particular applications of Megaco/H.248
Created by industry organizations, e.g. TA
Specifies which packages are to be supported and other
protocol options
For APRCOT, Feb 27, 2001 - 10
Megaco/H.248 Standards Status
Standardization of Base ProtocoI - DONE
Decided as TU-T Recommendation H.248 in June 2000
Published as ETF Megaco RFC 3015, in Nov 2000
Continued work on bug fixes for the base protocol
First issue of H.248 mplementor's Guide approved, Nov 2000
Package definition - Rapid Progression
"Starter Kit (Annex E) defined in base protocol
Additional packages defined as Annexes F, G, J and K to H.248 in Nov 2000
More ongoing in both ETF and TU
Megaco/H.248 InteroperabiIity - Second Event Just CompIeted!
First multi-vendor interoperability event was great success (Aug 2000)
18 participants including MGCs, MGs, and Test equipment
Ad-hoc group formed to test Megaco/H.248 implementations and collect feedback
on specification issues
Line to Line and Line to Trunk calls with and without digit collection completed with
bearer path
Second event just occurred last week (Feb 2001)
For APRCOT, Feb 27, 2001 - 11
SIP overview
SP (Session Initiation Protocol ETF RFC 2543)
Application-layer signaling protocol for creating,
modifying and terminating sessions with one or more
participants
For APRCOT, Feb 27, 2001 - 12
SIP overview
Light-weight generic signaling protocol
Used to initiate sessions and invite members to a
session
Text-based protocol (good for prototyping)
Syntax is textual and based on HTTP
There have been several bake-offs with different
vendors demonstrating interoperability of basic calls
For APRCOT, Feb 27, 2001 - 13
SIP ArchitecturaI ModeI
Pr|vate |P Network
Pub||c |P Network
8|P Agent
Reg|strar
Proxy
8erver
Red|rect
8erver
Locat|on
8erver
8|P Agent
UA8
UA6
UA6
UA8
For APRCOT, Feb 27, 2001 - 14
SIP messages
Message consists of initial line, headers and body
There are two types of SP message
Request
Response
Requests are always initiated by a UAC function
First line contains the method being invoked, e.g.
NVTE
RFC 2543 methods include NVTE, ACK, BYE,
REGSTER, CANCEL, OPTONS
Responses are generated by servers
First line contains the response code
Headers provide information needed to process or route the message
Body contains Session Description Protocol (SDP) describing media
flows or other materials such as encapsulated SUP messages.
New methods and header types can be added at any time without
changing the protocol
For APRCOT, Feb 27, 2001 - 15
SIP status
W ase proloco| |s RFC2513
Preserl|y oe|rg rev|sed - RFC2513o|s |s urder d|scuss|or
W 3lardard|zed |r lre lETF as RFC 2513 |r Varcr 99 (roW oe|rg
lurlrer rel|red |r lre 3lP Wor||rg group).
- RFC 2513 jusl covers oas|c lurcl|ora||ly. Trere are severa| re|aled
|rlerrel dralls cover|rg serv|ces.
W as rap|d|y groW|rg |rduslry rorerlur
- lrlerse ellorls urderWay lo deve|op serv|ce-spec|l|c exlers|ors
For APRCOT, Feb 27, 2001 - 16
SIP-T
SP-T = Session nitiation Protocol Telephony
previously referred to as SP+ or SP BCP-T
a collection of internet drafts that extend SP to support
inter-Media Gateway Controller (MGC) communications.
SP-T is an interface agreement on a collection of
standards as opposed to a separate protocol
SP-T describes how to interwork SP and SUP
SP-T directly negotiates a media connection between
gateways. Endpoint information is carried in SDP
(Session Description Protocol) which can describe both
P and ATM endpoints.
For APRCOT, Feb 27, 2001 - 17
SIP-T purpose
P8TN br|dg|ng (P8TN - |P - P8TN}
P8TN 8|gna||ng |s carr|ed transparent|y over the
|P network
P8TN to |P |nterwork|ng
HC6 1
HC6 2
Proxy
Proxy
8|P enab|ed
network
|P network
887
network
887
network
HC6
Proxy
Proxy
8|P enab|ed
network
|P network
887
network
8|P
agent
For APRCOT, Feb 27, 2001 - 18
SIP-T TechnicaI Approaches
SP-T uses two approaches:
1. Map SUP message contents to fields in the
SP header for interworking with pure SP
agents
2. Encapsulate SUP message within SP
message body for "PSTN bridging
For APRCOT, Feb 27, 2001 - 19
SIP-T ImpIementation
WTrree rajor exlers|ors requ|red:
lNF0 relrod exlers|or lo lre oase proloco| |r add|l|or lo olrers
W 3ess|or |r|l|al|or ard leardoWr |s rol erougr
W V|d-Ca|| everls
W Vore corp|ex serv|ces erao|ed
VlVE Type add|l|or
W 3lardard relrod ol ercapsu|al|rg |egacy s|gra||rg
W 3|rp||l|es lrler-Wor||rg:
- Loca| var|arl
- lrlercorrecl var|arl (LC0)
l3uP lo 3lP Vapp|rg
For APRCOT, Feb 27, 2001 - 20
SIP-T status
Work on SP-T was initiated by the nternational
SoftSwitch Consortium (SC) in early 1999.
SP-T is still a work in progress. The SC is continuing
to develop profiles for SP and telephony interworking.
For APRCOT, Feb 27, 2001 - 21
H.323Overview
Packet-based muIti-media communications system
It incIudes severaI protocoIs
H.225.0 RAS (registration, admission, status .)
H.225.0 Call Signalling
H.245 Logical channel signalling and media control
RFC 1889 RTP/RTCP for media transport
H.450.x Supplementary services
H.225.0 Annex G nter-domain registration and
billing information exchange
The originaI VoIP protocoI suite
WhoIe System Architecture
Provides nteroperability
Transport independence
Platform and application independence
Multipoint support
PrimariIy used in corporate networks
For APRCOT, Feb 27, 2001 - 22
H.323 overview continued
Comprised of severaI protocoIs:
3ysler Corlro| user lrlerlace 0ala v|deo Aud|o
LoWer Layers vary
lP
u0P or TCP u0P
RTP/RTCP
Ca||
Corlro|
RA3
.215
Corlro|
.225
T.120 .21
.23
0.Z11
0.Z22
0.Z23
0.Z28
0.Z29
AAL5
ATH
For APRCOT, Feb 27, 2001 - 23
0ale|eeper
VCu
0aleWay
Erdpo|rls
W car ra|e or rece|ve ca||s
W Rea||zed oy lerr|ra|s ard |og|ca||y preserl |r
0aleWays
0ale|eeper
W address lrars|al|or (lP, le|eprore)
W adr|ss|or corlro|
W carrol gererale or lerr|rale ca||s
0aleWay
W lrlerWor||rg W|lr
W olrer ru|l|red|a lerr|ra|s
W 03TN
Vu|l|po|rl Corlro| ur|l (VCu)
W 3upporl lor ru|l|po|rl corlererces
W A|Ways corla|rs a VC
W 0pl|ora||y corla|rs ar VP
Terr|ra|s
W PCs, lP prores, sel-lop
ooxes
W Aud|o
W v|deo (opl|ora|)
W 0ala (opl|ora|)
H.323 eIements and entities
For APRCOT, Feb 27, 2001 - 24
H.323 current status
H.323 version 4
ncludes many major changes
A significant number of contributions from Nortel
Networks
Approved in November 2000
H.245 and H.225.0 also updated
Currently working on version 5. No release date
specified.
For APRCOT, Feb 27, 2001 - 25
H.323/SIP comparison summary
H.323 SIP
Stds Body
TU-T SG-16 ETF SP, MMusic, ...
Properties
Complex, monolithic design
Difficult to extend & update
Based on H.320 conferencing and SDN
Q.931 legacy ("Bell headed)
Limited potential beyond telephony
Some QoS built in. CODEC types
specified
Higher degree of interoperability
Modular, simplistic design
Easily extended & updated
Based on Web principals ("nternet-
friendly)
Readily extensible beyond telephony
Status
w.r.t. end
device
H.450.x series provides minimal feature
set only, pure peer approach
Adding ( mixed peer/stimulus approach
soon poor architecture)
Slow moving
No real end-device features std, yet
Many options for advanced telephony
features (need to make specific
choices)
Astounding progress, velocity
Industry
acceptance
Established now, primarily system level
Few if any H.323-base telephones
End-user primarily driven by Siemens,
Microsoft (NetMeeting), ntel
Rapidly growing industry momentum,
at system and device level
Growing interest in SP-Phones and
soft clients, products appearing
3lP |s arl|c|paled |org-lerr W|rrer, oul .323 relWor|s W||| rera|r lor sore l|re, ard
are a source ol reverue |r lre |rlerral|ora| rar|el
For APRCOT, Feb 27, 2001 - 26
or More Information
IET:
ETF home page
http://www.ietf.org/
nternet-draft search engine
http://search.ietf.org/search/brokers/internet-drafts/query.html
RFC search engine
http://www.rfc-editor.org/rfcsearch.html
Megaco WG charter
http://ietf.org/html.charters/megaco-charter.html
Megaco documents repository
ftp://standards.nortelnetworks.com/megaco/
ftp://standards.nortelnetworks.com/megaco/docs/latest/
ITU:
TU home page
http://www.itu.int/ITU-T/index.html
SG-16 document repository (H.323, H.248)
ftp://standard.pictel.com/avc-site
Most Megaco/H.248 related documents should also be available through
Megaco WG, above
For APRCOT, Feb 27, 2001 - 27
Thank You!