(Logo Tech-invite)  

a Portal devoted to SIP and surrounding technologies

   (World Map)    
    Search Home Site Map Contact
 SIP/IMS Standardization
> IETF Standardization Process
> RFCs related to SIP (4 p.) o
> SIP-SIPPING-SIMPLE... I-Ds (22 p.) o
> Audio-Video Transport RFCs (2 p.)
> 3GPP Specifications (12 p.)
> OMA Specifications related to SIP
> TISPAN NGN Specifications (3 p.) o
> SIP Topics
> IMS Topics
 SIP/IMS Call Flows
> RFC3261's Example
> Basic -- RFC3665
> SIP PSTN -- RFC3666 (3 p.)
> SIP Service Examples (19 p.)
> IMS Signaling Flows (35 p.)
 SIP/IMS Architecture
> SIP Protocol Structure
> Dialogs & Routing
> UMTS Network Evolution
 Security
> PKIX-TLS-SMIME... Standards (20 p.) o
> Cryptography Basics
> ASN.1 for PKI Certificate & CRL Profile
> ASN.1 for CMS
> RFC3280's Certificate Examples (4)
> RFC4134's CMS-S/MIME Examples (14)
> RFC4474's SIP Authentication Service
> SSL/TLS Time-Diagrams
> IPSec Guides
 ABNF Grammars
> ABNF Notation & Rules
> URI Generic Syntax
> ABNF for SIP
> SIP Messages & URIs
> SIP Header Fields
> MIME Media Types
> ABNF for SDP
> ABNF for MSRP
> ABNF for MRCPv2
> ABNF for RTSP 2.0
> Internet Message Format
 DiffServ CoS Simulation
> IPVCoSS Simulator
> IP-VPN Case Study
  o (daily updated)

3GPP TS 24.228 -- IMS Signalling flows for session initiation: Non Hiding

MO#2 / S-S#3 / CS-T   (page 2 of 3)

- Mobile Origination, located in home network
- PSTN Termination performed by Home Network of Originator
- CS Network Termination
MO#2 / S-S#3 / CS-T
1) INVITE (UE1 to UE2) 2) 183 Session Progress 3) PRACK (UE1 to UE2) 4) 200 OK   Prev Next
5) UPDATE (UE1 to UE2) 6) 200 OK 7) 180 Ringing (INVITE) 8) PRACK (UE1 to UE2)     a)
9) 200 OK 10) 200 OK (INVITE) 11) ACK (UE1 to UE2)     p.#1 Top

fig3

3a)  from UE1 to P-CSCF1   (a) (b) (c) Prev Next Up

fig3a

- The request does not contain SDP because in the initial SDP offer/answer there was a single media stream with a single codec.
3b)  from P-CSCF1 to S-CSCF1   (a) (b) (c) Prev Next Up

fig3b

3c)  from S-CSCF1 to MGCF1   (a) (b) (c) Prev Next Up

fig3c

MO#2 / S-S#3 / CS-T
1) INVITE (UE1 to UE2) 2) 183 Session Progress 3) PRACK (UE1 to UE2) 4) 200 OK   Prev Next
5) UPDATE (UE1 to UE2) 6) 200 OK 7) 180 Ringing (INVITE) 8) PRACK (UE1 to UE2)     a)
9) 200 OK 10) 200 OK (INVITE) 11) ACK (UE1 to UE2)     p.#1 Top

fig4

4a)  from MGCF1 to S-CSCF1   (a) (b) (c) Prev Next Up

fig4a

4b)  from S-CSCF1 to P-CSCF1   (a) (b) (c) Prev Next Up

fig4b

4c)  from P-CSCF1 to UE1   (a) (b) (c) Prev Next Up

fig4c

MO#2 / S-S#3 / CS-T
1) INVITE (UE1 to UE2) 2) 183 Session Progress 3) PRACK (UE1 to UE2) 4) 200 OK   Prev Next
5) UPDATE (UE1 to UE2) 6) 200 OK 7) 180 Ringing (INVITE) 8) PRACK (UE1 to UE2)     a)
9) 200 OK 10) 200 OK (INVITE) 11) ACK (UE1 to UE2)     p.#1 Top

fig5

5a)  from UE1 to P-CSCF1   (a) (b) (c) Prev Next Up

fig5a

5b)  from P-CSCF1 to S-CSCF1   (a) (b) (c) Prev Next Up

fig5b

- P-Charging-Vector: The P-CSCF added the GPRS access network information to this header, which is removed and stored by the S-CSCF.
5c)  from S-CSCF1 to MGCF1   (a) (b) (c) Prev Next Up

fig5c

MO#2 / S-S#3 / CS-T
1) INVITE (UE1 to UE2) 2) 183 Session Progress 3) PRACK (UE1 to UE2) 4) 200 OK   Prev Next
5) UPDATE (UE1 to UE2) 6) 200 OK 7) 180 Ringing (INVITE) 8) PRACK (UE1 to UE2)     a)
9) 200 OK 10) 200 OK (INVITE) 11) ACK (UE1 to UE2)     p.#1 Top

fig6

6a)  from MGCF1 to S-CSCF1   (a) (b) (c) Prev Next Up

fig6a

6b)  from S-CSCF1 to P-CSCF1   (a) (b) (c) Prev Next Up

fig6b

6c)  from P-CSCF1 to UE1   (a) (b) (c) Prev Next Up

fig6c

  
Last update: December 31, 2007 
  
(to top) © 2005-2008 Joël Repiquet, All Rights Reserved.