Media Gateway Controller (MGC)
 - Media Gateway (MGW) interface; Stage 3

3GPP TS 29.232 V9.2.0 (2011-09)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Media Gateway Controller (MGC)
 - Media Gateway (MGW) interface;
Stage 3
(Release 9)
	 EMBED Word.Picture.8  

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.	 
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.


Keywords
UMTS, network, stage 3

3GPP
Postal address

3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
 HYPERLINK "http://www.3gpp.org" http://www.3gpp.org 

Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association

Contents
 TOC \o "1-9" Foreword	 PAGEREF _Toc304579107 \h 9
1	Scope	 PAGEREF _Toc304579108 \h 10
2	References	 PAGEREF _Toc304579109 \h 10
3	Definitions, symbols and abbreviations	 PAGEREF _Toc304579110 \h 13
3.1	Definitions	 PAGEREF _Toc304579111 \h 13
3.2	Symbols	 PAGEREF _Toc304579112 \h 13
3.3	Abbreviations	 PAGEREF _Toc304579113 \h 13
4	UMTS capability set	 PAGEREF _Toc304579114 \h 14
4.1	Profile Identification	 PAGEREF _Toc304579115 \h 14
4.2	Profile Registration	 PAGEREF _Toc304579116 \h 14
5	Naming conventions	 PAGEREF _Toc304579117 \h 14
5.1	MGC/MGW naming conventions	 PAGEREF _Toc304579118 \h 14
5.2	Termination names	 PAGEREF _Toc304579119 \h 14
6	Topology descriptor	 PAGEREF _Toc304579120 \h 14
7	Transaction timers	 PAGEREF _Toc304579121 \h 15
8	Transport	 PAGEREF _Toc304579122 \h 15
9	Multiple Virtual MG.	 PAGEREF _Toc304579123 \h 15
10	Formats and codes	 PAGEREF _Toc304579124 \h 15
10.1	Signalling Objects	 PAGEREF _Toc304579125 \h 15
10.2	SDP Media Parameters for RTP Terminations	 PAGEREF _Toc304579126 \h 19
10.2.1	Speech Codecs	 PAGEREF _Toc304579127 \h 19
10.2.2	DTMF	 PAGEREF _Toc304579128 \h 19
10.2.3	Auxiliary Payloads	 PAGEREF _Toc304579129 \h 19
10.2.3.1	Void	 PAGEREF _Toc304579130 \h 19
10.2.3.2	Void	 PAGEREF _Toc304579131 \h 19
10.2.3.3	Clearmode Codec	 PAGEREF _Toc304579132 \h 19
10.2.3.4	Silence suppression and Comfort Noise	 PAGEREF _Toc304579133 \h 19
10.2.3.5	CS Data Service	 PAGEREF _Toc304579134 \h 19
10.2.3.5.1	CS Data Service with no Redundancy	 PAGEREF _Toc304579135 \h 19
10.2.3.5.2	CS Data Service with Redundancy	 PAGEREF _Toc304579136 \h 20
10.2.4	Other Payload Types	 PAGEREF _Toc304579137 \h 20
11	Mandatory Support of SDP and H.248.1 annex C information elements	 PAGEREF _Toc304579138 \h 21
12	General on Packages and Transactions	 PAGEREF _Toc304579139 \h 22
13	BICC packages	 PAGEREF _Toc304579140 \h 22
13.1	Mandatory BICC packages	 PAGEREF _Toc304579141 \h 22
13.2	Optional BICC packages	 PAGEREF _Toc304579142 \h 22
14	H.248 standard packages	 PAGEREF _Toc304579143 \h 23
14.1	Call independent H.248 transactions	 PAGEREF _Toc304579144 \h 23
14.1.1	MGW Out of service/Maintenance Locking	 PAGEREF _Toc304579145 \h 24
14.1.2	MGW Communication Up	 PAGEREF _Toc304579146 \h 24
14.1.3	MGW Restoration	 PAGEREF _Toc304579147 \h 24
14.1.4	MGW Register	 PAGEREF _Toc304579148 \h 25
14.1.5	MGW Re-register	 PAGEREF _Toc304579149 \h 25
14.1.6	(G)MSC Server Ordered Re-register	 PAGEREF _Toc304579150 \h 25
14.1.7	(G)MSC Server Restoration	 PAGEREF _Toc304579151 \h 25
14.1.8	Termination Out-of-Service	 PAGEREF _Toc304579152 \h 26
14.1.9	Termination Restoration	 PAGEREF _Toc304579153 \h 26
14.1.10	Audit Value	 PAGEREF _Toc304579154 \h 27
14.1.11	Audit Capability	 PAGEREF _Toc304579155 \h 29
14.1.12	MGW Capability Change	 PAGEREF _Toc304579156 \h 29
14.1.13	(G)MSC Server Out of Service	 PAGEREF _Toc304579157 \h 29
14.1.14	MGW Resource Congestion Handling - Activate	 PAGEREF _Toc304579158 \h 30
14.1.15	MGW Resource Congestion Handling - Indication	 PAGEREF _Toc304579159 \h 30
14.1.16	Continuity Check Tone	 PAGEREF _Toc304579160 \h 30
14.1.17	Continuity Check Verify	 PAGEREF _Toc304579161 \h 31
14.1.18	Continuity Check Response	 PAGEREF _Toc304579162 \h 31
14.1.19	Inactivity Timeout - Activate	 PAGEREF _Toc304579163 \h 31
14.1.20	Inactivity Timeout – Indication	 PAGEREF _Toc304579164 \h 31
14.1. 21	Realm Availability Change – Activation	 PAGEREF _Toc304579165 \h 32
14.1. 22	Realm Availability Change – Indication	 PAGEREF _Toc304579166 \h 32
14.2	Call related H.248 transactions	 PAGEREF _Toc304579167 \h 33
14.2.1	Change Flow Direction	 PAGEREF _Toc304579168 \h 35
14.2.2	Isolate Bearer Termination	 PAGEREF _Toc304579169 \h 35
14.2.3	Join Bearer Termination	 PAGEREF _Toc304579170 \h 35
14.2.4	Establish Bearer	 PAGEREF _Toc304579171 \h 35
14.2.5	Prepare Bearer	 PAGEREF _Toc304579172 \h 36
14.2.6	Change Through Connection	 PAGEREF _Toc304579173 \h 38
14.2.7	Activate Interworking Function	 PAGEREF _Toc304579174 \h 38
14.2.8	Release procedures	 PAGEREF _Toc304579175 \h 38
14.2.8.1	Release Bearer	 PAGEREF _Toc304579176 \h 38
14.2.8.2	Release Termination	 PAGEREF _Toc304579177 \h 38
14.2.9	Bearer Released	 PAGEREF _Toc304579178 \h 39
14.2.10	Bearer Established	 PAGEREF _Toc304579179 \h 39
14.2.11	Send Tone	 PAGEREF _Toc304579180 \h 39
14.2.12	Play Announcement	 PAGEREF _Toc304579181 \h 39
14.2.13	Send DTMF	 PAGEREF _Toc304579182 \h 40
14.2.14	Detect DTMF	 PAGEREF _Toc304579183 \h 40
14.2.15	Report DTMF	 PAGEREF _Toc304579184 \h 40
14.2.16	Announcement Completed	 PAGEREF _Toc304579185 \h 40
14.2.17	Activate Voice Processing Function	 PAGEREF _Toc304579186 \h 40
14.2.18	Reserve Circuit	 PAGEREF _Toc304579187 \h 41
14.2.19	Tunnel Information Up	 PAGEREF _Toc304579188 \h 42
14.2.20	Tunnel Information Down	 PAGEREF _Toc304579189 \h 42
14.2.21	Tone Completed	 PAGEREF _Toc304579190 \h 42
14.2.22	Stop Announcement	 PAGEREF _Toc304579191 \h 42
14.2.23	Stop Tone	 PAGEREF _Toc304579192 \h 42
14.2.24	Stop DTMF Detection	 PAGEREF _Toc304579193 \h 42
14.2.25	Stop DTMF	 PAGEREF _Toc304579194 \h 42
14.2.26	Confirm Char	 PAGEREF _Toc304579195 \h 42
14.2.27	Modify Char	 PAGEREF _Toc304579196 \h 43
14.2.28	Reserve Char	 PAGEREF _Toc304579197 \h 43
14.2.29	Bearer Modified	 PAGEREF _Toc304579198 \h 43
14.2.30	Bearer Modification Failed	 PAGEREF _Toc304579199 \h 43
14.2.31	TFO Activation	 PAGEREF _Toc304579200 \h 43
14.2.32	Optimal Codec and Distant List_Notify	 PAGEREF _Toc304579201 \h 43
14.2.33	Codec Modify	 PAGEREF _Toc304579202 \h 44
14.2.34	Distant Codec List	 PAGEREF _Toc304579203 \h 44
14.2.35	Command Rejected	 PAGEREF _Toc304579204 \h 45
14.2.36	Modify Bearer Characteristics	 PAGEREF _Toc304579205 \h 45
14.2.37	Protocol Negotiation Result	 PAGEREF _Toc304579206 \h 46
14.2.38	Rate Change	 PAGEREF _Toc304579207 \h 46
14.2.39	Bearer Modification Support	 PAGEREF _Toc304579208 \h 46
14.2.40	CTM report	 PAGEREF _Toc304579209 \h 47
14.2.41	Prepare IP transport	 PAGEREF _Toc304579210 \h 47
14.2.42	Modify IP transport address	 PAGEREF _Toc304579211 \h 49
14.2.43	Reserve Bearer Characteristics	 PAGEREF _Toc304579212 \h 49
14.2.44	Confirm Bearer Characteristics	 PAGEREF _Toc304579213 \h 50
14.2.45	Trace activation/deactivation	 PAGEREF _Toc304579214 \h 50
14.2.46	Trace Activation result notification	 PAGEREF _Toc304579215 \h 51
14.2.47	Emergency Call Indication	 PAGEREF _Toc304579216 \h 51
14.2.48	TFO status Notify	 PAGEREF _Toc304579217 \h 53
14.2.49	TFO Status	 PAGEREF _Toc304579218 \h 53
14.2.50	Termination heartbeat indication	 PAGEREF _Toc304579219 \h 53
14.2.51	 Reserve RTP Connection Point	 PAGEREF _Toc304579220 \h 54
14.2.52	 Configure RTP Connection Point	 PAGEREF _Toc304579221 \h 56
14.2.53	 Reserve and Configure RTP Connection Point	 PAGEREF _Toc304579222 \h 58
14.2.54	 (void)	 PAGEREF _Toc304579223 \h 60
14.2.55	 Media Inactivity Notification	 PAGEREF _Toc304579224 \h 60
15	UMTS packages	 PAGEREF _Toc304579225 \h 62
15.1	Mandatory UMTS packages	 PAGEREF _Toc304579226 \h 62
15.1.1	3GUP package.	 PAGEREF _Toc304579227 \h 62
15.1.1.1	Properties	 PAGEREF _Toc304579228 \h 62
15.1.1.2	Events	 PAGEREF _Toc304579229 \h 64
15.1.1.3	Signals	 PAGEREF _Toc304579230 \h 64
15.1.1.4	Statistics	 PAGEREF _Toc304579231 \h 64
15.1.1.5	Procedures	 PAGEREF _Toc304579232 \h 64
15.2	Optional UMTS packages	 PAGEREF _Toc304579233 \h 66
15.2.1	Circuit Switched Data package	 PAGEREF _Toc304579234 \h 67
15.2.1.1	Properties	 PAGEREF _Toc304579235 \h 67
15.2.1.2	Events	 PAGEREF _Toc304579236 \h 67
15.2.1.3	Signals	 PAGEREF _Toc304579237 \h 68
15.2.1.4	Statistics	 PAGEREF _Toc304579238 \h 69
15.2.1.5	Procedures	 PAGEREF _Toc304579239 \h 69
15.2.2	TFO package	 PAGEREF _Toc304579240 \h 70
15.2.2.1	Properties	 PAGEREF _Toc304579241 \h 70
15.2.2.2	Events	 PAGEREF _Toc304579242 \h 71
15.2.2.3	Signals	 PAGEREF _Toc304579243 \h 72
15.2.2.4	Statistics	 PAGEREF _Toc304579244 \h 72
15.2.2.5	Procedures	 PAGEREF _Toc304579245 \h 72
15.2.3	3G Expanded Call Progress Tones Generator Package	 PAGEREF _Toc304579246 \h 72
15.2.3.1	Properties	 PAGEREF _Toc304579247 \h 73
15.2.3.2	Events	 PAGEREF _Toc304579248 \h 73
15.2.3.3	Signals	 PAGEREF _Toc304579249 \h 73
15.2.3.4	Statistics	 PAGEREF _Toc304579250 \h 73
15.2.3.5	Procedures	 PAGEREF _Toc304579251 \h 73
15.2.4	Modification Of Link Characteristics Bearer Capability	 PAGEREF _Toc304579252 \h 73
15.2.4.1	Properties	 PAGEREF _Toc304579253 \h 74
15.2.4.2	Events	 PAGEREF _Toc304579254 \h 74
15.2.4.3	Signals	 PAGEREF _Toc304579255 \h 74
15.2.4.4	Statistics	 PAGEREF _Toc304579256 \h 74
15.2.4.5	Procedures	 PAGEREF _Toc304579257 \h 74
15.2.5	Enhanced Circuit Switched Data package	 PAGEREF _Toc304579258 \h 74
15.2.5.1	Properties	 PAGEREF _Toc304579259 \h 74
15.2.5.2	Events	 PAGEREF _Toc304579260 \h 75
15.2.5.3	Signals	 PAGEREF _Toc304579261 \h 75
15.2.5.4	Statistics	 PAGEREF _Toc304579262 \h 75
15.2.5.5	Procedures	 PAGEREF _Toc304579263 \h 75
15.2.6	Cellular Text telephone Modem Text Transport	 PAGEREF _Toc304579264 \h 75
15.2.6.1	Properties	 PAGEREF _Toc304579265 \h 75
15.2.6.2	Events	 PAGEREF _Toc304579266 \h 76
15.2.6.3	Signals	 PAGEREF _Toc304579267 \h 77
15.2.6.4	Statistics	 PAGEREF _Toc304579268 \h 77
15.2.6.5	Procedures	 PAGEREF _Toc304579269 \h 77
15.2.7	IP transport package	 PAGEREF _Toc304579270 \h 77
15.2.8	Flexible Tone Generator Package	 PAGEREF _Toc304579271 \h 77
15.2.8.1	Properties	 PAGEREF _Toc304579272 \h 77
15.2.8.2	Events	 PAGEREF _Toc304579273 \h 77
15.2.8.3	Signals	 PAGEREF _Toc304579274 \h 78
15.2.8.4	Statistics	 PAGEREF _Toc304579275 \h 79
15.2.8.5	Procedures	 PAGEREF _Toc304579276 \h 79
15.2.9	Trace Package	 PAGEREF _Toc304579277 \h 79
15.2.9.1	Properties	 PAGEREF _Toc304579278 \h 79
15.2.9.2	Events	 PAGEREF _Toc304579279 \h 81
15.2.9.3	Signals	 PAGEREF _Toc304579280 \h 82
15.2.9.4	Statistics	 PAGEREF _Toc304579281 \h 82
15.2.9.5	Procedures	 PAGEREF _Toc304579282 \h 82
15.2.10	ASCI Group call package	 PAGEREF _Toc304579283 \h 82
15.2.10.1	Properties	 PAGEREF _Toc304579284 \h 82
15.2.10.2	Events	 PAGEREF _Toc304579285 \h 83
15.2.10.3	Signals	 PAGEREF _Toc304579286 \h 83
15.2.10.4	Statistics	 PAGEREF _Toc304579287 \h 83
15.2.10.5	Procedures	 PAGEREF _Toc304579288 \h 83
15.2.11	3G Interface Type package	 PAGEREF _Toc304579289 \h 83
15.2.11.1	Properties	 PAGEREF _Toc304579290 \h 83
15.2.11.2	Events	 PAGEREF _Toc304579291 \h 84
15.2.11.3	Signals	 PAGEREF _Toc304579292 \h 84
15.2.11.4	Statistics	 PAGEREF _Toc304579293 \h 84
15.2.11.5	Procedures	 PAGEREF _Toc304579294 \h 84
Annex A (informative):	Framing protocol Interworking Function (FPIF)	 PAGEREF _Toc304579295 \h 85
A.1	Introduction	 PAGEREF _Toc304579296 \h 85
A.2	FPIF procedures with respect to Iu framing protocol	 PAGEREF _Toc304579297 \h 86
A.2.1	Payload	 PAGEREF _Toc304579298 \h 86
A.2.2	RFCIs	 PAGEREF _Toc304579299 \h 86
A.2.3	FQC	 PAGEREF _Toc304579300 \h 86
A.2.4	Frame number	 PAGEREF _Toc304579301 \h 86
A.3	Relay of status information	 PAGEREF _Toc304579302 \h 87
A.3.1	Void	 PAGEREF _Toc304579303 \h 87
A.3.2	Rate Control Frames	 PAGEREF _Toc304579304 \h 87
A.3.2	Time Alignment	 PAGEREF _Toc304579305 \h 87
Annex B (informative):	Examples for Usage of the 3GUP Package "Initialization Direction" Property	 PAGEREF _Toc304579306 \h 88
Annex C (Normative):	Profile description	 PAGEREF _Toc304579307 \h 90
C.1	Profile Identification	 PAGEREF _Toc304579308 \h 90
C.2	Summary	 PAGEREF _Toc304579309 \h 90
C.3	Gateway Control Protocol Version	 PAGEREF _Toc304579310 \h 90
C.4	Connection Model	 PAGEREF _Toc304579311 \h 90
C.5	Context Attributes	 PAGEREF _Toc304579312 \h 91
C.6	Terminations	 PAGEREF _Toc304579313 \h 91
C.6.1	Termination Names	 PAGEREF _Toc304579314 \h 91
C.6.1.1	General	 PAGEREF _Toc304579315 \h 91
C.6.1.2	ASN.1 Coding	 PAGEREF _Toc304579316 \h 91
C.6.1.2.1	General Structure	 PAGEREF _Toc304579317 \h 91
C.6.1.2.2	Termination naming convention for TDM terminations	 PAGEREF _Toc304579318 \h 92
C.6.1.3	ABNF Coding	 PAGEREF _Toc304579319 \h 92
C.6.1.3.1	General Structure	 PAGEREF _Toc304579320 \h 92
C.6.1.3.2	Termination naming convention for TDM terminations	 PAGEREF _Toc304579321 \h 92
C.6.1.3.3	Termination naming convention for Ephemeral terminations	 PAGEREF _Toc304579322 \h 93
C.6.2	Multiplexed terminations	 PAGEREF _Toc304579323 \h 93
C.7	Descriptors	 PAGEREF _Toc304579324 \h 93
C.7.1	Stream Descriptor	 PAGEREF _Toc304579325 \h 93
C.7.1.1	LocalControl Descriptor	 PAGEREF _Toc304579326 \h 93
C.7.2	Events Descriptor	 PAGEREF _Toc304579327 \h 93
C.7.3	EventBuffer Descriptor	 PAGEREF _Toc304579328 \h 95
C.7.4	Signals Descriptor	 PAGEREF _Toc304579329 \h 96
C.7.5	DigitMap Descriptor	 PAGEREF _Toc304579330 \h 97
C.7.6	Statistics Descriptor	 PAGEREF _Toc304579331 \h 97
C.7.7	ObservedEvents Descriptor	 PAGEREF _Toc304579332 \h 97
C.7.8	Topology Descriptor	 PAGEREF _Toc304579333 \h 97
C.7.9	Error Descriptor	 PAGEREF _Toc304579334 \h 97
C.7.10	TerminationState Descriptor	 PAGEREF _Toc304579335 \h 98
C.8	Command API	 PAGEREF _Toc304579336 \h 99
C.8.1	Add	 PAGEREF _Toc304579337 \h 99
C.8.2	Modify	 PAGEREF _Toc304579338 \h 99
C.8.3	Subtract	 PAGEREF _Toc304579339 \h 99
C.8.4	Move	 PAGEREF _Toc304579340 \h 100
C.8.5	AuditValue	 PAGEREF _Toc304579341 \h 100
C.8.6	AuditCapability	 PAGEREF _Toc304579342 \h 100
C.8.7	Notify	 PAGEREF _Toc304579343 \h 101
C.8.8	ServiceChange	 PAGEREF _Toc304579344 \h 101
C.8.9	Manipulating and auditing context attributes	 PAGEREF _Toc304579345 \h 103
C.9	Generic command syntax and encoding	 PAGEREF _Toc304579346 \h 103
C.10	Transactions	 PAGEREF _Toc304579347 \h 103
C.11	Messages	 PAGEREF _Toc304579348 \h 104
C.12	Transport	 PAGEREF _Toc304579349 \h 104
C.13	Security	 PAGEREF _Toc304579350 \h 105
C.14	Packages	 PAGEREF _Toc304579351 \h 106
C.14.1	Generic Package	 PAGEREF _Toc304579352 \h 109
C.14.2	Base Root Package	 PAGEREF _Toc304579353 \h 110
C.14.3	Tone Generator Package	 PAGEREF _Toc304579354 \h 111
C.14.4	Tone Detection Package	 PAGEREF _Toc304579355 \h 112
C.14.5	Basic DTMF Generator Package	 PAGEREF _Toc304579356 \h 113
C.14.6	Basic DTMF Detection Package	 PAGEREF _Toc304579357 \h 114
C.14.7	Continuity Package	 PAGEREF _Toc304579358 \h 115
C.14.8	TDM Circuit Package	 PAGEREF _Toc304579359 \h 116
C.14.9	Text Telephony Package	 PAGEREF _Toc304579360 \h 117
C.14.10	Call Discrimination Package	 PAGEREF _Toc304579361 \h 118
C.14.11	Announcement Package	 PAGEREF _Toc304579362 \h 120
C.14.12	Media Gateway Resource Congestion handling Package	 PAGEREF _Toc304579363 \h 121
C.14.13	Hanging Termination Detection Package	 PAGEREF _Toc304579364 \h 121
C.14.14	Bearer Characteristics Package	 PAGEREF _Toc304579365 \h 122
C.14.15	Generic Bearer Connection Package	 PAGEREF _Toc304579366 \h 123
C.14.16	Bearer Control Tunnelling Package	 PAGEREF _Toc304579367 \h 124
C.14.17	Basic Call Progress Tones Generator with Directionality	 PAGEREF _Toc304579368 \h 125
C.14.18	Expanded Call Progress Tones Generator Package	 PAGEREF _Toc304579369 \h 126
C.14.19	Basic Services Tones Generation Package	 PAGEREF _Toc304579370 \h 127
C.14.20	Expanded Services Tones Generation Package	 PAGEREF _Toc304579371 \h 128
C.14.21	Intrusion Tones Generation Package	 PAGEREF _Toc304579372 \h 129
C.14.22	Business Tones Generation Package	 PAGEREF _Toc304579373 \h 130
C.14.23	3GUP Package	 PAGEREF _Toc304579374 \h 131
C.14.24	Modification of Link Characteristics Bearer Capability	 PAGEREF _Toc304579375 \h 132
C.14.25	TFO package	 PAGEREF _Toc304579376 \h 133
C.14.26	Circuit Switched Data package	 PAGEREF _Toc304579377 \h 134
C.14.27	Enhanced Circuit Switched Data package	 PAGEREF _Toc304579378 \h 135
C.14.28	3G Expanded Call Progress Tones package	 PAGEREF _Toc304579379 \h 135
C.14.29	Cellular Text Telephone Modem Text Transport Package	 PAGEREF _Toc304579380 \h 136
C.14.30	Void	 PAGEREF _Toc304579381 \h 137
C.14.31	Flexible Tone Generator package	 PAGEREF _Toc304579382 \h 138
C.14.32	Trace Package	 PAGEREF _Toc304579383 \h 139
C.14.33	ASCI Group call	 PAGEREF _Toc304579384 \h 140
C.14.34	IP domain connection	 PAGEREF _Toc304579385 \h 141
C.14.35	Inactivity Timer Package	 PAGEREF _Toc304579386 \h 142
C.14.36	3G Interface Type package	 PAGEREF _Toc304579387 \h 143
C.14.37	Differentiated Services (ds)	 PAGEREF _Toc304579388 \h 144
C.14.38	Gate Management (gm)	 PAGEREF _Toc304579389 \h 145
C.14.39	Traffic management (tman)	 PAGEREF _Toc304579390 \h 146
C.14.40	IP Realm Availability (ipra)	 PAGEREF _Toc304579391 \h 147
C.14.41	RTCP Handling Package (rtcph)	 PAGEREF _Toc304579392 \h 147
C.14.42	Application Data Inactivity Detection (adid)	 PAGEREF _Toc304579393 \h 148
C.15	Mandatory support of SDP and Annex C information elements	 PAGEREF _Toc304579394 \h 149
C.16	Optional support of SDP and Annex C information elements	 PAGEREF _Toc304579395 \h 150
Annex D (informative):	Change history	 PAGEREF _Toc304579396 \h 151

Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x	the first digit:
1	presented to TSG for information;
2	presented to TSG for approval;
3	or greater indicates TSG approved document under change control.
y	the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z	the third digit is incremented when editorial only changes have been incorporated in the document.
1	Scope
The present document describes the protocol to be used on the Media Gateway Controller (MGC) – Media Gateway (MGW) interface. The Media Gateway Controllers covered in this specification are the MSC server and the GMSC server. The basis for this interface profile is the H.248.1 [10] protocol as specified in ITU-T. The usage of this protocol is described in 3GPP TS 23.205 [2] and 3GPP TS 29.205 [7] for BICC circuit switched core network, in 3GPP TS 23.231 [54] and 3GPP TS 29.231 [57] for SIP-I circuit switched core network.
This profile includes the support for the enhanced MSC server to provide access to IMS Centralised services as described in 3GPP TS 23.292 [59] and thus the procedures related to this interface are described in 3GPP TS 29.292 [60]. As a result the interworking with SIP and the associated MGW control procedures described in 3GPP TS 29.163[61] for the interworking between BICC/ISUP circuit switched core network and IP Multimedia core network are incorporated.
This specification describes the changes to H.248 which are needed to handle 3GPP specific traffic cases. This is done by using the H.248 standard extension mechanism. In addition certain aspects of the base protocol H.248 are not needed for this interface and thus excluded by this profile.
2	References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]	3GPP TS 23.153: "Out of band transcoder control; Stage 2".
[2]	3GPP TS 23.205: "Bearer independent circuit-switched core network; Stage 2".
[3]	3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[4]	3GPP TS 25.415: "UTRAN Iu interface user plane protocols".
[5]	3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3".
[6]	3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
[7]	3GPP TS 29.205: "Application of Q.1900 series to Bearer Independent circuit-switched network architecture; Stage 3".
[8]	3GPP TS 29.415: "Core Network Nb interface user plane protocols".
[9]	3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC ‑ BSS) interface; Layer 3 specification".
[10]	ITU-T Recommendation H.248.1 (05/2002): "Gateway control protocol". Version 2, including the Corrigendum1 for Version 2 (03/04).
[11]	ITU-T Recommendation Q.2210 (1996): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140".
[12]	IETF RFC 2960: "Stream control transmission protocol".
[13]	3GPP TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3".
[14]	ITU-T Recommendation H.248.8 (09/2005): "Error codes and service change reason description".
[15] 	ITU-T Recommendation H.248.10 (07/2001): "Media gateway resource congestion handling package".
[16]	3GPP TS 26.103: "Speech codec list for GSM and UMTS".
[17] 	ITU-T Recommendation H.248.2 (01/2005): "Facsimile, text conversation and call discrimination packages".
[18]	3GPP TS 26.226: "Cellular text telephony; Transport of text in the voice channel".
[19]	ITU-T Recommendation T.140 (02/1998): "Protocol for multimedia application text conversation".
[20]	3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".
[21]	3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling".
[22]	3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2".
[23]	ITU-T Recommendation Q.1950 (12/2002):: "Bearer independent call bearer control protocol".
[24]	ITU-T Recommendation Q.765.5 (04/2004): "Signalling system No. 7 - Application transport mechanism: Bearer Independent Call Control (BICC)".
[25]	ITU-T Recommendation G.711 (11/1988): "Pulse code modulation (PCM) of voice frequencies". 
[26]	3GPP TS 26.102: "3rd Generation Partnership Project; Mandatory speech codec; AMR speech codec; Interface to Iu, Uu and Nb"
[27]	3GPP TS 23.014: "Technical Specification Group Core Network; Support of Dual Tone Multi-Frequency (DTMF) signalling".
[28] 	ITU-T Recommendation H.248.7 (03/2004): "Generic Announcement Package".
[29]	3GPP TS 32.421: " Subscriber and equipment trace: Trace concepts and requirements ".
[30]	3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management".
[31]	3GPP TS 32.423: "Subscriber and equipment trace: Trace data definition and management".
[32]	3GPP TS 29.414: "Core Network Nb data transport and transport signalling".
[33]	ITU-T Recommendation X.213 (11/95): "Information technology - Open systems interconnection - Network Service Definitions".
[34]	Void
[35]	3GPP TS 43.045: "Technical Realization Of Facsimile Group 3 service - Transparent".
[36]	ITU-T Recommendation H.248.36 (09/2005): "Hanging Termination Detection Package".
[37]	3GPP TS 23.172 : "Technical Specification Group Core Network and Terminals;Technical realization of Circuit Switched (CS);multimedia service UDI/RDI fallback and service modification;Stage 2
[38]	3GPP TS 33.210 : "Technical Specification Group Services and System Aspects;3G Security; Network Domain Security; IP Network Layer Security. 
[39]	3GPP TS 43.068: " Voice Group Call Service (VGCS)".
[40]	3GPP TS 43.069: " Voice Broadcast Service (VBS)".
[41]	ITU-T Recommendation X.690: "ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)"
[42]	ITU-T Recommendation H.248.41 (05/2006): " IP Domain Connection package ".
[43]	3GPP TS 23.003: "Numbering, addressing and identification".
[44]	RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change"
[45]	ITU-T Recommendation H.248.14 (03/2002):"Inactivity timer package"
[46]	Void
[47]	Void
[48]	3GPP TS 26.236: "Packet switched conversational multimedia applications; Transport protocols".
[49]	Void
[50]	Void
[51]	3GPP TS 29.332:  "Media Gateway Control Funtion (MGCF) - IM Media Gateway; Mn Interface". 
[52]	IETF RFC 3556: " Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth".
[53]	IETF RFC 4566: "SDP: Session Description Protocol".
[54]	3GPP TS 23.231: "SIP-I based circuit switched core network; stage 2".
[55]	IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call".
[56]	Void
[57]	3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3".
[58]	3GPP TS 32.407: "Telecommunication Management; Performance Management (PM) Performance measurements Core Network (CN) Circuit Switched (CS) domain"
[59]	3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2".
[60]	3GPP TS 29.292: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and MSC Server for IMS Centralized Services (ICS)".
[61]	3GPP TS 29.163: "Interworking between the IM CN subsystem and CS networks – Stage 3".
[62]	Void
[63]	3GPP TS 26.236: "Packet switched conversational multimedia applications; Transport protocols".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[64]	IETF RFC 2198: "RTP Payload for Redundant Audio Data".
[65]	3GPP TS 48.103: "Base Station System – Media GateWay (BSS-MGW) interface; User Plane transport mechanism".
[66]	ITU-T Recommendation H.248.57 (06/2008): "Gateway control protocol: RTP Control Protocol Package".
[67]	ITU-T Recommendation H.248.43 (06/2008): "Gateway control protocol: Gate Management and Gate Control packages".
[69]	ITU-T Recommendation H.248.53 (06/2008) inclusive Revision 1 (03/2009): "Gateway control protocol: Traffic management packages".
[70]	ITU-T Recommendation H.248.52 Amendment 1 (03/2009): "Gateway control protocol: QoS support packages ".
Editor’s Note:	Amendment 1 is still a Pre-published version. This should be checked when it is published.
[71]	ITU-T Recommendation H.248.40 (01/2007): "Gateway control protocol: Application Data Inactivity Detection package".
[72]	ITU-T Recommendation H.248.41 Amendment 1 (06/2008): "Gateway control protocol: IP domain connection package: IP Realm Availability Package".
[73]	IETF RFC 2216 (1997): "Network Element Service Specification Template".
3	Definitions, symbols and abbreviations
3.1	Definitions
For the purposes of the present document, the following terms and definitions apply:
context (H.248): association between a number of Terminations
The context describes the topology (who hears/sees whom) and the media mixing and/or switching parameters if more than two terminations are involved in the association.
package (H.248): different types of gateways may implement terminations which have differing characteristics
Variations in terminations are accommodated in the protocol by allowing terminations to have optional properties. Such options are grouped into packages, and a termination may realise a set of such packages.
termination (H.248): logical entity on an MGW which is the source and/or sink of media and/or control streams
A termination is described by a number of characterising properties, which are grouped in a set of descriptors which are included in commands. Each termination has a unique identity (TerminationID).
termination property (H.248): used to describe terminations
Related properties are grouped into descriptors. Each termination property has a unique identity (PropertyID).
3.2	Symbols
For the purposes of the present document, the following symbols apply:
Iu	Interface between the RNS and the core network. It is also considered as a reference point.
Mc	Interface between the server and the media gateway.
3.3	Abbreviations
For the purposes of the present document, the following abbreviations apply:
BICC	Bearer Independent Call Control
M3UA	SS7 MTP3 – User Adaptation Layer
MGC	Media Gateway Controller
MTP3	Message Transfer Part layer 3
RFC	Request For Comment; this includes both discussion documents and specifications in the IETF domain
SCTP	Stream Control Transmission Protocol
TFO	Tandem Free Operation
TrFO	Transcoder Free Operation
4	UMTS capability set
The support of the Mc interface capability set shall be identified by the Mc profile and support of this profile shall then be indicated in ServiceChange procedure via the ServiceChangeProfile parameter as defined in H.248.1 [10] and clarified in section 4.2.The mandatory parts of this profile shall be used in their entirety. Failure to do so will result in a non-standard implementation.
ITU-T Recommendation H.248.1 [10] shall be the basis for thisprofile. The compatibility rules for packages, signals, events, properties and statistics and the H.248 protocol are defined in ITU-T Recommendation H.248.1 [10] Their use or exclusion for this interface is clarified in clause 12.
4.1	Profile Identification
For Profile Identification see Annex C.1.
4.2	Profile Registration
The following description is based on H.248.1 profile registration procedure with some clarifications. The reply to the ServiceChange Request containing the SCP parameter indicates if the MSC Server supports the requested profile or if it does not support it and wants to propose an alternative profile. The profile (name and version) is only returned in the reply if the MGC cannot support the specified profile in the ServiceChangeRequest. The returned reply shall indicate the profile and version supported or "NoProfile" if no profile is supported. Upon reception of a profile in the reply, if the MGW supports the indicated profile, it shall issue a new ServiceChange Request with the agreed profile to explicitly confirm the acceptance of the profile to the MGC ; otherwise, if the MGW does not support the indicated profile, it may continue the registration or re-registration procedure by issuing a new ServiceChange Request with an alternative profile ; until such procedure is successfully completed the MGW shall remain out of service. In the instance that the MGW did not indicate a profile in the original ServiceChangeRequest and the MGC returned a profile in the reply, the MGW shall issue a new ServiceChangeRequest with the appropriate profile or "NoProfile" if no profile is supported. If the profile is not returned the MGC shall use the capabilities specified by the Profile indicated in the service change request.
NOTE:	It should be observed that the profile registration is not a "cold calling" negotiation; the operator shall have configured the network to support certain profiles and so the profile registration within the Mc interface permits network upgrade scenarios but otherwise is simply a means to confirm the connection of the profile to be used over the Mc interface between MGC and  MGW.
5	Naming conventions
5.1	MGC/MGW naming conventions
For definition see Annex C.11.
5.2	Termination names
For definition see Annex C.6.1.
6	Topology descriptor
For definition see Annex C.7.8.
7	Transaction timers
For definition see Annex C.10.
8	Transport
Each implementation of the Mc interface should provide the appropriate protocol options: MTP3B as defined in ITU-T Recommendation Q.2210 [11] (for ATM signalling transport) or SCTP as defined in RFC 2960 [12] and as updated by RFC3309 [44] (for IP signalling transport) and in the case where the signalling relation consists of both ATM signalling transport and IP signalling transport the M3UA protocol layer (3GPP TS 29.202 [13]) shall be added to SCTP to provide interworking. M3UA layer may also be added to SCTP for pure IP signalling transport. IPsec shall not be used by MSC Server or MGW for the Mc interface. Normally the Mc interface lies within a single operator's secure domain. If this is not the case then a Za interface (Security Gateway deploying IPSec) may be required, however this is a separate logical function/entity and thus is not attributed to Mc profile, the MSC Server or the MGW; for further details see 3GPP TS 33.210 [38]. For further definition see Annex C.12.
9	Multiple Virtual MG.
If an MGW is connected to more than one (G)MSC, the MGW shall fulfil the requirements outlined in the subclause "Multiple virtual MGW" in ITU-T Recommendation H.248.1 [10].
10	Formats and codes
10.1	Signalling Objects
Table 10.1 shows the parameters which are required, in addition to those defined in the subclause "Formats and Codes" of ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
The coding rules applied in ITU-T Recommendation H.248.1 [10] for the applicable coding technique shall be followed for the UMTS capability set.
Unsupported values of parameters or properties may be reported by the MGW and shall be supported by the MSC as such by using H.248.1 error code #449 " Unsupported or Unknown Parameter or Property Value ". Error Text in the error Descriptor: The unsupported or unknown value is included in the error text in the error descriptor.
Table 10.1: Additional parameters required
Signalling Object
H.248 Descriptor
Coding
actprot
Signal descriptor
As for the signal "Activate protocol" in subclause 15. 2.1.3
Mode
Local control
As for the property "UP mode of operation" in subclause 15.1.1.1
Version
Local control
As for the property "Upversion" in subclause 15.1.1.1
Value
Local control
As for the property " Delivery of erroneous SDUs" in subclause 15.1.1.1
Interface
Local control
As for the property " Interface" in subclause 15.1.1.1
Initdirection
Local control
As for the property " Initialization Direction" in subclause 15.1.1.1
PLMN bearer capability
Local control
As for the property "PLMN BC" in subclause 15. 2.1.1



Coding
Local control
As for the property " GSM channel coding" in subclause 15. 2.1.1
tfoactvalue
Local control
As for the property " TFO activity control" in subclause 15. 2.2.1
TFOcodeclist (NOTE)
 Local control
As for the property" TFO Codec List" in subclause 15. 2.2.1
Result
ObservedEvent descriptor
As for the ObservedEventDescriptor parameter "Protocol Negotiation Result" in subclause 15. 2.1.2
Cause
ObservedEvent descriptor
As for the ObservedEventDescriptor parameter "Protocol Negotiation Result" in subclause 15. 2.1.2
Rate 
ObservedEvent descriptor
As for the ObservedEventDescriptor parameter "Rate Change" in subclause 15. 2.1.2
Optimalcodec
ObservedEvent descriptor
As for the ObservedEventDescriptor parameter "Optimal Codec Type" in subclause 15. 2.2.2
Distlist
ObservedEvent descriptor
As for the ObservedEventDescriptor parameter "Distant TFO List" in subclause 15. 2.2.2
On/Off
Local control
As for the property "Echo cancelling" in subclause E.13.1 in ITU‑T Recommendation H.248.1 [10] . Default value is Off.
Error
Error descriptor
As defined in the subclause "Command error code" in ITU‑T Recommendation H.248.1 [10]
MGW Resource Congestion Handling - Indication
EventDescriptor
As for the EventDescriptor in subclause 4.2.1/H.248.10 "MGCongestion"
Reduction
ObservedEvent descriptor
As for the ObserverdEventDescriptor in subclause 4.2.1/H.248.10 "MGCongestion".
Bearer Modification Support
EventDescriptor
As for the EventsDescriptor in "Bearer Modification Support" in subclause 15. 2.3.2.
Bearer modification possible
ObservedEvent descriptor
As for the ObserverdEventDescriptor in "Bearer Modification Support" in subclause 15. 2.3.2.
Ctmstate 
TerminationState
As for the TerminationState "Text termination connection state" in subclause 15. 2.6.1.
Ctmtransport
Local control
As for the property  "Text Transport"  in subclause 15.2.6.1.
Ctmtext version
Local control
As for the property " Text Protocol Version" in subclause 15.2.6.1.
Connchng
ObservedEventDescriptor
As for the ObservedEventDescriptor " Connection State Change in subclause 15.2.6.2
Ctmbits
Statistics descriptor
As for the Statistics descriptor "Characters Transferred" in subclause 15.2.6.4
Bitrate
Local control
As for the property" Bitrate" in subclause 15.1.7.1
Iu IP Address
Local Descriptor or Remote Descriptor control
As defined in C.16 
IP Address
Local Descriptor or Remote Descriptor
 in SDP “c-line”

Port
Local Descriptor or Remote Descriptor
 in SDP m-line.
 in SDP m-line shall be set to value "RTP/AVP" for voice service
Editor’s note: the value for other services in FFS.
Iu IP Port
Local Descriptor or Remote Descriptor
As defined in C.16. Port Type is not defined in the Mc profile and shall be assumed always to be UDP.
Flextone
Signal descriptor
As for the signal "Flexible Tone " in subclause 15.2.8.3 
Trace reference
Local control
As for the property "Trace Reference" in subclause 15.2.9.1
Trace Recording Session Reference
Local control
As for the property "Trace Recording Session Reference" in subclause 15.2.1.1
Trace Depth
Local control
As for the property "Trace Depth" in subclause 15.2.9.1
Triggering  events
Local control
As for the property "Triggering events" in subclause 15.2.9.1
List of interfaces
Local control
As for the property "List of interfaces" in subclause 15.2.9.1
IMSI
Local control
As for the property "IMSI" in subclause 15.2.9.1
IMEI(SV)
Local control
As for the property "IMEI(SV)" in subclause 15.2.9.1
Trace activativity request
Local control
As for the property "Trace Activation Control" in subclause 15.2.9.1
Trace Activation Result
ObservedEvents descriptor
As for the ObservedEventDescriptor " Trace Activation result" in subclause 15.2.9.2
TFO Status
EventDescriptor
As for the EventsDescriptor in "TFO_Status Event" in subclause 15.2.2.2
tfostatus
ObservedEvent descriptor
As for the ObservedEventDescriptor parameter "TFO Status" in subclause 15.2.2.2
termination heartbeat
EventDescriptor
As for the EventsDescriptor in subclause 5.2.1/H.248.36 "Termination Heartbeat"
Termination heartbeat
ObservedEvent descriptor
As for the ObserverdEventDescriptor in subclause 5.2.1/H.248.36 "Termination Heartbeat"
Needed conference terminations
Local control
As for the property "Number of needed conference terminations" in subclause 15.2.10.1
Desired listener context terminations
Local control
As for the property "Number of desired listener context terminations" in subclause 15.2.10.1
IP realm identifier
Local control
As for the property "IP realm identifier " in subclause 5.1.1/H.248.41
inactivity timeout
EventDescriptor
As for the EventsDescriptor in subclause 5.2/H.248.14 "Inactivity Timeout"
Inactivity timeout
ObservedEvent descriptor
As for the ObserverdEventDescriptor in subclause 5.2/H.248.14 " Inactivity Timeout "
Warning tone
Signal descriptor
As for the signal "CAMEL Prepaid Warning Tone " in subclause 15.2.3.3
Reserve_Value
Local Control
ITU-T Recommendation H.248.1 [10] Mode property.
Binary Encoding: 	Encoding as per ITU-T Recommendation H.248.1 Annex A "reserveValue"
Textual Encoding: 	Encoding as per ITU-T Recommendation H.248.1 Annex B "reservedValueMode".
Codec List
Local Descriptor or Remote Descriptor
 in a single SDP m-line.
For a static RTP payload type, the codec type should be implied by the RTP payload type, if not then each codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). See Clause 10.2.
For a dynamic RTP payload type, for each codec information on the codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). See Clause 10.2
RtcpbwRS
Local Descriptor or Remote Descriptor
 in SDP “b:RS”-lineas per IETF RFC 3556 [52].

RtcpbwRR
Local Descriptor or Remote Descriptor
 in SDP “b:RR”-line as per IETF RFC 3556 [52]. 

RTPpayload
Local Descriptor or Remote Descriptor
 in SDP m-line

IP interface
Local Control
As for the property "IP interface type " in subclause 15.2.11.1
Changed Realms
Observed Events
According to Observed Events Parameters for Available Realms Changed event in ITU-T Recommendation H.248.41 [72].
Delay Variation Tolerance
Local Control
This is the tman/dvt property from ITU-T Recommendation H.248.53 [69]
Diffserv Code Point
Local Control
Defined according to the Differentiated Services Code Point property in ITU-T Recommendation H.248.52 [70].
Diffserv Tagging Behaviour
Local Control
Defined according to the Tagging Behaviour property in ITU-T Recommendation H.248.52 [70].
IP Version
Local Descriptor or Remote Descriptor
 in SDP "c-line", see C.16

Maximum Burst Size
Local Control
This is the tman/mbs property from ITU-T Recommendation H.248.53 [69]
Media Inactivity Detection
Events, 
Observed Events
Defined according to IP Flow Stop Detection event in ITU-T Recommendation H.248.40 [71].
Media Inactivity Detection Time
Events
As for the Event Parameter in ITU-T Recommendation H.248.40 [71] "Detection Time"
Media Inactivity Detection Direction
Events
As for the Event Parameter in ITU-T Recommendation H.248.40 [71] "Direction"
Peak Data Rate
Local Control
This is the tman/pdr property from ITU-T Recommendation H.248.53 [69].
Policing Required
Local Control
This is the tman/pol property from ITU-T Recommendation H.248.53 [69].
Realm Availability Change
Events, 
Observed Events
According to Available Realms Changed event in ITU-T Recommendation H.248.41 [72].
Remote Source Address Filtering
Local Control
Defined according to Remote Source Address Filtering property in ITU-T Recommendation H.248.43 [67].
Remote Source Address Mask
Local Control
Defined according to Remote Source Address Mask property in ITU-T Recommendation H.248.43 [67].
Remote Source Port Filtering
Local Control
Defined according to Remote Source Port Filtering property in ITU-T Recommendation H.248.43 [67].
Remote Source Port
Local Control
Defined according to Remote Source Port property in ITU-T Recommendation H.248.43 [67].
Remote Source Port Range
Local Control
Defined according to Remote Source Port Range property in ITU-T Recommendation H.248.43 [67].
RTCP allocation
Local Control
Defined according to RTCP Allocation Specific Behaviour 
  property in ITU-T Recommendation H.248.57 [66].
Sustainable Data Rate
Local Control
This is the tman/sdr property from ITU-T Recommendation H.248.53 [69]
NOTE: 	TFOcodeclist was named Codeclist in pre-release 8.

10.2	SDP Media Parameters for RTP Terminations
10.2.1	Speech Codecs
The speech codecs and their configuration permitted for use over SIP-I and AoIP are defined in 3GPP TS 26.102 [26], Clauses 9 and 10. The SDP parameters for those codecs are defined in 3GPP TS 26.103 [16], Clause 7. 
The speech codecs permitted for use for Enhanced MSC are defined in 3GPP TS 26.236 [63].
Codec types may have static or dynamic RTP payload types as defined by the above references. 
For dynamic payload type being used the codecs shall be signalled accordingly in the SDP "a=rtpmap"-line, where the selected  options are expressed as MIME parameters in SDP "a=fmtp"-line.
For static payloads type being used the codecs shall be allowed to be signalled accordingly in the SDP "a=rtpmap"-line,when the selected options are expressed as MIME parameters in SDP "a=fmtp"-line. Otherwise the codec type is implied by the RTP payload type.
10.2.2	DTMF
DTMF support is defined within 3GPP TS 23.231 [54] and the RTP Payload Type shall be supported as defined in 3GPP TS 26.102 [26].
10.2.3	Auxiliary Payloads
10.2.3.1	Void
10.2.3.2	Void
10.2.3.3	Clearmode Codec
On RTP terminations, Clearmode codec is transported according to IETF RFC 4040[55].
When the MGC determines that a 64 kbit/s unrestricted bearer service is requested, the clearmode codec shall be used. A dynamic payload type with CLEARMODE as encoding name shall be included in both the local and remote descriptor.
The behaviour of the MGW shall then conform to IETF RFC 4040[55]. All voice and signal processing functions such as silence suppression, comfort noise insertion and gain adjustment shall be automatically turned off. The MGW shall inherit the same QoS objectives as the ISDN bearer service.
10.2.3.4	Silence suppression and Comfort Noise
Support of silence suppression and comfort noise is defined in 3GPP TS 26.102 [26].
10.2.3.5	CS Data Service
10.2.3.5.1	CS Data Service with no Redundancy
RTP transport for CS Data services on the A-Interface User Plane over IP (AoIP) is based on RFC 4040 (CLEARMODE) [55], when this payload type is used by itself it means no redundancy is offered, which results in a 64kbps net bit stream. 
A specific Payload Type value (120) is defined in TS 48.103 [65] in the range of dynamic Payload Types for CSData without redundancy.
The SDP-syntax on the Mc interface for CS Data without redundancy is:
m=audio  RTP/AVP 120
a=rtpmap:120 CLEARMODE/8000
10.2.3.5.2	CS Data Service with Redundancy
A second specific Payload Type value (121) is defined in TS 48.103 [65] in the range of dynamic Payload Types for RTP Payload for Redundant Audio Data over AoIP. Redundancy for the CS Data service on AoIP is realised according to IETF RFC 2198 [64]. The SDP-syntax (red, fmtp) defined in this RFC is used to inform the MGW about the negotiated redundancy level. The encapsulated payload structure for CS Data is based on IETF RFC 4040 [55]. On AoIP RTP terminations, IETF RFC 2198 [64] shall be used for redundant data of the CLEARMODE payload type being used for the CSD service. Only the redundancy level 2 and level 3 are supported on the AoIP RTP terminations.For details at start and stop of a redundant data stream as well as in handover cases see TS 48.103 [65].
The MGC determines by BSSMAP negotiation with the BSS, whether redundancy is used and if so which level to use for the CS Data service. A dynamic payload type with "red" as encoding name shall be included in both the local and remote descriptor with the fmtp attribute to signal the redundancy level. The same redundancy level shall be used in the Local Descriptor and the Remote Descriptor to use the same redundancy level in both directions between the MGW with the BSS.
NOTE:	Whether the RTP payload for Redundant Audio Data is supported by the MGW is known by the MSC due to configuration data.
The MGC shall include both the CLEARMODE payload type and the Redundant RTP Payload for Audio Data in the Mc interface towards the MGW when the Redundant RTP Payload for Audio Data encapsulating the CLEARMODE payload shall be used. The MGW shall then apply the procedures for support of RTP redundancy as described in 3GPP TS 48.103 [65].
The SDP-syntax on the Mc interface for CS Data with redundancy level 2 is:
m=audio  RTP/AVP 121 120
a=rtpmap:120 CLEARMODE/8000
a=rtpmap:121 red/8000
a=fmtp:121 120/120
The SDP-syntax on the Mc interface for CS Data with redundancy level 3 is:
m=audio  RTP/AVP 121 120
a=rtpmap:120 CLEARMODE/8000
a=rtpmap:121 red/8000
a=fmtp:121 120/120/120
10.2.4	Other Payload Types
On RTP terminations, other payload types such as additional ITU-T codecs can be transported according to the RTP payload formats in IETF but their support is outside the scope of 3GPP specifications.
11	Mandatory Support of SDP and H.248.1 annex C information elements
This section shall be in accordance with the subclause "Mandatory Support of SDP and H.248.1 annex C information elements" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following requirements: 
Mc Single Codec encoding:
The ACodec property in H.248 binary encoding and codecconfig attribute in H.248 text encoding are set as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The codecconfig and ACodec parameters contain the contents of the Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information.
The ‘vsel’ attribute is omitted in H.248 text encoding.
Example of encoding of an AMR codec:
Acodec = 0206959504 (binary encoding)
codecconfig = 0206959504  (text encoding)
	where the AMR parameters are: ETSI, UMTS_AMR_2, [ACS={4.75, 5.90, 7.4, 12.2}, SCS={4.75, 5.90, 7.4, 12.2}, OM=0, MACS=4] 
Example of encoding of a G.711 codec:
Acodec = 0101  (binary encoding)
codecconfig = 0101  (text encoding) 
	where the G.711 parameters are: ITU-T, G.711 64kps A-law
NOTE:	The "Mc Single Codec IE" differs from the ITU-T defined "Single Codec IE", while on the Nc interface (i.e. in OoBTC) the ITU-T Single Codec IE is used without deviation.
	The Acodec property or codecconfig attribute set to the MuMe Dummy codec denotes a multimedia call. The Acodec property and codecconfig attribute shall never be set to the MuMe2 Dummy codec. See 3GPP TS 26.103 [16] and 3GPP TS 23.172 [37].
For further definition see Annex C.15.
12	General on Packages and Transactions
The use of "Overspecified" (e.g. range of values) and "Underspecified" (e.g. "?") parameter specification shall not be permitted except where explicitly indicated in or referenced by the Mc interface specification.
The use of wildcarding for the Termination Id shall be performed using 1 octet only.
Notifications shall not be sent by the MGW in response to Release Termination procedure.
Parameter modification and event notification shall not be permitted on non-ROOT Terminations in the NULL Context.
Commands on ROOT Termination shall only use the NULL Context. 
If a command cannot be executed by the MSC Server due to a temporary congestion/ongoing task the error code 511 ("Temporarily Busy") may be returned; the MGW may then re-issue the command as the condition may have abated. 
NOTE:	At the time of inclusion this error code did not exist in the H.248.8  further details of this error code see ITU-T Sub-series Implementors' Guide.(13 April 2006).
If a circumstance arises at an MGW where a substantial number of notifications accumulate, either because of transmission difficulties or because the MGW recognised a number of events in a short time period, the MGW should send the notifications in a restricted manner (e.g. via configuration) until the backlog is cleared.
For further definition see Annex C.
13	BICC packages
13.1	Mandatory BICC packages
Mandatory BICC packages are listed in Annex C.14.
13.2	Optional BICC packages
Optional BICC packages are listed in Annex C.14.
14	H.248 standard packages
Mandatory and Optional H.248 packages are listed in Annex C.14.
14.1	Call independent H.248 transactions
Table 2 shows the relationship between each non call-related procedure in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) and the corresponding stage 2 procedure defined in 3GPP TS 23.205 [2].
For further description of error codes and service change reasons, refer to ITU-T Recommendation H.248.8 [14].
Table 14.1.1: Correspondence between ITU-T Recommendation Q.1950 [23]
non call-related transactions and 3GPP TS 23.205 [2] procedures 
Transaction used in ITU-T Recommendation Q.1950 [23]
Procedure defined in 3GPP TS 23.205 [2]
Support
Comments
BIWF_Service_Cancellation_Indication
MGW Out of Service
Mandatory

BIWF_Lost_Communication
MGW Communication Up
Mandatory

BIWF_Service_Restoration_Indication
MGW Restoration
Mandatory

BIWF_Registration
MGW Register
Mandatory

BIWF_Re-Registration
MGW Re-register
Mandatory

CCU Ordered BIWF Re-Registration
(G)MSC Server Ordered Re-register
Mandatory

CCU Initiated Service Restoration
(G)MSC Server Restoration
Optional

CCU Initiated Service Cancellation
(G)MSC Server Out of Service
Optional

BIWF_Service_Cancellation_Indication
Termination Out-of-Service
Mandatory
Is a part of BIWF Service cancellation in Q.1950 
BIWF_Service_Restoration_Indication
Termination Restoration
Mandatory
Is a part of BIWF Service cancellation in Q.1950 
Audit_Values
Audit Value
Mandatory
Shall be supported for the audit of Termination State and for periodic audit of MGW (empty Audit descriptor). 
May be supported for the audit of packages.

Audit_Capabilities
Audit Capability
Optional
The capabilities to be audited shall be defined in clause 12.
BIWF_Capability_Change
Capability Update
Optional
This corresponds to MGW Capability Change in this document.

MGW Resource Congestion Handling - Activate
Mandatory


MGW Resource Congestion Handling - Indication
Mandatory

Continuity Check Tone

Optional

Continuity Check Verify

Optional

Continuity Check Response

Optional

Not Defined
Inactivity Timeout - Activate
Optional

Not Defined
Inactivity Timeout - Indication
Optional

Not Defined
Realm Availability Change - Activation
Optional

Not Defined
Realm Availability Change - Indication
Optional


14.1.1	MGW Out of service/Maintenance Locking
This procedure is the same as described in the subclause "BIWF Service Cancellation Indication" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]), with the following clarification.
Table 14.1.1.1: MGW Out of service/Maintenance Locking
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null 
Termination ID  = Root
Service Change Reason = MGW impending failure
Termination Taken out of service
Service Change Method = Graceful / Forced


Delay is not used.
NOTE:	The termination that is taken out of service is a Media Gateway.
14.1.2	MGW Communication Up
This procedure is the same as described in the subclause "BIWF Lost Communication" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7])  with the following clarification.
Use of time stamps is optional.
Context Id value Null shall be used in this procedure.
The ServiceChangeMGCId parameter may be returned in the MGW Communication Up response if the MGC does not wish to sustain an association with the MGW. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs.
14.1.3	MGW Restoration
This procedure is the same as described in the subclause "BIWF Service Restoration Indication" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification.
Table 14.1.3: MGW Restoration
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null
Termination ID  = Root 


Delay is not used.
The ServiceChangeMGCId parameter may be returned in the MGW Restoration response if the MGC does not wish to sustain an association with the MGW. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs.
14.1.4	MGW Register
This procedure is the same as that described in the subclause "BIWF Registration" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification.
14.1.4: MGW Register
Address Information
Control information
Bearer information

     ServiceChangeProfile = 
     mcprofilename / version


Use of time stamps is optional.
Context Id value Null shall be used in this procedure.
Non Standard Data is shall not be supported.
Service Change Address shall not be used.
The ServiceChangeMGCId parameter may be returned in the MGW Register response. If present in theRegister response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs.
14.1.5	MGW Re-register 
This procedure is the same as that described in the subclause "BIWF Re-Registration" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification.
Table 14.1.5.1: MGW Re-register
Address Information
Control information
Bearer information

     ServiceChangeProfile = 
     mcprofilename / version


Use of time stamps is optional.
Context Id value Null shall be used in this procedure.
Non Standard Data is shall not be supported.
Service Change Address shall not be used.
The ServiceChangeMGCId parameter may be returned in the MGW Re-register response. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs.
14.1.6	(G)MSC Server Ordered Re-register
This procedure is the same as described in the subclause "CCU Ordered BIWF Re-registration" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications: 
Context Id value Null shall be used in this procedure. 
14.1.7	(G)MSC Server Restoration
This procedure is the same as described in the subclause "CCU Initiated Service Restoration" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification.
Table 14.1.7.1: (G)MSC Server Restoration
Address Information
Control information
Bearer information

Context ID = Null
Termination ID = 
Root
Service Change Reason = Cold Boot / Warm Boot
Service Change Method = Restart


Delay is not used.
14.1.8	Termination Out-of-Service
This procedure is the same as described in the subclause "BIWF Service Cancellation Indication" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications. This procedure may be used to inform the MSC Server of the Service State of Terminations after MGW Restart or Registration.
Table 14.1.8.1:ServiceChange.req (Termination Out-of-Service)	MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Contexts / Null / All
Termination ID = ALL/Termination(s)
Service Change Reason = Transmission failure / Termination malfunctioning / Loss of lower layer connectivity / Termination taken out of service
Service Change Method = Graceful / Forced

NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at  a T1/E1. 


Delay is not used.
The MGW shall delay initiating a TDM Termination Out-of-Service procedure till completion of any on-going Termination Restoration procedure for the same TDM termination, if any, unless the MGW considers the previous transaction request or  reply lost, due to e.g. failure of the control association.
The following table illustrates the allowed combinations that can be obtained with the ServiceChange Command:
Table 14.1.8.2: Combinations of ContextID and TerminationID in Termination Out-of- Service Procedure
ContextID
TerminationID
Description
Specific
Specific
Service Change of a specific Termination in a specific Context
Null
Wildcard
Service Change of all matching TDM T1/E1 level terminations in the Null Context
Null
Specific
Service Change of a specific termination in the Null Context
All
Wildcard
Service Change of all matching TDM T1/E1 level terminations in specific (non-Null) contexts in which the terminations currently exist.

14.1.9	Termination Restoration
This procedure is the same as described in the subclause "BIWF Service Restoration Indication" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. This procedure may be used to inform the MSC Server of the Service State of Terminations after MGW Restart or Registration and shall be used when individual trunks are commissioned.
Table 14.1.9.1: Termination Restoration
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Contexts / Null / All
Termination ID = ALL/Termination(s)
Service Change Reason = Service Restored
Service Change Method = Restart 

NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at  a T1/E1. 


Delay shall not be used.
The MGW shall delay initiating a TDM Termination Restoration procedure till completion of any on-going Termination Out-of-Service procedure for the same TDM termination, if any, unless the MGW considers the previous transaction request or  reply lost, due to e.g. failure of the control association.
The following table illustrates the allowed combinations that can be obtained with the ServiceChange Command:
Table 14.1.9.2: Combinations of ContextID and TerminationID in Termination Restoration Procedure
ContextID
TerminationID
Description
Specific
Specific
Service Change of a specific Termination in a specific Context
Null
Wildcard
Service Change of all matching TDM T1/E1 level terminations in the Null Context
Null
Specific
Service Change of a specific termination in the Null Context
All
Wildcard
Service Change of all matching TDM T1/E1 level terminations in specific (non-Null) contexts in which the terminations currently exist.

14.1.10	Audit Value
This procedure is the same as described in the subclause "Audit Values" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) , with the following clarifications. This procedure shall be used by the MSC Server to determine the service state of physical terminations when the MSC Server itself has restarted if it is subsequently unsure of the service state of terminations or when O&M procedures indicate new physical trunks have been commissioned to an in service MGW. It shall also be used for determining the Termination State after MGW Registration (Cold Boot) prior to deblocking devices in the network if the MSC Server has not been informed specifically by Termination Restoration or Termination Out Of Service Procedure.Table 14.1.10.1: AUD_VAL.req (Audit_Values) MGC to MGW

Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null/Context ID/ALL
Termination ID = 
  Termination/Root/ALL(see NOTE1)
Audit Descriptor =
 Empty/ 
IndAuditParameter:=
     IndAudMediaDescriptor:=
     TermStateDescriptor (NOTE3) 

 
 Packages (See NOTE2)


NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at  a T1/E1 level It shall not be used for ATM or IP termination.
               "Termination" may be used for individual TDM, IP or ATM terminations. 

NOTE2: Packages is for 
- Null/Root Combination

NOTE3: Pre Rel6 this is performed with Audit Token


Upon reception of the command in the MGW: 
The Service State returns the current Service State
When Packages are requested, the Package Names and Versions are returned
The following table illustrates the allowed combinations that can be obtained with the AuditValue Command:
Table 14.1.10.2: Combinations of AuditValue Command
ContextID
TerminationID
Information Obtained
Specific
Wildcard
Audit of matching Terminations in a Context
Specific
Specific
Audit of a single Termination in a Context
Null
Root
Audit of Media Gateway state and events
Null
Wildcard
Audit of all matching TDM T1/E1 level Terminations in the null Context
Null
Specific
Audit of a single Termination outside of any Context
All
Wildcard
Audit of all matching TDM T1/E1 level Terminations and the Context to which they are associated
All
Specific
(Non-null) ContextID in which the Termination currently exists

Table 14.1.10.3: AUD_VAL.resp MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null/Context ID
Termination ID = 
  Termination/Root/All(seeNOTE1)
Empty Audit Descriptor:
-

AuditToken = Media/IndAudMediaDescriptor=TermStateDescriptor:
Service State = Current Service State

AuditToken = Packages:
Packages Descriptor = 
  Package Names + Versions

NOTE1: ALL may be returned for a TDM group.


14.1.11	Audit Capability
This procedure is the same as described in the subclause "Audit Capabilities" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.1.12	MGW Capability Change
This procedure is the same as described in the subclause "BIWF Capability Change" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:.
For Capability changes concerning the whole MGW:
Service Change Reason Media/Event or Signal Capability Failure shall not be used instead the following information shall be used: 
ServiceChange.req (MGW Capability Change)	MGW to MGC
Table 14.1.12.1: MGW Capability Change
Address Information
Control information
Bearer information

Service Change Reason =
Packages Change/ Capability Change
Service Change Info = changed package/property/signal/event/ statistics 

Note: 	The changed package/property/signal/event/ statistics information is FFS


14.1.13	(G)MSC Server Out of Service
This procedure is the same as that described in the subclause "CCU Initiated Service Cancellation" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification.
Table 14.1.13.1: (G)MSC Server Out of Service
Address Information
Control information
Bearer information

Service Change Reason = Termination taken out of service


Delay shall not be used.
14.1.14	MGW Resource Congestion Handling - Activate
If the procedure "MGW Resource Congestion Handling - Activate" is required the following procedure is initiated.

The MGC sends a MOD.req command with the following information.
Table 14.1.14.1: MOD.req(MGW Resource Congestion Handling - Activate) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null 
Termination ID  = Root

NotificationRequested (Event ID = x, "MGW Resource Congestion Handling - Indication")


When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.1.14.2: MOD.resp (MGW Resource Congestion Handling - Activate) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null
TerminationID = Root


14.1.15	MGW Resource Congestion Handling - Indication
If the procedure "MGW Resource Congestion Handling - Indication" is required, the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.1.15.1: NOT.req (MGW Resource Congestion Handling - Indication) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null
Termination ID = Root 

Event_ID (Event ID = x, "MGW Resource Congestion Handling - Indication (Reduction)")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.1.15.2: NOT.resp (MGW Resource Congestion Handling - Indication) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null
Termination ID = Root


14.1.16	Continuity Check Tone
This procedure is the same as described in Annex B.7.1.1 of ITU-T Recommendation Q.1950 [23] with the following clarification:
The addition to "Prepare BNC Notify" defined in Annex B.7.1.1 of ITU-T Recommendation Q.1950 [23] shall be applied instead to "Reserve  Circuit", as defined in Clause 13.2.2.1
Note: 	This does not preclude the use of the continuity check tone for other maintenance procedures. If the termination is audited it shall report state in service.
14.1.17	Continuity Check Verify
This procedure is the same as described in Annex B.7.2.1 of ITU-T Recommendation Q.1950 [23].
14.1.18	Continuity Check Response
This procedure is the same as described in Annex B.7.1.2 of ITU-T Recommendation Q.1950 [23] with the following clarification:
The addition to "Prepare BNC Notify" defined in Annex B.7.1.2 of ITU-T Recommendation Q.1950 [23] shall be applied instead to "Reserve  Circuit", as defined in Clause 13.2.2.1
Note: 	This does not preclude the use of the continuity check response for other maintenance procedures. If the termination is audited is shall report state in service.
14.1.19	Inactivity Timeout - Activate
If the procedure "Inactivity Timeout - Activate" is required the following procedure is initiated.
The MGC sends a MOD.req command with the following information.
Table 14.1.19.1: MOD.req (Inactivity Timeout - Activate) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null 
Termination ID  = Root

NotificationRequested (Event ID = x, "Inactivity Timeout - Indication")


When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.1.19.2: MOD.resp (Inactivity Timeout - Activate) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = Null
TerminationID = Root


14.1.20	Inactivity Timeout – Indication
When the procedure "Inactivity Timeout indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information.
Table 14.1.20.1: NOT.req (Inactivity Timeout - Indication)	MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = NULL
Termination ID = Root 

    Event_ID (Event ID = x, 
             " Inactivity Timeout - Indication ")


When the processing of command is complete, the MGC initiates the following procedure.
Table 14.1.20.2: NOT.resp (Inactivity Timeout - Indication)	MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = NULL
Termination ID = Root


14.1. 21	Realm Availability Change – Activation
The MGC sends a MODIFY request command as in Table 14.1.221.1.
Table 14.1.21.1: Realm Availability Change – Activation
Address Information
Control information
Bearer information

Transaction ID = x
Context ID= -
Termination ID = ROOT

NotificationRequested (Event ID = x,
"Realm Availability Change")


The MGW responds as in Table 14.1.21.2.
Table 14.1.21.2: Realm Availability Change – Activation Ack
Address Information
Control information
Bearer information

Transaction ID = x
Context ID = -
Termination ID = ROOT


14.1. 22	Realm Availability Change – Indication
The MGW sends a NOTIFY request command as in Table 14.1.22.1.
Table 14.1.22.1: Realm Availability Change – Indication
Address Information
Control information
Bearer information

Transaction ID = x
Context ID= -
Termination ID = ROOT

Event_ID (Event ID = x, 
"Realm Availability Change (Changed Realms)")

NOTE:    The ObservedEvent Parameters returned within the Changed Realms are defined as mandatory since it shall contain at minimum 1 parameter but may contain both Newly Available Realms and Newly Unavailable Realms.


The MGC responds as in Table 14.1.22.2
Table 14.1.22.2: Realm Availability Change – Indication Ack
Address Information
Control information
Bearer information

Transaction ID = x
Context ID = -
Termination ID = ROOT 


14.2	Call related H.248 transactions
Table 14.2.1 shows the relationship between each call-related procedure in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) and the corresponding stage 2 procedure defined in 3GPP TS 23.205 [2] , as well as specifying the requirement for support of each procedure on the Mc interface.
Table 14.2.1: Correspondence between ITU-T Recommendation Q.1950 [23] call-related transactions
and 3GPP TS 23.205 [2] and 3GPP TS 23.153 [1] procedures 
Transaction used in Q.1950 
Procedure defined in 3GPP TS 23.205 [2] , 23.153 [1] or 23.231 [54]
Support
Comments
Change_Topology
Change Flow Direction
Mandatory

Join
Join Bearer Termination
Mandatory

Isolate
Isolate Bearer Termination
Mandatory

Establish_BNC_Notify+(tunnel)
Establish Bearer
Mandatory

Prepare_BNC_Notify+(tunnel)
Prepare Bearer
Mandatory

Cut_Through
Change Through Connection
Mandatory

Not defined in Q.1950 
Activate Interworking Function
Optional

Cut_BNC (include several procedures).
Release Bearer (Release Bearer and Release termination)
Mandatory

BNC Established
Bearer Established
Mandatory

BNC Release
Bearer Released
Mandatory

Insert_Tone
Send Tone
Mandatory

Insert_Annoucement
Play Announcement
Mandatory

Signal Completion 
Announcement Completed
Mandatory

Detect_Digit
Detect DTMF
Mandatory

Insert_Digit
Send DTMF
Mandatory

Digit Detected
Report DTMF
Mandatory

Confirm_Char
Confirm Char
Optional

Modify_Char
Modify Char
Optional

Reserve_Char
Reserve Char
Optional

BNC Modified
Bearer Modified
Optional

Echo Canceller
Activate Voice Processing Function
Mandatory

BNC Modification failed
Bearer Modified Failed
Optional

Tunnel (MGC-MGW)
Tunnel Information Down
Optional
Shall be supported for BICC associated Nb interface transport protocol on IP
Tunnel (MGW-MGC)
Tunnel Information Up
Optional
Shall be supported for BICC associated Nb interface transport protocol on IP
Insert _Tone
Stop Tone
Mandatory

Insert _Announcement
Stop Announcement
Mandatory

Detect_Digit
Stop DTMF Detection
Optional

Insert_Digit
Stop DTMF
Mandatory

Signal Completion
Tone Completed
Optional

Not defined
Reserve Circuit
Mandatory

Not defined
Command Rejected
Mandatory

Not defined
TFO Activation
Optional

Not defined
Codec Modify
Optional

Not defined
Optimal Codec and Distant List_Notify
Optional

Not defined
Distant Codec List
Optional

Not defined
TFO status Notify
Optional

Not defined
TFO status
Optional

Modify_Char
Modify Bearer Characteristics
Mandatory

Not defined
Rate Change
Optional

Not defined 
Bearer Modification Support
Optional

Not defined 
Protocol Negotiation Result
Optional

Reserve_Char
Reserve Bearer Characteristics
Optional

Confirm_Char 
Confirm Bearer Characteristics
Optional

ECS_Indication
Emergency Call Indication
Optional

Continuity Check Tone
Continuity Check Tone
Optional
See 14.1.16
Continuity Check Verify
Continuity Check Verify
Optional
See 14.1.17
Continuity Check Response
Continuity Check Response
Optional
See 14.1.18
Not Defined
Prepare IP Transport
Optional
Shall be supported if IP used on Iu interface
Not Defined
Modify IP Transport Address
Optional
Shall be supported if IP used on Iu interface
Not defined
Termination heartbeat
Mandatory
To allow detection of hanging contexts and terminations in the MGW that may result e.g. from a loss of communication between the MSC-S and the MGW
Not Defined
Reserve RTP Connection Point
Optional
Required for SIP-I associated Nb and A interface over IP
Not Defined
Configure RTP Connection Point
Optional
Required for SIP-I associated Nb and A interface over IP
Not defined
Reserve and Configure RTP Connection Point 
Optional
Required for SIP-I associated Nb and A interface over IP
Not defined
Media Inactivity Notification
Optional
See 14.2.55
NOTE 1:	A procedure defined in table 3 can be combined with another procedure in the same action. This means that they can share the same contextID and termination ID(s).

14.2.1	Change Flow Direction 
This procedure is the same as that defined in the subclause "Change Connection Topology" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following additions.
Table 14.2.1.1: Change Flow Direction request additions
Address Information
Control information
Bearer information


Context ID = c1,?
Connection Configuration = 
	(TerminationID= x1, ? 
	TerminationID=x2,? 
	[type = x]),…


This procedure shall not be used for Multiparty bridge contexts.
The Change Flow Direction response shall contain the Context ID. 
A command is only required if this procedure is combined with some other procedure which changes a termination functionality.
14.2.2	Isolate Bearer Termination
This procedure is the same as that defined in the subclause "Isolate" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.3	Join Bearer Termination
This procedure is the same as that defined in the subclause "Join" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.4	Establish Bearer
This procedure is the same as that defined in the subclause "Establish BNC_notify" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) except that the Command MOV shall not be used, BNC events are requested optionally and independently and with additions as shown below. If IPBCP Tunnel Option 1 is required then the Command Response shall always precede the IPBCP Notify Command.
Table 14.2.4.1: Establish Bearer additions
Address Information
Control information
Bearer information

UP mode = Mode 
UP version = version
Delivery of erroneous SDUs = value
Interface = interface
If support mode:
        Initdirection = initdir


If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If detection of hanging termination is requested: (NOTE 3)
NotificationRequested (Event ID = x,
"termination heartbeat")

If Listener context: number of desired listener context terminations = required listener context terminations

If multiple IP realms: IP realm Identifier = required IP realm identifier

If indication on BNC Established requested:
NotificationRequested (Event ID = x, "BNC Established")

If indication on BNC Modified requested:
NotificationRequested (Event ID = x, "BNC Modified")

If indication on BNC Mod Failed requested:
NotificationRequested (Event ID = x, "BNC Mod Failed")

If indication on BNC Release requested:
NotificationRequested (Event ID = x, "BNC Release")
If SCUDIF multimedia call :
   MuMe codec (NOTE 1)


If data call other than SCUDIF multimedia call and Access Termination or Anchor MGW Network Termination:
   PLMN bearer capability = PLMN capability (NOTE2)
If GSM data call other than SCUDIF multimedia call and (Anchor MGW Network Termination):
   GSM channel coding = coding

NOTE1: 	Bearer Service Characteristics shall be excluded when this property is included.
NOTE2: 	Bearer Service Characteristics may be included.
NOTE3: 	Termination heartbeat notification shall be included when requesting a new bearer termination.

14.2.5	Prepare Bearer
This procedure is the same as that defined in the subclause "Prepare_BNC_notify" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) except that the Commands MOD and MOV shall not be used, the MGW shall not choose the BNC Characteristics, the BNC-cut-through-capability shall not be used, BNC events are requested optionally and independently and with additions as shown below.
Table 14.2.5.1: Prepare Bearer additions
Address Information
Control information
Bearer information

UP mode = mode 
UP version = version
Delivery of erroneous SDUs = value
Interface = interface
If support mode:
        Initdirection = initdir

If CTM call and Access Termination:
State= ctmstate 
Transport= ctmtransport
Version= ctmtext version
If data call and Non-Anchor MGW RAN-side termination:
   Bitrate = bitrate (NOTE1)

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If indication on Bearer Modification requested:
NotificationRequested (Event ID = x, "Bearer Modification Support")
If notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")

NotificationRequested (Event ID = x,
"termination heartbeat") 

If VGCS/VBS context: number of needed conference terminations = required conference terminations

If multiple IP realms:
IP realm Identifier = required IP realm identifier.

If indication on BNC Established requested:
NotificationRequested (Event ID = x, "BNC Established")

If indication on BNC Modified requested:
NotificationRequested (Event ID = x, "BNC Modified")

If indication on BNC Mod Failed requested:
NotificationRequested (Event ID = x, "BNC Mod Failed")

If indication on BNC Release requested:
NotificationRequested (Event ID = x, "BNC Release")
If SCUDIF multimedia call and (network termination or Anchor MGW Access Termination):
   MuMe codec (NOTE2)

If data call other than SCUDIF multimedia call and (Anchor MGW Access Termination or Anchor MGW Network Termination):
   PLMN bearer capability = PLMN capability (NOTE3)

If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
   GSM channel coding = coding

NOTE1 : 	Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.
NOTE2: 	Bearer Service Characteristics shall be excluded when this property is included.
NOTE3: 	Bearer Service Characteristics shall be excluded when this property is included, except for Anchor MGW network termination for which it may be included.

14.2.6	Change Through Connection
This procedure is the same as that defined in the subclause "Cut Through" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification and deletion.
NotificationRequested = (Event ID = x,"Cut Through") is deleted and therefore only the Explicit (MGC Controlled Cut-Through procedure is supported.
The MGW may support No_Data RTP frames on RTP-A and RTP-CN terminations during the call establishment phase, i.e. when not in TrFO (see 3GPP TS 26.102 [26]), in which case it shall support it independently of the Stream Mode.
14.2.7	Activate Interworking Function
When the procedure "Activate Interworking Function" is required the following procedure is initiated:
The MGC sends a MOD.req command with the following information.
Table 14.2.7.1: MOD.req (Activate Interworking function) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1

Signal=actpro 

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")


When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.7.2: MOD.resp (Activate Interworking function) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID = bearer1


14.2.8	Release procedures
This subclause includes a number of procedures.
14.2.8.1	Release Bearer
This procedure is the same as that defined in the subclause "Release" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) including the Modify command in the transaction with the clarification that the Termination ID and/or Context ID may be wildcarded (ALL).
14.2.8.2	Release Termination
This procedure is the same as that defined in the subclause "Release"in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) including a Subtract command in the transaction with the following additions.
Table 14.2.8.1 Sub.req (Release termination)	 MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1/ALL
Termination ID = bearer1/ALL


Table 14.2.8.2.2: Sub.resp (Release termination) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1/ALL
Termination ID = bearer1/ALL
If requested 
Statistics= Ctmbits


14.2.9	Bearer Released
This procedure is the same as that defined in the subclause "BNC Release" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:
Termination ID shall be provided in the response. .
The MGW may, as a configurable option, inhibit the reporting of normal AAL2 bearer release on a Iu termination.
14.2.10	Bearer Established
This procedure is the same as that defined in the subclause "BNC Established" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:
Termination ID shall be provided in the response.
14.2.11	Send Tone
This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Tone" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following additions.
Table 14.2.11.1: Send Tone additions
Address Information
Control information
Bearer information

If CAMEL Prepaid Warning Tone
Signal = warning tone 
Or
Signal =  flextone

If detection of hanging termination is requested: 
NotificationRequested (Event ID = x,
"termination heartbeat")


Signal Direction shall be either "internal" or "external".
Only the Tone Signal Ids shall be used, not the Tone Ids within the PlayTone Signal Id. 
The termination heartbeat event shall be configured when requesting a new ephemeral bearer termination.
14.2.12	Play Announcement
This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Announcement" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications: 
Table 14.2.12.1: Play Announcement additions
Address Information
Control information
Bearer information

If detection of hanging termination is requested: 
NotificationRequested (Event ID = x,
"termination heartbeat")


Signal Direction shall be either "internal" or "external". 
Stream mode may be maintained as for the ongoing call or may be restricted to "send only". 
Signal Lists shall be supported. 
The termination heartbeat event shall be configured when requesting a new ephemeral bearer termination.
14.2.13	Send DTMF
This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Digit" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The MGW shall ensure the minimum duration timing and minimum interval timing is achieved in accordance with the DTMF timing defined in TS 23.014 [27]. Maximum duration shall also be controlled by the MGW if required by the network.
14.2.14	Detect DTMF
This procedure is the same as that defined in the subclause "Media Content Detection" - "Detect Digit" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the exception that "long tone detected" (Event Id ltd) shall not be used. In addition "start tone detected" (EventId std) is optional and if not supported shall result in the command error code #449 "Unsupported or Unknown Parameter or Property Value". If both a request for "start tone detected" and "end tone detected" is received by the MGW that does not support "start tone detected" then it shall only report a notification upon detecting the end of a digit.
Parameter Duration shall not be used.
All digits shall be requested i.e. Tone_Id shall be wildcarded.
14.2.15	Report DTMF
This procedure is the same as that defined in the subclause "Detected Digit" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:
Termination ID shall be provided in the response.
14.2.16	Announcement Completed
This procedure is the same as that defined in the subclause "Signal Completion" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:
Termination ID shall be provided in the response. 
The Signal List ID should be provided additionally if the completed Announcement belongs to a Signal List.
14.2.17	Activate Voice Processing Function
When the procedure "Activate Voice Processing Function" (VPF) is required the following procedure is initiated:
The MGC sends an ADD.req, MOD.req or MOV.req command with the following information.
Table 14.2.17.1: ADD.req/MOD.req/MOV.req (Activate Voice Processing Function) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1

ActivateVPF "ec"= on/off


When the MGW receives the command, it shall associate the relevant voice processing function resources with the specified termination.
When the processing of command (1) is complete, the MGW may initiate the "Voice Processing Function Ack" procedure.
14.2.17.2: ADD.resp/MOD.resp/MOV.resp (Voice Processing Function Ack) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.18	Reserve Circuit
This procedure is activated when the "Reserve Circuit" procedure is initiated.
An ADD.req command is sent with the following information.
Table14.2.18.1: ADD.req (Reserve_Circuit) CSM to BIWF
Address Information
Control information
Bearer information

Transaction ID = z
Termination ID = bearer1

Context Requested:
Context ID = ?
Context Provided:
Context ID = c1

If CTM call and Access Termination:
State= ctmstate 
Transport= ctmtransport
Version= ctmtext version

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")
If detection of hanging termination is requested:
NotificationRequested (Event ID = x,"termination heartbeat")

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950 [23] 

If Listener context: number of desired listener context terminations = required listener context terminations

Bearer Service Characteristics

If data call, Access Termination:
PLMN capabilities 
If GSM data call, Access Termination:
GSM channel coding = coding


Upon completion of processing command (1) an ADD.resp command (2) is sent.
Table14.2.18.2: ADD.resp BIWF to CSM
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID = bearer1


14.2.19	Tunnel Information Up
This procedure is the same as that defined in the subclause "Tunnel" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the clarification that BT/TunOpt = ? and BT/TunOpt = NO shall not be used.
NOTE:	This procedure is always initiated from the MGW.
14.2.20	Tunnel Information Down
This procedure is the same as that defined in the subclause "Tunnel" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the clarification that BT/TunOpt = ? and BT/TunOpt = NO shall not be used.
NOTE:	This procedure is always initiated from the MGC.
14.2.21	Tone Completed
This procedure is the same as that defined in the subclause "Signal.Completion" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:
Termination ID shall be provided in the response.
14.2.22	Stop Announcement
This procedure is the same as that defined in the subclause "Insert Announcement" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The signal descriptor shall not include any signal.
14.2.23	Stop Tone
This procedure is the same as that defined in the subclause "Insert Tone" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The signal descriptor shall not include any signal.
14.2.24	Stop DTMF Detection
This procedure is the same as that defined in the subclause "Detect Digit" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The eventDescriptor shall not include any event.
14.2.25	Stop DTMF 
This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Digit" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The signal descriptor shall not include any signal. The MGW shall ensure the minimum duration timing and minimum interval timing is achieved in accordance with the DTMF timing defined in TS 23.014 [27]. Maximum duration shall also be controlled by the MGW if required by the network.
14.2.26	Confirm Char
This procedure is the same as that defined in the subclause "Confirm Char" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.27	Modify Char
This procedure is the same as that defined in the subclause "Modify Char" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.28	Reserve Char
This procedure is the same as that defined in the subclause "Reserve Char" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.29	Bearer Modified 
This procedure is the same as that defined in the subclause "BNC Modified" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.30	Bearer Modification Failed
This procedure is the same as that defined in the subclause "BNC Modification failure" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]).
14.2.31	TFO Activation
When the procedure "TFO activation" is required the following procedure is initiated:
The MGC sends a ADD.req, MOD.req or MOV.req command with the following information.
Table 14.2.31.1: ADD.req/MOD.req/MOV.req (TFO activation) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1
tfoenable = tfoactvalue
If TFO codec list:
Property= TFOcodeclist


When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.31.2: ADD.resp/MOD.resp/MOV.resp (TFO activation) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID=bearer1


14.2.32	Optimal Codec and Distant List_Notify
When the procedure "Optimal Codec and Distant List" is required the following procedure is initiated:
The MGC sends a ADD.req, MOD.req or MOV req. command with the following information.
Table 14.2.32.1: ADD.req/MOD.req/MOV.req (Codec modify and distant list) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1
Property= TFOcodeclist

NotificationRequested (Event ID = x, "Codec modify")
NotificationRequested (Event ID = x, "Distant List")


When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.32.2: ADD.resp/MOD.resp/MOV.resp (Optimal codec and codec list) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID= bearer1


14.2.33	Codec Modify
When the procedure "Codec Modify" is required the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.2.33.1: NOT.req (Codec modify) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1 

Event ( Event Id = x, "codec_modify (optimalcodec)")



When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.33.2: NOT.resp (Codec modify) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.34	Distant Codec List
When the procedure "Distant Codec List" is required the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.2.34.1: NOT.req (Distant codec list) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event(Event ID = x, " distant_codec_list(distlist) ")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.34.2: NOT.resp (Distant codec list) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.35	Command Rejected 
When the procedure "Command Reject" is required the following procedure is initiated:
The MGW/MGC sends .resp to any command.req with the following information.
Table 14.2.34.1: NYcommand.resp (command reject ) GW/MGC to MGC/MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1 or no context

Reason=Error


14.2.36	Modify Bearer Characteristics
This procedure is the same as that defined in the subclause "Modify Char" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below.
Table 14.2.36.1: Modify bearer Characteristics additions
Address Information
Control information
Bearer information

If framing protocol used:

UP mode = mode 
UPversion =version
Delivery of erroneous  SDUs=value
Interface=interface

If support mode:
        Initdirection=initdir

If data call and Non-Anchor MGW RAN-side termination:
   Bitrate = bitrate (NOTE1)
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If SCUDIF multimedia call and (network termination or Anchor MGW Access Termination):
   MuMe codec (NOTE 2)

If data call other than SCUDIF multimedia call and (Anchor MGW Access Termination or Anchor MGW Network Termination):

PLMN bearer capbility = PLMN capability (NOTE3)

If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding=coding

NOTE1 : 	Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.
NOTE2: 	Bearer Service Characteristics shall be excluded when this property is included.
NOTE3: 	Bearer Service Characteristics shall be excluded when this property is included, except for Anchor MGW network termination for which it may be included.

If the "Modify Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Modify Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation.
14.2.37	Protocol Negotiation Result
When the procedure "Protocol Negotiation Result" is required the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.2.37.1: NOT.req (Protocol negotiation result) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1 

Event (Event ID = x, " protres (Result,Cause)")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.37.2: NOT.resp (Protocol negotiation result) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.38	Rate Change
When the procedure  "Rate Change" is required the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.2.38.1: NOT.req (Rate change) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1 

Event (Event ID = x, "ratechg(rate)")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.38.2: NOT.resp (Rate change) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.39	Bearer Modification Support
When the procedure "Bearer Modification Support" is required, the following procedure is initiated:
The MGW sends a NOT.req command with the following information to indicate that the bearer can be modified.
Table 14.2.39.1: NOT.req (Bearer Modification Support) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event (Event ID = x, "mod_link_supp")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.39.2: NOT.resp (Bearer Modification Support) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.40	CTM report
When the procedure "CTM report" is required the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.2.40.1: NOT.req (CTM report) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1 

Event (Event ID = x, "connchange (connchng) ")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.40.2: NOT.resp (CTM report) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.41	Prepare IP transport
This procedure is activated when the "Prepare IP transport" procedure is initiated. 
An ADD.req command is sent with the following information.
Table 14.2.41.1: ADD.req (Prepare IP transport) MGC to MGW
Address Information
Control information
Bearer information

Local Descriptor {
Iu IP Address = ?  
Iu IP Port = ?

}

Transaction ID = z
Termination ID = ?
Logical Port ID = y
If Context Requested:
Context ID = ?
If Context Provided:
Context ID = c1

UP mode = mode 
UP version = version
Delivery of erroneous SDUs = value
Interface = interface

If support mode:
        Initdirection = initdir

If CTM call and Access Termination:
State= ctmstate 
Transport= ctmtransport
Version= ctmtext version
If data call and Non-Anchor MGW RAN-side termination:
   Bitrate = bitrate (NOTE1)


If indication of BNC Established requested:

Notification_Requested (Event ID = x, "BNC Connected")

If indication of BNC Release requested:
Notification_Requested (Event ID = x, "BNC Release (Cause)")

If indication of BNC Modified requested:
Notification_Requested (Event ID = x,"BNC Modifed")

If indication of BNC Mod Failed requested:
Notification_Requested (Event ID = x, "BNC Mod Failed")

(all bearer change notifications as defined in ITU‑T Recommendation Q.1950 [23])

If multiple IP realms:
IP realm Identifier = required IP realm identifier

NotificationRequested (Event ID = x,
"termination heartbeat")

If SCUDIF multimedia call and Anchor MGW Access Termination:
   MuMe codec (NOTE 2)

If data call other than SCUDIF multimedia call, Anchor MGW Access Termination:
   PLMN bearer capability = PLMN capability (NOTE2)

If data call and Non-Achor RAN termination: 
Bearer Service Characteristics
(NOTE 1)

If speech call, Access Termination: Codec

Bearer Characteristics = "IP"

NOTE1 :	Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s..
NOTE2:	Bearer Service Characteristics shall be excluded when this property is included.

When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.41.2: ADD.resp (Prepare IP transport) MGW to MGC
Address Information
Control information
Bearer information

Local Descriptor {
   Iu IP Address = IPaddress
   Iu IP Port = UDPport

}
Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.42	Modify IP transport address
This procedure is activated when the "Modify IP transport address" procedure is initiated. 
A MOD.req  command is sent with the following information.
Table 14.2.42.1: MOD.req (Modify IP transport address) MSC to MGW
Address Information
Control information
Bearer information

 Remote Descriptor {
   Iu IP Address = IPaddress
   Iu IP Port = UDPport

}
Transaction ID = z
Context ID = c1
Termination ID = bearer1



When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.42.2: MOD.resp (Modify Ip transport address) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID=bearer1


14.2.43	Reserve Bearer Characteristics
This procedure is the same as that defined in the subclause "Reserve Char" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below.
Table 14.2.43.1: Reserve Bearer Characteristics additions
Address Information
Control information
Bearer information

If framing protocol used:

UP mode = mode 
UPversion =version
Delivery of erroneous  SDUs=value
Interface=interface
Initdirerection=initdirection


If the "Reserve Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Reserve Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation.
14.2.44	Confirm Bearer Characteristics
This procedure is the same as that defined in the subclause "Confirm Char" in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below.
Table 14.2.44: Confirm Bearer Characteristics additions
Address Information
Control information
Bearer information

If framing protocol used:

UP mode = mode 
UPversion =version
Delivery of erroneous  SDUs=value
Interface=interface
Initdirerection=initdirection


If the "Confirm Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Confirm Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation.
14.2.45	Trace activation/deactivation 
This procedure is activated when the "Trace activation/deactivation" procedure is initiated.
An ADD.req command is sent with the following information.
Table 14.2.45.1: ADD.req/MOD.req (Trace activation/deactivation) MGC to MGW
 Address Information
 Control information
Bearer information 

Transaction ID = z
Termination ID = bearer1

Context ID = c1

Trace Reference
Trace Recording Session Reference
Trace Depth
Triggering events
List of interfaces

IMSI
IMEI(SV)


Trace activity control = trace activity request


If indication on Trace Activation Result requested: 
NotificationRequested (Event ID = x, "Trace activation result")


Upon completion of processing command (1) an ADD.resp or MOD.resp command (2) is sent.
Table 14.2.45.2: ADD.resp/MOD.resp/ MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID = bearer1



14.2.46	Trace Activation result notification
When the procedure "Trace Activation result notification" is required, the following procedure is initiated:
The MGW sends a NOT.req command with the following information to indicate the result of the trace activation.
Table 14.2.46.1: NOT.req (Trace Activation result Notification) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1

Event_ID (Event ID = x, " tracact (res)")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.46.2: NOT.resp (Trace Activation result Notification) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.47	Emergency Call Indication
This procedure is the same as that defined in the subclause " ECS_Indication " in ITU‑T Recommendation Q.1950 Annex F [23] (see 3GPP TS 29.205 [7]) with additions as shown below.
Table 14.2.47.1: Emergency Call Indication additions
Address Information
Control information
Bearer information
Or as per flow 14.2.4
Establish Bearer

Or as per flow 14.2.5
Prepare Bearer

Or as per flow 14.2.12
Play Announcement

Or as per flow 14.2.18
Reserve_Circuit

Or as per flow 14.2.41
Prepare_IP_transport

Or as per flow 14.2.2
Isolate Bearer Termination

Or as per flow 14.2.3
Join Bearer Termination

Or as per flow 14.2.51
Reserve RTP Connection Point


Or as per flow 14.2.53
Reserve and Configure RTP Connection Point

Or as per flow 14.2.4
Establish Bearer
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.5
Prepare Bearer
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.12
Play Announcement
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.18
Reserve_Circuit 
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.41
Prepare_IP_transport
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.2
Isolate Bearer Termination 
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.3
Join Bearer Termination 
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication

Or as per flow 14.2.51
Reserve RTP Connection Point With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication


Or as per flow 14.2.53
Reserve and Configure RTP Connection Point                    With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication
Or as per flow 14.2.4
Establish Bearer

Or as per flow 14.2.5
Prepare Bearer

Or as per flow 14.2.12
Play Announcement

Or as per flow 14.2.18
Reserve_Circuit 

Or as per flow 14.2.41
Prepare_IP_transport

Or as per flow 14.2.2
Isolate Bearer Termination

Or as per flow 14.2.3
Join Bearer Termination

Or as per flow 14.2.51
Reserve RTP Connection Point


Or as per flow 14.2.53
Reserve and Configure RTP Connection Point

14.2.48	TFO status Notify
When the procedure "TFO status notify" is required the following procedure is initiated:
The MGC sends a ADD.req, MOD.req or MOV req. command with the following information.
Table 14.2.48.1: ADD.req/MOD.req/MOV.req (TFO status) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1

NotificationRequested (Event ID = x, "TFO Status")


The support of the TFO status notification is optional in the TFO package.  If supported, when the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.48.2: ADD.resp/MOD.resp/MOV.resp (TFO status) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
TerminationID= bearer1


Otherwise it returns an error codec to the MGC indicating that the requested event is unsupported or unknown., as specified in ITU-T Recommendation H.248.8 [14].
14.2.49	TFO Status
When the procedure "TFO Status" is required the following procedure is initiated:
The MGW sends a NOT.req command with the following information.
Table 14.2.49.1: NOT.req (TFO Status) MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1 

Event_ID (Event ID = x, " TFO_status(tfostatus) ")


When the processing of command (1) is complete, the MGC initiates the following procedure.
Table 14.2.49.2: NOT.resp (TFO Status) MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


14.2.50	Termination heartbeat indication
When the procedure  "Termination heartbeat indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information.
Table 14.2.50.1: NOT.req (Termination heartbeat)	MGW to MGC
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1 

    Event_ID (Event ID = x, 
             "termination heartbeat")


When the processing of command  is complete, the MGC initiates the following procedure.
Table 14.2.50.2: NOT.resp (Termination heartbeat)	MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = z
Context ID = c1
Termination ID = bearer1


The heartbeat timer shall be configured to a value much greater than the mean call holding time.
The MSC-S is in charge of correcting any detected mismatch, by substracting hanging terminations or clearing hanging contexts. 
14.2.51		Reserve RTP Connection Point
This procedure is used to reserve an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 3GPP TS 48.103 [65]. When the procedure "Reserve RTP Connection Point" is required the following procedure is initiated.
The MGC sends an ADD.req command with the following information.
Table 14.2.51.1: ADD.req (Reserve RTP Connection Point Request) MGC to MGW
Address Information
Control information
Bearer information
Local Descriptor {
   Port = ?
   IP Address = ? 
  IP Version = IPv4 or IPv6

}
Transaction ID = z
Termination ID = ?



If Context Requested:
   Context ID = ?

If Context Provided:
   Context ID = c1

If IP Interface Type:
    IP interface = "IP interface type"

If CTM call and Access Termination:
     State= ctmstate 
     Transport= ctmtransport
     Version= ctmtext version

If Resources for multiple Codecs shall be reserved:
   Reserve_Value 

NotificationRequested (Event ID = x,
"termination heartbeat")

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950

If multiple IP realms: IP realm Identifier = required IP realm identifier

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If access termination and
notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")


If access termination and Listener context: number of desired listener context terminations = required listener context terminations
If diffserv required  (NOTE 1):- 
   Diffserv Code Point
   If tagging behaviour
    Diffserv Tagging Behaviour

If Remote Source Address Filtering required (NOTE 1):-
   Remote Source Address Filtering
    If Remote Source Address range required:-
       Remote Source Address Mask
    If Remote Source Port Filtering
    required:-
       Remote Source Port Filtering
        If individual port:-
           Remote Source Port 
        If range of ports: 
           Remote Source Port Range

If Media Inactivity Detection Required (NOTE 1):
   NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE 2)

If Sustainable Data Rate Policing Required (NOTE 1):-
      Policing Required
      Sustainable Data Rate
      Maximum Burst Size

If peak data rate policing (NOTE 1)
      Policing Required
      Peak Data Rate
      If Delay Variation required 
            Delay Variation Tolerance

If RTCP handling required (NOTE 1):
   RTCP allocation


Local Descriptor {
   Codec List
   RTP Payloads
   RtcpbwRS
   RtcpbwRR
}

If data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
   PLMN bearer capability = PLMN capability 

If GSM data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
   GSM channel coding = coding

NOTE 1: 	Only for terminations with border control functions support.
NOTE 2:	The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.

When the processing of command (1) is complete, the MGW initiates the following procedure.
Table14.2.51.2: ADD.resp (Reserve RTP Connection Point Acknowledge) MGW to MGC
Address Information
Control information
Bearer information
Local Descriptor {
   Port
   IP Address
   IP Version
}
Transaction ID
Termination ID
Context ID
Local Descriptor {
   Codec List
   RTP Payloads
   RtcpbwRS
   RtcpbwRR
}

14.2.52		Configure RTP Connection Point
This procedure is used to configure or reconfigure an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 48.103 [65]. 
When the procedure "Configure RTP Connection Point" is required the following procedure is initiated:
The MGC sends an MOD.req command with the following information.
Table 14.2.52.1: MOD.req (Configure RTP Connection Point Request) MGC to MGW
Address Information
Control information
Bearer information
If local resources are modified:
   Local Descriptor {
      Port
      IP Address
      IP Version
   }
If remote resources are modified:
   Remote Descriptor {
      Port
      IP Address
      IP Version
   }
Transaction ID
Termination ID
Context ID

If IP Interface Type:
    IP interface = "IP interface type"
(NOTE 1)

If Resources for multiple Codecs shall be reserved:
   Reserve_Value

If CTM call and Access Termination:
     State= ctmstate 
     Transport= ctmtransport
     Version= ctmtext version

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")

If access termination and Listener context: number of desired listener context terminations = required listener context terminations

If diffserv required  (NOTE 2):- 
   Diffserv Code Point
   If tagging behaviour
     Diffserv Tagging Behaviour

If Remote Source Address Filtering required (NOTE 2):
   Remote Source Address Filtering
    If Remote Source Address range required:-
       Remote Source Address Mask
    If Remote Source Port Filtering required:-
       Remote Source Port Filtering
        If individual port:-
           Remote Source Port 
        If range of ports: 
           Remote Source Port Range

If Media Inactivity Detection Required (NOTE 2):
   NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE 3)

If Sustainable Data Rate Policing Required (NOTE 2):-
      Policing Required
      Sustainable Data Rate
      Maximum Burst Size

If peak data rate policing (NOTE 2)
      Policing Required
      Peak Data Rate
      If Delay Variation required 
            Delay Variation Tolerance

If RTCP handling required (NOTE 2):
   RTCP allocation

If local resources are modified:
   Local Descriptor {
      Codec List
      RTP Payloads
      RtcpbwRS
      RtcpbwRR
   }
If remote resources are modified:
   Remote Descriptor {
      Codec List
      RTP Payloads
      RtcpbwRS
      RtcpbwRR
   }

If data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
   PLMN bearer capability = PLMN capability 

If GSM data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
   GSM channel coding = coding

NOTE 1: 	If this property is included within the Reserve Connection Point procedure or the Reserve and Configure RTP Connection Point then it shall not be modified by this procedure.
NOTE 2: 	Only for terminations with border control functions support.
NOTE 3:	The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.

When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.52.2: MOD.resp (Configure RTP Connection Point Acknowledge) MGW to MGC
Address Information
Control information
Bearer information
If local resources were provided in request:
   Local Descriptor {
      Port
      IP Address
      IP Version
   }
If remote resources were provided in request:
   Remote Descriptor {
      Port
      IP Address
      IP Version
   } NOTE
Transaction ID
Context ID
Termination ID

If local resources were provided in request:
   Local Descriptor {
      Codec List
      RTP Payloads
      RtcpbwRS
      RtcpbwRR
   }
If remote resources were provided in request:
   Remote Descriptor {
      Codec List
      RTP Payloads
      RtcpbwRS
      RtcpbwRR
   } NOTE
NOTE:     Sending of the Remote Descriptor is optional

14.2.53		Reserve and Configure RTP Connection Point 
This procedure is used to reserve and coonfigure an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 48.103 [65]. 
When the procedure "Reserve and Configure RTP Connection Point" is required the following procedure is initiated:
The MGC sends a ADD.req command with the following information.
Table 14.2.53.1: ADD.req (Reserve and Configure RTP Connection Point Request) MGC to MGW
Address Information
Control information
Bearer information
Local Descriptor {
   Port = ?
   IP Address = ?
IP Version = IPv4 or IPv6

}
Remote Descriptor {
   Port
   IP Address
IP Version = IPv4 or IPv6

}
Transaction ID
Termination ID = ?

If Context Requested:
   Context ID = ?

If Context Provided:
   Context ID = c1

If IP Interface Type:
    IP interface = "IP interface type"

If Resources for multiple Codecs shall be reserved:
   Reserve_Value 

If CTM call and Access Termination:
     State= ctmstate 
     Transport= ctmtransport
     Version= ctmtext version

NotificationRequested (Event ID = x,
“termination heartbeat”) 

If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950

If multiple IP realms: IP realm Identifier = required IP realm identifier

If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")

If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")

If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")

If diffserv required  (NOTE 1):- 
   Diffserv Code Point
   If tagging behaviour
    Diffserv Tagging Behaviour

If Remote Source Address Filtering required (NOTE 1):-
   Remote Source Address Filtering
    If Remote Source Address range required:-
       Remote Source Address Mask
    If Remote Source Port Filtering
    required:-
       Remote Source Port Filtering
        If individual port:-
           Remote Source Port 
        If range of ports: 
           Remote Source Port Range

If Media Inactivity Detection Required (NOTE 1):
   NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE2)

If Sustainable Data Rate Policing Required (NOTE 1):-
      Policing Required
      Sustainable Data Rate
      Maximum Burst Size

If peak data rate policing (NOTE 1)
      Policing Required
      Peak Data Rate
      If Delay Variation required 
            Delay Variation Tolerance

If RTCP handling required (NOTE 1):
   RTCP allocation

Local Descriptor {
   Codec List
   RTP Payloads
   RtcpbwRS
   RtcpbwRR
}
Remote Descriptor {
   Codec List
   RTP Payloads
   RtcpbwRS
   RtcpbwRR
}

If data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
   PLMN bearer capability = PLMN capability 

If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
   GSM channel coding = coding

NOTE 1: 	Only for terminations with border control functions support.
NOTE 2:	The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.

When the processing of command (1) is complete, the MGW initiates the following procedure.
Table 14.2.53.2: ADD.resp(Reserve and Configure RTP Connection Point Acknowledge) MGW to MGC 
Address Information
Control information
Bearer information
Local Descriptor {
   Port
   IP Address
   IP Version
}
Remote Descriptor {
   Port
   IP Address
   IP Version
} NOTE
Transaction ID
Termination ID
Context ID
Local Descriptor {
   Codec List
   RTP Payloads
   RtcpbwRS
   RtcpbwRR
}
Remote Descriptor {
   Codec List
   RTP Payloads
   RtcpbwRS
   RtcpbwRR
} NOTE
NOTE:     Sending of the Remote Descriptor is optional
Editor's note: The usage of the Call Type Discrimination IE and Text Telephony IE is ffs.
14.2.54		(void)
14.2.55		Media Inactivity Notification
When the procedure "Media Inactivity Notification" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information.
14.2.55.1	NOT.req (Media Inactivity) MGW to MGC 
Address Information
Control information
Bearer information

Transaction ID = x
Context ID = C1
Termination ID = T1

Event_ID (Event ID = x, "Media Inactivity Detection")


When the processing of command is complete, the MGC initiates the following procedure.
14.2.55.2	NOT.resp (Media Inactivity)	MGC to MGW
Address Information
Control information
Bearer information

Transaction ID = x
Context ID = C1
Termination ID = T1


15	UMTS packages
15.1	Mandatory UMTS packages
The following package shall be supported for the UMTS Bearer Independent Circuit-Switched Core Network:
-	3GUP (User Plane) package (see subclause 15.1.1).
15.1.1	3GUP package.
PackageID:	threegup (0x002f)
Version:	1
Extends:	None
This package identifies that the User Plane package is used for the termination. It also contains some parameters for the User Plane functions in the MGW.
The UP Protocol operates independently of the stream mode property, i.e. type 14 UP PDUs (which are used for inband UP signalling) can be transported between UP peers, irrespective of the stream mode direction. However, other types of UP PDUs shall be handled according to the stream mode property.
15.1.1.1	Properties
UP Mode of operation:
	PropertyID: mode (0x0001).
	Description: Defines the mode of operation of the User Plane functions , for further definitions see 3GPP TS 25.415 [4] and 29.415 [8].
	Type: Enumeration.
	Possible Values:
-	"Trans" (0x0001) Transparent mode.
-	"Supp" (0x0002) Support mode for predefined SDU sizes.
	Default: "Trans" (0x0001) Transparent mode.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
UP versions:
	PropertyID: upversions (0x0002).
	Description: Defines the required versions of the UP mode of operation.
	Type: Sub-list of enumeration.
	Possible Values:
-	"1" (0x01)	Version 1.
-	"2" (0x02)	Version 2.
-	"3" (0x03)	Version 3.
-	"4" (0x04)	Version 4.
-	"5" (0x05)	Version 5.
-	"6" (0x06)	Version 6.
-	"7" (0x07)	Version 7.
-	"8" (0x08)	Version 8.
-	"9" (0x09)	Version 9.
-	"10" (0x0A)	Version 10.
-	"11" (0x0B)	Version 11.
-	"12" (0x0C)	Version 12.
-	"13" (0x0D)	Version 13.
-	"14" (0x0E)	Version 14.
-	"15" (0x0F)	Version 15.
-	"16" (0x10)	Version 16.
-	Default: "1" (0x01)	Version 1.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
Delivery of erroneous SDUs:
	PropertyID: delerrsdu (0x0003).
	Description: Indicates how erroneous SDUs should be handled. If it is set to YES then the UP entity implements error checking and sets Frame Quality Classification (FQC) bits accordingly; bad frames are delivered to the UP layer. If it is set to NO then the UP entity performs error checking and if a bad frame is detected then it is discarded. These settings are required only when the payload is to be examined by upper layer services; an MGW may ignore the settings of this parameter if it passes frames transparently through the UP entities. If it is set to NA then no checking is performed.
	Type: Enumeration.
	Possible Values:
-	"Yes" (0x0001) Yes.
-	"No" (0x0002) No.
-	"NA" (0x0003) Not Applicable.
	Default: "NA" (0x0003) Not Applicable.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
Interface:
	PropertyID: interface (0x0004).
	Description: Indicates the type of interface on which the termination is used.
	Type: Enumeration.
	Possible Values:
-	"RAN" (0x0001) Iu interface.
-	"CN" (0x0002) Nb interface.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
Initialisation Direction:
	PropertyID: initdir (0x0005).
	Description: Indicates whether or not the termination in the MGW should expect initialisation information, or initiate UP initialisation itself.
	For a termination with property "interface = CN":
-	If Initialisation Direction is set to Incoming then the MGW shall expect to receive an initialisation either at this termination or from an other Nb or Iu termination in the same context.
-	If Initialisation Direction is set to outgoing, then the MGW shall send out an initialisation procedure from this termination. If another termination in the same context is initialised with the same codec type and configuration the MGW should re-use the RFCI values for its Initialisation PDU, otherwise it must assign its own values.
	For a termination with property "interface = RAN":
-	If Initialisation Direction is set to "incoming", then the initialisation received at this termination is from the originating RAN and can be forwarded internally to other terminations for subsequent UP initialisations.
If Initialisation Direction is set to "outgoing", then initialisations received are from the terminating RAN and cannot be forwarded internally. RFCI value correction can be performed at this termination, and initialisations can be sent out to the RAN.
	Examples for the usage of this property are given in annex B.
	Type: Enumeration.
	Possible Values:
-	"In" (0x0001) Incoming.
-	"Out" (0x0002) Outgoing.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
15.1.1.2	Events
None.
15.1.1.3	Signals
None.
15.1.1.4	Statistics
None.
15.1.1.5	Procedures
The MGC uses this package to indicate to the MGW that the Iu (or Nb) User Plane is used between the RNC (or distant MGW) and the MGW. The package is sent in the Establish bearer, Modify Bearer Characteristics and Prepare bearer procedures. For more information on the User Plane and for a description of ' UP mode of operation', 'UP versions' and 'Delivery of erroneous SDUs' see 3GPP TS 25.415 [4].
The following procedures are valid for UP in Support Mode:
-	The MGW shall be able to initiate and respond to the UP control procedures (PDU type 14 frames) independently of the Stream Mode during the call establishment phase, i.e. when not in TrFO.
-	Otherwise, during TrFO the MGW shall be able to forward UP control procedures (PDU type 14 frames) received at one termination to the other termination.
-	The UP Initialisation procedure is always acknowledged between MGW peers. If an MGW receives a request for a notification for the bearer establishment then the MGW shall not send the notification until after it has either sent or received the acknowledgement for the UP initialisation.
-	The MGW shall always store RFCI parameters against the MGW termination that received or that sent the UP initialisation.
-	If an MGW has the UP termination property Initialisation Direction = Incoming then it expects to either receive an Initialisation (externally) or after receiving initialisation information internally send an initialisation (externally), based on what occurs first.
-	If an MGW has UP termination property Initialisation Direction = Outgoing and interface CN, then it generates a network originated Initialisation PDU as soon as the bearer towards the succeeding node is successfully established, with RFCIs corresponding to the last codec configured on the termination. If another termination in the same context is initialised with the same codec type and configuration the MGW should re-use the RFCI values for its Initialisation PDU, otherwise it must assign its own values. The initialisation information sent by the MGW depends on the service that the bearer supports. For CSD service see 3GPP TS 29.007 [6] chapter 11.5. For speech service see 3GPP TS 26.102 [26] chapter 8.
-	If an MGW has UP termination property Initialisation Direction = Outgoing and interface RAN, then it expects to receive an Initialisation externally. It shall not pass the initialisation parameters internally. It may initiate RFCI Value Correction out from this termination. 
-	A CN incoming or outgoing termination having already completed its UP initialisation towards a peer MGW shall not send externally any new UP initialisation except if a reserve / modify characteristic procedure occured on that termination since the last initialisation. 
-	RAN Outgoing termination may perform, during its lifetime, subsequent RFCI Value corrections, e.g. due to changes of RFCIs on other terminations. 
-	If an MGW has two terminations in the same context defined as supporting the UP package and with Initialisation Direction incoming, then when it receives an Initialisation procedure from one side (provided the bearer connection from the other termination to its peer MGW is established) it shall start the UP initialisation procedure towards the peer MGW. The MGW shall perform this procedure independently of the through-connection of the terminations in the context. The MGW shall relay control information from the first initialisation to the UP peer for use at the subsequent initialisation. Also, subsequent control procedures received on one UP shall be relayed to the other UP entity when the two UP entities are connected within the MGW. This behaviour is described in more detail in Annex A. -	When adding a new CN incoming termination to a context that has already a RAN or CN incoming termination, if the existing termination has already completed its UP initialisation, the MGW shall not start an initialisation procedure on the new termination based on the control information already stored at the initialised incoming termination in the context. 
-	If an MGW has one termination with properties "interface = RAN" and "initialisation direction = outgoing" and another termination with property "initialisation direction = Incoming" in the same context, then the MGW shall not forward the UP initialisation from the Incoming termination until it has received a UP initialisation at the "RAN"/"outgoing" side. If the codec type and codec modes configured on both terminations are identical, and if the RFCI values stored at the "incoming"  termination do not match the RFCI values stored at the "outgoing" RAN side then "RFCI Value Correction" may be performed to the "outgoing" RAN side: The MGW starts UP initialisation with the RFCI values 'relayed' from the "Incoming" side. No "RFCI Value Correction" is permitted at an outgoing RAN termination whose Iu initialisation negotiates the version 1 of the support mode, at an "incoming" Iu termination or at any Nb termination. 
-	If a new RAN outgoing termination is added to a context that has already a RAN incoming or CN incoming termination, and if the existing termination has already completed its UP initialisation, the MGW may carry out a RFCI value correction on the new RAN outgoing termination., The control information to be used for the RFCI value correction shall be relayed from the initialised incoming termination in the context.  
-	No RFCI value correction shall be triggered for data call.
-	As an implementation option, "RFCI Value Correction" may be delayed if terminations are not through-connected; it will be triggered by connection modification. Otherwise it shall be performed immediately
-	If "RFCI Value Correction" is not performed the MGW  shall map the indexes for  frames from one side to the RFCI indexes for frames from the other side. This behaviour is described in more detail in Annex A.
-	If an MGW has two RAN terminations connected to the same context then the "RFCI Value Correction" is performed by the Outgoing termination.
-	If an MGW has two terminations which support the UP package connected to the same context and both RFCI sets match then the MGW may pass frames transparently through the UP entities; no monitoring of the frames is performed, provided that the terminations are through-connected. This behaviour is described further in Annex A.
-	If the MGW is passing frames transparently, no UP monitoring is performed. When the MGW receives an H.248 procedure request which requires interpretation or interaction with the UP, then it shall resume its UP protocol responsibilities, i.e. perform monitoring or termination of the UP protocol.
-	If an MGW sends an FP UP initialization message from a termination, the MGW shall only offer versions of the FP UP, which are given in the property "UP versions" of this termination and which are supported by the MGW for this termination.
-	If an MGW receives an FP UP initialization message at a termination, the MGW shall only positively acknowledge this initialization message, if versions of the FP UP are offered, which are given in the property "UP versions" and which are supported at the MGW for this termination. In the positive FP UP initialization acknowledge message, the MGW shall select one of these versions. If none of these versions are offered in the FP UP initialization message, the MGW shall send a negative FP UP acknowledge message and it shall not forward the initialization to a possible second FP UP termination in the same context.
-	If PCM is used on the Nb then FP UP initialization shall be performed by the termination with property "Outgoing". If the termination property is "Incoming" then it shall receive the RFCI's from its IuFP peer (or from internal MGW termination with IuFP and same codec). If IuFP is defined on another termination in the MGW but the codec is different, i.e. not TrFO then the relaying of RFCI's shall not be performed. These IuFP peer connection shall be seen as completely separate.
- 	the UP initialisation information attached to a termination (RFCI values, codec type and mode(s), UP initialisation completed or not) are kept unchanged when the termination is moved to a new context.
-	the initialisation direction may be changed during the lifetime of a termination ; upon such a change, the MGW shall apply the behaviour attached to the new initialisation direction.
The procedures for a termination configured in UP Transparent Mode are those described in 3GPP TS 25.415 [4].
15.2	Optional UMTS packages
The following packages may be supported by the UMTS Bearer Independent Circuit-Switched Core Network as required by the network services deployed in the network:
Circuit Switched Data package (see subclause 15.2.1);
TFO package (see subclause 15.2.2);
3G Expanded Call Progress Tones Generator package (see subclause 15.2.3);
Modification of Link Characteristics Bearer Capabiltity package (see subclause 15.2.4);
Enhanced Circuit Switched Data package (see subclause 15.2.5);
Cellular Text telephone Modem Text Transport package (see subclause 15.2.6);
IP transport package (see subclause 15.2.7);
Flexible Tone Generator Package (see subclause 15.2.8);
Trace Package (see subclause 15.2.9);
ASCI Group Call package (see subclause 15.2.10);
3G Interface Type package.
15.2.1	Circuit Switched Data package
PackageID:	threegcsd (0x0030)
Version:	1
Extends:	None
This package contains the information needed to be able to support GSM and UMTS Circuit Switched Data from the media gateway.
15.2.1.1	Properties
PLMN BC:
	PropertyID: plmnbc (0x0001).
	Description: The PLMN Bearer Capability.
	Type: Octet string.
	Possible values:
-	Specified in the subclause "Bearer capability" in 3GPP TS 24.008 [3] , including the Bearer Capability IEI and Length.
	Defined in: Local Control Descriptor.
	Characteristics: Read/Write.
GSM channel coding:
	PropertyID: gsmchancod (0x0002).
	Description: Channel information needed for GSM.
	Type: Octet string.
	Possible values:
-	The second octet of Chosen Channel as specified in the subclause "Chosen Channel" in 3GPP TS 48.008 [9].
	Defined in: Local Control Descriptor.
	Characteristics: Read/Write.
15.2.1.2	Events
Protocol Negotiation Result:
	EventID: protres (0x0001).
	Description: This event is used to report the result of the protocol negotiation.
	EventsDescriptor Parameters: None.
	ObservedEventsDescriptor Parameters:
-	Negotiation Result:
ParameterId: result (0x0001).
Description: reports whether the protocol negotiation has been successful.
Type: Enumeration.
Possible Values:
"Success" (0x0001): the protocol negotiation on the termination has been successful.
"Failure" (0x0000): the protocol negotiation on the termination has failed.
-	Possible Failure Cause:
ParameterId: cause (0x0002).
Description: indicates the possible failure cause.
Type: Enumeration.
Possible Values:
"Unsp" (0x0001): the protocol negotiation has failed for an unspecified reason.
"V8V34" (0x0002): the V.8 or the V.34 protocol negotiation has failed (modem termination only).
Rate Change:
	EventID: ratechg (0x0002).
	Description: This event is used to report a rate change. For example for GSM FAX if the detected rate does not match the channel rate the MGW shall use this to request a new channel rate. See CMM in 3GPP TS 43.045 [35].
	EventsDescriptor Parameters: None.
	ObservedEventsDescriptor Parameters:
-	New Rate:
ParameterId: rate (0x0001).
Description: reports the new rate for the termination.
Type: Integer.
Possible Values: transmission rate in bits per second, rounded to the nearest integer value. The value must be a valid bitrate; one of the following rates: 2400, 4800, 9600, 14400, 28800, 57600. An invalid rate shall cause the call to be released by the MSC Server.
15.2.1.3	Signals
Activate Protocol:
	SignalID: actprot (0x0001).
	Description: Activate the higher layer protocol.
	Signal type: Brief.
	Duration: N/A.
	Additional parameter:
-	Local Peer Role:
ParameterID: localpeer (0x0001).
Type: Enumeration.
Possible values:
"Orig" (0x0000): originating.
"Term" (0x0001): terminating.
Description: This parameter is optional, but is required for modem and fax calls. It is used to inform the modem whether it should act as originating or terminating peer. This parameter is only included within signal towards the radio access. This may either be an Access Termination or a CN Termination toward another MGW that serves the radio access.
15.2.1.4	Statistics
None.
15.2.1.5	Procedures
This package is used to set up data calls within the CS domain. For more information on the IWF, refer to 3GPP TS 29.007 [6].
When the Media Gateway Controller initiates the "Establish Bearer" procedure, the "Prepare Bearer" procedure, the "Modify Bearer Characteristics" procedure, the "Reserve Circuit" procedure, the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure or the "Reserve and Configure RTP Connection Point" procedure, it shall provide the PLMN BC ("plmnbc" property above) for the termination on the mobile side and the ISDN BC (standard H.248 properties, subclause "Bearer Capabilities") for the termination on the fixed side. For a mobile-to-mobile call, it shall provide the PLMN BC on both terminations.
The presence of the PLMN BC property may trigger the use of the IWF.
Once the bearer has been established, after B-answer, the "Activate Interworking Function" procedure is used to activate the IWF. The Activate Protocol signal ("actprot") will start the negotiation of the layer 2 protocols on both sides. If a modem or fax service is requested, the signal shall contain the Local Peer Role parameter ("localpeer"), to tell the modem whether it should act as originating or terminating peer.
NOTE:	The Activate Protocol signal is needed only after B-answer as described above or after successful in-call modification from speech to fax, to activate the protocol timers at the correct time. This is the only time when this signal is needed (specifically, the signal is not used after a handover sequence or for lawful interception).
The IWF Protocol Indication notifications are used by the MGW to inform the MSC server about IWF protocol events. The MSC has to request the detection of the events "Protocol Negotiation Result" and "Rate Change" in the "Activate IWF" procedure, the "Establish Bearer" procedure, the "Prepare Bearer" procedure, the "Modify Bearer Characteristics " procedure, the "Reserve Circuit" procedure, the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure or the "Reserve and Configure RTP Connection Point" procedure.
For handover to GSM, or change of channel characteristics within the GSM network, the property GSM Channel Coding ("gsmchancod"), which contains the information about the channel type and the number of channels, shall be transmitted to the termination on the mobile side in the "Establish Bearer", the "Prepare Bearer", the "Reserve Circuit", the "Reserve RTP Connection Point", the "Configure RTP Connection Point" and the "Reserve and Configure RTP Connection Point" procedures together with the PLMN BC. The presence of the GSM Channel Coding property also indicates that the termination is using a GSM access network. 
If the MGW has requested a rate change due to GSM fax rate mismatch (CMM procedure see 3GPP TS 43.045 [35]) then it shall suspend transmission until the MSC Server has modified the PLMN Bearer Capability and GSM Channel Coding property to match the required rate. If this occurs while other context manipulations are occurring the MGW shall only resume transmission when the streams are bothway connected and the PLMN Bearer Capability and Channel Coding are correct. The MGW shall not send subsequent rate change notifications while the outstanding rate change has not been performed by the MSC Server.
15.2.2	TFO package
PackageID:	threegtfoc (0x0031)
Version:	2
Extends:	None
This package defines events and properties for Tandem Free Operation (TFO) control. TFO uses inband signalling and procedures for Transcoders to enable compressed speech to be maintained between a tandem pair of transcoders. This package allows an MGW, which has inserted a transcoder, to support TFO.
15.2.2.1	Properties
TFO Activity Control:
	PropertyID: tfoenable (0x0001).
	Description: Defines if TFO is enabled or not.
	Type: Enumeration.
	Possible Values:
-	"On" (0x0001): TFO is enabled, TFO protocol is supported.
-	"Off" (0x0002): TFO is not enabled, TFO protocol is not initiated or terminated.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
TFO Codec List:
	PropertyID: codeclist (0x0002).
	Description: List of codecs for use in TFO protocol, the Local Used Codec (see 3GPP TS 28.062 [5]) is always the first entry in the list. The MSC Server may enable TFO without providing a TFO Codec List ; in this case, the MGW shall behave as if it had received a TFO Codec List composed of the selected codec of the opposing termination within the Context.
	Type: Sub-list of Octet string.
	Possible Values:
-	List of codec types; each entry:
Mc Single Codec, similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. 
In H.248 text encoding, the value of the codeclist property shall be encoded as: 
LBRKT codecconfig *(COMMA codecconfig) RBRKT
Example: H.248 text encoding of the TFO codec list  (UMTS_AMR_2 with Preferred Configuration set 1, and UMTS_AMR-WB with Preferred Configuration set 0):
Threegtfoc/codeclist = { 0206959504 , 020A00 }
Where:
UMTS_AMR_2 parameters are: ETSI, UMTS_AMR_2, ACS={12.2, 7.4, 5.9, 4.75}, SCS={12.2, 7.4, 5.9, 4.75}, OM=0 plus MACS=4
UMTS_AMR_WB parameters are: ETSI, UTMS_AMR_WB, Config-WB-Code=00 
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
15.2.2.2	Events
Optimal Codec Event:
	EventID: codec_modify (0x0010).
	Description: The event is used to notify the MGC that TFO negotiation has resulted in an optimal codec type being proposed.
	EventsDescriptor Parameters: None.
	ObservedEventsDescriptor Parameters:
-	Optimal Codec Type.
ParameterID: optimalcodec (0x0011).
Description: indicates which is the proposed codec type for TFO.
Type: Octet string.
Possible Values:
Mc Single Codec; 
Similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information.
Codec List Event:
	EventID: distant_codec_list (0x0012).
	Description: The event is used to notify the MGC of the distant TFO partner's supported codec list.
	EventsDescriptor Parameters: None.
	ObservedEventsDescriptor Parameters:
-	Distant Codec List:
ParameterID: distlist(0x0013).
Description: indicates the codec list for TFO.
Type: Sub-list of Octet string.
Possible Values:
List of codec types; each entry: 
Mc Single Codec similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information.
The first Codec Type in the list is the Distant Used Codec, received from the distant TFO partner (see 3GPP TS 28.062 [5]). .
In H.248 text encoding, the value of the distlist parameter shall be encoded as: 
 LBRKT codecconfig *(COMMA codecconfig) RBRKT
TFO Status Event:
	EventID: TFO_status (0x0014).
	Description: The event is used to notify the MGC that a TFO link has been established or broken.
	EventsDescriptor Parameters: None.
	ObservedEventsDescriptor Parameters:
-	TFO Status:
ParameterId: tfostatus (0x0015).
Description: reports whether TFO has been established or broken. Upon TFO activation, no notification is sent if TFO has not been established. A TFO_Off notification is only reported when a TFO link previously established is broken. The MGW should not report transient TFO status change.
Type: Boolean
Possible Values:
"TFO_On" : TFO has been established.
"TFO_Off" : TFO is no more established.
15.2.2.3	Signals
None.
15.2.2.4	Statistics
None.
15.2.2.5	Procedures
For the procedures for TFO see 3GPP TS 28.062 [5].
To enable TFO, the MSC Server shall configure the properties of this package on a MGW Termination with the media stream property for Codec Type set to ITU‑T Recommendation G.711 [25] (see annex C of ITU‑T Recommendation H.248 [10]) or Bearer Service Characteristics set to " Speech" or "3.1 kHz Audio" in TMR or USI due to Reserve Circuit Procedure, see in ITU‑T Recommendation Q.1950 (see 3GPP TS 29.205 [7]). 
The TFO protocol shall be disabled if the call configuration becomes no longer TFO compatible or if the Codec Type property of the media stream at the opposing termination in the Context is reconfigured to G.711 or if the Bearer Service Characteristics of the opposing Termination is reconfigured to "Speech" or "3.1 kHz Audio".  The TFO protocol may be disabled either by the MSC Server by using the TFO Activity Control property of this package or by the MGW in accordance with the TFO rules as described in [5] when it detects that TFO operation is no longer possible (for example it has G.711 encoding at opposing Terminations).
15.2.3	3G Expanded Call Progress Tones Generator Package
PackageID:	threegxcg(0x0032)
Version:	1
Extends:	xcg version1
This package extends "Expanded Call Progress Tones Generator Package", as defined in ITU‑T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The package adds a new toneId for CAMEL prepaid warning tone.
15.2.3.1	Properties
None.
15.2.3.2	Events
None.
15.2.3.3	Signals
CAMEL Prepaid Warning Tone:
	SignalID: cpwt (0x004f).
	Description: Generate CAMEL prepaid warning tone to inform the party that the Max Call Period Duration is about to expire. CAMEL prepaid warning tone is defined in 3GPP TS 23.078 [22]. The physical characteristic of CAMEL prepaid warning tone is available in the gateway.
	Signal type: Brief.
	Duration: Provisioned, Not Auditable.
	Additional parameters:
-	Tone Direction.
-	ParameterID: td (0x0010).
-	Type: Enumeration.
-	Values:
-	"Ext" (0x01): external.
-	"Int" (0x02): internal.
-	"Both" (0x03): Both.
-	Default: "Ext".
15.2.3.4	Statistics
None.
15.2.3.5	Procedures
None.
15.2.4	Modification Of Link Characteristics Bearer Capability
PackageName:	Modification of Link Characteristics Bearer Capability
PackageID:	threegmlc(0x0046)
Description:	This package contains an event that when requested by the MGC will cause the MG to notify the MGC that modification of the link characteristics is allowed. This notification is typically generated when the bearer has been established.
Version:	1
Extends:	None
15.2.4.1	Properties
None.
15.2.4.2	Events
Bearer Modification Support Event.
	EventID: mod_link_supp (0x0001).
	Description: The event is used to notify the MGC that modification of the link characteristics of the current bearer connection is permitted.
	EventsDescriptor Parameters: None.
	ObservedEventsDescriptor Parameters: None.
15.2.4.3	Signals
None.
15.2.4.4	Statistics
None.
15.2.4.5	Procedures
If the MGC is interested in determining whether or not the bearer associated with a termination supports modification of its link characteristics it shall send a request (Add/Modify/Move) with the Bearer Modification Support Event. When the bearer is established the MG will indicate in a Notify request to the MGC if modification of link characteristics is supported. A notify will NOT be generated if modification is NOT supported on the bearer.
15.2.5	Enhanced Circuit Switched Data package
PackageID:	threegcsden (0x0082)
Version:	1
Extends:	threegcsd (0x030) Version 1
This package extends "Circuit Switched Data Package", as defined in subclause 15.1.2. This package adds a new property to define the user bitrate at a Iu termination.
15.2.5.1	Properties
Bitrate
	PropertyID: bitrate (0x0003).
	Description: user bitrate.
	Type: Integer.
	Possible Values: transmission rate in bits per second, rounded to the nearest integer value. The value shall be a valid bitrate; one of the following rates: 2400, 4800, 9600, 14400, 28800, 57600, 64000. 
	Defined in: Local Control Descriptor.
	Characteristics: Read/Write.
15.2.5.2	Events
None.
15.2.5.3	Signals
None.
15.2.5.4	Statistics
None.
15.2.5.5	Procedures
This package is used in addition to the 3GCSD package for CS data calls. It is used for indicating the user data rates for Inter-MSC SRNS Relocation and handover cases. If the Bitrate is not 64 kb/s at one termination in the MGW but its opposing termination has properties that define its bitrate to be 64 kb/s (e.g. TMR=UDI) then A-TRAU' protocol shall be applied by the MGW. For further details see 3GPP TS 29.007 [6].
15.2.6	Cellular Text telephone Modem Text Transport
PackageName:	CTM Text Transport
PackageID:	threegctm (0x0068)
Description:	The CTM text transport package is intended for enabling robust real time text conversation through a voice channel primarily intended for communication over mobile networks. This package includes the mechanisms needed to transport T.140 text conversation streams [19] in a voice channel environment, using the CTM Cellular Text Telephone Modem specified in 3GPP TS 26.226 [18]. The transport mechanism allows for alternating transport of voice and text. 
Version:	1
Extends:	None
15.2.6.1	Properties
Text termination connection state:
	PropertyID: connstate (0x0001).
	Description: The connection state property is used to reflect details of the achieved text connection. For each new session connstate should be reset to "Prepare".
	Type: Enumeration.
	Possible values:
-	"Idle" (0x0001) meaning that CTM availability negotiation has failed; CTM is disabled except for monitoring the incoming line for CTM signals.
-		"Prepare" (0x0002) for CTM being enabled, monitoring for CTM signals and ready to send CTM signals.
-		"Connected" (0x0006) for CTM being enabled and to have detected CTM availability in the current session.
	Defined in: TerminationState.
	Characteristics: Read/Write.
Text Transport:
	PropertyID: trpt (0x0002)
	Description: The transport parameter reflects the transport mechanism selected for the Text Conversation termination. In 3GPP, one possible transport mechanism is the Cellular Text Telephone Modem as in 3GPP TS 26.226 [18]. It is used when it is desired to transport the text conversation in a voice channel. CTM enables alternating use of the voice channel for voice and text during the call.
	Type: Enumeration.
	Possible values:
-	"ctm" (0x0008) for text transport in mobile voice channel as in 3GPP TS 26.226 [18].
	Defined in: LocalControl.
	Characteristics: Read/Write.
Text Protocol Version:
	PropertyID: textproto (0x0003).
	Description: The version of the ITU-T Recommendation T.140 [19] protocol used in the connection.
	Type: Integer.
	Possible values:
-	Any integer corresponding to a T.140 version number (currently 1) as in ITU-T Recommendation H.248 .2 [17].
	Defined in: LocalControl.
	Characteristics: Read/Write.
15.2.6.2	Events
Connection State Change:
	EventID: connchange (0x0001).
	Description:
-	This event will occur when the text connection state for the termination has changed.
-	The parameter values are the same as the Connection State property.
-	If a CTM availability request timed out, the state is returned to Idle.
EventDescriptorParameters:
	None.
ObservedEventDescriptorParameters:
	ParameterName: Connection Change.
	ParameterID: connchng (0x0001).
	Type: Enumeration.
	Possible Values: As property threegctm/connstate.
15.2.6.3	Signals
None.
15.2.6.4	Statistics
Characters Transferred:
	StatisticsID: chartrans (0x0001).
	Description: Number of bytes of ITU-T Recommendation T.140 [19] data transferred through the termination.
	Units: count.
15.2.6.5	Procedures
If the MGC detects a CTM indication it shall send a request (Add/Modify/Move) with the CTM Transport property. Upon receivable of it, the MGW shall allocate a termination with CTM capabilities. Normal usage is that the CTM enabled termination handles one text stream and one voice stream and alternates between transporting voice and text in  the voice channel according to the functionality of CTM. This termination could for example be combined in a context with a termination with the txp and ctyp packages for gateway functionality between PSTN text telephony and mobile CTM based text telephony. These packages are described in ITU-T Recommendation H.248.2 [17].
The CTM algorithm has states. The states defined in the text termination connection state property are mapped into CTM states in the following way:
-	Idle: CTM disabled because of an unsuccessful CTM availability negotiation.
-	Prepare: normal initial state with CTM monitoring active.
-	Connected: CTM negotiation is completed.
For each new call, the CTM termination shall be put in the Prepare state.
When the CTM availability negotiation is completed, the state is Connected.
The state transitions are automatic, except for setting Prepare state as described above.
15.2.7	IP transport package
This package has been replaced by the use of Annex C.6 IP and UDP properties (see subclauses 14.2.41 and 14.2.42). 
15.2.8	Flexible Tone Generator Package
PackageID:	threegflex (0x0084)
Version:	1
Extends:	threegxcg version 1
This package extends "3G Expanded Call Progress Tones Generator Package", as defined in chapter 15.1.4 above. This package adds a new tone for call duration control in CAMEL phase 4, supporting variable sequence of tones and burst list.
15.2.8.1	Properties
None.
15.2.8.2	Events
None.
15.2.8.3	Signals
	Signal Name: Flexible Tone.
	SignalID: ft (0x0050).
	Description: Generate flexible 900 Hz tone. The physical characteristics of Flexible Tone is not described in the additional parameters. It shall be available in the Media Gateway.
	SignalType: Brief.
	Duration: Provisioned.
	Additional Parameters:
-	Parameter Name: Burst List Direction
	Description: Used to indicate the direction the tone is to be sent. External indicates that the tone is sent from the MG to an external point. Internal indicates that the tone is played into the Context to the other terminations. Both way indicates both internal and external behaviour.
	ParameterID: bld (0x0001).
	Type: Enumeration.
	Possible Values:
-	"Ext" (0x01): External.
-	"Int" (0x02): Internal.
-	"Both" (0x03): Both way.
-	Default: "Ext" (0x01).
	Parameter Name: numberOfBursts.
	Description: Number of bursts in the burst list.
	ParameterID: nob (0x0002).
	Type: Integer.
	Possible values: 1 to 3.
	Default: 1.
	Parameter Name: burstInterval.
	Description: Time interval between two consecutive bursts expressed in amount of 100 ms units.
	ParameterID: bi (0x0003).
	Type: Integer.
	Possible values: 1 to 1200.
	Default: 2.
	Parameter Name: numberOfTonesInBurst.
	Description: Number of tones to be played in each burst.
	ParameterID: notib (0x0004).
	Type: Integer.
	Possible values: 1 to 3.
	Default: 3.
	Parameter Name: toneDuration.
	Description: Duration of each tone in a burst expressed in amount of 100 ms units.
	ParameterID: td (0x0005).
	Type: Integer.
	Possible values: 1 to 20.
	Default: 2.
	Parameter Name: toneInterval.
	Description: Time interval between two consecutive tones in a burst expressed in amount of 100 ms units.
	ParameterID: ti (0x0006).
	Type: Integer.
	Possible values: 1 to 20.
	Default: 2.
15.2.8.4	Statistics
None.
15.2.8.5	Procedures
The MGW should generate the tones using the above mentioned parameters as specified in 3GPP TS 23.078 [22] subclause 4.5.7.1.2
In case MGC requests to generate a flexible tone specifying a signal type "Timeout" and a "Duration" longer than the time needed to play the whole Burst List no action will be taken on the incoming stream to fill the gap. I.e. if any user plane stream is received on one side of the termination after the end of the burst list, it will be present, unchanged, on the other side of the termination as well (transparent mode).
15.2.9	Trace Package
PackageID: calltrace (0x0097)
Version: 1
Extends: None
This package defines properties for subscriber and equipment trace activation and deactivation properties to be attached to the trace record generated by MGW.
15.2.9.1	Properties
Trace Activation Control
PropertyID: traceactivityrequest(0x0001)
Description: Defines if trace is activated or deactivated.
Type: Bool
Possible Values: 
"on" (true):  Trace Session is activated in MGW
"off" (false):  Trace Session is deactivated in MGW
Defined in: Local Control descriptor
Characteristics: Read/Write 
IMSI
PropertyID: imsi(0x0002)
Description: IMSI number of the traced subscriber to be attached to the trace record. Used for record identification like trace reference. 
Type: Octet string
Possible Values:  The IMSI is coded as defined in 3GPP TS 23.003 [43]. The IMSI is TBCD-coded with a fixed length of 8 octets. Two digits are encoded per octet, each digit is encoded 0000 to 1001 (0 to 9). Bits 8765 of octet n encodes digit 2n, bits 4321 of octet n encodes digit 2(n-1) +1 (i.e the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [43]). 1111 is used as filler when there is an odd number of digits. Digits are packed contiguously with no internal padding.
Defined in: Local Control descriptor
Characteristics: Read/Write
IMEI(SV)
PropertyID: imei_sv(0x0003)
Description: IMEI(SV) number of the traced equipment to be attached to the trace record. Used for record identification like trace reference. 
Type: Octet string
Possible Values: The IMEI(SV) is coded as defined in 3GPP TS 23.003 [43]. The IMEI(SV) is TBCD encoded. Two digits are encoded per octet, each digit is encoded 0000 to 1001 (0 to 9). Bits 8765 of octet n encodes digit 2n, bits 4321 of octet n encodes digit 2(n-1) +1 (i.e the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [43]). 1111 is used as filler when there is an odd number of digits. Digits are packed contiguously with no internal padding.
Defined in: Local Control descriptor
Characteristics: Read/Write
Trace Reference
PropertyID: tracereference(0x0004)
Description: Reference number to identify different Trace Session in OSS as defined in 3GPP TS 32.421 [29] and 3GPP TS 32.422 [30].
Type: Octet string
Possible Values: OSS (EM) defines when activating a Trace Session
Defined in: Local Control descriptor
Characteristics: Read/Write
Trace Recording  Session Reference
PropertyID: tracerecsessionref(0x0005)
Description: A unique identifier within the Trace Session for identifying the Trace Recording sessions. Defined in 3GPP TS 32.421 [29] and in 3GPP TS 32.422 [30].
Type: Octet string
Possible Values:  Described in 3GPP 32.422 [30]
Defined in: Local Control descriptor
Characteristics: Read/Write
Trace Depth
PropertyID: tracedepth(0x0006)
Description: Trace Depth as defined in 3GPP TS 32.421 [29] 
Type: Enumaration
Possible Values: Defined in 3GPP TS 32.422 [30]
Defined in: Local Control descriptor
Characteristics: Read/Write

Triggrering Events 
PropertyID: triggeringevent(0x0007)
Description: Triggrering Events as defined in 3GPP TS 32.422 [30]. 
Type: Octet string
Possible Values: Defined in 3GPP TS 32.422 [30].
Defined in: Local Control descriptor
Characteristics: Read/Write
List of interfaces
PropertyID: listofinterfaces(0x0008)
Description: List of interfaces to trace as defined in 3GPP TS 32.422 [30]
Type: Octet string
Possible Values: Defined in 3GPP TS 32.422 [30]
Defined in: Local Control descriptor
Characteristics: Read/Write
15.2.9.2	Events
Trace result
EventID: tracact (0x0001)
Description: Notification to the MSC Server if trace activation was successful/unsuccessfull in the MGW.
EventDescriptor parameters: None
ObservedEventsDescriptor parameters:
Result: Trace Activation Result
res (0x0001)
Type: enumeration
Possible values:
success (0x0001): "Trace Succesfully activated"
failure (0x0000): "Failure in trace activation"
15.2.9.3	Signals
None
15.2.9.4	Statistics
None
15.2.9.5	Procedures
For the network level procedures of  the tracing see 3GPP 32.422 [30].
For the trace records of the MGW see 3GPP 32.423 [31].
In H.248 interface MSC Server uses 'Trace Activity Control' property  to indicate MGW that a termination should be placed under trace or should be taken out of trace. In the call establishing phase MSC Server sets trace package information into proper command (Add or Modify) associated to the termination to be traced. Tracing can be activated either by giving IMEI(SV) or IMSI number as a further information. MSC Server shall also provide the values for all other properties described in this package that is IMSI if trace is activated based on IMSI, IMEI(SV) if trace is activated based on IMEI(SV), Trace reference, Trace recording session reference, Trace depth, triggering events in MGW, list of interfaces in MGW.  When MSC Server activates the trace, it shall use 'Trace Activation Result' Event to detect if the Trace Activation was succesful or not. MGW shall not reject the Add/Modify because of unsuccesful Trace Activation, but only send a Notification with this Event. Tracing  is automatically deactivated in MGW when termination is taken out of the context in the end of the call. If the Termination is Moved to another Context, trace is automatically forwarded to new termination.
15.2.10	ASCI Group call package
PackageID:	threegasci (0x00b2)
Version:	2
Extends:	None
This package contains the information needed to be able to support VGCS (3GPP TS 43.068 [39]) and VBS (3GPP TS 43.069 [40]) services.
15.2.10.1	Properties
Number of needed conference terminations
PropertyID: nct (0x0001)
Description: Indicates the number of needed conference terminations for the call.
Type: Integer
Defined in Descriptor: Local Control Descriptor
Characteristics: Read/Write 
Number of desired listener context terminations
PropertyID: nlct (0x0002)
Description: Indicates the number of desired terminations for a listener context.
Type: Integer
Defined in Descriptor: Local Control Descriptor
Characteristics: Read/Write
15.2.10.2	Events
None.
15.2.10.3	Signals
None.
15.2.10.4	Statistics
None
15.2.10.5	Procedures
The MSC server receives the number of needed conference terminations from GCR (see 3GPP TS 43.068 [39]) and 3GPP TS 43.069 [40]) and reserves the requested number of needed Conference terminations for that call. The parameter "Number of needed conference terminations" shall be included when allocating the first termination of an ASCI-conference context. It is optional when adding further terminations. If the MGW is unable to reserve the number of requested terminations for that call, it shall response with error code 510 "insufficien resources".
The parameter "Number of desired listener context terminations" should be included when allocating the first termination of a Listener context.
15.2.11	3G Interface Type package
PackageID:	threegint (0x00e3) 
Version:	1
Extends:	None
This package contains a property to specify the used interface type for IP terminations.
15.2.11.1	Properties
IP Interface Type
PropertyID: ipint (0x0001)
Description: Indicates the type of external interface used by the termination.
	Type: Enumeration.
	Possible Values:
-	"NboIP" (0x0001) Nb over IP with SIP-I based Nc, see 29.414 [32].
-	"AoIP" (0x0002) A interface over IP.
-	"MboIP" (0x0003) Mb interface
-	"ExtSIPI" (0x0004) External SIP-I based network
All other values reserved.
	Defined in: Local Control descriptor.
	Characteristics: Read/Write.
15.2.11.2	Events
None.
15.2.11.3	Signals
None.
15.2.11.4	Statistics
None
15.2.11.5	Procedures
The MSC server may indicate the interface type (reference point) associated with the RTP bearer termination to the MGW with this package. This allows MGW to collect statistics per interface type associated with the RTP bearer termination as required by 3GPP TS 32.407[58]. The provision of these statistics is outside of the scope of this specification.
Annex A (informative):
Framing protocol Interworking Function (FPIF)
A.1	Introduction
SDUs transmitted over an Iu or Nb interface and received at a MGW whose outgoing UP is also Iu or Nb shall be relayed to the outgoing UP MGW termination.  If no interworking function (other than the FPIF) or transcoder device is inserted by the MGW, and if UP terminations are present, then PDUs and control procedures are passed between MGW terminations by the FPIF. The FPIF is the functional entity responsible for aligning or mapping control procedures (including RFCIs, frame numbers etc) on the separate UP interfaces according to the package procedures described in the main text. The FPIF determines if the two UP configurations are identical and thus the UP PDUs may be passed transparently. If the FPIF determines that the two UP configurations are not identical it applies the required mapping. The relaying of PDUs transparently can also be considered as FPIF bypass.
NOTE:	the implementation in the MGW can perform a more efficient processing of the PDUs in this case. The MGW switching and bypassing of the protocol functions during TrFO is left to the manufacturer's implementation.
UP initialisations are not handled by the FPIF, only receipt of the Subflow combinations and the RFCI allocations are received by the FPIF for each UP.
The RFCIs are relayed by the FPIF as described in main text for the UP package procedures.

Figure A.1: The Framing Protocol Interworking Function
A.2	FPIF procedures with respect to Iu framing protocol
This clause handles relay of user data indicated to the FPIF in a Nb- or Iu-UP-data-indication message and transmitted between peer UP layer entities in PDU types 0 and 1. The FPIF passes this information to the UP layer on the sending side in a Nb- or Iu-UP-data-request message.
A.2.1	Payload
Received SDUs shall be forwarded unmodified to the next MGW. Note that if "delivery of erroneous SDUs" is set to 'no', faulty SDUs are already discarded by the Iu or Nb support mode functions and, hence, not delivered to the FPIF.
A.2.2	RFCIs
If the RFCI values on the outgoing UP interface match those initialised on the incoming UP interface then the RFCI indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side.
If the RFCI sets on the outgoing UP interface do not match those initialised on the incoming UP interface then the FPIF performs mapping between the RFCIs on each UP for the same initialised Subflow Combination.
The FPIF is the entity that may perform the RFCI value correction procedure as described in the main text, after this procedure then relaying of the received RFCI shall be performed.
A.2.3	FQC
The FQC indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side.
A.2.4	Frame number
The frame number indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side.
A discontinuity in framing protocol support mode frame numbers is allowed at the end of the TrFO break.
A.3	Relay of status information
This clause handles relay of status information indicated to the FPIF in a Nb- or Iu-UP-status-indication message and transmitted between peer UP layer entities in PDU type 14. The FPIF in general passes this information to the UP layer on the sending side.
A.3.1	Void
A.3.2	Rate Control Frames
The FPIF shall pass rate control request and rate control acknowledgement frames transparently between incoming UP interface and outgoing UP interface.
Before a MGW reverts from TrFO break operation (for example during handover or relocation where the rate control procedures may have been operating independently between each UP interface) the FPIF may perform rate control procedures to each UP peer. It shall then use the Maximum rate and Current rate settings from the opposite UP configurations. This is performed to align the UP's on each side of the MGW to enable relaying of all subsequent PDUs as described above.
Optionally, the UP layer protocol entity on the sending side may substitute the frame number received in a status request by another number, but shall then substitute the initial number back in the status indication containing the acknowledgement. Figure A.2 shows an example of the relay of the rate control procedure.

Figure A.2: Relay of a control procedure
A.3.2	Time Alignment
Time alignment frames shall be relayed unmodified.
Annex B (informative):
Examples for Usage of the 3GUP Package "Initialization Direction" Property
 EMBED Word.Picture.8  
Figure B.1: 3G to 3G Call (A to B) , originating RAB established after Nb bearer, 
same codec configuration on originating Iu and Nb bearers
NOTE: 	The Initialization Direction property of the Nb termination of MGW A could alternatively be set to 'Outgoing', but different RFCIs may then be initialized on the Iu and Nb bearers.
 EMBED Word.Picture.8  
Figure B.2: 3G Originating Call, originating RAB established after Nb bearer, 
same codec configuration on originating Iu and Nb bearers 
NOTE: 	The Initialization Direction property of the Nb termination of MGW A could alternatively be set to 'Outgoing', but different RFCIs may then be initialized on the Iu and Nb bearers.

 EMBED Word.Picture.8  
Figure B.3: 3G Terminating Call
 EMBED Word.Picture.8  
Figure B.4: 3G to 3G Call (A to B), originating RAB established before or in parallel to the Nb bearer or different codec configuration on originating Iu and Nb bearers

 EMBED Word.Picture.8  
Figure B.5: 3G Originating Call, originating RAB established before or in parallel to the Nb bearer or 
different codec configuration on originating Iu and Nb bearers
 EMBED Word.Picture.8  
Figure B.6: 2G to 2G Call (A to B)


Annex C (Normative):
Profile description
C.1	Profile Identification

Profile name:
Threegbicsn
Version:
5
The name and version of the profile that is sent in the service change command.
C.2	Summary
This Profile describes the minimum mandatory settings and procedures required to fulfil the requirements of the Mc interface media gateway control. In addition optional settings and procedures are described which fulfil optional features and where supported, the minimum mandatory settings within the optional procedures and packages are identified that must be supported in order to support that feature.
"Optional" or "O" means that it is optional for either the sender or the receiver to implement an element. If the receiving entity receives an optional element that it has not implemented it should send an Error Code (e.g. 445" Unsupported or Unknown Property", 501"Not Implemented", etc.) . "Mandatory" or "M" means that it is mandatory for the receiver to implement an element. Whether it is mandatory for the sender to implement depends on specific functions; detail of whether elements of the core protocol are manadatory to be sent are defined in the stage 2 procedures, stage 3 procedures and/or the descriptions of individual packages. 
The setting or modification of elements described in the profile under the heading "Used in Command" has the meaning that the property can be set/modified with that command. The property may be present in other commands (in order to preserve its value in accordance with ITU-T H.248.1[10]) when those commands are used for other procedures that affect the same descriptor.
C.3	Gateway Control Protocol Version
ITU Recommendation H.248.1 Version 2
The minimum H.248 version required to support the profile. This should be based upon base syntax support and not an arbitrary version assignment. This is related to the ServiceChangeVersion in clause C.8.8.
C.4	Connection Model
Table C.4: Connection Model
Maximum number of contexts:
No restriction
Maximum number of terminations per context:
32
Allowed termination type combinations in a context:
All 

C.5	Context Attributes
Table C.5/1: Context attributes
Context Attribute
Supported
Values Supported
Topology
Yes (NOTE 1)
See clause  C.7.8 Topology Descriptor
Priority Indicator
No
NA
Emergency Indicator
Yes
NA
IEPS Indicator (NOTE 2)
No
NA
ContextAttribute Descriptor (NOTE 2)
No
NA
ContextIDList Parameter (NOTE 2)
No
NA
NOTE 1: 	Stream ID in Topology Descriptor shall not be supported.
NOTE 2:	This field requires at least version 3 of the H.248.1 protocol.
 
Table C.5/2: AND/OR Context attributes
AND/OR Context Attribute
No
NA
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

C.6	Terminations
C.6.1	Termination Names
C.6.1.1	General
The Termination ID structure shall follow the guidelines of H.248 and the structure is either relevant or irrelevant for MGC and MGW.
The relevance depends on the utilized bearer type for termination. With ephemeral ATM/AAL2 and IP endpoint bearer types the internal structure of Termination ID is irrelevant for MGW and MGC and therefore Termination ID is only numeric identifier for termination. When bearer type is physical timeslot within TDM circuit the Termination ID structure shall follow the Termination naming convention for TDM circuit bearer. 
Ephemeral terminations are further denoted in the profile by the following: 
BICC (meaning applies to terminations towards BICC)
BICC ATM (meaning applies to terminations towards BICC with ATM transport)
BICC IP (meaning applies to terminations towards BICC with IP transport)
Iu (meaning applies to terminations towards Iu interface) 
RTP (meaning applies to all IP terminations, e.g. SIP-I/Nb, Mb, AoIP)
RTP-CN (meaning applies to terminations towards SIP-I)
RTP-A (meaning applies to terminations towards A interface over IP)
Editor's Note: it is FFS if specific handling in the profile for the RTP-CN or RTP-A types is needed.
C.6.1.2	ASN.1 Coding
C.6.1.2.1	General Structure
The following general structure of termination ID shall be used:
4 octets shall be used for the termination ID. The following defines the general structure for the termination ID:
Table C.6.1.2.1: ASN.1 coding
Termination type 
X

Termination type:
Length 3 bits
Values:
000 Reserved
001 Ephemeral termination
010 TDM termination
011 - 110 Reserved
111 Reserved for ROOT termination Id (ROOT Termination ID = 0xFFFFFFFF)
X:
Length 29 bits.
Usage dependent on Termination type. TDM terminations specified below in subclause C.6.1.2.2. Other usage un-specified.
C.6.1.2.2	Termination naming convention for TDM terminations
Table C.6.1.2.2 ASN.1 coding
Termination type (=010 )
PCM system
Individual

PCM system:
Length 24 bits
Usage unspecified. Uniquely identifies PCM interface in MGW
Individual:
Length: 5 bits
Max. of 32 individuals (timeslots) per PCM system (max. 24 for a 24 channel system)
C.6.1.3	ABNF Coding
C.6.1.3.1	General Structure
The following general structure of termination ID shall be used:
TerminationID      = "ROOT"  /  pathName  /  "$" /  "*"	; According to H.248.1 annex B
C.6.1.3.2	Termination naming convention for TDM terminations
pathName = TDMToken UNDERSCORE ((PCMsystem / "*") SLASH (Individual / "*"))
TDMToken = "TDM"
UNDERSCORE = %x5F	;"_"
PCMsystem : Usage not specified
Individual = 1 * 2 (DIGIT)	; 0-31

C.6.1.3.3	Termination naming convention for Ephemeral terminations
pathName	= EphTokenUNDERSCORE(EPHsystem/"*")
EphToken = "Ephemeral"
UNDERSCORE = %x5F	;"_"
EPHsystem : Usage is not specified
C.6.2	Multiplexed terminations
Table C.6.2: Multiplexed terminations
Multiplex terminations supported?
No

C.7	Descriptors
C.7.1	Stream Descriptor
Table C.7.1: Stream descriptors
Maximum number of streams per termination type
 All
1

C.7.1.1	LocalControl Descriptor
Table C.7.1.1/1: Local Control Descriptor
If not generic list appropriate termination and stream types.
Termination Type
Stream Type
ReserveGroup used:
No
-
-
ReserveValue used:
Yes
 BICC (NOTE), RTP
 Not Applicable
NOTE: 	The support is needed for the optional procedures Modify Char (see 14.2.27) and Reserve Char (see 14.2.28). These procedures use Q.1950 procedures which define the use of  the Reserve Value.

Table C.7.1.1/2: Allowed Stream Modes
Termination Type
Stream Type
Allowed StreamMode Values
All 
 Not Applicable
SendOnly, RecvOnly, SendRecv, Inactive 

C.7.2	Events Descriptor
All events contained in this profile may be set on any termination/stream with the following exceptions.
Table C.7.2/1: Events Descriptor 
Events settable on termination types and stream types:
Yes
If yes
EventID 
Termination Type 
Stream Type
Cause (g/cause, 0x0001/0x0001)
All except ROOT
 Not Applicable
Signal Completion (g/sc, 0x0001/0x0002)
All except ROOT 
Not Applicable
Start tone detected (tonedet/std, 0x0004/0x0001)
All except ROOT
Not Applicable
End Tone detected (tonedet/etd, 0x0004/0x0002)
All except ROOT
Not Applicable
DTMF character 0
(dd/d0, 0x0006/0x0010) 
to DTMF character D
(dd/dd, 0x0006/0x001d)
All except ROOT
Not Applicable
Completion (ct/cmp, 0x000a/0x0005)
TDM
Not Applicable
BNC Change (GB/BNCChange, 0x0021/0x01)
BICC, Iu
Not Applicable
Tunnel Indication (BT/TIND, 0x0022/0x01)
BICC IP
Not Applicable
MGCon    (chp/mgcon,  0x0029/0x0001)
ROOT
Not Applicable
Termination Heartbeat (hangterm/thb, 0x0098/0x0001)
All except ROOT
Not Applicable
Protocol Negotiation Result: (threegcsd/protres, 0x0030/0x0001) 
All except ROOT
Not Applicable
Rate Change (threegcsd/ratechg, 0x0030/0x0002)
All except ROOT
Not Applicable
Optimal Codec Event (threegtfoc/codec_modify, 0x0031/0x0010)
All except ROOT
Not Applicable
Codec List Event (threegtfoc/distant_codec_list, 0x0031/0x0012)
All except ROOT
Not Applicable
TFO Status Event (threegtfoc/TFO_status, 0x0031/0x0014)
All except ROOT
Not Applicable
Bearer Modification Support Event (threegmlc/mod_link_supp, 0x0046/0x0001)
Iu
Not Applicable
Connection State Change (threegctm/connchange, 0x0068/0x0001)
All except ROOT
Not Applicable
Trace result (calltrace/ tracact, 0x0097/0x0001)
All except ROOT
Not Applicable
Inactivity Timeout (it/ito, 0x0045/0x0001)
ROOT
Not Applicable
Available Realms Changed (ipra/arc, 0x00e0/0x0001)
ROOT
Not Applicable
IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001)
RTP-CN
Not Applicable
NOTE:	Stream ID may be ignored in Events Descriptor

Table C.7.2/2: Event Buffer Control
EventBuffer Control used:
No

Table C.7.2/3: Keep active
KeepActive used on events:
Yes

Table C.7.2/4: Embedded events and signals
Embedded events in an Events Descriptor:
No
Embedded signals in an Events Descriptor:
No

Table C.7.2/5: Regulated Embedded events
Regulated Embedded events are triggered on:
None
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.7.2/6: ResetEventsDescriptor
ResetEventsDescriptor used with events:
None
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.7.2/7: Notification Behaviour
NotifyImmediate:
ALL Events
NotifyRegulated:
None
NeverNotify:
None
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

C.7.3	EventBuffer Descriptor
Table C.7.3: Event Buffer Descriptor
EventBuffer Descriptor used:
No

C.7.4	Signals Descriptor
Table C.7.4/1: Signals Descriptor
The setting of signals is dependant on termination or streams types:
Yes

NOTE: 	"No" means that all signals can be played on any termination or stream. If "Yes", any signal not listed below may be played on any termination or stream, except Signals on ROOT termination shall not be supported.
If yes
SignalID 
Termination Type 
Stream Type / ID
Establish BNC (GB/EstBNC, 0x0021/0x01)
BICC
Not Applicable
Modify BNC (GB/ModBNC, 0x0021/0x02)
BICC
Not Applicable
Release BNC (GB/RelBNC, 0x0021/0x03)
BICC ATM
Not Applicable
Bearer Information Transport (BT/BIT, 0x0022/0x01)
BICC IP
Not Applicable
Continuity Test (ct/ct, 0x000a/0x0003)
TDM
Not Applicable
Respond (ct/rsp, 0x000a/0x0004)
TDM
Not Applicable
NOTE:	Stream ID may be ignored for Signals Descriptor

Table C.7.4/2: Signal Lists
Signals Lists supported:
Yes
If yes
Termination Type Supporting Lists:
ALL except ROOT 
Stream Type Supporting lists:
ALL
Maximum number of signals to a signal list:
FFS 
Intersignal delay parameter supported: (NOTE)
No
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.7.4/3: Overriding Signal type and duration
Signal type and duration supported:
Yes
If yes
SignalID 
Type or duration override
All Tones, Announcements and DTMFs 
Both

Table C.7.4/4: Signal Direction
Signal Direction supported:
No
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.7.4/5: Notify completion
NotifyCompletion supported:
Yes
If yes
SignalID 
Type of completion supported
All Tones and Announcements 
TO, EV, SD, NC
RequestID Parameter supported: (NOTE)
No
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.7.4/6: Signals played simultaneously
Signals played simultaneously:
No

Table C.7.4/7: Keep active
KeepActive used on signals:
Yes

C.7.5	DigitMap Descriptor
Table C.7.5: DigitMap Descriptor
DigitMaps supported:
No

C.7.6	Statistics Descriptor
Table C.7.6/1: Statistics Descriptor support
Statistics supported on:
Termination

Table C.7.6/2: Statistics Report on Subtract
Statistics reported on Subtract:
Yes
If yes
StatisticIDs reported:
If Global Text Telephony used:
Characters Transferred (threegctm/chartrans , 0x0068/0x0001)

C.7.7	ObservedEvents Descriptor
Table C.7.7: ObservedEvents Descriptor
Event detection time supported:
No

C.7.8	Topology Descriptor
Table C.7.8: Topology Descriptor
Allowed triples:
(T1, T2, isolate) (T1, T2, oneway) (T1, T2, bothway)
NOTE: 	The Topology Descriptor shall be supported by the MGW and MGC for VGCS, VBS, handover and lawful interception. It can also be used for sending tones and playing announcements.

C.7.9	Error Descriptor
Which H.248.8 and package defined error codes are supported?
Table C.7.9/1: Error Codes Sent by MGC
Supported H.248.8 Error Codes:
ALL H.248.8, list of individual numbers>
Supported Error Codes defined in packages:
For a list of error codes see clauses 5.14.x  

Table C.7.9/2: Error Codes Sent by MGW:
Supported H.248.8 Error Codes:

Supported Error Codes defined in packages:
For a list of error codes see clauses 5.14.x  

C.7.10	TerminationState Descriptor
Table C.7.10/1: TerminationState Descriptor
TerminationState: ServiceStates:
InService/OutofService
TerminationState: EventBufferControl:
OFF

C.8	Command API
NOTE – It is assumed that an Error Descriptor may be returned in any command reply.
C.8.1	Add 
Table C.8.1/1: Descriptors used by Command Add Request
Descriptors used by Add request:
Events, Signals, Media (LocalControl, Local And Remote), Audit

Table C.8.1/2: Descriptors used by Command Add Reply
Descriptors used by Add reply:
Media (LocalControl, Local And Remote), Error

When ADD commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. Exceptions to this rule are:
The Error Descriptor
SDP properties returned in "Reserve RTP Connection Point"  and "Reserve and Configure RTP Connection Point" procedures, as specified in 14.2.51 and 14.2.53
The applicability of this restriction for text encoding is FFS.

C.8.2	Modify
Table C.8.2/1: Descriptors used by Command Modify Request
Descriptors used by Modify request:
 Events, Signals, Media (LocalControl, Local And Remote), Audit

Table C.8.2/2: Descriptors used by Command Modify Reply
Descriptors used by Modify reply:
Media (LocalControl, Local And Remote), Error

When MOD commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. Exceptions to this rule are:
The Error Descriptor
SDP properties returned in "Configure RTP Connection Point" in 14.2.52.
The applicability of this restriction for text encoding is FFS.

C.8.3	Subtract
Table C.8.3/1: Descriptor used by Command Subtract Request
Descriptors used by Subtract request:
None
Table C.8.3/2: Descriptor used by Command Subtract Reply
Descriptors used by Subtract reply:
None or Statistics
Ctmbits statistics are returned in the Subtract reply when related to a termination with CTM capabilities. Otherwise no statistics are returned.

C.8.4	Move
Table C.8.4/1: Command Move
Move command used:
Yes
Table C.8.4/2: Descriptors used by Move Request
Descriptors used by Move request:
 Events, Signals, Media (LocalControl, Local And Remote), Audit

Table C.8.4/3: Descriptors used by Move Reply
Descriptors used by Move reply:
Media (LocalControl, Local And Remote), Error

When MOVE commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request, with the exception of the Error Descriptor. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. 
The applicability of this restriction for text encoding is FFS.

C.8.5	AuditValue
Table C.8.5: Auditvalue
Audited Properties:
Property Name and Identity
Descriptor 
Termination ID
TerminationState:
- TDM: ALL (indicating 1 TDM group) , individual termination (NOTE2)
- ATM/IP: individual termination 
- Root (MGW Audit)
TerminationState Descriptor

Termination ID
For Packages:
Root
Packages Descriptor (NOTE1)
Termination ID
None (MGW Audit) :
- Root
Audit (empty) Descriptor
Termination ID
IP Realm Availability :
- ipra/* (ROOT)
TerminationState Descriptor
Audited Statistics:
None
Audited Signals:
None
Audited Events:
None
Packages Audit Possible
Yes
NOTE1: 	Support of this capability is optional.
NOTE2: 	Auditing a single termination of a TDM group is an alternative to the wildcarded audit (TDM: ALL) to derive the service state of the TDM group (all the terminations of the TDM group share the same service state).

C.8.6	AuditCapability
Table C.8.6/1: Auditcapability
Audited Properties:
Property Name and Identity
Descriptor

FFS
FFS
Audited Statistics:
None
Audited Signals:
None
Audited Events:
None

Table C.8.6/2: Scoped Auditing
Audited Properties / ContextAttributes used for a scoped audit :
None
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

C.8.7	Notify
Table C.8.7: Descriptors Used Notify
Descriptors used by Notify Request or Reply:
ObservedEvents, Error
NOTE :	The Error Descriptor shall not be used in Notify Request. 

C.8.8	ServiceChange
Table C.8.8/1: ServiceChangeMethods and ServiceChangeReasons sent by MGC: 
Service Change Methods Supported:
ServiceChange Reasons supported:
Restart (NOTE1)
"901 Cold Boot" (Optional)
"902 Warm Boot" (Optional)
Handoff (NOTE 1, NOTE 2)
"903 MGC Directed Change" (Mandatory)
Forced (NOTE1)
"905 Termination Taken Out Of Service" (Optional) 
Graceful (NOTE1)
"905 Termination Taken Out Of Service" (Optional) 
NOTE: 	When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests.  A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message.	
NOTE1: 	ROOT Only.
NOTE2: 	Not involving more than 1 MSC-S.                  This does not preclude the use of the MGCId in a ServiceChange (Handoff) scenario, nor does it change the expected MG behaviour upon receipt of such a message, as the MGW has actually no means to differentiate whether the ServiceChangeMgcId parameter that may be received in a ServiceChange (handoff) message relates to a logical MGC inside the same MSC server or is part of another MSC-Server.


Table C.8.8/2: ServiceChangeMethods and ServiceChangeReasons sent by MG: 
Service Change Methods Supported:
ServiceChange Reasons supported:
Restart 
"900 Service Restored" (Mandatory)
"901 Cold Boot" (Mandatory) (NOTE1)
"902 Warm Boot" (Mandatory) (NOTE1)
"910 Media Capability Failure " ALL except ROOT (Optional) 
"913 Signal Capability Failure " ALL except ROOT (Optional)"914 Event Capability Failure " ALL except ROOT (Optional)
"916 Packages Change" (Optional)
"917 Capability Change "(Optional)
Graceful 
"904 Termination Malfunction" , ALL except ROOT,(Mandatory)
"905 Termination Taken Out Of Service" , ALL,(Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT,(Mandatory)
"907 Transmission Failure" , ALL except ROOT,(Mandatory)
"908 MG Impending Failure" ROOT only (Mandatory)
Forced
"904 Termination Malfunction", ALL except ROOT (Mandatory)
"905 Termination Taken Out Of Service" , Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT (Mandatory)
"907 Transmission Failure" , ALL except ROOT (Mandatory)
"908 MG Impending Failure" ROOT only (Mandatory)
Handoff (NOTE 1, NOTE 2)
"903 MGC Directed Change" (Mandatory)
Disconnected (NOTE 1)
"900 Service Restored" (Mandatory)
"916 Packages Change" (Optional)
"917 Capability Change" (Optional)
NOTE:	When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests.  A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message.
NOTE 1: 	ROOT Only.
NOTE 2: 	In response to a MGC Ordered Re-Register.

Table C.8.8/3: Service Change Address
ServiceChangeAddress used:
No

Table C.8.8/4: Service Change Delay
ServiceChangeDelay used:
No

Table C.8.8/5: Service Change Incomplete Flag
ServiceChange Incomplete Flag used:
No
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.8.8/6: Service Change Version
Version used in ServiceChangeVersion:
2

Table C.8.8/7: Service Change Profile
ServiceChangeProfile mandatory:
Yes

Table C.8.8/8: Profile negotiation
Profile negotiation as per H.248.18:
No

C.8.9	Manipulating and auditing context attributes
Table C.8.9: Manipulating and auditing context attributes
Context Attributes Manipulated:
Topology, Emergency
Context Attributes Audited:
None

C.9	Generic command syntax and encoding
Table C.9.1: Encodings
Supported Encodings:
Binary (optional) (NOTE 2)
Text (optional) (NOTE 1)
If binary encoding, is indefinite length encoding supported:
Yes (NOTE 3)
NOTE 1:	For a BICC network with IP transport and IPBCP is transported within H.248 messages, text encoding is not recommended to be used on Mc interface until ITU has resolved the contradiction in RFC2327 [34] and H.248.1 [10] on the usage of CR (ASCII carriage return 0x0d) and/or LF (ASCII newline 0x0a) characters e.g. in SDP these Characters are missing when using the currently specified "quotedString" type.
NOTE 2: 	Binary encoding is strongly recommended if only one encoding is selected to ensure interoperability.
NOTE 3: 	The binary encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.690 [41].  Specifically in accordance with ITU-T Recommendation X.690 [41] section 7.3, alternative encodings based on the definite and indefinite form of length are permitted by the basic encoding rules as a sender's option. Receivers shall support both alternatives.

C.10	Transactions 
Table C.10/1: Transactions per Message
Maximum number of TransactionRequests / TransactionReplies / TransResponseAcks / Segment Replies per message:
10

Table C.10/2: Commands per Transaction Requests
Maximum number of commands per TransactionRequest:
Unspecified

Table C.10/3: Commands per Transaction Reply
Maximum number of commands per TransactionReply:
Unspecified
NOTE:	For auditing with wildcarded requests (e.g TDM E1) then the reply may include up to 32 commands to indicate the termination state)

Table C.10/4: Optional Commands
Commands able to be marked "Optional":
ALL

Table C.10/5: Commands for Wildcarded Responses
Wildcarded responses may be requested for:
Modify, Subtract, AuditValue

Table C.10/6: Procedures for Wildcarded Responses
Procedures that make use of wildcarded responses:
Release Bearer, Release Termination, Audit Value
NOTE:	Used when multiple terminations are released with one command and in audit responses where multiple terminations are implied by the audit request. 

Table C.10/7: Transaction Timers
Transaction Timer:
Value
normalMGExecutionTime
Provisioned
normalMGCExecutionTime
Provisioned
MGOriginatedPendingLimit
Provisioned
MGCOriginatedPendingLimit
Provisioned
MGProvisionalResponseTimerValue
Provisioned
MGCProvisionalResponseTimerValue
Provisioned

C.11	Messages
The MGC/MGW shall be named according to the naming structure of the underlying transport protocol which carries the H.248 protocol. 
C.12	Transport
Table C.12/1: Transport
Supported Transports:

1)	For pure IP connections, H.248/SCTP/IP should be used. In addition, to allow for flexible implementations of gateways and controllers in order to offer efficient use of SCTP associations the M3UA layer may also be added on top of SCTP
2)	For pure ATM connections, H.248/MTP3b/SSCF/SSCOP/AAL5/ATM should be used.
3)	For mixed IP&ATM connections, H.248/M3UA/SCTP/IP shall be used as the IP transport.
NOTE1: 	If using SCTP as defined in IETF RFC 2960 [12] the MGW shall always be the node to perform the "Initiation". 
NOTE2:	Checksum calculation for SCTP shall be supported as specified in RFC 3309 [44] instead of the method specified in RFC 2960 [12].

Table C.12/2: Segmentation
Segmentation Supported:
No
NOTE:	This field requires at least version 3 of the H.248.1 protocol.

Table C.12/3: Support of Control Association Monitoring
Control Association Monitoring Supported:
Inherent in Transport
H.248.14 (optional MGW-driven monitoring)
Empty AuditValue on Root (MGC-driven monitoring

C.13	Security
Table C.13: Security
Supported Security:
None

C.14	Packages
Table C.14/1: Mandatory packages 
Mandatory Packages:
Package Name
PackageID
Version
 Generic (see ITU-T Recommendation H.248.1 [10] annex E.1)
 g, (0x0001)
v1
Base Root Package (see ITU-T Recommendation H.248.1 [10] annex E.2)
root, (0x0002)
v2
Tone Detection Package (see ITU-T Recommendation H.248.1 [10] annex E.4)
tonedet, (0x0004)
(NOTE 1)
v1
Basic DTMF Generator Package (see ITU-T Recommendation H.248.1 [10] annex E.5)
dg, (0x0005)
v1
DTMF Detection Package (see ITU-T Recommendation H.248.1 [10] annex E.6)
dd, (0x0006)
v1
Generic Announcement Package (see ITU-T Recommendation H.248.7 [28]) – Fixed Announcements.
an, (0x001d)
v1
TDM Circuit Package (see ITU-T Recommendation H.248.1 [10] annex E.13) 
NOTE 2
tdmc, (0x000d)
v1
Media Gateway Resource Congestion Handling Package (see ITU-T Recommendation H.248.10 [15] )
chp, (0x0029)
v1
Hanging Termination Detection package (see ITU-T Recommendation H.248.36 [36]).
hangterm, (0x0098)
v1
NOTE 1: 	This package is "for extension only" and shall not be published over the Mc interface. 
NOTE 2: 	Network Package is not supported.

Table C.14/2: Optional packages 
Optional Packages:
Package Name
PackageID
Version
Support dependent on:
 Basic Call Progress Tones Generator with Directionality, (see ITU-T Recommendation Q.1950 [23] annex A.8)
 bcg,  (0x0023)
v1
 Services provided by network
Expanded Call Progress tones Generator Package (see ITU-T Recommendation Q.1950 [23] annex A.9)
xcg, (0x0024)
v1
Services provided by network
Basic Services Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.10)
srvtn, (0x0025)
v1
Services provided by network
Bearer Control Tunnelling  Package (see ITU-T Recommendation Q.1950 [23] annex A.7)
Bt, (0x0022)
v1
Interworking with BICC and IP transport
Expanded Services Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.11)
xsrvtn, (0x0026)
v1
Services provided by network
Intrusion Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.12)
Int, (0x0027)
v1
Services provided by network
Business Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.13)
BIZTN, (0x0028)
v1
Services provided by network
Tone Generator Package  (see ITU-T Recommendation H.248.1 [10] annex E.3)
tongen, (0x0003)
v1
(NOTE)
Generic Announcement Package (see ITU-T Recommendation H.248.7 [28]) – Variable Announcements
an, (0x001d)
v1
Variable Announcements
Text Telephony Package (see ITU-T Recommendation H.248.2 [17]).
txp, (0x0010)
v1
Global text telephony support
Call Discrimination package (see ITU-T Recommendation H.248.2 [17]).
ctyp, (0x0011)
v2
Global text telephony support
Basic Continuity Package (see ITU-T Recommendation H.248.1 [10] annex E.10).
ct, (0x000a)
v1
Only required for TDM side terminations
Circuit Switched Data package (see subclause 15.2.1);
threegcsd, (0x0030)
v1
Circuit Switched Data support
TFO package (see subclause 15.2.2);
threegtfoc, (0x0031)
v2
TFO support
3G Expanded Call Progress Tones Generator package (see subclause 15.2.3);
threegxcg, (0x0032)
v1
Services provided by network
Modification of Link Characteristics Bearer Capabiltity package (see subclause 15.2.4);
threegmlc, (0x0046)

v1

Enhanced Circuit Switched Data package (see subclause 15.2.5);
threegcsden,(0x0082)
v1
Circuit Switched Data support
Cellular Text telephone Modem Text Transport package (see subclause 15.2.6);
threegctm, (0x0068)
v1
Global text telephony support
Flexible Tone Generator Package (see subclause 15.2.8).
threegflex, (0x0084)
v1
Services provided by network
Trace Package (see subclause 15.2.9)
calltrace, (0x0097)
v1

ASCI Group call package
(see subclause 15.2.10)
 threegasci, (0x00b2)
v2
VGCS and VBS services supported
IP Domain connection package (see ITU-T Recommendation H.248.41 [42])
ipdc, (0x009d)
v1
Multiple IP realms supported
Inactivity (see ITU-T Recommendation. H248.14 [45])
it, (0x0045)
v1

3GUP (User Plane) package (see subclause 15.1.1)
threegup, (0x002f)
v1
Mandatory for BICC and Iu terminations
Bearer Characteristics Package (see ITU-T Recommendation Q.1950 [23] annex A.3)
bcp, (0x001e)
v2
Mandatory for BICC terminations
Generic Bearer Connection  Package (see ITU-T Recommendation Q.1950 [23] annex A.6)
Gb, (0x0021)
v1
Mandatory only for BICC and Iu terminations
3G Interface Type package (see subclause 15.2.11)
threegint (0x00e3)
v1

RTP Control Protocol Package (ITU-T Recommendation H.248.57 [66])
rtcph. (0x00b5)
v1
Border control functions support
Gate management Source Address/Port Filtering Package (ITU-T Recommendation H.248.43, Clause 7 [67])
gm, (0x008c)
v2
Border control functions support
Traffic management (ITU-T Recommendation H.248.53 [69])
tman, (0x008d)
v1
Border control functions support
Diffserv (ITU-T Recommendation H.248.52 [70])
ds, (0x008b)
v2
Border control functions support
Application Data Inactivity Detection (ITU-T Recommendation H.248.40 [71])
adid (0x009c)
v1
Border control functions support
IP realm availability (ITU-T Recommendation H.248.41  Amendment 1) [72]
ipra (0x00e0)
v1
Border control functions support
NOTE:	This package is "for extension only" and shall not be published over the Mc interface.

Package Usage Information 
This table specifies how the packages above will be used. For example:
-	it lists whether the properties/signals/events/statistics are optional or mandatory
-	if the value of the property/signal/event provisioned the provisioned value should be specified. (e.g. names and number of cycles for an H.248.7 announcement).
Specifies the values of properties which are specified as provisioned 
Package Usage Information:
C.14.1	Generic Package 
Table C.14.1: Package Usage Information For Generic Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-

Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
 Cause (g/cause, 0x0001/0x0001)
M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
General Cause (GeneralCause, 0x0001)
M
"NR" (0x0001) Normal Release 
	"UR" (0x0002) Unavailable Resources 
"FT" (0x0003) Failure, Temporary 
"FP" (0x0004) Failure, Permanent 
"IW" (0x0005) Interworking Error 
"UN" (0x0006) Unsupported 
Not Applicable
Failure Cause (FailureCause, 0x0002)
O
Octet String
Not Applicable
Events
Mandatory/
Optional
Used in command:
Signal Completion. (g/sc, 0x0001/0x0002)
M
ADD, MOD, MOVE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Signal Identity (SIgID , 0x0001)
M
pkgdName syntax 
Not Applicable
Termination Method (Meth,0x0002)
M

"TO" (0x0001) Signal timed out or otherwise completed on its own
"EV" (0x0002) Interrupted by event
"SD" (0x0003) Halted by new Signals descriptor
"NC" (0x0004) Not completed, other cause
Not Applicable
Signal List Id
O
Integer
Not Applicable
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.2	Base Root Package
Table C.14.2: Package Usage Information For Base Root Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
MaxNrOfContexts (root/maxNumberOfContexts, 0x0002/0x0001)
O
Not used in command
1 and up
Not Applicable
MaxTerminationsPerContext (root/maxTerminationPerContext, 0x0002/0x0002)
O
Not used in command
See C.4
Not Applicable
normalMGExecutionTime (root/normalMGExecutionTime, 0x0002/0x0003)
O
Not used in command
Integer
Operator Defined
normalMGCExecutionTime (root/normalMGCExecutionTime, 0x0002/0x0004)
O
Not used in command
Integer
Operator Defined
MGProvisionalResponsetimerValue (root/MGProvisionalResponseTimerValue, 0x0002/0x0005)
O
Not used in command
Integer (initially NormalMGExecutionTime + networkdelay)
Operator Defined
MGCProvisionalResponseTimerValue (root/MGCProvisionalResponseTimerValue, 0x0002/0x0006)
O
Not used in command
Integer (initially NormalMGCExecutionTime + networkdelay)
Operator Defined
MGCOriginatedPendingLimit (root/MGCOriginatedPendingLimit, 0x0002/0x0007)
O
Not used in command
Integer
Operator Defined
MGOriginatedPendingLimit (root/MGOriginatedPendingLimit, 0x0002/0x0008)
O
Not used in command
Integer
Operator Defined
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.3	Tone Generator Package
Table C.14.3: Package Usage Information For Tone Generator Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
 Play Tone (tonegen/pt,0x0003/0x0001)
Not Used
-
-
 Signal Parameters
 Mandatory/
Optional
 Supported
Values:
 Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
- 
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.4	Tone Detection Package
Table C.14.4: Package Usage Information For Tone Detection Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Start tone detected (tonedet/std, 0x0004/0x0001)
O
ADD, MOD, MOVE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Tone ID List (tl,0x0001)
M
wildcard
Not Applicable
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Tone ID (tid,0x0003)
M
Value 

Not Applicable
Events
Mandatory/
Optional
Used in command:
End Tone detected (tonedet/etd, 0x0004/0x0002)
M
ADD, MOD, MOVE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Tone ID List (tl,0x0001)
M
wildcard
Not Applicable
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Tone ID (tid,0x0003)
M
Value
Not Applicable
Duration (dur,0x0002)

O
Value
Not Applicable
Events
Mandatory/
Optional
Used in command:
Long Tone detected (tonedet/ltd, 0x0004/0x0003)
Not Used
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.5	Basic DTMF Generator Package
Table C.14.5: Package Usage Information For Basic DTMF Generator Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
DTMF character 0
(dg/d0,0x0005/0x0010) 
DTMF character 1
(dg/d1,0x0005/0x0011) 
DTMF character 2
(dg/d2,0x0005/0x0012) 
DTMF character 3
(dg/d3,0x0005/0x0013) 
DTMF character 4
(dg/d4,0x0005/0x0014) 
DTMF character 5
(dg/d5,0x0005/0x0015) 
DTMF character 6
(dg/d6,0x0005/0x0016)
DTMF character 7
(dg/d7,0x0005/0x0017) 
DTMF character 8
(dg/d8,0x0005/0x0018)
DTMF character 9
(dg/d9,0x0005/0x0019)
DTMF character *
(dg/ds,0x0005/0x0020) 
DTMF character #
(dg/do,0x0005/0x0021) 
DTMF character A
(dg/da,0x0005/0x001a) 
DTMF character B
(dg/db,0x0005/0x001b)
DTMF character C
(dg/dc,0x0005/0x001c)
DTMF character D
(dg/dd,0x0005/0x001d) 
M
ADD, MOD, MOVE

Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
None
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.6	Basic DTMF Detection Package
Table C.14.6: Package Usage Information For Basic DTMF Generator Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
DTMF character 0
(dd/d0,0x0006/0x0010) 
DTMF character 1
(dd/d1,0x0006/0x0011) 
DTMF character 2
(dd/d2,0x0006/0x0012) 
DTMF character 3
(dd/d3,0x0006/0x0013) 
DTMF character 4
(dd/d4,0x0006/0x0014) 
DTMF character 5
(dd/d5,0x0006/0x0015) 
DTMF character 6
(dd/d6,0x0006/0x0016)
DTMF character 7
(dd/d7,0x0006/0x0017) 
DTMF character 8
(dd/d8,0x0006/0x0018)
DTMF character 9
(dd/d9,0x0006/0x0019)
DTMF character *
(dd/ds,0x0006/0x0020) 
DTMF character #
(dd/do,0x0006/0x0021) 
DTMF character A
(dd/da,0x0006/0x001a) 
DTMF character B
(dd/db,0x0006/0x001b)
DTMF character C
(dd/dc,0x0006/0x001c)
DTMF character D
(dd/dd,0x0006/0x001d)
M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
Events
Mandatory/
Optional
Used in command:
DigitMap Completion Event
(dd/ce,0x0006/0x0004) 

Not used
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.7	Continuity Package
Table C.14.7: Package Usage Information For Basic Continuity Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Continuity Test (ct/ct, 0x000a/0x0003)
Respond 
(ct/rsp, 0x000a/0x0004)
M
ADD, MOD, MOVE
Default
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
None
-
-
-
Events
Mandatory/
Optional
Used in command:
Completion, (ct/cmp, 0x000a/0x0005)
M
ADD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Result (res,0x0008)
M
success, failure
Not Applicable
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.8	TDM Circuit Package
Table C.14.8: Package Usage Information For TDM Circuit Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Echo Cancellation (tdmc/ec,0x000d/0x0008)
M
ADD, MOD, MOVE
ALL 
Default=off (False)
Gain Control (tdmc/gain,0x000d/0x000a)
Not Used
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.9	Text Telephony Package
Table C.14.9: Package Usage Information For Text Telephony Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Conversation mode (txp/convmode, 0x0010/0x0001)
O
ADD, MOD, MOVE 
ALL 
 None
Communication Mode (txp/commode, 0x0010/0x0002)
O
ADD, MOD, MOVE 
ALL 
None 
Connection Mode (txp/connmode, 0x0010/0x0003)
O
ADD, MOD, MOVE 
ALL 
None 
Action at Loss of Connection (txp/lossconnection, 0x0010/0x0006)
O
ADD, MOD, MOVE 
ALL 
None 
V18 Options (txp/v18opt, 0x0010/0x0007)

O
ADD, MOD, MOVE 
ALL 
None 
Character Set (txp/characterset, 0x0010/0x0008)

O
ADD, MOD, MOVE 
ALL 
None 
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Connection Mode Changed (txp/connchng, 0x0010/0x0001)
O 
ADD, MOD, MOVE, NOTIFY 
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Communication Mode (commode, 0x0002)
O
As property commode
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
Number of Characters Transferred (txp/chartrans, 0x0010/0x0001)
O
SUBTRACT

Number of Alternating Turns (txp/altturns, 0x0010/0x0002)
O
SUBTRACT

Error Codes
Mandatory/ Optional
None
-

C.14.10	Call Discrimination Package
Table C.14.10: Package Usage Information For Call Discrimination Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Call Types  (ctyp/calltyp, 0x0011/0x0001)
O
ADD, MOD, MOVE
ALL
None
Text Call Types (ctyp/ttyp, 0x0011/0x0002)
O
ADD, MOD, MOVE
ALL
None
V8bis Support (ctyp/v8bsup, 0x0011/0x0003)
O
ADD, MOD, MOVE
ALL
None
Probe Message  (ctyp/probemsg, 0x0011/0x0004)
O
ADD, MOD, MOVE
ALL
None
Probe Order (ctyp/probeorder, 0x0011/0x0005)
O
ADD, MOD, MOVE
ALL
None
Phase Reversal Detect  (ctyp/phrevdet, 0x0011/0x0006)
O
ADD, MOD, MOVE
ALL
None
MG Responsible for Call Discrimination Signalling (ctyp/MGCallSig, 0x0011/0x0007)
O
ADD, MOD, MOVE
ALL
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
V8 Signal (ctyp/v8sig, 0x0011/0x0001)
O
MOD
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
V.8 Signal Type (ctyp/v8styp, 0x0011/0x0001)
O
ALL
-
V8Sig Cont (ctyp/v8scont, 0x0011/0x0002)
O
ALL
-
V18 XCI Enable (ctyp/v18xcien, 0x0011/0x0003)
O
ALL
-
Answer Signal (ctyp/ans, 0x0011/0x0002)
O
MOD
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
ANS Type (ctyp/AnsType, 0x0011/0x0001)
O
ALL
-
Calling Signal (ctyp/callsig, 0x0011/0x0003)
O
MOD
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
Call Signal Name (ctyp/csn, 0x0011/0x0001)
O
ALL
-
V8bis Signal
O
MOD
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
V8bisSigname (ctyp/V8bsn, 0x0011/0x0001)
O
ALL
-
V8bis Signal Contents (ctyp/V8bscont, 0x0011/0x0002)
O
ALL
-
V18 Probe (ctyp/v18prob, 0x0011/0x0005)
O
MOD
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
None
-
-
-
Events
Mandatory/
Optional
Used in command:
Discriminating Tone Detected (ctyp/dtone, 0x0011/0x0001)
O
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Discriminating Tone Type (dtt,0x0001)
O

ALL
-
Discriminating Tone Value (dtvalue, 0x0002)
O
ALL
-
V8bis Type (v8bist, 0x0003)
O
ALL
-
Call Type Discrimination Result (ctyp/calldisres, 0x0011/0x0002)
O
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Discriminated Call Type (dct,0x0001)
O
ALL
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.11	Announcement Package
Table C.14.11: Package Usage Information For Announcement Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Fixed Announcement Play (an/apf, 0x001d/0x0001)
M
ADD, MOD, MOVE

Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Announcement name (an,0x0001)
M
enumeration
Not Applicable
Number Of Cycles (noc,0x0002)
M
Any Integer
-
Announcement Variant (av,0x0003)
O
string
-
Number 
(num,0x0004)
O
integer
-
Specific parameters interpretation 
 (spi, 0x0005)
O
enumeration
-
Specific parameters  (sp,0x0006)
O
string
-
Announcement Direction 
(di,0x0006)
M
Internal, External
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.12	Media Gateway Resource Congestion handling Package
Table C.14.12: Package Usage Information For Media Gateway Resource Congestion handling Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
MGCon (chp/mgcon, 0x0029/0x0001)
M
MOD, NOTIFY 
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Reduction (reduction,0x0001)
M
0-100
Not Applicable
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.13	Hanging Termination Detection Package
Table C.14.13: Package Usage Information For Hanging Termination Detection Package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Termination Heartbeat (hangterm/thb, 0x0098/0x0001)

M
ADD, MOD, MOVE, AUDITVALUE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Timer X (timerx,0x0001)
M
ALL
0 (no heartbeat message)
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.14	Bearer Characteristics Package
Table C.14.14: Package Usage Information For Bearer Characteristics Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
 BNC Characteristics (BCP/BNCChar,0x001e/0x01)
M
ADD
AAL type 2 / IP/RTP 
Not Applicable
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.15	Generic Bearer Connection Package
Table C.14.15: Package Usage Information For Generic Bearer Connection Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Establish BNC (GB/EstBNC, 0x0021/0x01)
M
ADD, MOD
Not Applicable
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Not Applicable
-
-
Not Applicable
Modify BNC (GB/ModBNC, 0x0021/0x02)
O
MOD
Not Applicable
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Not Applicable
-
-
Not Applicable
 Release BNC (GB/RelBNC, 0x0021/0x03)
 M (NOTE)
MOD
Not Applicable
 Signal Parameters
 Mandatory/
Optional
 Supported
Values:
 Duration Provisioned Value:
 General cause (Generalcause,0x01)
O
 Normal Release/ Unavailable Resources/ Failure Temporary/ Failure Permanent/  Interworking Error/ Unsupported 
Not Applicable
Failure Cause (Failurecause,0x02)
O
OCTET STRING
Not Applicable
Reset (Reset,0x03)
O
0/ 1
Not Applicable
Events
Mandatory/
Optional
Used in command:
BNC Change (GB/BNCChange, 0x0021/0x01)
M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Type (Type ,0x01)
M
Bearer Established / Bearer Modified/ Bearer Mofification Failure
Not Applicable
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Type (Type,0x01)
M
Bearer Established / Bearer Modified/ Bearer Mofification Failure 
Not Applicable
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-
NOTE: 	Mandatory for BICC ATM Terminations. If received as part of a wildcarded command including other types of terminations then for other type of terminations no action is required from MGW, but a successful command reply.

C.14.16	Bearer Control Tunnelling Package 
Table C.14.16: Package Usage Information For Bearer Control Tunnelling Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Tunneling Options (BT/TunOpt, 0x0022/0x01)
M
ADD
1 /2
Not Applicable
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Bearer Information Transport (BT/BIT, 0x0022/0x01)
M
ADD, MOD
Not Applicable
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Bearer Information Tunnel (BIT,0x01)
M
Octet String
Not Applicable
Events
Mandatory/
Optional
Used in command:
Tunnel Indication (BT/TIND, 0x0022/0x01)
M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Not applicable
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Bearer Information transport (BIT,0x01)
M
Octet String
Not Applicable
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.17	Basic Call Progress Tones Generator with Directionality
Table C.14.17: Package Usage Information For Basic Call Progress Tones Generator with Directionality Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Dial Tone (bcg/bdt, 0x0023/0x0040)
Ringing Tone (bcg/brt,0x0023/0x0041)
Busy Tone (bcg/bbt,0x0023/0x0042)
Congestion Tone (bcg/bct,0x0023/0x0043)
Special Information Tone (bcg/bsit,0x0023/0x0044)
Warning Tone (bcg/bwt,0x0023/0x0045)
Payphone Recognition Tone (bcg/bpt,0x0023/0x0046)  Call Waiting Tone (bcg/bcw,0x0023/0x0047)
Caller Waiting Tone (bcg/bcr, 0x0023/0x0048)
Pay Tone (bcg/bpy, 0x0023/0x0049)
O
ADD, MOD, MOVE
Value
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Tone Direction (btd, 0x0001) 
M
Internal / External
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.18	Expanded Call Progress Tones Generator Package
Table C.14.18: Package Usage Information For Expanded Call Progress Tones Generator Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Comfort Tone (xcg/cmft,0x0024/0x004a)
Off-hook warning Tone (xcg/roh, 0x0024/0x004b)
Negative Acknowledgement (xcg/nack,0x0024/0x004c)
Vacant Number Tone (xcg/vac, 0x0024/0x004d)
Special Conditions Dial Tone (xcg/spec,0x0024/0x004e) 
O
ADD, MOD, MOVE
Value
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Tone Direction (btd, 0x0001) 
M
Internal / External 
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.19	Basic Services Tones Generation Package
Table C.14.19: Package Usage Information For Basic Services Tones Generation Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Recall Dial Tone (srvtn/rdt,0x0025/0x004f)
Confirmation Tone (srvtn/conf,0x0025/0x0050)
Held Tone (srvtn/ht,0x0025/0x0051)
Message Waiting Tone (srvtn/mwt,0x0025/0x0052)

O
ADD, MOD, MOVE
Value
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Tone Direction (btd, 0x0001) 
M
Internal / External 
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.20	Expanded Services Tones Generation Package 
Table C.14.20: Package Usage Information For Expanded Services Tones Generation Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
 None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Call Transfer Dial Tone (xsrvtn/xferdt,0x0026/0x0053)
Call Forward Tone (xsrvtn/cft,0x0026/0x0054)
Credit Card service Tone (xsrvtn/ccst,0x0026/0x0055)
Special Recall Dial Tone (xsrvtn/srdt,0x0026/0x0056)

O
ADD, MOD, MOVE
Value
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Tone Direction (btd, 0x0001) 
M
Internal / External 
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.21	Intrusion Tones Generation Package 
Table C.14.21: Package Usage Information For Intrusion Tones Generation Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Intrusion Pending Tone (int/pend,0x0027/0x0057)
Intrusion Tone (int/int,0x0027/0x0058)
Intrusion Reminder Tone (int/rem,0x0027/0x0059)
Toll Break-In Tone (int/tbi,0x0027/0x005a)
Intrusion Queue Tone (int/intque,0x0027/0x005b)
Busy Verification Tone (int/bv,0x0027/0x005c)

O
ADD, MOD, MOVE
Value
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Tone Direction (btd, 0x0001) 
M
Internal / External 
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.22	Business Tones Generation Package 
Table C.14.22: Package Usage Information For Business Tones Generation Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Off-Hook Queuing Tone (biztn/ofque,0x0028/0x005d)
Expensive Route Warning Tone (biztn/erwt,0x0028/0x005e)
Distinctive Dial Tone (biztn/ddt,0x0028/0x005f)
Internal Dial Tone (biztn/idt,0x0028/0x0060)

O
ADD, MOD, MOVE
Value
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Tone Direction (btd, 0x0001) 
M
Internal / External 
Default=External
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.23	3GUP Package 
Table C.14.23: Package Usage Information For 3GUP Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
UP Mode of operation (threegup/mode, 0x002f/0x0001) 
M
ADD, MOD, MOVE
ALL
Default=1 (transparent)
UP versions (threegup/ upversions, 0x002f/0x0002)
M
ADD, MOD, MOVE
1, 2
Default = 1
Delivery of erroneous SDUs (threegup/ delerrsdu, 0x002f/0x0003)
M
ADD, MOD, MOVE
ALL
Default = 3 (NA)
Interface (threegup/ interface, 0x002f/0x0004)
M
ADD, MOD, MOVE
ALL
None
Initialisation Direction (threegup/ initdir, 0x002f/0x0005)
M
ADD, MOD, MOVE
ALL
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None 
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None 
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None 
-
-
-
Error Codes
Mandatory/ Optional
None 
-

C.14.24	Modification of Link Characteristics Bearer Capability
Table C.14.24: Package Usage Information For Modification of Link Characteristics Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None 
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Bearer Modification Support Event.( threegmlc/ mod_link_supp, 0x0046/0x0001) 
M
ADD, MOD, MOVE  NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None 
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None 
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None 
-
-
-
Error Codes
Mandatory/ Optional
None 
-

C.14.25	TFO package 
Table C.14.25: Package Usage Information For TFO
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
TFO Activity Control 
(threegtfoc /tfoenable, (0x0031/0x0001)
M
ADD, MOD, MOVE
ALL
None  (default =Off)
TFO Codec List
(threegtfoc / codeclist, (0x0031/0x0002)
M
ADD, MOD, MOVE
See 3GPP TS 29.232 §15.2.2
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Optimal Codec Event
(threegtfoc / codec_modify, (0x0031/0x0010)
O
ADD, MOD, MOVE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None



ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Optimal Codec Type (optimalcodec 0x0011)
M
See 3GPP TS 29.232 §15.2.2
None
Codec List Event
(threegtfoc /distant_codec_list, (0x0031/0x0012)
O
ADD, MOD, MOVE,NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None



ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Distant Codec List (distlist 0x0013)
M
See 3GPP TS 29.232 §15.2.2
None
TFO Status Event 
(threegtfoc /
TFO_status) (0x0031/0x0014)
O
ADD, MOD, MOVE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
TFO Status (tfo_status 0x0015)
M
ALL
None
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional

-

C.14.26	Circuit Switched Data package 
Table C.14.26: Package Usage Information For CSD
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
PLMNBC (threegcsd /plmnbc, 0x0030/0x0001)
M
ADD, MOD, MOVE
Specified in the subclause "Bearer capability" in 3GPP TS 24.008 [3].
None
GSM Channel Coding (threegcsd / gsmchancod, 0x0030/0x0002)
M
ADD, MOD, MOVE
The second octet of Chosen Channel as specified in the subclause "Chosen Channel" in 3GPP TS 48.008 [9].
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Activate Protocol
(threegcsd/ actprot, 0x0030/0x0001)
M
MOD
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Local Peer Role (Localpeer 0x0001)
O
ALL
None
Events
Mandatory/
Optional
Used in command:
Protocol Negotiation Result (threegcsd / protres, (0x0030/0x0001)
 M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Negotiation Result (result 0x0001)
M
ALL
None
Possible Failure Cause (cause 0x0002)
O
ALL
None
Rate Change (threegcsd / ratechg, (0x0030/0x0002)
 M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
New Rate (rate 0x0001)
M
2400, 4800, 9600, 14400, 28800, 57600
None
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.27	Enhanced Circuit Switched Data package 
Table C.14.27: Package Usage Information For Enhanced CSD
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Bitrate (threegcsden /bitrate, 0x0082/0x0003)
 M
ADD, MOD, MOVE
2400, 4800, 9600, 14400, 28800, 57600, 64000
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.28	3G Expanded Call Progress Tones package 
Table C.14.28: Package Usage Information For 3G Expanded Call Progress Tones
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None




Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
CAMEL Prepaid Warning Tone (threegxcg/cpwt, 0x0032/0x004f)
M
ADD, MOD, MOVE
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
ToneDirection(td, 0x0010)
M
Ext, Int
Default=Ext
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:

-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.29	Cellular Text Telephone Modem Text Transport Package
Table C.14.29: Package Usage Information For CTM
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Termination connection state(threegctm/ connstate, 0x0068/0x0001)
 M
ADD, MOD, MOVE
ALL 

Text Transport (threegctm/ trpt (0x0068/0x0002
M
ADD, MOD, MOVE
CTM

Text Protocol Version (threegctm/ textproto 0x0068/0x0003)
M
ADD, MOD, MOVE
ALL 
Default=1
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
--
-
Events
Mandatory/
Optional
Used in command:
Connection State Change (threegctm/ connchange 0x0068/0x0001)

M
ADD, MOD, MOVE, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Connchng
M
As property connstate
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
Number of Characters Transferred (threegctm/ chartrans 0x0068/0x0001)
M
SUB 

Error Codes
Mandatory/ Optional
None
-

C.14.30	Void
C.14.31	Flexible Tone Generator package
Table C.14.31: Package Usage Information For Flexible Tone Generator
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
Flexible Tone (threegflex/ft, 0x0084/0x0050)
M
ADD, MOD, MOVE
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
Burst list direction(bld, 0x0001)
M
Int, Ext
Default=Ext

NumberOfBursts (nob, 0x0002)
M
1-3
Default = 1

BurstInterval (bi, 0x0003)
M
1-1200
Default = 2

numberOfTonesInBurst  (notib 0x0004)
M
1-3
Default=3

toneDuration (td 0x0005)
M
1-20
Default=2

toneInterval (ti 0x0006)
M
1-20
Default=2
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.32	Trace Package
Table C.14.32: Package Usage Information For Trace Package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
 Trace Activity Control (calltrace/traceactivityrequest,
0x0097/0x0001)
M
ADD, MOD
Trace Session is activated in MGW / 
Trace Session is deactivated in MGW 
Not Applicable
 IMSI (calltrace/imsi,
0x0097/0x0002)
M
ADD, MOD
Octet string 
Not Applicable
 IMEI(SV)  (calltrace/imei_sv,
0x0097/0x0003)
M
ADD, MOD
Octet string
Not Applicable
 Trace Reference  (calltrace/tracereference,
0x0097/0x0004)
M
ADD, MOD
Octet string
Not Applicable
 Trace Recording Session Reference  (calltrace/tracerecsessionref,
0x0097/0x0005)
M
ADD, MOD
Octet string
Not Applicable
 Trace Depth  (calltrace/tracedepth,
0x0097/0x0006)
M
ADD, MOD
Octet string
Not Applicable
 Triggering Events  (calltrace/triggeringevent,
0x0097/0x0007)
M
ADD, MOD
Octet string
Not Applicable
 List of interfaces  (calltrace/listofinterfaces,
0x0097/0x0008)
M
ADD, MOD
Octet string
Not Applicable
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Trace result 
(calltrace/tracact,
0x0097/0x0001)
M
ADD, MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
TraceActivation Result (res,0x0001)
M
Trace Succesfully activated/ Failure in trace activation
Not Applicable
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.33	ASCI Group call
Table C.14.33: Package usage information for ASCI Group Call package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
Number of needed conferenceterminations
 (threegasci/nct, 0x00b2/0x0001)
M
ADD
upto 32
None
Number of desired listener context terminations
(threegasci/nlct, 0x00b2/0x0002)
O
ADD
upto 32
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.34	IP domain connection
Table C.14.34: Package usage information for IP domain connection package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
IP Realm Identifier 
 (ipdc /realm, 0x009d /0x0001)
M
ADD
String
Operator Defined (NOTE)
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported Values:
Duration 
Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-
NOTE: 	A default IP realm may be configured such that if the MGW has not received the IP realm identifier and the MGW supports multiple IP realms then the default IP realm shall be used.

C.14.35	Inactivity Timer Package
Table C.14.35: Package Usage Information for Inactivity Timer package
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
None
-
-
-
-
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
Inactivity Timeout (it/ito, 0x0045/0x0001)

M
MOD, NOTIFY
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
Maximum Inactivity Time (mit,0x0001)
M
Any integer
unspecified
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
None
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None
-
-
-
Error Codes
Mandatory/ Optional
None
-

C.14.36	3G Interface Type package 
Table C.14.36: Package Usage Information for 3G Interface Type package 
Properties 
Mandatory/
Optional
Used in command:
Supported Values:
Provisioned Value:
IP interface type, (threegint/ipint, 0x00e3/0x0001)
M
ADD, MOD
"NboIP" (0x0001)
"AoIP" (0x0002)
"MboIP" (0x0003)
"ExtSIPI" (0x0004)
NOTE
None
Signals 
Mandatory/
Optional
Used in command:
Duration Provisioned Value:
None 
-
-
-
Signal Parameters
Mandatory/
Optional
Supported
Values:
Duration Provisioned Value:
-
-
-
-
Events
Mandatory/
Optional
Used in command:
None 
-
-
Event
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
ObservedEvent
Parameters
Mandatory/
Optional
Supported
Values:
Provisioned Value:
-
-
-
-
Statistics
Mandatory/
Optional
Used in command:
Supported Values:
None 
-
-
-
Error Codes
Mandatory/ Optional
None 
-
NOTE: 	Other values reserved

C.14.37	Differentiated Services (ds)
Table C.14.37: Differentiated Services package
Properties Mandatory/OptionalUsed in commandSupported ValuesProvisioned ValueDifferentiated Services Code Point 
(ds/dscp,0x008b/0x0001)
M
ADD, MODIFY
ALL
Yes 
Tagging Behaviour
(ds/tb, 0x008b/0x0002)
O
ADD, MODIFY
ALL
Yes
Signals
Mandatory/Optional
Used in command
Duration Provisioned Value
None
-
-
-
Signal ParametersMandatory/OptionalSupported ValuesDuration Provisioned Value-
-
-
-
Events
Mandatory/Optional
Used in command
None
-
-
Event ParametersMandatory/OptionalSupported ValuesProvisioned Value-
-
-
-
ObservedEvent
ParametersMandatory/OptionalSupported ValuesProvisioned Value-
-
-
-
Statistics
Mandatory/Optional
Used in command
Supported Values
None
-
-
-
Error Codes
Mandatory/Optional
None
-


C.14.38	Gate Management (gm)
Table C.14.38: Gate Management Package
Properties Mandatory/OptionalUsed in commandSupported ValuesProvisioned ValueRemote Source Address Filtering (gm/saf,0x008c/0x0001)
M
ADD, MODIFY
ALL
Not Applicable

Remote Source Address Mask (gm/sam,0x008c/0x0002)
O
ADD, MODIFY
ALL
Not Applicable
Remote Source Port Filtering (gm/spf,0x008c/0x0003)
M
ADD, MODIFY
ALL
Not Applicable

Remote Source Port (gm/spr,0x008c/0x0004)
O
ADD, MODIFY
ALL
Not Applicable
Explicit Source Address Setting (gm/esas,0x008c/0x0005)
Not Supported
NONE
-
-
Local Source Address (gm/lsa,0x008c/0x0006)
Not Supported
NONE
-
-
Explicit Source Port Setting (gm/esps,0x008c/0x0007)
Not Supported
NONE
-
-
Local Source Port 
(gm/lsp,0x008c/0x0008)
Not Supported
NONE
-
-
Remote Source Port Range (gm/sprr,0x008c/0x000A)
O 

ADD, MODIFY
ALL
Not Applicable





Signals
Mandatory/Optional
Used in command
Duration Provisioned Value
None
-
-
-
Signal ParametersMandatory/
OptionalSupported
ValuesDuration Provisioned Value-
-
-
-
Events
Mandatory/Optional
Used in command
None
-
-
Event ParametersMandatory/
OptionalSupported
ValuesProvisioned Value-
-
-
-
ObservedEvent
ParametersMandatory/
OptionalSupported
ValuesProvisioned Value-
-
-
-
Statistics
Mandatory/Optional
Used in command
Supported Values
Discarded Packets
(gm/dp,0x008c/0x0001)
Not Supported
None
-
Error Codes
Mandatory/Optional
None
-
NOTE :	This package extends RTP Control Protocol package (ITU-T Recommendation H.248.57 [66]) and thus inherits RTCP Allocation Specific Behaviour property (rsb). 


C.14.39	Traffic management (tman)
Table C.14.39: Traffic Management Package
PropertiesMandatory/OptionalUsed in commandSupported ValuesProvisioned ValuePolicing (tman/pol, 0x008d/0x0005)
M
ADD, MODIFY
ALL
Not Applicable
Peak Data Rate 
(tman/pdr, 0x008d/0x0001)
O
ADD, MODIFY
ALL
Not Applicable
Delay Variation Tolerance 
(tman/dvt, 0x008d/0x0004)
O
ADD, MODIFY
ALL
ANY
Sustainable Data Rate 
(tman/sdr, 0x008d/0x0002)
M
ADD, MODIFY
ALL
Not Applicable
Maximum burst size 
(tman/mbs, 0x008d/0x0003)
M
ADD, MODIFY
ALL
Not Applicable
Signals
Mandatory/Optional
Used in command
Duration Provisioned Value
None
-
-
-
Signal ParametersMandatory/OptionalSupported ValuesDuration Provisioned Value-
-
-
-
Events
Mandatory/Optional
Used in command
None
-
-
Event ParametersMandatory/OptionalSupported ValuesProvisioned Value-
-
-
-
ObservedEvent
ParametersMandatory/OptionalSupported ValuesProvisioned Value-
-
-
-
Statistics
Mandatory/Optional
Used in command
Supported Values
None
-
-
-
Error Codes
Mandatory/Optional
None
-
NOTE: 	The data rate shall be calculated using the packet size from IP layer upwards. The Token Bucket method as described by ITU-T Recommendation H.248.53 [69] sub-clause 9.4.3 (as per IETF RFC 2216 [73]) shall be followed where SDR = "r" and MBS = "b" (i.e. the additional "M" value does not apply).

C.14.40	IP Realm Availability (ipra)
Table C.14.40: IP Realm Availability Package
Properties Mandatory/OptionalUsed in commandSupported ValuesProvisioned ValueAvailable Realms, (ipra/ar, 0x00e0/0x0001)
M
AUDITVALUE
ALL
Not Applicable
Signals 
Mandatory/Optional
Used in command
Duration Provisioned Value
None
-
-
-
Signal ParametersMandatory/OptionalSupported ValuesDuration Provisioned Value-
-
-
-
Events
Mandatory/Optional
Used in command
Available Realms Changed, (ipra/arc, 0x00e0/0x001)
M
MODIFY,  NOTIFY
Event ParametersMandatory/OptionalSupported
Values:Provisioned Value-
-
-
-
ObservedEvent
ParametersMandatory/OptionalSupported ValuesProvisioned ValueNewly Available Realms (nar, 0x0001)
M
ALL
Not applicable
Newly Unavailable Realms (nur, 0x0002)
M
ALL
Not applicable
Statistics
Mandatory/Optional
Used in command
Supported Values
None
-
-
-
Error Codes
Mandatory/Optional
None
-

C.14.41	RTCP Handling Package (rtcph)
Table C.14.41: RTCP Handling Package
Properties Mandatory/OptionalUsed in commandSupported ValuesProvisioned ValueRTCP Allocation Specific Behaviour (rtcph/rsb,0x00b5/0x0009)

M
ADD, MODIFY
ALL
OFF 

Signals
Mandatory/Optional
Used in command
Duration Provisioned Value
None
-
-
-
Signal ParametersMandatory/
OptionalSupported
ValuesDuration Provisioned Value-
-
-
-
Events
Mandatory/Optional
Used in command
None
-
-
Event ParametersMandatory/
OptionalSupported
ValuesProvisioned Value-
-
-
-
ObservedEvent
ParametersMandatory/
OptionalSupported
ValuesProvisioned Value-
-
-
-
Statistics
Mandatory/Optional
Used in command
Supported Values
None
-
- 
-
Error Codes
Mandatory/Optional
None
-


C.14.42	Application Data Inactivity Detection (adid)
Table C.14.42: Application Data Inactivity Detection package
Properties Mandatory/OptionalUsed in commandSupported ValuesProvisioned ValueNone
-
-
-
-

Signals
Mandatory/Optional
Used in command
Duration Provisioned Value
None
-
-
-
Signal ParametersMandatory/
OptionalSupported
ValuesDuration Provisioned Value-
-
-
-
Events
Mandatory/Optional
Used in command
IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001)
M
ADD, MODIFY, NOTIFY
Event ParametersMandatory/
OptionalSupported
ValuesProvisioned ValueDetection time (dt,0x0001)
M
ALL
Yes
Direction (dir, 0x002)
M
ALL
Yes
ObservedEvent
ParametersMandatory/
OptionalSupported
ValuesProvisioned Value-
-
-
-
Statistics
Mandatory/Optional
Used in command
Supported Values
None
-
- 
-
Error Codes
Mandatory/Optional
None
-

C.15	Mandatory support of SDP and Annex C information elements 
Mandatory support of SDP and Annex C information elements shall be in accordance with subclause 11.
Table C.15: Mandatory Annex C and SDP information elements
Information Element
Annex C Support
SDP Support 
Bearer Service Characteristics
TMR

ISDN BC
USI
NOTE 1:	 When text encoding is used, all the Information Elements shall be supported via their corresponding SDP parameters, as specified in subclause 11. Annex C SDP equivalents shall not be used.


C.16	Optional support of SDP and Annex C information elements 
Table C.16: Optional Annex C and SDP information elements
Information Element
Annex C Support
SDP Support 
v-line
"SDP_V "
As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1)
m-line
"SDP_M "
As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1)
c-line
"SDP_C "
As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1)
a-line
"SDP_A "
As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) (NOTE 7)
b-line
"SDP_B "
As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) (NOTE 8)


o-line

"SDP_O"
As in 3GPP TS 29.332 [51], clause A.15
s-line

"SDP_S"
The session name (s=) line contains a single field:
s= .


The MG  shall return the value received from the MGC or if there is no s-line sent by the MGC, the MG shall populate this line as follows:
- "s=-"  (NOTE 1)
Codec
Acodec 
Mandatory for BICC and Iu terminations. (NOTE 2)
BNC-Id
BIR (NOTE 3)
Mandatory for BICC-ATM (NOTE 2)
BIWF_Address
NSAP (NOTE 4)
Mandatory for BICC-ATM (NOTE 2)
Iu IP Address
IPv4
IPv6
As defined in ITU‑T Recommendation H.248.1 [10] C6. Mandatory for Iu termination with IP transport (NOTE 5)
Iu IP Port
Port
As defined in ITU‑T Recommendation H.248.1 [10] C6. Mandatory for Iu termination with IP transport (NOTE 6)

NOTE 1: 	If the procedures Reserve RTP Connection Point, Configure RTP Connection Point, Reserve and Configure RTP Connection Point are supported, these properties shall be supported. 
NOTE 2: 	When text encoding is used, all the Information Elements shall be supported via their corresponding SDP parameters, as specified in subclause 11. Annex C SDP equivalents shall not be used.
NOTE 3:	The BIR length shall be fixed at 4 Octets.
NOTE 4:	The NSAP length shall be fixed at 20 Octets. The content of the RNC Transport Address or BIWF Address depends on the used transport interface but the principle is that NSAP format is used. See 3GPP TS 25.414 [21] for RNC and for core network see 3GPP TS 29.414 [32]. For IP the IANA ICP IDI format of the NSAP addressing format as specified in X.213 [33] shall be used.  For Ipv4 networks the IPv4 format recommended by X.213 shall be adopted.
NOTE 5: 	The value is mapped to/from the first 4(or 16) octets of the IPv4 (or IPv6) address part of the Transport Layer Address in 3GPP TS 25.413 [20].
NOTE 6: 	The value is mapped to/from the Binding ID in the RANAP IE Iu transport Association, 3GPP TS 25.413 [20].
NOTE 7:	For the RTP Payload for Redundant Audio Data, the encoding name with "red" and "fmtp" attributes shall be provided to indicate the redundancy level and shall always be signalled in conjunction with the CLEARMODE Payload type as described in 10.2.3.5.2. No other Payload types are currently defined for use with the Redundant RTP Payload.
NOTE 8:   For RTP flows, where RTCP resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the MGC may also supply additional RTCP bandwidth modifiers (i.e. RR and RS, see IETF RFC 3556 [52]). The AS bandwidth value will include the bandwidth used by RTP. In the absence of the RTCP bandwidth modifiers, the MGW shall allow an additional 5% of the AS bandwidth value for the bandwidth for RTCP, in accordance with IETF RFC 3556 [52].

Annex D (informative):
Change history
Change history
DateTSG #TSG Doc.CRRevSubject/CommentOldNewSep 2000Initial draft created after N4#4 based on N4-0006200.0.10.1.0Oct 2000Updated after N4 R2000 Ad Hoc Stockholm based on N4-00823 and N4-000842 0.1.00.2.0Nov 2000Reference for MTP 3B corrected; RFC reference for SCTP added0.2.00.3.0Nov 2000Updated according to N4‑000996, N4‑000998, N4‑000999, N4‑001000, N4‑001021, N4‑001028 & N4‑001097 as agreed in CN4 #50.3.01.0.0Nov 2000CN#10To TSG-CN Plenary #10 for information1.0.01.1.0Jan 2001Updated according to NJ‑010069, NJ‑010030, NJ‑010098, NJ‑010094, NJ‑010033, NJ‑010097, NJ‑010095, NJ‑010112 as agreed in the Joint CN3/CN4 Meeting held during the CN4#61.1.01.1.1Jan 2001References ordered by specification/recommendation number; references to 3GPP specifications include full titles as shown on the title page; literal reference numbers and references to subclauses replaced with fields; all table cells outlined with 0.5pt lines; appropriate 3GPP paragraph styles applied.1.1.11.2.0Feb 2001Updated according to N4‑010245, N4‑010248, N4‑010249, N4‑010303, N4‑010304, N4‑010305, agreed in CN4 Release 4 ad hoc, Madrid.
References to Q.1902.x replaced by references to 29.205; 3GPP styles applied consistently; form for ITU-T recommendations in text is now "ITU‑T Recommendation A.NNNN".1.2.01.3.0Mar 2001Updated according to N4‑010384, N4‑010401 (part) & N4‑010472, agreed in CN4 in Sophia Antipolis.
References to Q.1950, Q.1970 and Q.1990 replaced by reference to 29.205. Reference to SIP-T deleted. Editor's note in 15.1.2.3 deleted.
Editorial clean-up.1.3.02.0.0Mar 2001Sent to TSG CN#11 for approval2.0.02.1.0Mar 2001CN#11References updated after comments in TSG CN #11
Approved in CN#112.1.04.0.0Jun 2001CN#12NP-01028411Text encoding of codec information on Mc interface4.0.04.1.0Jun 2001CN#12NP-01028442ATM-IP signalling transport Interworking4.0.04.1.0Jun 2001CN#12NP-01028451Alignment of Procedure names to TS 23.205 and Q.19504.0.04.1.0Jun 2001CN#12NP-01028463Clarifications in 3GUP package4.0.04.1.0Jun 2001CN#12NP-01028471Clarification of Use of UP version property in 3GUP package4.0.04.1.0Jun 2001CN#12NP-01028481Updates to UP Relay Function, Appendix A4.0.04.1.0Sep 2001CN#13Editorial clean up4.1.04.2.0Sep 2001CN#13NP-010452009Addition of package numbers allocated by IANA4.1.04.2.0Sep 2001CN#13NP-0104520101Mc signalling transport in IP environment4.1.04.2.0Dec 2001CN#14NP-0106190111Inclusion of H.248 Annex L, "Error Codes and Service Change Reason Description"4.2.04.3.0Dec 2001CN#14NP-010619012Removal of the Reuse Idle Package4.2.04.3.0Dec 2001CN#14NP-010619014Correction of Release Procedures4.2.04.3.0Dec 2001CN#14NP-010619015Clarification Of Use Of 3GUP package For PCM4.2.04.3.0Dec 2001CN#14NP-010619016Corrections to ABNF coding of PackageIDs4.2.04.3.0Dec 2001CN#14NP-010619017Correction of BICC packages4.2.04.3.0Dec 2001CN#14NP-0106190201Correction of 3GUP package sub-list type4.2.04.3.0Dec 2001CN#14NP-0106310131Introduction of MGW Congestion Handling4.3.05.0.0Dec 2001CN#14NP-0106310192Maintenance locking of MG4.3.05.0.0Jan 2002A coverdheet fixed5.0.05.0.1Mar 2002CN#15NP-0200290252Naming convention for TDM resources5.0.15.1.0Mar 2002CN#15NP-0200290272Correction of Bearer Modification Handling5.0.15.1.0Jun 2002CN#16NP-0202600301GTT enhancement on Mc5.1.05.2.0Jun 2002CN#16NP-020260032Update to TFO package to explicitly reference TS 26.103 for 3GPP codecs5.1.05.2.0Jun 2002CN#16NP-0202600332CTM Text Transport package5.1.05.2.0Jun 2002CN#16NP-020260034Allow the usage of logical port5.1.05.2.0Jun 2002CN#16NP-020249036Correction subclause 14.1.6 of 3GPP TS 29.3325.1.05.2.0Sep 2002CN#17NP-0204590371Misalignment between TS 23.226 and TS 29.232 for Global Text Telephony5.2.05.3.0Sep 2002CN#17NP-0204590381Alignment of text in TS 29.232 for Global Text Telephony5.2.05.3.0Sep 2002CN#17NP-0204590391Alignment between prepare bearer and reserve bearer in TS 29.232 for Global Text Telephony.5.2.05.3.0Sep 2002CN#17NP-0204630441Missing Properties For Circuit Switched Data Calls5.2.05.3.0Dec 2002CN#18NP-0205790412Termination ID Correction5.3.05.4.0Dec 2002CN#18NP-0205970423New Procedures/Package for handling IP transport for Iu interface5.3.05.4.0Dec 2002CN#18NP-0205780462Updates to support Codec Modification5.3.05.4.0Dec 2002CN#18NP-0205940522CAMEL4 flexible tone package5.3.05.4.0Mar 2003CN#19NP-030108053Update to 3GUP – clarification of IuUP Initialisation handling5.4.05.5.0Mar 2003CN#19NP-0301080541Update to 3GUP – addition of reference to SDU format definition for Nb interface5.4.05.5.0Jun 2003CN#20NP-0302110571Alignment of references after renumbering of H248 by ITU-T5.5.05.6.0Jun 2003CN#20NP-030211059Clarification of handling of DTMF in split architecture – DTMF timing5.5.05.6.0Mar 2004CN#23NP-040052061Addition of Package Id for CTM5.6.05.7.0Mar 2004Addition of Package Ids allocated by IANA (0082 - 0084)5.6.05.7.0Sep 2004CN#25NP-040392063Correction of Procedure "Activate Voice Processing Function"5.7.05.8.0Sep 2004CN#25NP-04041807523GUP package corrections5.7.05.8.0Sep 2004CN#25NP-040418064Provisioning Of Base Root package properties5.7.05.8.0Sep 2004CN#25NP-040418065Service Change Address5.7.05.8.0Sep 2004CN#25NP-040418066Use Of Event Buffers5.7.05.8.0Sep 2004CN#25NP-040418067Digit Maps5.7.05.8.0Sep 2004CN#25NP-040418068IP secured transport5.7.05.8.0Sep 2004CN#25NP-040418074Termination Restoration5.7.05.8.0Sep 2004CN#25NP-0403920721Use Of Statistics5.7.05.8.0Dec 2004CN#26NP-040521078Correction of distant codec list5.8.05.9.0Dec 2004CN#26NP-040528079IP transport package Duplicate property ID in ASN.1 encoding5.8.05.9.0Dec 2004CN#26NP-0405290801H.248 Scope5.8.05.9.0Dec 2004CN#26NP-0405290811Q.1950 reference5.8.05.9.0Dec 2004CN#26NP-040529082Emdedded events5.8.05.9.0Dec 2004CN#26NP-040529084Multiple streams5.8.05.9.0Dec 2004CN#26NP-0405290851Overspec/underspec parameters5.8.05.9.0Dec 2004CN#26NP-0405290882Procedures and Commands – removal of unwanted commands5.8.05.9.0Dec 2004CN#26NP-040547092Update of referenced H.248.1 version to version 25.9.06.0.0Mar 2005CN#27NP-0500570607Addition of the trace package6.0.06.1.0NP-0500291011Requirements for support of H.248 packagesNP-0500291041Completion of specification of UMTS PackagesNP-050036106Correction of implied option for Embedded Signals and EventsNP-0500361082Removal of the ‘Test’ ServiceStates value from the TerminationState DescriptorNP-0500361111Removal of the usage of the ContextAttributeAuditReq constructNP-050036113Removal of the Multiplex descriptorNP-050036115Removal of the Modem descriptorNP-0501331204Requirements for support of proceduresNP-0500341222Procedure for Emergency Call IndicationNP-050036128Removal of the Error Descriptor usage in NotifyRequestNP-050036130Updating incomplete parameter definition for MGW Resource congestion handling proceduresNP-050055131Removal of Signals on ROOTNP-050055132Removal of usage of Stream ID in Topology descriptorNP-050055133H.248.1 version contradictionNP-050036135Directionality of tones and announcementsNP-0500361381New ‘TFO status’ eventNP-0500281391TFO procedure clarificationNP-0500281421TFO activation without TFO Codec ListNP-0500361481Commands on ROOTNP-0500361491Use Of Audit ValueNP-050036151Service Change Reasons Not supportedNP-0500361551Descriptors in command repliesNP-0500361571Introduction of formal profile name for Mc interfaceNP-050036158Service Change for Failover not defined for Mc InterfaceNP-050029161Removal Of VPF typeNP-050029164Alignment of TFO Actvation Procedure and associated parametersNP-0500551652Continuity TestJun 2005CT#28CP-0502361841BNC Cut-Through Capability Package Removed6.1.06.2.0CP-0502361871Format of IP addressCP-0501011882Profile Registration Mandatory/Negotiation ClarificationCP-0502361961Clarification of Maintenance ProceduresCP-0502361981Clarification of Use Of Topology and MultipartyCP-050236200Removal of Option in Prepare Bearer that the MGW can chose the BNC CharacteristicsCP-0502362021Clarification Of Use of WildcardingCP-0500802092Text encoding of IPBCP for IP transport on Mc interfaceCP-0500802122Definition of requirement for support of commandsCP-0502382131Correction to Profile registration proceduresSep 2005CT#29CP-0504352181Codec IE and Codec List on the Mc interface6.2.06.3.0CP-050290224Value range for BIR/NSAPCP-050290229Clarification of ‘extended only’ packagesCP-050290231Correction to Prepare IP Transport procedureCP-0502902331Wildcarding of Release ProceduresCP-050290235Clarification to use of local peer for CSDCP-0502802382Correction to clarify use of FAX and Channel Mode ModifyCP-0502902421Clarification to use of PLMN-BC, GSM-Chanel Coding for CSDCP-0502902441Clarification to use of Init Dir parameterCP-0502902461Clarification to Termination Restoration and Termination Out Of ServiceCP-050290248Remove provisioning of Resource Congestion EventCP-050290250Remove Priority propertyCP-050290252Notifications for IP Bearer EstablishmentCP-0502902541Clarification for Use of Stream Mode Property with AnnouncementsCP-050290256Removal of Stream Mode LoopbackCP-050290258Correction to IPBCP Tunnel ProceduresCP-050290263Exclusion of use of Signal ID Play Tone for DTMFCP-0502902651Miscellaneous Open Mc correctionsCP-0503082661Use of Individual Audit TokenCP-0504382681Restriction of Service Change Address in MGW RestrictionCP-050308271Removal of BNC-cut-through-capability from Prepare Bearer procedureCP-050308272Updating Mc interface profile "threegbicsn" to version 2CP-050290276Defining a default value for "Echo cancelling" propertyCP-0503092781Correction on Burst interval durationCP-0503082811Clarification of "Normal Release" parameterDec 2005CT#30CP-05060302612Correction to clarify TFO Package use6.3.06.4.0CP-05060702881Clarification to client/server behaviour with regards to SCTP InitiationCP-05060702891Inclusion of Error Code #449 for unsupported parameter valueCP-05061802901Correction to Continuity Test ProcedureCP-05060702961Setting of CN/Outgoing Nb termination prior to bearer establishmentCP-05060703042Correction to use of BITRATE for CSD callsCP-05060703081Bearer Released Event to Reserve Circuit procedureCP-05060703221Corrections to use of GSM-Channel Coding for CSDCP-05061803233Correct MCC Error in implementing CR #2382005-12CT#30CP-05062903022Clean-up of hanging contexts and terminations6.4.07.0.0CP-05062903091Clarification of MGW capability change2006-03CT#31CP-06007803072Clarification of Termination Restoration and Termination Out-of-Service procedures7.0.07.1.0CP-06006403262Correction To Termination State HandlingCP-06006403291Send Tone procedureCP-06006403301ContextID in Change Flow Direction responseCP-06006403331Correction To DTMF DetectionCP-06007803371Clarification to use of ServiceChangeMGCIdCP-0600780338Clarification to cut-through procedureCP-06006403452Adding missing termination ID to Acknowledgement part of notification proceduresCP-06007803421Correction to syntax for event descriptionsCP-0600640348Adding missing Codec, Bearer Characteristics and Bearer Service Characteristics to Prepare IP transport procedureCP-06006703521Correction on the used descriptor for trace package2006-06CT#32CP-06031503772Introduction of Profile Description Annex to Mc interface7.1.07.2.0CP-0603150379Corrections to Formats and  Codes tableCP-06031503821Clarification of H.248.2 version in referencesCP-0603150386Correction of the error definition of FlextoneCP-0603070370Corrigendum for H.248.1 version 2CP-06030103652DTMF Detection TypeCP-06030103681Sequential Signal ListsCP-06030103742Multimedia & CSD callsCP-06030103851Clarification of ROOT termination naming2006-09CT#33CP-06041103881Profile Description Annex: Connection model and Context Attributes7.2.07.3.0CP-06041103892Profile Description Annex: TerminationsCP-06041103902Profile Description Annex: DescriptorsCP-06041103911Profile Description Annex: Message, Transport and SecurityCP-06041103921Profile Description Annex: Mandatory and optional packagesCP-06041103932Profile Description Annex: H.248 packagesCP-06041103942Profile Description Annex: BICC packagesCP-06041103952Profile Description Annex: Mandatory and optional 3G packagesCP-06041103961Profile Description Annex : Command APICP-06041103971Profile Description Annex : Generic command syntax and encodingCP-06041103981Profile Description Annex : TransactionsCP-06041103991Profile Description Annex : Mandatory support of SDP and Annex C information elementsCP-06041104001Profile Description Annex : Optional support of SDP and Annex C information elementsCP-0604110401Encoding of G.711 codecCP-06040004043Profile registration procedureCP-06041104072Definition of the use of mandatory and optional in Mc Profile TemplateCP-0604020409Trace Package IDCP-0604000412AuditValue procedureCP-06040004151Use of topology for tones and announcementsCP-0603970420Modification of eventId named distant codec_list in threegtfoc packageCP-0604020427Wildcarding of Release Termination ResponseCP-0604000430Correction to Emergency Call Indication ProcedureCP-06040004361Use of IPSec for Mc InterfaceCP-06040004392Correction to use of Local Peer for CSD when Anchor MGWCP-06041104412New Error Code for Temporary BusyCP-06041104421Profile Description Annex: Descriptors (complements)CP-0604110443Profile Description Annex: Trace packageCP-0604020447Incomplete list of optional UMTS packages2006-12CT#34CP-06056903766Enhancements for VGCS/VBS in SPLIT architecture7.3.07.4.0CP-0605690452Correct the initiator of NOT.resp commandCP-06056904741Removal of TBD for Number of Commands Per TransactionCP-06056904851Event Tunnel indication for type BICC IPCP-0605690486Tunnel Option shall be used with Add.Req onlyCP-0605690487IP transport package properties not used within Mov.ReqCP-0605520459Encoding of PLMN BCCP-06056104611Trace package correctionCP-0605540464Commands in Change flow direction procedureCP-06071804813Definite vs Indefinite encoding rules for binary H.2482007-03CT#35CP-07001404903IP domain connection indication7.4.07.5.0CP-0700140491Commands Marked OptionalCP-07001404941Prevention of signalling overload due to NotificationsCP-0700090497Exclusion of use of inherited properties from network packageCP-07001404981Changing Profile description Annex C from Informative to NormativeCP-07000905011Signal List ID to Announcement Completed procedureCP-07001405081Stream ID parameters in Signals and Events2007-06CT#36CP-07031405111IMSI/IMEI encoding in trace package7.5.07.6.0CP-0703220512Adding package ID to ASCI packageCP-0703220513ServiceChangeMGCId parameterCP-0703080520RFC 3309 for SCTP checksumCP-0703220522Modification to EventID name difinition2007-09CT#37CP-07053005243Service Change Methods and Reasons7.6.07.7.0CP-0705300527H.248 Message EncodingCP-07053005281General Corrections To ProfileCP-07053005312Mc profile correctionsCP-07053005352Support inactivity timer (H.248.14) for MGWs detecting the failure of MGCCP-07053005371Completion of Text Telephony and Call Discrimination Packages2007-09CT#37CP-07056905363Mandatory use termination heartbeat (H.248.36) when establish bearer/prepare bearer7.7.08.0.02007-10Track marks removed8.0.08.0.12007-12CT#38CP-07075205382Mc enhancements for SIP-I support8.0.18.1.0CP-07075605391Examples for Usage of the 3GUP Package "Initialization Direction" PropertyCP-07075605411Optional reporting of normal AAL2 bearer releaseCP-07075605561Individual audit of TDM terminationCP-0707490545Heartbeat event in Send Tone and Play Announcement proceduresCP-07074905511Event Descriptor correction in Mc profileCP-0707490553Reference correctionsCP-07074905551Number of needed listener context terminations to ASCI packageCP-07074005491Sequencing of Termination Out-of-Service and Termination Restoration procedures2008-03CT#39CP-08002005571Reserve / Configure  RTP Connection Point, Modify Bearer Characteristics8.1.08.2.0CP-08002005581Other codecs for SIP-I based NcCP-08001105621BNC events in Prepare Bearer / Establish Bearer proceduresCP-0800250564CAMEL prepaid warning tone missing from formats and codes tableCP-08002005751Applicability of descriptors to RTP terminations2008-06CT#40CP-0802700585Coding of the UDP Port Property8.2.08.3.0CP-08026905811Use of Release Bearer ProcedureCP-08027105761Correction of the inconsistencies in several procedures’ descriptionCP-08026405772A interface over IP supportCP-08026205781Addition of SIP-I based Nc within the scope of TS 29.2322008-09CT#41CP-08046605913IP interface type indicator8.3.08.4.0CP-08046605921Use of Global Text Telephony with A over IPCP-0804660593Use of ‘plmnbc’ and ‘gsm channel coding’ in AoIPCP-08046105941Expansion of  scope for IMS Centralised Service AccessCP-0804660599Support of GSM codecCP-0804680601CTM properties settingCP-08046606041Emergency Call Indication for AoIP and SIP-I terminationsCP-0804530608Service Change Reason in (G)MSC Server Out of Service2008-12CT#42CP-08068606101SDP Media Parameters For RTP Terminations8.4.08.5.0CP-08070506111IP transport package properties handlingCP-08069706122No_Data frame handling independent of Stream Mode propertyCP-0807050613Adding package ID to 3G Interface Type package06172Support of Redundancy for CSD in Mc interface for AoIP06181CTM transport property in the Reserve and Configure RTP connection Point procedure0621IP interface type for external SIP-I based network2009-03CT#43CP-0900340622Solving Incorrect references8.5.08.6.00623Removing of IP transport package from packages chapter of Mc profile2009-06CT#44CP-09029706241Missing Signalling Object in Formats and Codes table8.6.08.7.02009-09CT#45CP-0905410625Clarification of Use of Reserve and Configure RTP Connection Point8.7.08.8.0CP-09054106261Missing RTP procedures from Circuit Switched Data packge descriptionCP-0905440627Audit of Hanging Termination Detection package2009-12CT#46CP-0907630628Commands Using IP Interface Type8.8.08.9.02009-12CT#46Upgraded unchanged from Rel-88.9.09.0.02010-04History table corrected9.0.09.0.12011-03CT#51CP-11010006291Adding CS-Ix functionalities to Mc-profile9.0.19.1.02011-09CT#53CP-1105630638Media inactivity notification procedure9.1.09.2.0




















 STYLEREF ZA 3GPP TS 29.232 V9.2.0 (2011-09)
 PAGE 5
 STYLEREF ZGSM Release 9


3GPP