SIP-T

What is SIP-T?
 SIP-T(SIP for Telephones) is define by IETF
 Not an extension to SIP – a set of practices for in
terfacing SIP to the PSTN, It provides two key
characteristics
 Encapsulation of ISUP in SIP
 Translation of ISUP parameters to SIP headers
 Implemented at PSTN gateways, and carried en
d-to-end
 SIP-T Specification families :
 RFC3372 : SIP for Telephones (SIP-T): Context and Architecture
s
 RFC3398 : ISUP to SIP Mapping
 RFC2976 : The Session Initiation Protocol (SIP) INFO Method
 RFC3204 : MIME media types for ISUP and QSIG Objects
2
IP network interworking with PSTN
using SIP-T architecture

3
Translation of SIP-T

4
SIP-T scenario 1

5
SIP-T scenario 2

6
Encapsulation of ISUP in SIP-T
 Extending SIP-T by encoding SS7 ISUP signaling messages allows MGCs
using SIP-T to be compatible with the PSTN.
 SIP-T encodes and transmits the native signaling messages from one SCN t
o another. To do this, SIP-T has been extended with MIME encoding of sign
aling messages. The PSTN signaling messages are appended to the SIP-T
messages (such as INVITE, ACK, BYE) using binary encoding.
 The use of MIME encoding with content type: APPLICATION allows PSTN s
ignaling messages to be tunneled between MGCs. The use of content SUB
TYPE enables SS7 ISUP messages to be differentiated by the receiving MG
C.

7
SIP-T scenario 3

8
 PSTN-SIP v.s PSTN-SIP-PSTN
INVITE sip:+1-972-555-2222@proxy.carriew.com/user=phone SIP/2.0
Via : SIP/2/0/UDP gw1/carriwe.com:5060
From : sip:+1-314-555-2222@gw1.carrier.woo,.com;user=phone
To: sip:+1-972-555-2222@proxy.carriew.com/user=phone
Call-ID:12345602@gw1.carrier.com

CSeq: 1 INVITE
Contact : sip:+1-314-555-2222@gw1.carrier.woo,.com;user=phone
Content-Type: application/sdp
Content-length: 156

v=0
o= GATEway1 2890844527 2890844527 IN IP4 gatewayone.carrier.com
s=Session SDP
c= IN IP4 gatewayone carrier.com
t= 0 0
m= audio 3456 RTP/AVP 0
a = rtpmap:0 PCMU/8000

Content-Type: application/isup

9
SIP-I
Specification of SIP-I
 SIP-I (SIPwithEncapsulatedISUP ) is defined
by ITU-T
 ITU-T Series Q Supplement 45: Technical
Report TRQ.2815 (Requirements for Interworking BICC/ISUP
Network with Originating/Destination Networks based on Session Initi
ation Protocol and Session Description Protocol)
 ITU-T Recommendation Q.1912.5 (Interworking betwee
n Session Initiation Protocol (SIP) and the Bearer Independent Call Control Prot
ocol or ISDN User Part

11
 TRQ. 2815
Defines the signaling interworking between the Bearer Independent Ca
ll Control (BICC) or ISDN User Part (ISUP) protocols and Session Initiat
ion Protocol (SIP) with its associated Session Description Protocol (SD
P) at an Interworking Unit (IWU)

Profile C supports the trunking of traf

fic via transit SIP networks using MIM
Profile A was defi E encoded encapsulatedISUP
ned to satisfy the (SIP-I)
demand represen
ted by 3GPP in T
A 24.229 V5.1.0

Profile B complements Profile A, and both

of them are intended to support traffic tha
t terminates within the SIP network.
12
Scenario

13
 Q.1912.5
 ISUP to SIP/SDP mapping
 Message mapping
 Parameter mapping
 Scope of parameter

 Mapping of ISUP parameters to SIP/SDP

 Initial address message (IAM) mapping to SIP

 Encapsulation

SIP Network

ISUP O-IWU SIP-I I-IWU ISUP SIP header ISUP message encapsulated in ful

Scenario Encapsulation format 14

 ISUP- SIP-I Message mapping
ISUP Acro ISUP Message name SIP message GRA Circuit group reset acknowledgement

ACM Address complete 180 Ringing 183 Session progress GRS Circuit group reset BYE 500 Server Internal Error
(profile C only)
IAM Initial address INVITE
ANM Answer 200 OK INVITE
IDR Identification request INFO 183 Session progress
APM Application transport INFO or 183 Session progress
IRS Identification response INFO 183 Session progress
BLA Blocking acknowledgement ISUP side only
INF Information
BLO Blocking ISUP side only
INR Information request
CCR Continuity check request ISUP side only
LPA Loop back acknowledgement
CFN Confusion INFO or 183 Session progress
LOP Loop prevention INFO 183 Session progress
CGB Circuit group blocking BYE 500 Server Internal Error
NRM Network resource management INFO 183 Session progress
CGBA Circuit group blocking ACK ISUP side only
OLM Overload
CGU Circuit group unblocking ISUP side only
PAM Pass-along
CGUA Circuit group unblocking ACK ISUP side only
PRI Pre-release information INFO 183 Session progress
CON Connect 200 OK INVITE
REL Release BYE Message codes]
COT Continuity UPDATE
RES Resume INFO 183 Session progress
CPG Call progress 180 Ringing 183 Session progress
(profile C only) RLC Release complete BYE (note)

CRG Charge information RSC Reset circuit BYE 500 Server Internal Error

CQM Circuit group query SAM Subsequent address

CQR Circuit group query response SDM Subsequent directory number

DRS Delayed release SGM Segmentation Reassembled message ncapsulated.

(reserved – used in
SUS Suspend INFO 183 Session progress
1988 version)
UBL Unblocking
FAA Facility accepted INFO 183 Session progress
UBA Unblocking acknowledgement
FAC Facility INFO 183 Session progress
UCIC Unequipped circuit identification code
FAR Facility request INFO 183 Session progress
UPA User part available
FOT Forward transfer INFO 183 Session progress

FRJ Facility reject INFO 183 Session progress

UPT User part test ISUP side only 15
USR User-to-user information INFO 183 Session progress
SIP interworking capability “profiles”

16
Reference
 Keith Mainwaring :IP Telephony Migration
Challenges
 RFC3398 - ISUP to SIP Mapping
 RFC3372 - SIP-T-Context and Architectures
 ITU-T Recommendation Q.1912.5

17