Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.163  Word version:  17.2.0

Top   Top   Up   Prev   Next
1…   3…   4…   7…   7.3…   8…   B…

 

7  Control plane interworkingWord‑p. 30

7.1  GeneralWord‑p. 31

7.2  Interworking between CS networks supporting ISUP and the IM CN subsystemWord‑p. 32

7.2.1  Services performed by network entities in the control planeWord‑p. 32

7.2.2  Signalling interactions between network entities in the control planeWord‑p. 33

7.2.3  SIP-ISUP protocol interworkingWord‑p. 33

7.2.3.1  Incoming call interworking from SIP to ISUP at I-MGCFWord‑p. 34

7.2.3.1.1  Sending of IAMWord‑p. 34
7.2.3.1.2  Coding of the IAMWord‑p. 35
7.2.3.1.2A  Coding of the IAM when Number Portability is supported |R8|Word‑p. 50
7.2.3.1.2B  Coding of the IAM for Carrier Routeing |R8|Word‑p. 53
7.2.3.1.3  Sending of COTWord‑p. 53
7.2.3.1.3A  Sending of SAM |R8|Word‑p. 54
7.2.3.1.4  Sending of 180 ringingWord‑p. 55
7.2.3.1.4A  Sending of 183 Session Progress for early media scenarios |R7|Word‑p. 58
7.2.3.1.4B  Sending of 181Call is being forwarded |R7|Word‑p. 61
7.2.3.1.4C  Sending of 183 Session Progress for overlap signalling using the in-dialog method |R8|Word‑p. 62
7.2.3.1.4D  Sending of 183 Session Progress to carry ISUP Cause |R9|Word‑p. 62
7.2.3.1.4E  Sending of 183 Session Progress for ICS call |R12|Word‑p. 62
7.2.3.1.5  Sending of the 200 OK (INVITE)Word‑p. 63
7.2.3.1.6  Sending of the Release message (REL)Word‑p. 65
7.2.3.1.7  Coding of the RELWord‑p. 65
7.2.3.1.8  Receipt of the Release MessageWord‑p. 67
7.2.3.1.9  Receipt of RSC, GRS or CGB (H/W oriented)Word‑p. 70
7.2.3.1.9a  Receipt of REFER |R7|Word‑p. 70
7.2.3.1.10  Autonomous Release at I-MGCFWord‑p. 71
7.2.3.1.11  Internal through connection of the bearer pathWord‑p. 71

7.2.3.2  Outgoing Call Interworking from ISUP to SIP at O-MGCFWord‑p. 71

7.2.3.2.1  Sending of INVITEWord‑p. 71
7.2.3.2.1a  Sending of INVITE without determining the end of address signalling |R7|Word‑p. 74
7.2.3.2.2  Coding of the INVITEWord‑p. 76
7.2.3.2.2A  Coding of the INVITE when Number Portability is supported |R8|Word‑p. 88
7.2.3.2.2B  Coding of the INVITE for Carrier Routeing |R8|Word‑p. 90
7.2.3.2.2C  Coding of INVITE with instance-id in form of IMEI URN |R9|Word‑p. 90
7.2.3.2.3  Receipt of CONTINUITYWord‑p. 91
7.2.3.2.4  Sending of ACM and awaiting answer indicationWord‑p. 92
7.2.3.2.5  Coding of the ACMWord‑p. 94
7.2.3.2.6  Sending of the Call Progress message (CPG)Word‑p. 97
7.2.3.2.7  Coding of the CPGWord‑p. 99
7.2.3.2.7a  Receipt of 200 OK(INVITE)Word‑p. 101
7.2.3.2.7b  Internal through connection of the bearer path |R7|Word‑p. 101
7.2.3.2.8  Sending of the Answer Message (ANM)Word‑p. 101
7.2.3.2.9  Coding of the ANMWord‑p. 101
7.2.3.2.10  Sending of the Connect message (CON)Word‑p. 103
7.2.3.2.11  Coding of the CONWord‑p. 103
7.2.3.2.11A  Receipt of a reINVITE request |R8|Word‑p. 103
7.2.3.2.12  Receipt of Status Codes 4xx, 5xx or 6xxWord‑p. 103
7.2.3.2.13  Receipt of a BYEWord‑p. 106
7.2.3.2.14  Receipt of the Release MessageWord‑p. 106
7.2.3.2.15  Receipt of RSC, GRS or CGB (H/W oriented)Word‑p. 107
7.2.3.2.16  Autonomous Release at O-MGCFWord‑p. 107
7.2.3.2.17  Special handling of 580 precondition failure received in response to either an INVITE or UPDATEWord‑p. 107
7.2.3.2.18  Sending of CANCELWord‑p. 108
7.2.3.2.19  Receipt of SIP redirect (3xx) responseWord‑p. 108
7.2.3.2.20  Sending of INFO for overlap signalling using the in-dialog method |R8|Word‑p. 108

7.2.3.3  TimersWord‑p. 109


Up   Top   ToC