ts_127007v110800p

Recommendations

Info

3GPP TS 27.007 version 11.8.0 Release 11 275 ETSI TS 127 007 V11.8.0 (2013-10) The communication client in the MT shall take into account SDP a-line rtpmap and fmtp attributes when negotiating media. Which other attributes in media level SDP a-lines are taken into account by the communication client is implementation specific. Partial SDP m-lines include nothing but a media type. For every media either an SDP m-line or a partial SDP m-line must be provided. SDP m-lines indicate that the described media is encoded/decoded outside the MT. Partial SDP m-lines indicate that the described media is encoded/decoded by the MT. When negotiating media the MT adds payload information to the partial SDP m-line. The communication client in the MT shall use the provided SDP line information when negotiating media. The communication client shall add other SDP lines required for negotiating media. Example: +CDEFMP=,"m=audio%x0D%x0Am=video 98%x0D%x0Aa=rtpmap:98 L16/16000/2" Implementation Optional. 13.2.5 Control and modify media description +CCMMD Table 13.2.5-1: +CCMMD parameter command syntax Command +CCMMD=,[,] Possible response(s) +CCMMD +CCMMD= Description This command allows control of the media used in a multimedia call. The command can be used to initiate modification of the media of an ongoing call, to accept / reject incoming changes in media or to accept / reject the media for an incoming call. When matches the index of an ongoing call, the TA/MT will attempt to add or remove media to the call by triggering an SDP renegotiation over the SIP protocol. When =1, the set command requests an unconditional change the media of the call to that described by . When =2, the set command proposes a change of media to that described by , to which the remote party has to respond before the media of the call is changed. The response from the remote party will be indicated in a +CMCCSI unsolicited result code. If the remote party accepts the change of media, the value in +CMCCSI will be set to 3. If the remote party rejects the change of media, will be set to 4. In both cases the value in +CMCCSI will describe the currently active media of the call (if any). If the remote party unconditionally changes the media of the call, this will be indicated in a +CMCCSI unsolicited result code, with =1 and containing the updated (and now active) media description. If the remote party proposes to change the media of an ongoing call, this will be indicated in a +CMCCSI unsolicited result code, with =2. The set command should be used to respond to the proposal, either accepting it by setting =3, or rejecting it by setting =4. When the MT receives an incoming call from a remote party, the +CMCCSI unsolicited result code will be sent to the TE with =2. This proposed media for the new call should either be accepted, (as described above) or it should be rejected and a new media should be proposed using the set command with =2. ETSI
3GPP TS 27.007 version 11.8.0 Release 11 276 ETSI TS 127 007 V11.8.0 (2013-10) Defined values : integer type. Call identification number as defined in the +CMCCS and +CLCCS commands. : integer type 1 The parameter describes the desired set of media for the call. 2 The parameter describes a proposal for a new set of media for the call. 3 Accept the most recently received media proposal. The parameter describes the accepted media for the call. 4 Reject the most recently received media proposal. : string type represented with IRA characters. Media description as per the +CDEFMP command. This parameter shall not be subject to conventional character conversion as per +CSCS. Implementation Optional. 13.3 Informative examples Below is an example where a voice call originated with +CDU is placed to a tel-URI. This example outlines how the call is initiated by the AT command +CDU, and how the unsolicited result code +CDUU is used to indicate how the callsetup progress until it is terminated. Both successful and unsuccessful outcome of a call attempt is shown in the example. AT+CDU=1,"tel:+47-123-45678" +CDU: 2 OK (Voice call initiated) (Call initiated, call identification number 2 provided) (Call initiation successful) (Call setup progress, unsolicited result codes appear as appropriate) +CDUU: 2,"ANSWERED" +CDUU: 2,"NO ANSWER" +CDUU: 2,"BUSY" +CDUU: 2,"CONNECTION TERMINATED" AT+CHCCS=2 +CHCCSI: 2 OK (If call is answered by the remote party) (Remote party has answered) (If remote party does not answer) (Connection completion timeout) (If remote party is busy) (Busy signal detected) (If call is terminated from remote party) (Connection terminated from remote party) (If call is terminated from calling party) (Connection with call identification number 2 terminated from calling party) Below is an example where a multimedia-call (voice) originated with +CDU is placed to a SIP-URI. This example outlines how the call is initiated by the AT command +CDU, and how the unsolicited result codes +CDUU and +CMCCSI are used to indicate how the call-setup progress until it is terminated. A precondition for this example is that the basic event for the call monitoring function is successfully enabled with +CMCCS=2. AT+CDU=1,"sip:veronica@university.org" +CDU: 4 OK (Multimedia-call (voice) initiated) (Call initiated, call identification number 4 provided) (Call initiation successful) (+CDUU and +CMCCSI appear as appropriate) +CMCCSI: 4,0,0,0,"",0,2,0,1,0,"sip:veronica@university.org",0,0 +CMCCSI: 4,0,0,0,"",0,3,0,1,0,"sip:veronica@university.org",0,0 +CMCCSI: 4,0,0,0,"",0,4,0,1,0,"sip:veronica@university.org",0,0 (Call setup is started) (Call is in progress) (Alert indication received) CDUU: 4,"ANSWERED" (Remote party answered) ETSI
Page 1 and 2:
ETSI TS 127 007 V11.8.0 (2013-10) T
Page 3 and 4:
3GPP TS 27.007 version 11.8.0 Relea
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226: 3GPP TS 27.007 version 11.8.0 Relea
Page 275: 3GPP TS 27.007 version 11.8.0 Relea
show all

ts_127007v110800p

Create successful ePaper yourself

Delete template?

Save as template?