| 1 |
<pre>Network Working Group A. van Wijk, Ed. |
| 2 |
Request for Comments: 5194 G. Gybels, Ed. |
| 3 |
Category: Informational June 2008 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Framework for Real-Time Text over IP Using</span> |
| 7 |
<span class="h1">the Session Initiation Protocol (SIP)</span> |
| 8 |
|
| 9 |
Status of This Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. It does |
| 12 |
not specify an Internet standard of any kind. Distribution of this |
| 13 |
memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
This document lists the essential requirements for real-time Text- |
| 18 |
over-IP (ToIP) and defines a framework for implementation of all |
| 19 |
required functions based on the Session Initiation Protocol (SIP) and |
| 20 |
the Real-Time Transport Protocol (RTP). This includes interworking |
| 21 |
between Text-over-IP and existing text telephony on the Public |
| 22 |
Switched Telephone Network (PSTN) and other networks. |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">van Wijk & Gybels Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 60 |
<a href="#section-2">2</a>. Scope ...........................................................<a href="#page-4">4</a> |
| 61 |
<a href="#section-3">3</a>. Terminology .....................................................<a href="#page-4">4</a> |
| 62 |
<a href="#section-4">4</a>. Definitions .....................................................<a href="#page-4">4</a> |
| 63 |
<a href="#section-5">5</a>. Requirements ....................................................<a href="#page-6">6</a> |
| 64 |
<a href="#section-5.1">5.1</a>. General Requirements for ToIP ..............................<a href="#page-6">6</a> |
| 65 |
<a href="#section-5.2">5.2</a>. Detailed Requirements for ToIP .............................<a href="#page-8">8</a> |
| 66 |
<a href="#section-5.2.1">5.2.1</a>. Session Setup and Control Requirements ..............<a href="#page-9">9</a> |
| 67 |
<a href="#section-5.2.2">5.2.2</a>. Transport Requirements .............................<a href="#page-10">10</a> |
| 68 |
<a href="#section-5.2.3">5.2.3</a>. Transcoding Service Requirements ...................<a href="#page-10">10</a> |
| 69 |
<a href="#section-5.2.4">5.2.4</a>. Presentation and User Control Requirements .........<a href="#page-11">11</a> |
| 70 |
<a href="#section-5.2.5">5.2.5</a>. Interworking Requirements ..........................<a href="#page-13">13</a> |
| 71 |
<a href="#section-5.2.5.1">5.2.5.1</a>. PSTN Interworking Requirements ............<a href="#page-13">13</a> |
| 72 |
<a href="#section-5.2.5.2">5.2.5.2</a>. Cellular Interworking Requirements ........<a href="#page-14">14</a> |
| 73 |
5.2.5.3. Instant Messaging Interworking |
| 74 |
Requirements ..............................<a href="#page-14">14</a> |
| 75 |
<a href="#section-6">6</a>. Implementation Framework .......................................<a href="#page-15">15</a> |
| 76 |
<a href="#section-6.1">6.1</a>. General Implementation Framework ..........................<a href="#page-15">15</a> |
| 77 |
<a href="#section-6.2">6.2</a>. Detailed Implementation Framework .........................<a href="#page-15">15</a> |
| 78 |
<a href="#section-6.2.1">6.2.1</a>. Session Control and Setup ..........................<a href="#page-15">15</a> |
| 79 |
<a href="#section-6.2.1.1">6.2.1.1</a>. Pre-Session Setup .........................<a href="#page-15">15</a> |
| 80 |
<a href="#section-6.2.1.2">6.2.1.2</a>. Session Negotiations ......................<a href="#page-16">16</a> |
| 81 |
<a href="#section-6.2.2">6.2.2</a>. Transport ..........................................<a href="#page-17">17</a> |
| 82 |
<a href="#section-6.2.3">6.2.3</a>. Transcoding Services ...............................<a href="#page-18">18</a> |
| 83 |
<a href="#section-6.2.4">6.2.4</a>. Presentation and User Control Functions ............<a href="#page-18">18</a> |
| 84 |
<a href="#section-6.2.4.1">6.2.4.1</a>. Progress and Status Information ...........<a href="#page-18">18</a> |
| 85 |
<a href="#section-6.2.4.2">6.2.4.2</a>. Alerting ..................................<a href="#page-18">18</a> |
| 86 |
<a href="#section-6.2.4.3">6.2.4.3</a>. Text Presentation .........................<a href="#page-19">19</a> |
| 87 |
<a href="#section-6.2.4.4">6.2.4.4</a>. File Storage ..............................<a href="#page-19">19</a> |
| 88 |
<a href="#section-6.2.5">6.2.5</a>. Interworking Functions .............................<a href="#page-19">19</a> |
| 89 |
<a href="#section-6.2.5.1">6.2.5.1</a>. PSTN Interworking .........................<a href="#page-20">20</a> |
| 90 |
<a href="#section-6.2.5.2">6.2.5.2</a>. Mobile Interworking .......................<a href="#page-22">22</a> |
| 91 |
<a href="#section-6.2.5.2.1">6.2.5.2.1</a>. Cellular "No-gain" .............<a href="#page-22">22</a> |
| 92 |
6.2.5.2.2. Cellular Text Telephone |
| 93 |
Modem (CTM) ....................<a href="#page-22">22</a> |
| 94 |
<a href="#section-6.2.5.2.3">6.2.5.2.3</a>. Cellular "Baudot mode" .........<a href="#page-22">22</a> |
| 95 |
<a href="#section-6.2.5.2.4">6.2.5.2.4</a>. Mobile Data Channel Mode .......<a href="#page-23">23</a> |
| 96 |
<a href="#section-6.2.5.2.5">6.2.5.2.5</a>. Mobile ToIP ....................<a href="#page-23">23</a> |
| 97 |
<a href="#section-6.2.5.3">6.2.5.3</a>. Instant Messaging Interworking ............<a href="#page-23">23</a> |
| 98 |
<a href="#section-6.2.5.4">6.2.5.4</a>. Multi-Functional Combination Gateways .....<a href="#page-24">24</a> |
| 99 |
<a href="#section-6.2.5.5">6.2.5.5</a>. Character Set Transcoding .................<a href="#page-25">25</a> |
| 100 |
7. Further Recommendations for Implementers and Service |
| 101 |
Providers ......................................................<a href="#page-25">25</a> |
| 102 |
<a href="#section-7.1">7.1</a>. Access to Emergency Services ..............................<a href="#page-25">25</a> |
| 103 |
<a href="#section-7.2">7.2</a>. Home Gateways or Analog Terminal Adapters .................<a href="#page-25">25</a> |
| 104 |
<a href="#section-7.3">7.3</a>. User Mobility .............................................<a href="#page-26">26</a> |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">van Wijk & Gybels Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 111 |
|
| 112 |
|
| 113 |
<a href="#section-7.4">7.4</a>. Firewalls and NATs ........................................<a href="#page-26">26</a> |
| 114 |
<a href="#section-7.5">7.5</a>. Quality of Service ........................................<a href="#page-26">26</a> |
| 115 |
<a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-26">26</a> |
| 116 |
<a href="#section-9">9</a>. Contributors ...................................................<a href="#page-27">27</a> |
| 117 |
<a href="#section-10">10</a>. References ....................................................<a href="#page-27">27</a> |
| 118 |
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-27">27</a> |
| 119 |
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-29">29</a> |
| 120 |
|
| 121 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 122 |
|
| 123 |
For many years, real-time text has been in use as a medium for |
| 124 |
conversational, interactive dialogue between users in a similar way |
| 125 |
to how voice telephony is used. Such interactive text is different |
| 126 |
from messaging and semi-interactive solutions like Instant Messaging |
| 127 |
in that it offers an equivalent conversational experience to users |
| 128 |
who cannot, or do not wish to, use voice. It therefore meets a |
| 129 |
different set of requirements from other text-based solutions already |
| 130 |
available on IP networks. |
| 131 |
|
| 132 |
Traditionally, deaf, hard-of-hearing, and speech-impaired people are |
| 133 |
amongst the most prolific users of real-time, conversational, text |
| 134 |
but, because of its interactivity, it is becoming popular amongst |
| 135 |
mainstream users as well. Real-time text conversation can be |
| 136 |
combined with other conversational media like video or voice. |
| 137 |
|
| 138 |
This document describes how existing IETF protocols can be used to |
| 139 |
implement a Text-over-IP solution (ToIP). Therefore, this document |
| 140 |
describes how to use a set of existing components and protocols and |
| 141 |
provides the requirements and rules for that resulting structure, |
| 142 |
which is why it is called a "framework", fitting commonly accepted |
| 143 |
dictionary definitions of that term. |
| 144 |
|
| 145 |
This ToIP framework is specifically designed to be compatible with |
| 146 |
Voice-over-IP (VoIP), Video-over-IP, and Multimedia-over-IP (MoIP) |
| 147 |
environments. This ToIP framework also builds upon, and is |
| 148 |
compatible with, the high-level user requirements of deaf, hard-of- |
| 149 |
hearing and speech-impaired users as described in <a href="./rfc3351">RFC3351</a> [<a href="#ref-22" title=""User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals"">22</a>]. It |
| 150 |
also meets real-time text requirements of mainstream users. |
| 151 |
|
| 152 |
ToIP also offers an IP equivalent of analog text telephony services |
| 153 |
as used by deaf, hard-of-hearing, speech-impaired, and mainstream |
| 154 |
users. |
| 155 |
|
| 156 |
The Session Initiation Protocol (SIP) [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] is the protocol of choice |
| 157 |
for control of Multimedia communications and Voice-over-IP (VoIP) in |
| 158 |
particular. It offers all the necessary control and signalling |
| 159 |
required for the ToIP framework. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">van Wijk & Gybels Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 167 |
|
| 168 |
|
| 169 |
The Real-Time Transport Protocol (RTP) [<a href="#ref-3" title=""RTP: A Transport Protocol for Real-Time Applications"">3</a>] is the protocol of choice |
| 170 |
for real-time data transmission, and its use for real-time text |
| 171 |
payloads is described in <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>]. |
| 172 |
|
| 173 |
This document defines a framework for ToIP to be used either by |
| 174 |
itself or as part of integrated, multi-media services, including |
| 175 |
Total Conversation [<a href="#ref-5" title=""Multimedia Conversational Services"">5</a>]. |
| 176 |
|
| 177 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Scope</span> |
| 178 |
|
| 179 |
This document defines a framework for the implementation of real-time |
| 180 |
ToIP, either stand-alone or as a part of multimedia services, |
| 181 |
including Total Conversation [<a href="#ref-5" title=""Multimedia Conversational Services"">5</a>]. It provides the: |
| 182 |
|
| 183 |
a. requirements for real-time text; |
| 184 |
|
| 185 |
b. requirements for ToIP interworking; |
| 186 |
|
| 187 |
c. description of ToIP implementation using SIP and RTP; |
| 188 |
|
| 189 |
d. description of ToIP interworking with other text services. |
| 190 |
|
| 191 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span> |
| 192 |
|
| 193 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 194 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 195 |
"OPTIONAL" in this document are to be interpreted as described in <a href="./rfc2119">RFC</a> |
| 196 |
<a href="./rfc2119">2119</a> [<a href="#ref-6" title=""Key words for use in RFCs to Indicate Requirement Levels"">6</a>] and indicate requirement levels for compliant |
| 197 |
implementations. |
| 198 |
|
| 199 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span> |
| 200 |
|
| 201 |
Audio bridging: a function of an audio media bridge server, gateway, |
| 202 |
or relay service that sends to each destination the combination of |
| 203 |
audio from all participants in a conference, excluding the |
| 204 |
participant(s) at that destination. At the RTP level, this is an |
| 205 |
instance of the mixer function as defined in <a href="./rfc3550">RFC 3550</a> [<a href="#ref-3" title=""RTP: A Transport Protocol for Real-Time Applications"">3</a>]. |
| 206 |
|
| 207 |
Cellular: a telecommunication network that has wireless access and |
| 208 |
can support voice and data services over very large geographical |
| 209 |
areas. Also called Mobile. |
| 210 |
|
| 211 |
Full duplex: media is sent independently in both directions. |
| 212 |
|
| 213 |
Half duplex: media can only be sent in one direction at a time, or if |
| 214 |
an attempt to send information in both directions is made, errors may |
| 215 |
be introduced into the presented media. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">van Wijk & Gybels Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 223 |
|
| 224 |
|
| 225 |
Interactive text: another term for real-time text, as defined below. |
| 226 |
|
| 227 |
Real-time text: a term for real-time transmission of text in a |
| 228 |
character-by-character fashion for use in conversational services, |
| 229 |
often as a text equivalent to voice-based conversational services. |
| 230 |
Conversational text is defined in the ITU-T Framework for multimedia |
| 231 |
services, Recommendation F.700 [<a href="#ref-21" title=""Framework Recommendation for Multimedia Services"">21</a>]. |
| 232 |
|
| 233 |
Text gateway: a function that transcodes between different forms of |
| 234 |
text transport methods, e.g., between ToIP in IP networks and Baudot |
| 235 |
or ITU-T V.21 text telephony in the PSTN. |
| 236 |
|
| 237 |
Textphone: also "text telephone". A terminal device that allows |
| 238 |
end-to-end real-time text communication using analog transmission. A |
| 239 |
variety of PSTN textphone protocols exists world-wide. A textphone |
| 240 |
can often be combined with a voice telephone, or include voice |
| 241 |
communication functions for simultaneous or alternating use of text |
| 242 |
and voice in a call. |
| 243 |
|
| 244 |
Text bridging: a function of the text media bridge server, gateway |
| 245 |
(including transcoding gateways), or relay service analogous to that |
| 246 |
of audio bridging as defined above, except that text is the medium of |
| 247 |
conversation. |
| 248 |
|
| 249 |
Text relay service: a third-party or intermediary that enables |
| 250 |
communications between deaf, hard-of-hearing, and speech-impaired |
| 251 |
people and voice telephone users by translating between voice and |
| 252 |
real-time text in a call. |
| 253 |
|
| 254 |
Text telephony: analog textphone service. |
| 255 |
|
| 256 |
Total Conversation: a multimedia service offering real-time |
| 257 |
conversation in video, real-time text and voice according to |
| 258 |
interoperable standards. All media streams flow in real time. (See |
| 259 |
ITU-T F.703, "Multimedia conversational services" [<a href="#ref-5" title=""Multimedia Conversational Services"">5</a>].) |
| 260 |
|
| 261 |
Transcoding service: a service provided by a third-party User Agent |
| 262 |
that transcodes one stream into another. Transcoding can be done by |
| 263 |
human operators, in an automated manner, or by a combination of both |
| 264 |
methods. Within this document, the term particularly applies to |
| 265 |
conversion between different types of media. A text relay service is |
| 266 |
an example of a transcoding service that converts between real-time |
| 267 |
text and audio. |
| 268 |
|
| 269 |
TTY: originally, an abbreviation for "teletype". Often used in North |
| 270 |
America as an alternative designation for a text telephone or |
| 271 |
textphone. Also called TDD, Telecommunication Device for the Deaf. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">van Wijk & Gybels Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 279 |
|
| 280 |
|
| 281 |
Video relay service: a service that enables communications between |
| 282 |
deaf and hard-of-hearing people and hearing persons with voice |
| 283 |
telephones by translating between sign language and spoken language |
| 284 |
in a call. |
| 285 |
|
| 286 |
Acronyms: |
| 287 |
|
| 288 |
2G Second generation cellular (mobile) |
| 289 |
2.5G Enhanced second generation cellular (mobile) |
| 290 |
3G Third generation cellular (mobile) |
| 291 |
ATA Analog Telephone Adaptor |
| 292 |
CDMA Code Division Multiple Access |
| 293 |
CLI Calling Line Identification |
| 294 |
CTM Cellular Text Telephone Modem |
| 295 |
ENUM E.164 number storage in DNS (see <a href="./rfc3761">RFC3761</a>) |
| 296 |
GSM Global System for Mobile Communications |
| 297 |
ISDN Integrated Services Digital Network |
| 298 |
ITU-T International Telecommunications |
| 299 |
Union-Telecommunications Standardisation Sector |
| 300 |
NAT Network Address Translation |
| 301 |
PSTN Public Switched Telephone Network |
| 302 |
RTP Real-Time Transport Protocol |
| 303 |
SDP Session Description Protocol |
| 304 |
SIP Session Initiation Protocol |
| 305 |
SRTP Secure Real Time Transport Protocol |
| 306 |
TDD Telecommunication Device for the Deaf |
| 307 |
TDMA Time Division Multiple Access |
| 308 |
TTY Analog textphone (Teletypewriter) |
| 309 |
ToIP Real-time Text over Internet Protocol |
| 310 |
URI Uniform Resource Identifier |
| 311 |
UTF-8 UCS/Unicode Transformation Format-8 |
| 312 |
VCO/HCO Voice Carry Over/Hearing Carry Over |
| 313 |
VoIP Voice over Internet Protocol |
| 314 |
|
| 315 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Requirements</span> |
| 316 |
|
| 317 |
The framework described in <a href="#section-6">Section 6</a> defines a real-time text-based |
| 318 |
conversational service that is the text equivalent of voice-based |
| 319 |
telephony. This section describes the requirements that the |
| 320 |
framework is designed to meet and the functionality it should offer. |
| 321 |
|
| 322 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. General Requirements for ToIP</span> |
| 323 |
|
| 324 |
Any framework for ToIP must be derived from the requirements of <a href="./rfc3351">RFC</a> |
| 325 |
<a href="./rfc3351">3351</a> [<a href="#ref-22" title=""User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals"">22</a>]. A basic requirement is that it must provide a |
| 326 |
standardized way for offering real-time text-based conversational |
| 327 |
services that can be used as an equivalent to voice telephony by |
| 328 |
deaf, hard-of-hearing, speech-impaired, and mainstream users. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">van Wijk & Gybels Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 335 |
|
| 336 |
|
| 337 |
It is important to understand that real-time text conversations are |
| 338 |
significantly different from other text-based communications like |
| 339 |
email or Instant Messaging. Real-time text conversations deliver an |
| 340 |
equivalent mode to voice conversations by providing transmission of |
| 341 |
text character by character as it is entered, so that the |
| 342 |
conversation can be followed closely and that immediate interaction |
| 343 |
takes place. |
| 344 |
|
| 345 |
Store-and-forward systems like email or messaging on mobile networks, |
| 346 |
or non-streaming systems like instant messaging, are unable to |
| 347 |
provide that functionality. In particular, they do not allow for |
| 348 |
smooth communication through a Text Relay Service. |
| 349 |
|
| 350 |
In order to make ToIP the text equivalent of voice services, ToIP |
| 351 |
needs to offer equivalent features in terms of conversationality to |
| 352 |
those provided by voice. To achieve that, ToIP needs to: |
| 353 |
|
| 354 |
a. offer real-time transport and presentation of the conversation; |
| 355 |
|
| 356 |
b. provide simultaneous transmission in both directions; |
| 357 |
|
| 358 |
c. support both point-to-point and multipoint communication; |
| 359 |
|
| 360 |
d. allow other media, like audio and video, to be used in conjunction |
| 361 |
with ToIP; |
| 362 |
|
| 363 |
e. ensure that the real-time text service is always available. |
| 364 |
|
| 365 |
Real-time text is a useful subset of Total Conversation as defined in |
| 366 |
ITU-T F.703 [<a href="#ref-5" title=""Multimedia Conversational Services"">5</a>]. Total Conversation allows participants to use |
| 367 |
multiple modes of communication during the conversation, either at |
| 368 |
the same time or by switching between modes, e.g., between real-time |
| 369 |
text and audio. |
| 370 |
|
| 371 |
Deaf, hard-of-hearing, and mainstream users may invoke ToIP services |
| 372 |
for many different reasons: |
| 373 |
|
| 374 |
- because they are in a noisy environment, e.g., in a machine room of |
| 375 |
a factory where listening is difficult; |
| 376 |
|
| 377 |
- because they are busy with another call and want to participate in |
| 378 |
two calls at the same time; |
| 379 |
|
| 380 |
- for implementing text and/or speech recording services (e.g., text |
| 381 |
documentation/audio recording) for legal purposes, for clarity, or |
| 382 |
for flexibility; |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">van Wijk & Gybels Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 391 |
|
| 392 |
|
| 393 |
- to overcome language barriers through speech translation and/or |
| 394 |
transcoding services; |
| 395 |
|
| 396 |
- because of hearing loss, deafness, or tinnitus as a result of the |
| 397 |
aging process or for any other reason, creating a need to replace |
| 398 |
or complement voice with real-time text in conversational sessions. |
| 399 |
|
| 400 |
In many of the above examples, real-time text may accompany speech. |
| 401 |
The text could be displayed side by side, or in a manner similar to |
| 402 |
subtitling in broadcasting environments, or in any other suitable |
| 403 |
manner. This could occur with users who are hard of hearing and also |
| 404 |
for mixed media calls with both hearing and deaf people participating |
| 405 |
in the call. |
| 406 |
|
| 407 |
A ToIP user may wish to call another ToIP user, join a conference |
| 408 |
session involving several users, or initiate or join a multimedia |
| 409 |
session, such as a Total Conversation session. |
| 410 |
|
| 411 |
A common scenario for multipoint real-time text is conference calling |
| 412 |
with many participants. Implementers could, for example, use |
| 413 |
different colours to render different participants' text, or could |
| 414 |
create separate windows or rendering areas for each participant. |
| 415 |
|
| 416 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Detailed Requirements for ToIP</span> |
| 417 |
|
| 418 |
The following sections list individual requirements for ToIP. Each |
| 419 |
requirement has been given a unique identifier (R1, R2, etc.). |
| 420 |
<a href="#section-6">Section 6</a> (Implementation Framework) describes how to implement ToIP |
| 421 |
based on these requirements by using existing protocols and |
| 422 |
techniques. |
| 423 |
|
| 424 |
The requirements are organized under the following headings: |
| 425 |
|
| 426 |
- session setup and session control; |
| 427 |
|
| 428 |
- transport; |
| 429 |
|
| 430 |
- use of transcoding services; |
| 431 |
|
| 432 |
- presentation and user control; |
| 433 |
|
| 434 |
- interworking. |
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">van Wijk & Gybels Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Session Setup and Control Requirements</span> |
| 450 |
|
| 451 |
Conversations could be started using a mode other than real-time |
| 452 |
text. Simultaneous or alternating voice and real-time text is used |
| 453 |
by a large number of people who can send voice but must receive text |
| 454 |
(due to a hearing impairment), or who can hear but must send text |
| 455 |
(due to a speech impairment). |
| 456 |
|
| 457 |
R1: It SHOULD be possible to start conversations in any mode (real- |
| 458 |
time text, voice, video) or combination of modes. |
| 459 |
|
| 460 |
R2: It MUST be possible for the users to switch to real-time text, or |
| 461 |
add real-time text as an additional modality, during the |
| 462 |
conversation. |
| 463 |
|
| 464 |
R3: Systems supporting ToIP MUST allow users to select any of the |
| 465 |
supported conversation modes at any time, including in mid- |
| 466 |
conversation. |
| 467 |
|
| 468 |
R4: Systems SHOULD allow the user to specify a preferred mode of |
| 469 |
communication in each direction, with the ability to fall back to |
| 470 |
alternatives that the user has indicated are acceptable. |
| 471 |
|
| 472 |
R5: If the user requests simultaneous use of real-time text and |
| 473 |
audio, and this is not possible because of constraints in the |
| 474 |
network, the system SHOULD try to establish text-only communication |
| 475 |
if that is what the user has specified as his/her preference. |
| 476 |
|
| 477 |
R6: If the user has expressed a preference for real-time text, |
| 478 |
establishment of a connection including real-time text MUST have |
| 479 |
priority over other outcomes of the session setup. |
| 480 |
|
| 481 |
R7: It MUST be possible to use real-time text in conferences both as |
| 482 |
a medium of discussion between individual participants (for example, |
| 483 |
for sidebar discussions in real-time text while listening to the main |
| 484 |
conference audio) and for central support of the conference with |
| 485 |
real-time text interpretation of speech. |
| 486 |
|
| 487 |
R8: Session setup and negotiation of modalities MUST allow users to |
| 488 |
specify the language of the real-time text to be used. (It is |
| 489 |
RECOMMENDED that similar functionality be provided for the video part |
| 490 |
of the conversation, i.e., to specify the sign language being used). |
| 491 |
|
| 492 |
R9: Where certain session services are available for the audio media |
| 493 |
part of a session, these functions MUST also be supported for the |
| 494 |
real-time text media part of the same session. For example, call |
| 495 |
transfer must act on all media in the session. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">van Wijk & Gybels Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Transport Requirements</span> |
| 506 |
|
| 507 |
ToIP will often be used to access a relay service [<a href="#ref-24" title=""Human Factors (HF); Guidelines for Telecommunication Relay Services for Text Telephones"">24</a>], allowing |
| 508 |
real-time text users to communicate with voice users. With relay |
| 509 |
services, as well as in direct user-to-user conversation, it is |
| 510 |
crucial that text characters are sent as soon as possible after they |
| 511 |
are entered. While buffering may be done to improve efficiency, the |
| 512 |
delays SHOULD be kept minimal. In particular, buffering of whole |
| 513 |
lines of text will not meet character delay requirements. |
| 514 |
|
| 515 |
R10: Characters must be transmitted soon after entry of each |
| 516 |
character so that the maximum delay requirement can be met. An end- |
| 517 |
to-end delay time of one second is regarded as good, while users note |
| 518 |
and appreciate shorter delays, down to 300ms. A delay of up to two |
| 519 |
seconds is possible to use. |
| 520 |
|
| 521 |
R11: Real-time text transmission from a terminal SHALL be performed |
| 522 |
character by character as entered, or in small groups of characters, |
| 523 |
so that no character is delayed from entry to transmission by more |
| 524 |
than 300 milliseconds. |
| 525 |
|
| 526 |
R12: It MUST be possible to transmit characters at a rate sufficient |
| 527 |
to support fast human typing as well as speech-to-text methods of |
| 528 |
generating real-time text. A rate of 30 characters per second is |
| 529 |
regarded as sufficient. |
| 530 |
|
| 531 |
R13: A ToIP service MUST be able to deal with international character |
| 532 |
sets. |
| 533 |
|
| 534 |
R14: Where it is possible, loss or corruption of real-time text |
| 535 |
during transport SHOULD be detected and the user should be informed. |
| 536 |
|
| 537 |
R15: Transport of real-time text SHOULD be as robust as possible, so |
| 538 |
as to minimize loss of characters. |
| 539 |
|
| 540 |
R16: It SHOULD be possible to send and receive real-time text |
| 541 |
simultaneously. |
| 542 |
|
| 543 |
<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. Transcoding Service Requirements</span> |
| 544 |
|
| 545 |
If the User Agents of different participants indicate that there is |
| 546 |
an incompatibility between their capabilities to support certain |
| 547 |
media types, e.g., one User Agent only offering T.140 over IP, as |
| 548 |
described in <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>], and the other one only supporting audio, |
| 549 |
the user might want to invoke a transcoding service. |
| 550 |
|
| 551 |
Some users may indicate their preferred modality to be audio while |
| 552 |
others may indicate real-time text. In this case, transcoding |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">van Wijk & Gybels Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 559 |
|
| 560 |
|
| 561 |
services might be needed for text-to-speech (TTS) and speech-to-text |
| 562 |
(STT). Other examples of possible scenarios for including a relay |
| 563 |
service in the conversation are: text bridging after conversion from |
| 564 |
speech, audio bridging after conversion from real-time text, etc. |
| 565 |
|
| 566 |
A number of requirements, motivations, and implementation guidelines |
| 567 |
for relay service invocation can be found in <a href="./rfc3351">RFC 3351</a> [<a href="#ref-22" title=""User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals"">22</a>]. |
| 568 |
|
| 569 |
R17: It MUST be possible for users to invoke a transcoding service |
| 570 |
where such service is available. |
| 571 |
|
| 572 |
R18: It MUST be possible for users to indicate their preferred |
| 573 |
modality (e.g., ToIP). |
| 574 |
|
| 575 |
R19: It MUST be possible to negotiate the requirements for |
| 576 |
transcoding services in real time in the process of setting up a |
| 577 |
call. |
| 578 |
|
| 579 |
R20: It MUST be possible to negotiate the requirements for |
| 580 |
transcoding services in mid-call, for the immediate addition of those |
| 581 |
services to the call. |
| 582 |
|
| 583 |
R21: Communication between the end participants SHOULD continue after |
| 584 |
the addition or removal of a text relay service, and the effect of |
| 585 |
the change should be limited in the users' perception to the direct |
| 586 |
effect of having or not having the transcoding service in the |
| 587 |
connection. |
| 588 |
|
| 589 |
R22: When setting up a session, it MUST be possible for a user to |
| 590 |
specify the type of relay service requested (e.g., speech to text or |
| 591 |
text to speech). The specification of a type of relay SHOULD include |
| 592 |
a language specifier. |
| 593 |
|
| 594 |
R23: It SHOULD be possible to route the session to a preferred relay |
| 595 |
service even if the user invokes the session from another region or |
| 596 |
network than that usually used. |
| 597 |
|
| 598 |
R24: It is RECOMMENDED that ToIP implementations make the invocation |
| 599 |
and use of relay services as easy as possible. |
| 600 |
|
| 601 |
<span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a>. Presentation and User Control Requirements</span> |
| 602 |
|
| 603 |
A user should never be in doubt about the status of the session, even |
| 604 |
if the user is unable to make use of the audio or visual indication. |
| 605 |
For example, tactile indications could be used by deaf-blind |
| 606 |
individuals. |
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">van Wijk & Gybels Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 615 |
|
| 616 |
|
| 617 |
R25: User Agents for ToIP services MUST have alerting methods (e.g., |
| 618 |
for incoming sessions) that can be used by deaf and hard-of-hearing |
| 619 |
people or provide a range of alternative, but equivalent, alerting |
| 620 |
methods that can be selected by all users, regardless of their |
| 621 |
abilities. |
| 622 |
|
| 623 |
R26: Where real-time text is used in conjunction with other media, |
| 624 |
exposure of user control functions through the User Interface needs |
| 625 |
to be done in an equivalent manner for all supported media. For |
| 626 |
example, it must be possible for the user to select between audio, |
| 627 |
visual, or tactile prompts, or all must be supplied. |
| 628 |
|
| 629 |
R27: If available, identification of the originating party (e.g., in |
| 630 |
the form of a URI or a Calling Line Identification (CLI)) MUST be |
| 631 |
clearly presented to the user in a form suitable for the user BEFORE |
| 632 |
the session invitation is answered. |
| 633 |
|
| 634 |
R28: When a session invitation involving ToIP originates from a |
| 635 |
Public Switched Telephone Network (PSTN) text telephone (e.g., |
| 636 |
transcoded via a text gateway), this SHOULD be indicated to the user. |
| 637 |
The ToIP client MAY adjust the presentation of the real-time text to |
| 638 |
the user as a consequence. |
| 639 |
|
| 640 |
R29: An indication SHOULD be given to the user when real-time text is |
| 641 |
available during the call, even if it is not invoked at call setup |
| 642 |
(e.g., when only voice and/or video is used initially). |
| 643 |
|
| 644 |
R30: The user MUST be informed of any change in modalities. |
| 645 |
|
| 646 |
R31: Users MUST be presented with appropriate session progress |
| 647 |
information at all times. |
| 648 |
|
| 649 |
R32: Systems for ToIP SHOULD support an answering machine function, |
| 650 |
equivalent to answering machines on telephony networks. |
| 651 |
|
| 652 |
R33: If an answering machine function is supported, it MUST support |
| 653 |
at least 160 characters for the greeting message. It MUST support |
| 654 |
incoming text message storage of a minimum of 4096 characters, |
| 655 |
although systems MAY support much larger storage. It is RECOMMENDED |
| 656 |
that systems support storage of at least 20 incoming messages of up |
| 657 |
to 16000 characters per message. |
| 658 |
|
| 659 |
R34: When the answering machine is activated, user alerting SHOULD |
| 660 |
still take place. The user SHOULD be allowed to monitor the auto- |
| 661 |
answer progress, and where this is provided, the user SHOULD be |
| 662 |
allowed to intervene during any stage of the answering machine |
| 663 |
procedure and take control of the session. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">van Wijk & Gybels Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 671 |
|
| 672 |
|
| 673 |
R35: It SHOULD be possible to save the text portion of a |
| 674 |
conversation. |
| 675 |
|
| 676 |
R36: The presentation of the conversation SHOULD be done in such a |
| 677 |
way that users can easily identify which party generated any given |
| 678 |
portion of text. |
| 679 |
|
| 680 |
R37: ToIP SHOULD handle characters such as new line, erasure, and |
| 681 |
alerting during a session as specified in ITU-T T.140 [<a href="#ref-8" title=""Protocol for Multimedia Application Text Conversation"">8</a>]. |
| 682 |
|
| 683 |
<span class="h4"><a class="selflink" id="section-5.2.5" href="#section-5.2.5">5.2.5</a>. Interworking Requirements</span> |
| 684 |
|
| 685 |
There is a range of existing real-time text services. There is also |
| 686 |
a range of network technologies that could support real-time text |
| 687 |
services. |
| 688 |
|
| 689 |
Real-time/interactive texting facilities exist already in various |
| 690 |
forms and on various networks. In the PSTN, they are commonly |
| 691 |
referred to as text telephony. |
| 692 |
|
| 693 |
Text gateways are used for converting between different protocols for |
| 694 |
text conversation. They can be used between networks or within |
| 695 |
networks where different transport technologies are used. |
| 696 |
|
| 697 |
R38: ToIP SHOULD provide interoperability with text conversation |
| 698 |
features in other networks, for instance the PSTN. |
| 699 |
|
| 700 |
R39: When communicating via a gateway to other networks and |
| 701 |
protocols, the ToIP service SHOULD support the functionality for |
| 702 |
alternating or simultaneous use of modalities as offered by the |
| 703 |
interworking network. |
| 704 |
|
| 705 |
R40: Calling party identification information, such as CLI, MUST be |
| 706 |
passed by gateways and converted to an appropriate form, if required. |
| 707 |
|
| 708 |
R41: When interworking with other networks and services, the ToIP |
| 709 |
service SHOULD provide buffering mechanisms to deal with delays in |
| 710 |
call setup and with differences in transmission speeds, and/or to |
| 711 |
interwork with half-duplex services. |
| 712 |
|
| 713 |
<span class="h5"><a class="selflink" id="section-5.2.5.1" href="#section-5.2.5.1">5.2.5.1</a>. PSTN Interworking Requirements</span> |
| 714 |
|
| 715 |
Analog text telephony is used in many countries, mainly by deaf, |
| 716 |
hard-of-hearing and speech-impaired individuals. |
| 717 |
|
| 718 |
R42: ToIP services MUST provide interworking with PSTN legacy text |
| 719 |
telephony devices. |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">van Wijk & Gybels Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 727 |
|
| 728 |
|
| 729 |
R43: When interworking with PSTN legacy text telephony services, |
| 730 |
alternating text and voice function MAY be supported. (Called "voice |
| 731 |
carry over (VCO) and hearing carry over (HCO)"). |
| 732 |
|
| 733 |
<span class="h5"><a class="selflink" id="section-5.2.5.2" href="#section-5.2.5.2">5.2.5.2</a>. Cellular Interworking Requirements</span> |
| 734 |
|
| 735 |
As mobile communications have been adopted widely, various solutions |
| 736 |
for real-time texting while on the move were developed. ToIP |
| 737 |
services should provide interworking with such services as well. |
| 738 |
|
| 739 |
Alternative means of transferring the text telephony data have been |
| 740 |
developed when TTY services over cellular were mandated by the FCC in |
| 741 |
the USA. They are the a) "No-gain" codec solution, and b) the |
| 742 |
Cellular Text Telephony Modem (CTM) solution [<a href="#ref-7" title=""Cellular Text Telephone Modem Description"">7</a>], both collectively |
| 743 |
called "Baudot mode" solution in the USA. |
| 744 |
|
| 745 |
The GSM and 3G standards from 3GPP make use of the CTM modem in the |
| 746 |
voice channel for text telephony. However, implementations also |
| 747 |
exist that use the data channel to provide such functionality. |
| 748 |
Interworking with these solutions should be done using text gateways |
| 749 |
that set up the data channel connection at the GSM side and provide |
| 750 |
ToIP at the other side. |
| 751 |
|
| 752 |
R44: a ToIP service SHOULD provide interworking with mobile text |
| 753 |
conversation services. |
| 754 |
|
| 755 |
<span class="h5"><a class="selflink" id="section-5.2.5.3" href="#section-5.2.5.3">5.2.5.3</a>. Instant Messaging Interworking Requirements</span> |
| 756 |
|
| 757 |
Many people use Instant Messaging to communicate via the Internet |
| 758 |
using text. Instant Messaging usually transfers blocks of text |
| 759 |
rather than streaming as is used by ToIP. Usually a specific action |
| 760 |
is required by the user to activate transmission, such as pressing |
| 761 |
the ENTER key or a send button. As such, it is not a replacement for |
| 762 |
ToIP; in particular, it does not meet the needs for real-time |
| 763 |
conversations including those of deaf, hard-of-hearing, and speech- |
| 764 |
impaired users as defined in <a href="./rfc3351">RFC 3351</a> [<a href="#ref-22" title=""User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals"">22</a>]. It is less suitable for |
| 765 |
communications through a relay service [<a href="#ref-24" title=""Human Factors (HF); Guidelines for Telecommunication Relay Services for Text Telephones"">24</a>]. |
| 766 |
|
| 767 |
The streaming nature of ToIP provides a more direct conversational |
| 768 |
user experience and, when given the choice, users may prefer ToIP. |
| 769 |
|
| 770 |
R45: a ToIP service MAY provide interworking with Instant Messaging |
| 771 |
services. |
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">van Wijk & Gybels Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Implementation Framework</span> |
| 786 |
|
| 787 |
This section describes an implementation framework for ToIP that |
| 788 |
meets the requirements and offers the functionality as set out in |
| 789 |
<a href="#section-5">Section 5</a>. The framework presented here uses existing standards that |
| 790 |
are already commonly used for voice-based conversational services on |
| 791 |
IP networks. |
| 792 |
|
| 793 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. General Implementation Framework</span> |
| 794 |
|
| 795 |
This framework specifies the use of the Session Initiation Protocol |
| 796 |
(SIP) [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] to set up, control, and tear down the connections between |
| 797 |
ToIP users whilst the media is transported using the Real-Time |
| 798 |
Transport Protocol (RTP) [<a href="#ref-3" title=""RTP: A Transport Protocol for Real-Time Applications"">3</a>] as described in <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>]. |
| 799 |
|
| 800 |
<a href="./rfc4504">RFC 4504</a> describes how to implement support for real-time text in SIP |
| 801 |
telephony devices [<a href="#ref-23" title=""SIP Telephony Device Requirements and Configuration"">23</a>]. |
| 802 |
|
| 803 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Detailed Implementation Framework</span> |
| 804 |
|
| 805 |
<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Session Control and Setup</span> |
| 806 |
|
| 807 |
ToIP services MUST use the Session Initiation Protocol (SIP) [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] for |
| 808 |
setting up, controlling, and terminating sessions for real-time text |
| 809 |
conversation with one or more participants and possibly including |
| 810 |
other media like video or audio. The Session Description Protocol |
| 811 |
(SDP) used in SIP to describe the session is used to express the |
| 812 |
attributes of the session and to negotiate a set of compatible media |
| 813 |
types. |
| 814 |
|
| 815 |
SIP [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] allows participants to negotiate all media, including real- |
| 816 |
time text conversation [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>]. ToIP services can provide the ability to |
| 817 |
set up conversation sessions from any location as well as provision |
| 818 |
for privacy and security through the application of standard SIP |
| 819 |
techniques. |
| 820 |
|
| 821 |
<span class="h5"><a class="selflink" id="section-6.2.1.1" href="#section-6.2.1.1">6.2.1.1</a>. Pre-Session Setup</span> |
| 822 |
|
| 823 |
The requirements of the user to be reached at a consistent address |
| 824 |
and to store preferences for evaluation at session setup are met by |
| 825 |
pre-session setup actions. That includes storing of registration |
| 826 |
information in the SIP registrar to provide information about how a |
| 827 |
user can be contacted. This will allow sessions to be set up rapidly |
| 828 |
and with proper routing and addressing. |
| 829 |
|
| 830 |
The need to use real-time text as a medium of communications can be |
| 831 |
expressed by users during registration time. Two situations need to |
| 832 |
be considered in the pre-session setup environment: |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">van Wijk & Gybels Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 839 |
|
| 840 |
|
| 841 |
a. User Preferences: It MUST be possible for a user to indicate a |
| 842 |
preference for real-time text by registering that preference with |
| 843 |
a SIP server that is part of the ToIP service. |
| 844 |
|
| 845 |
b. Server Support of User Preferences: SIP servers that support ToIP |
| 846 |
services MUST have the capability to act on calling user |
| 847 |
preferences for real-time text in order to accept or reject the |
| 848 |
session. The actions taken can be based on the called users |
| 849 |
preferences defined as part of the pre-session setup registration. |
| 850 |
For example, if the user is called by another party, and it is |
| 851 |
determined that a transcoding server is needed, the session should |
| 852 |
be re-directed or otherwise handled accordingly. |
| 853 |
|
| 854 |
The ability to include a transcoding service MUST NOT require user |
| 855 |
registration in any specific SIP registrar, but MAY require |
| 856 |
authorisation of the SIP registrar to invoke the service. |
| 857 |
|
| 858 |
A point-to-point session takes place between two parties. For ToIP, |
| 859 |
one or both of the communicating parties will indicate real-time text |
| 860 |
as a possible or preferred medium for conversation using SIP in the |
| 861 |
session setup. |
| 862 |
|
| 863 |
The following features MAY be implemented to facilitate the session |
| 864 |
establishment using ToIP: |
| 865 |
|
| 866 |
a. Caller Preferences: SIP headers (e.g., Contact) [<a href="#ref-10" title=""Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)"">10</a>] can be used |
| 867 |
to show that real-time text is the medium of choice for |
| 868 |
communications. |
| 869 |
|
| 870 |
b. Called Party Preferences [<a href="#ref-11" title=""Caller Preferences for the Session Initiation Protocol (SIP)"">11</a>]: The called party being passive can |
| 871 |
formulate a clear rule indicating how a session should be handled, |
| 872 |
either using real-time text as a preferred medium or not, and |
| 873 |
whether this session needs to be handled by a designated SIP proxy |
| 874 |
or the SIP User Agent. |
| 875 |
|
| 876 |
c. SIP Server Support for User Preferences: It is RECOMMENDED that |
| 877 |
SIP servers also handle the incoming sessions in accordance with |
| 878 |
preferences expressed for real-time text. The SIP server can also |
| 879 |
enforce ToIP policy rules for communications (e.g., use of the |
| 880 |
transcoding server for ToIP). |
| 881 |
|
| 882 |
<span class="h5"><a class="selflink" id="section-6.2.1.2" href="#section-6.2.1.2">6.2.1.2</a>. Session Negotiations</span> |
| 883 |
|
| 884 |
The Session Description Protocol (SDP) used in SIP [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] provides the |
| 885 |
capabilities to indicate real-time text as a medium in the session |
| 886 |
setup. <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>] uses the RTP payload types "text/red" and |
| 887 |
"text/t140" for support of ToIP, which can be indicated in the SDP as |
| 888 |
a part of the SIP INVITE, OK, and SIP/200/ACK media negotiations. In |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">van Wijk & Gybels Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 895 |
|
| 896 |
|
| 897 |
addition, SIP's offer/answer model [<a href="#ref-12" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">12</a>] can also be used in |
| 898 |
conjunction with other capabilities, including the use of a |
| 899 |
transcoding server for enhanced session negotiations [<a href="#ref-28" title=""Framework for Transcoding with the Session Initiation Protocol"">28</a>,<a href="#ref-29" title=""The SIP Conference Bridge Transcoding Model"">29</a>,<a href="#ref-13" title=""Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)"">13</a>]. |
| 900 |
|
| 901 |
<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. Transport</span> |
| 902 |
|
| 903 |
ToIP services MUST support the Real-Time Transport Protocol (RTP) [<a href="#ref-3" title=""RTP: A Transport Protocol for Real-Time Applications"">3</a>] |
| 904 |
according to the specification of <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>] for the transport of |
| 905 |
real-time text between participants. |
| 906 |
|
| 907 |
<a href="./rfc4103">RFC 4103</a> describes the transmission of T.140 [<a href="#ref-8" title=""Protocol for Multimedia Application Text Conversation"">8</a>] real-time text on IP |
| 908 |
networks. |
| 909 |
|
| 910 |
In order to enable the use of international character sets, the |
| 911 |
transmission format for real-time text conversation SHALL be UTF-8 |
| 912 |
[<a href="#ref-14" title=""UTF-8, a transformation format of ISO 10646"">14</a>], in accordance with ITU-T T.140. |
| 913 |
|
| 914 |
If real-time text is detected to be missing after transmission, there |
| 915 |
SHOULD be a "text loss" indication in the real-time text as specified |
| 916 |
in T.140 Addendum 1 [<a href="#ref-8" title=""Protocol for Multimedia Application Text Conversation"">8</a>]. |
| 917 |
|
| 918 |
The redundancy method of <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>] SHOULD be used to significantly |
| 919 |
increase the reliability of the real-time text transmission. A |
| 920 |
redundancy level using 2 generations gives very reliable results and |
| 921 |
is therefore strongly RECOMMENDED. |
| 922 |
|
| 923 |
In order to avoid exceeding the capabilities of the sender, receiver, |
| 924 |
or network (congestion), the transmission rate SHOULD be kept at or |
| 925 |
below 30 characters per second, which is the default maximum rate |
| 926 |
specified in <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>]. Lower rates MAY be negotiated when needed |
| 927 |
through the "cps" parameter as specified in <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>]. |
| 928 |
|
| 929 |
Real-time text capability is announced in SDP by a declaration |
| 930 |
similar to this example: |
| 931 |
|
| 932 |
m=text 11000 RTP/AVP 100 98 |
| 933 |
a=rtpmap:98 t140/1000 |
| 934 |
a=rtpmap:100 red/1000 |
| 935 |
a=fmtp:100 98/98/98 |
| 936 |
|
| 937 |
By having this single coding and transmission scheme for real-time |
| 938 |
text defined in the SIP session control environment, the opportunity |
| 939 |
for interoperability is optimized. However, if good reasons exist, |
| 940 |
other transport mechanisms MAY be offered and used for the T.140- |
| 941 |
coded text, provided that proper negotiation is introduced, but the |
| 942 |
<a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>] transport MUST be used as both the default and the |
| 943 |
fallback transport. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">van Wijk & Gybels Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. Transcoding Services</span> |
| 954 |
|
| 955 |
Invocation of a transcoding service MAY happen automatically when the |
| 956 |
session is being set up based on any valid indication or negotiation |
| 957 |
of supported or preferred media types. A transcoding framework |
| 958 |
document using SIP [<a href="#ref-28" title=""Framework for Transcoding with the Session Initiation Protocol"">28</a>] describes invoking relay services, where the |
| 959 |
relay acts as a conference bridge or uses the third-party control |
| 960 |
mechanism. ToIP implementations SHOULD support this transcoding |
| 961 |
framework. |
| 962 |
|
| 963 |
<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. Presentation and User Control Functions</span> |
| 964 |
|
| 965 |
<span class="h5"><a class="selflink" id="section-6.2.4.1" href="#section-6.2.4.1">6.2.4.1</a>. Progress and Status Information</span> |
| 966 |
|
| 967 |
Session progress information SHOULD use simple language so that as |
| 968 |
many users as possible can understand it. The use of jargon or |
| 969 |
ambiguous terminology SHOULD be avoided. It is RECOMMENDED that text |
| 970 |
information be used together with icons to symbolise the session |
| 971 |
progress information. |
| 972 |
|
| 973 |
In summary, it SHOULD be possible to observe indicators about: |
| 974 |
|
| 975 |
- Incoming session |
| 976 |
|
| 977 |
- Availability of real-time text, voice, and video channels |
| 978 |
|
| 979 |
- Session progress |
| 980 |
|
| 981 |
- Incoming real-time text |
| 982 |
|
| 983 |
- Any loss in incoming real-time text |
| 984 |
|
| 985 |
- Typed and transmitted real-time text |
| 986 |
|
| 987 |
<span class="h5"><a class="selflink" id="section-6.2.4.2" href="#section-6.2.4.2">6.2.4.2</a>. Alerting</span> |
| 988 |
|
| 989 |
For users who cannot use the audible alerter for incoming sessions, |
| 990 |
it is RECOMMENDED to include a tactile, as well as a visual, |
| 991 |
indicator. |
| 992 |
|
| 993 |
Among the alerting options are alerting by the User Agent's User |
| 994 |
Interface and specific alerting User Agents registered to the same |
| 995 |
registrar as the main User Agent. |
| 996 |
|
| 997 |
It should be noted that external alerting systems exist and one |
| 998 |
common interface for triggering the alerting action is a contact |
| 999 |
closure between two conductors. |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">van Wijk & Gybels Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h5"><a class="selflink" id="section-6.2.4.3" href="#section-6.2.4.3">6.2.4.3</a>. Text Presentation</span> |
| 1010 |
|
| 1011 |
Requirement R32 states that, in the display of text conversations, |
| 1012 |
users must be able to distinguish easily between different speakers. |
| 1013 |
This could be done using color, positioning of the text (i.e., |
| 1014 |
incoming real-time text and outgoing real-time text in different |
| 1015 |
display areas), in-band identifiers of the parties, or a combination |
| 1016 |
of any of these techniques. |
| 1017 |
|
| 1018 |
<span class="h5"><a class="selflink" id="section-6.2.4.4" href="#section-6.2.4.4">6.2.4.4</a>. File Storage</span> |
| 1019 |
|
| 1020 |
Requirement R31 recommends that ToIP systems allow the user to save |
| 1021 |
text conversations. This SHOULD be done using a standard file |
| 1022 |
format. For example: a UTF-8 text file in XHTML format [<a href="#ref-15" title=""XHTML 1.0: The Extensible HyperText Markup Language: A Reformulation of HTML 4 in XML 1.0"">15</a>], |
| 1023 |
including timestamps, party names (or addresses), and the |
| 1024 |
conversation text. |
| 1025 |
|
| 1026 |
<span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>. Interworking Functions</span> |
| 1027 |
|
| 1028 |
A number of systems for real-time text conversation already exist as |
| 1029 |
well as a number of message-oriented text communication systems. |
| 1030 |
Interoperability is of interest between ToIP and some of these |
| 1031 |
systems. |
| 1032 |
|
| 1033 |
Interoperation of half-duplex and full-duplex protocols, and between |
| 1034 |
protocols that have different data rates, may require text buffering. |
| 1035 |
Some intelligence will be needed to determine when to change |
| 1036 |
direction when operating in half-duplex mode. Identification may be |
| 1037 |
required of half-duplex operation either at the "user" level (i.e., |
| 1038 |
users must inform each other) or at the "protocol" level (where an |
| 1039 |
indication must be sent back to the gateway). However, special care |
| 1040 |
needs to be taken to provide the best possible real-time performance. |
| 1041 |
|
| 1042 |
Buffering schemes SHOULD be dimensioned to adjust for receiving at 30 |
| 1043 |
characters per second and transmitting at 6 characters per second for |
| 1044 |
up to 4 minutes (i.e., less than 3000 characters). |
| 1045 |
|
| 1046 |
When converting between simultaneous voice and text on the IP side, |
| 1047 |
and alternating voice and text on the other side of a gateway, a |
| 1048 |
conflict can occur if the IP user transmits both audio and text at |
| 1049 |
the same time. In such situations, text transmission SHOULD have |
| 1050 |
precedence, so that while text is transmitted, audio is lost. |
| 1051 |
|
| 1052 |
Transcoding of text to and from other coding formats may need to take |
| 1053 |
place in gateways between ToIP and other forms of text conversation, |
| 1054 |
for example, to connect to a PSTN text telephone. |
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">van Wijk & Gybels Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Session setup through gateways to other networks may require the use |
| 1066 |
of specially formatted addresses or other mechanisms for invoking |
| 1067 |
those gateways. |
| 1068 |
|
| 1069 |
ToIP interworking requires a method to invoke a text gateway. These |
| 1070 |
text gateways act as User Agents at the IP side. The capabilities of |
| 1071 |
the gateway during the call will be determined by the call |
| 1072 |
capabilities of the terminal that is using the gateway. For example, |
| 1073 |
a PSTN textphone is generally only able to receive voice and real- |
| 1074 |
time text, so the gateway will only allow ToIP and audio. |
| 1075 |
|
| 1076 |
Examples of possible scenarios for invocation of the text gateway |
| 1077 |
are: |
| 1078 |
|
| 1079 |
a. PSTN textphone users dial a prefix number before dialing out. |
| 1080 |
|
| 1081 |
b. Separate real-time text subscriptions, linked to the phone number |
| 1082 |
or terminal identifier/ IP address. |
| 1083 |
|
| 1084 |
c. Real-time text capability indicators. |
| 1085 |
|
| 1086 |
d. Real-time text preference indicators. |
| 1087 |
|
| 1088 |
e. Listen for V.18 modem modulation text activity in all PSTN calls |
| 1089 |
and routing of the call to an appropriate gateway. |
| 1090 |
|
| 1091 |
f. Call transfer request by the called user. |
| 1092 |
|
| 1093 |
g. Placing a call via the Web, and using one of the methods described |
| 1094 |
here |
| 1095 |
|
| 1096 |
h. A text gateway with its own telephone number and/or SIP address |
| 1097 |
(this requires user interaction with the gateway to place a call). |
| 1098 |
|
| 1099 |
i. ENUM address analysis and number plan. |
| 1100 |
|
| 1101 |
j. Number or address analysis leads to a gateway for all PSTN calls. |
| 1102 |
|
| 1103 |
<span class="h5"><a class="selflink" id="section-6.2.5.1" href="#section-6.2.5.1">6.2.5.1</a>. PSTN Interworking</span> |
| 1104 |
|
| 1105 |
Analog text telephony is cumbersome because of incompatible national |
| 1106 |
implementations where interworking was never considered. A large |
| 1107 |
number of these implementations have been documented in ITU-T V.18 |
| 1108 |
[<a href="#ref-16" title=""Operational and Interworking Requirements for DCEs operating in Text Telephone Mode"">16</a>], which also defines the modem detection sequences for the |
| 1109 |
different text protocols. In rare cases, the modem type |
| 1110 |
identification may take considerable time, depending on user actions. |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">van Wijk & Gybels Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
To resolve analog textphone incompatibilities, text telephone |
| 1122 |
gateways are needed to transcode incoming analog signals into T.140 |
| 1123 |
and vice versa. The modem capability exchange time can be reduced by |
| 1124 |
the text telephone gateways initially assuming the analog text |
| 1125 |
telephone protocol used in the region where the gateway is located. |
| 1126 |
For example, in the USA, Baudot [<a href="#ref-25" title=""A Frequency Shift Keyed Modem for Use on the Public Switched Telephone Network."">25</a>] might be tried as the initial |
| 1127 |
protocol. If negotiation for Baudot fails, the full V.18 modem |
| 1128 |
capability exchange will take place. In the UK, ITU-T V.21 [<a href="#ref-26" title=""300 bits per second duplex modem standardized for use in the general switched telephone network"">26</a>] |
| 1129 |
might be the first choice. |
| 1130 |
|
| 1131 |
In particular, transmission of real-time text on PSTN networks takes |
| 1132 |
place using a variety of codings and modulations, including ITU-T |
| 1133 |
V.21 [<a href="#ref-26" title=""300 bits per second duplex modem standardized for use in the general switched telephone network"">26</a>], Baudot [<a href="#ref-25" title=""A Frequency Shift Keyed Modem for Use on the Public Switched Telephone Network."">25</a>], dual-tone multi-frequency (DTMF), V.23 [<a href="#ref-27" title=""600/1200-baud modem standardized for use in the general switched telephone network"">27</a>], |
| 1134 |
and others. Many difficulties have arisen as a result of this |
| 1135 |
variety in text telephony protocols and the ITU-T V.18 [<a href="#ref-16" title=""Operational and Interworking Requirements for DCEs operating in Text Telephone Mode"">16</a>] standard |
| 1136 |
was developed to address some of these issues. |
| 1137 |
|
| 1138 |
ITU-T V.18 [<a href="#ref-16" title=""Operational and Interworking Requirements for DCEs operating in Text Telephone Mode"">16</a>] offers a native text telephony method, plus it |
| 1139 |
defines interworking with current protocols. In the interworking |
| 1140 |
mode, it will recognise one of the older protocols and fall back to |
| 1141 |
that transmission method when required. |
| 1142 |
|
| 1143 |
Text gateways MUST use the ITU-T V.18 [<a href="#ref-16" title=""Operational and Interworking Requirements for DCEs operating in Text Telephone Mode"">16</a>] standard at the PSTN side. |
| 1144 |
A text gateway MUST act as a SIP User Agent on the IP side and |
| 1145 |
support <a href="./rfc4103">RFC 4103</a> real-time text transport. |
| 1146 |
|
| 1147 |
While ToIP allows receiving and sending real-time text simultaneously |
| 1148 |
and is displayed on a split screen, many analog text telephones |
| 1149 |
require users to take turns typing. This is because many text |
| 1150 |
telephones operate strictly half duplex. Only one can transmit text |
| 1151 |
at a time. The users apply strict turn-taking rules. |
| 1152 |
|
| 1153 |
There are several text telephones which communicate in full duplex, |
| 1154 |
but merge transmitted text and received text in the same line in the |
| 1155 |
same display window. Here too the users apply strict turn taking |
| 1156 |
rules. |
| 1157 |
|
| 1158 |
Native V.18 text telephones support full duplex and separate display |
| 1159 |
from reception and transmission so that the full duplex capability |
| 1160 |
can be used fully. Such devices could use the ToIP split screen as |
| 1161 |
well, but almost all text telephones use a restricted character set |
| 1162 |
and many use low text transmission speeds (4 to 7 characters per |
| 1163 |
second). |
| 1164 |
|
| 1165 |
That is why it is important for the ToIP user to know that he or she |
| 1166 |
is connected with an analog text telephone. The session description |
| 1167 |
[<a href="#ref-9" title=""SDP: Session Description Protocol"">9</a>] SHOULD contain an indication that the other endpoint for the call |
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">van Wijk & Gybels Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
is a PSTN textphone (e.g., connected via an ATA or through a text |
| 1178 |
gateway). This means that the textphone user may be used to formal |
| 1179 |
turn taking during the call. |
| 1180 |
|
| 1181 |
<span class="h5"><a class="selflink" id="section-6.2.5.2" href="#section-6.2.5.2">6.2.5.2</a>. Mobile Interworking</span> |
| 1182 |
|
| 1183 |
Mobile wireless (or cellular) circuit switched connections provide a |
| 1184 |
digital real-time transport service for voice or data. The access |
| 1185 |
technologies include GSM, CDMA, TDMA, iDen, and various 3G |
| 1186 |
technologies, as well as WiFi or WiMAX. |
| 1187 |
|
| 1188 |
ToIP may be supported over the cellular wireless packet-switched |
| 1189 |
service. It interfaces to the Internet. |
| 1190 |
|
| 1191 |
The following sections describe how mobile text telephony is |
| 1192 |
supported. |
| 1193 |
|
| 1194 |
<span class="h6"><a class="selflink" id="section-6.2.5.2.1" href="#section-6.2.5.2.1">6.2.5.2.1</a>. Cellular "No-gain"</span> |
| 1195 |
|
| 1196 |
The "No-gain" text telephone transporting technology uses specially |
| 1197 |
modified Enhanced Full Rate (EFR) [<a href="#ref-17">17</a>] and Enhanced Variable Rate |
| 1198 |
(EVR) [<a href="#ref-18" title=""Enhanced Variable Rate Codec">18</a>] speech vocoders in mobile terminals used to provide a text |
| 1199 |
telephony call. It provides full duplex operation and supports |
| 1200 |
alternating between voice and text ("VCO/HCO"). It is dedicated to |
| 1201 |
CDMA and TDMA mobile technologies and the US Baudot (i.e., 45 bit/s) |
| 1202 |
type of text telephones. |
| 1203 |
|
| 1204 |
<span class="h6"><a class="selflink" id="section-6.2.5.2.2" href="#section-6.2.5.2.2">6.2.5.2.2</a>. Cellular Text Telephone Modem (CTM)</span> |
| 1205 |
|
| 1206 |
CTM [<a href="#ref-7" title=""Cellular Text Telephone Modem Description"">7</a>] is a technology-independent modem technology that provides |
| 1207 |
the transport of text telephone characters at up to 10 characters/sec |
| 1208 |
using modem signals that can be carried by many voice codecs and uses |
| 1209 |
a highly redundant encoding technique to overcome the fading and cell |
| 1210 |
changing losses. |
| 1211 |
|
| 1212 |
<span class="h6"><a class="selflink" id="section-6.2.5.2.3" href="#section-6.2.5.2.3">6.2.5.2.3</a>. Cellular "Baudot mode"</span> |
| 1213 |
|
| 1214 |
This term is often used by cellular terminal suppliers for a cellular |
| 1215 |
phone mode that allows TTYs to operate into a cellular phone and to |
| 1216 |
communicate with a fixed-line TTY. Thus it is a common name for the |
| 1217 |
"No-Gain" and the CTM solutions when applied to the Baudot-type |
| 1218 |
textphones. |
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">van Wijk & Gybels Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
<span class="h6"><a class="selflink" id="section-6.2.5.2.4" href="#section-6.2.5.2.4">6.2.5.2.4</a>. Mobile Data Channel Mode</span> |
| 1234 |
|
| 1235 |
Many mobile terminals allow the use of the circuit-switched data |
| 1236 |
channel to transfer data in real time. Data rates of 9600 bit/s are |
| 1237 |
usually supported on the 2G mobile network. Gateways provide |
| 1238 |
interoperability with PSTN textphones. |
| 1239 |
|
| 1240 |
<span class="h6"><a class="selflink" id="section-6.2.5.2.5" href="#section-6.2.5.2.5">6.2.5.2.5</a>. Mobile ToIP</span> |
| 1241 |
|
| 1242 |
ToIP could be supported over mobile wireless packet-switched services |
| 1243 |
that interface to the Internet. For 3GPP 3G services, ToIP support |
| 1244 |
is described in 3G TS 26.235 [<a href="#ref-19" title=""IP Multimedia default codecs"">19</a>]. |
| 1245 |
|
| 1246 |
<span class="h5"><a class="selflink" id="section-6.2.5.3" href="#section-6.2.5.3">6.2.5.3</a>. Instant Messaging Interworking</span> |
| 1247 |
|
| 1248 |
Text gateways MAY be used to allow interworking between Instant |
| 1249 |
Messaging systems and ToIP solutions. Because Instant Messaging is |
| 1250 |
based on blocks of text, rather than on a continuous stream of |
| 1251 |
characters like ToIP, gateways MUST transcode between the two |
| 1252 |
formats. Text gateways for interworking between Instant Messaging |
| 1253 |
and ToIP MUST apply a procedure for bridging the different |
| 1254 |
conversational formats of real-time text versus text messaging. The |
| 1255 |
following advice may improve user experience for both parties in a |
| 1256 |
call through a messaging gateway. |
| 1257 |
|
| 1258 |
a. Concatenate individual characters originating at the ToIP side |
| 1259 |
into blocks of text. |
| 1260 |
|
| 1261 |
b. When the length of the concatenated message becomes longer than 50 |
| 1262 |
characters, the buffered text SHOULD be transmitted to the Instant |
| 1263 |
Messaging side as soon as any non-alphanumerical character is |
| 1264 |
received from the ToIP side. |
| 1265 |
|
| 1266 |
c. When a new line indicator is received from the ToIP side, the |
| 1267 |
buffered characters up to that point, including the carriage |
| 1268 |
return and/or line-feed characters, SHOULD be transmitted to the |
| 1269 |
Instant Messaging side. |
| 1270 |
|
| 1271 |
d. When the ToIP side has been idle for at least 5 seconds, all |
| 1272 |
buffered text up to that point SHOULD be transmitted to the |
| 1273 |
Instant Messaging side. |
| 1274 |
|
| 1275 |
e. Text Gateways must be capable of maintaining the real-time |
| 1276 |
performance for ToIP while providing the interworking services. |
| 1277 |
|
| 1278 |
It is RECOMMENDED that during the session, both users be constantly |
| 1279 |
updated on the progress of the text input. Many Instant Messaging |
| 1280 |
protocols signal that a user is typing to the other party in the |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">van Wijk & Gybels Informational [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
conversation. Text gateways between such Instant Messaging protocols |
| 1290 |
and ToIP MUST provide this signalling to the Instant Messaging side |
| 1291 |
when characters start being received, or at the beginning of the |
| 1292 |
conversation. |
| 1293 |
|
| 1294 |
At the ToIP side, an indicator of writing the Instant Message MUST be |
| 1295 |
present where the Instant Messaging protocol provides one. For |
| 1296 |
example, the real-time text user MAY see ". . . waiting for replying |
| 1297 |
IM. . . " and when 5 seconds have passed another . (dot) can be |
| 1298 |
shown. |
| 1299 |
|
| 1300 |
Those solutions will reduce the difficulties between streaming and |
| 1301 |
blocked text services. |
| 1302 |
|
| 1303 |
Even though the text gateway can connect Instant Messaging and ToIP, |
| 1304 |
the best solution is to take advantage of the fact that the user |
| 1305 |
interfaces and the user communities for instant messaging and ToIP |
| 1306 |
telephony are very similar. After all, the character input, |
| 1307 |
character display, Internet connectivity, and SIP stack can be the |
| 1308 |
same for Instant Messaging (SIMPLE) and ToIP. Thus, the user may |
| 1309 |
simply use different applications for ToIP and text messaging in the |
| 1310 |
same terminal. |
| 1311 |
|
| 1312 |
Devices that implement Instant Messaging SHOULD implement ToIP as |
| 1313 |
described in this document so that a more complete text communication |
| 1314 |
service can be provided. |
| 1315 |
|
| 1316 |
<span class="h5"><a class="selflink" id="section-6.2.5.4" href="#section-6.2.5.4">6.2.5.4</a>. Multi-Functional Combination Gateways</span> |
| 1317 |
|
| 1318 |
In practice, many interworking gateways will be implemented as |
| 1319 |
gateways that combine different functions. As such, a text gateway |
| 1320 |
could be built to have modems to interwork with the PSTN and support |
| 1321 |
both Instant Messaging as well as ToIP. Such interworking functions |
| 1322 |
are called combination gateways. |
| 1323 |
|
| 1324 |
Combination gateways could provide interworking between all of their |
| 1325 |
supported text-based functions. For example, a text gateway that has |
| 1326 |
modems to interwork with the PSTN and that support both Instant |
| 1327 |
Messaging and ToIP could support the following interworking |
| 1328 |
functions: |
| 1329 |
|
| 1330 |
- PSTN text telephony to ToIP |
| 1331 |
|
| 1332 |
- PSTN text telephony to Instant Messaging |
| 1333 |
|
| 1334 |
- Instant Messaging to ToIP |
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">van Wijk & Gybels Informational [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
<span class="h5"><a class="selflink" id="section-6.2.5.5" href="#section-6.2.5.5">6.2.5.5</a>. Character Set Transcoding</span> |
| 1346 |
|
| 1347 |
Gateways between the ToIP network and other networks MAY need to |
| 1348 |
transcode text streams. ToIP makes use of the ISO 10646 character |
| 1349 |
set. Most PSTN textphones use a 7-bit character set, or a character |
| 1350 |
set that is converted to a 7-bit character set by the V.18 modem. |
| 1351 |
|
| 1352 |
When transcoding between character sets and T.140 in gateways, |
| 1353 |
special consideration MUST be given to the national variants of the |
| 1354 |
7-bit codes, with national characters mapping into different codes in |
| 1355 |
the ISO 10646 code space. The national variant to be used could be |
| 1356 |
selectable by the user on a per-call basis, or be configured as a |
| 1357 |
national default for the gateway. |
| 1358 |
|
| 1359 |
The indicator of missing text in T.140, specified in T.140 amendment |
| 1360 |
1, cannot be represented in the 7-bit character codes. Therefore the |
| 1361 |
indicator of missing text SHOULD be transcoded to the ' (apostrophe) |
| 1362 |
character in legacy text telephone systems, where this character |
| 1363 |
exists. For legacy systems where the ' character does not exist, the |
| 1364 |
. (full stop) character SHOULD be used instead. |
| 1365 |
|
| 1366 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Further Recommendations for Implementers and Service Providers</span> |
| 1367 |
|
| 1368 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Access to Emergency Services</span> |
| 1369 |
|
| 1370 |
It must be possible to place an emergency call using ToIP and it must |
| 1371 |
be possible to use a relay service in such a call. The emergency |
| 1372 |
service provided to users utilising the real-time text medium must be |
| 1373 |
equivalent to the emergency service provided to users utilising |
| 1374 |
speech or other media. |
| 1375 |
|
| 1376 |
A text gateway must be able to route real-time text calls to |
| 1377 |
emergency service providers when any of the recognised emergency |
| 1378 |
numbers that support text communications for the country or region |
| 1379 |
are called, e.g., "911" in the USA and "112" in Europe. Routing |
| 1380 |
real-time text calls to emergency services may require the use of a |
| 1381 |
transcoding service. |
| 1382 |
|
| 1383 |
A text gateway with cellular wireless packet-switched services must |
| 1384 |
be able to route real-time text calls to emergency service providers |
| 1385 |
when any of the recognized emergency numbers that support real-time |
| 1386 |
text communication for the country is called. |
| 1387 |
|
| 1388 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Home Gateways or Analog Terminal Adapters</span> |
| 1389 |
|
| 1390 |
Analog terminal adapters (ATA) using SIP-based IP communication and |
| 1391 |
RJ-11 connectors for connecting traditional PSTN devices SHOULD |
| 1392 |
enable connection of legacy PSTN text telephones [<a href="#ref-23" title=""SIP Telephony Device Requirements and Configuration"">23</a>]. |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">van Wijk & Gybels Informational [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
These adapters SHOULD contain V.18 modem functionality, voice |
| 1402 |
handling functionality, and conversion functions to/from SIP-based |
| 1403 |
ToIP with T.140 transported according to <a href="./rfc4103">RFC 4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>], in a similar |
| 1404 |
way as it provides interoperability for voice sessions. |
| 1405 |
|
| 1406 |
If a session is set up and text/t140 capability is not declared by |
| 1407 |
the destination endpoint (by the endpoint terminal or the text |
| 1408 |
gateway in the network at the endpoint), a method for invoking a |
| 1409 |
transcoding server SHALL be used. If no such server is available, |
| 1410 |
the signals from the textphone MAY be transmitted in the voice |
| 1411 |
channel as audio with a high quality of service. |
| 1412 |
|
| 1413 |
NOTE: It is preferred that such analog terminal adaptors do use <a href="./rfc4103">RFC</a> |
| 1414 |
<a href="./rfc4103">4103</a> [<a href="#ref-4" title=""RTP Payload for Text Conversation"">4</a>] on board and thus act as a text gateway. Sending textphone |
| 1415 |
signals over the voice channel is undesirable due to possible |
| 1416 |
filtering and compression and packet loss between the endpoints. |
| 1417 |
This can result in character loss in the textphone conversation or |
| 1418 |
even not allowing the textphones to connect to each other. |
| 1419 |
|
| 1420 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. User Mobility</span> |
| 1421 |
|
| 1422 |
ToIP User Agents SHOULD use the same mechanisms as other SIP User |
| 1423 |
Agents to resolve mobility issues. It is RECOMMENDED that users use |
| 1424 |
a SIP address, resolved by a SIP registrar, to enable basic user |
| 1425 |
mobility. Further mechanisms are defined for all session types for |
| 1426 |
3G IP multimedia systems. |
| 1427 |
|
| 1428 |
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Firewalls and NATs</span> |
| 1429 |
|
| 1430 |
ToIP uses the same signalling and transport protocols as VoIP. |
| 1431 |
Hence, the same firewall and NAT solutions and network functionality |
| 1432 |
that apply to VoIP MUST also apply to ToIP. |
| 1433 |
|
| 1434 |
<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Quality of Service</span> |
| 1435 |
|
| 1436 |
Where Quality of Service (QoS) mechanisms are used, the real-time |
| 1437 |
text streams should be assigned appropriate QoS characteristics, so |
| 1438 |
that the performance requirements can be met and the real-time text |
| 1439 |
stream is not degraded unfavourably in comparison to voice |
| 1440 |
performance in congested situations. |
| 1441 |
|
| 1442 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 1443 |
|
| 1444 |
User confidentiality and privacy need to be met as described in SIP |
| 1445 |
[<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>]. For example, nothing should reveal in an obvious way the fact |
| 1446 |
that the ToIP user might be a person with a hearing or speech |
| 1447 |
impairment. It is up to the ToIP user to make his or her hearing or |
| 1448 |
speech impairment public. If a transcoding server is being used, |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">van Wijk & Gybels Informational [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
this SHOULD be as transparent as possible. However, it might still |
| 1458 |
be possible to discern that a user might be hearing or speech |
| 1459 |
impaired based on the attributes present in SDP, although the |
| 1460 |
intention is that mainstream users might also choose to use ToIP. |
| 1461 |
Encryption SHOULD be used on an end-to-end or hop-by-hop basis as |
| 1462 |
described in SIP [<a href="#ref-2" title=""SIP: Session Initiation Protocol"">2</a>] and SRTP [<a href="#ref-20" title=""The Secure Real-time Transport Protocol (SRTP)"">20</a>]. |
| 1463 |
|
| 1464 |
Authentication MUST be provided for users in addition to message |
| 1465 |
integrity and access control. |
| 1466 |
|
| 1467 |
Protection against Denial-of-Service (DoS) attacks needs to be |
| 1468 |
provided, considering the case that the ToIP users might need |
| 1469 |
transcoding servers. |
| 1470 |
|
| 1471 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Contributors</span> |
| 1472 |
|
| 1473 |
The following people contributed to this document: Willem Dijkstra, |
| 1474 |
Barry Dingle, Gunnar Hellstrom, Radhika R. Roy, Henry Sinnreich, and |
| 1475 |
Gregg C. Vanderheiden. |
| 1476 |
|
| 1477 |
The content and concepts within are a product of the SIPPING Working |
| 1478 |
Group. Tom Taylor (Nortel) acted as independent reviewer and |
| 1479 |
contributed significantly to the structure and content of this |
| 1480 |
document. |
| 1481 |
|
| 1482 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span> |
| 1483 |
|
| 1484 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span> |
| 1485 |
|
| 1486 |
[<a id="ref-1">1</a>] Bradner, S., Ed., "Intellectual Property Rights in IETF |
| 1487 |
Technology", <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>, <a href="./rfc3979">RFC 3979</a>, March 2005. |
| 1488 |
|
| 1489 |
[<a id="ref-2">2</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., |
| 1490 |
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: |
| 1491 |
Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002. |
| 1492 |
|
| 1493 |
[<a id="ref-3">3</a>] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, |
| 1494 |
"RTP: A Transport Protocol for Real-Time Applications", STD 64, |
| 1495 |
<a href="./rfc3550">RFC 3550</a>, July 2003. |
| 1496 |
|
| 1497 |
[<a id="ref-4">4</a>] Hellstrom, G. and P. Jones, "RTP Payload for Text |
| 1498 |
Conversation", <a href="./rfc4103">RFC 4103</a>, June 2005. |
| 1499 |
|
| 1500 |
[<a id="ref-5">5</a>] ITU-T Recommendation F.703,"Multimedia Conversational |
| 1501 |
Services", November 2000. |
| 1502 |
|
| 1503 |
[<a id="ref-6">6</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement |
| 1504 |
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">van Wijk & Gybels Informational [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
[<a id="ref-7">7</a>] 3GPP TS 26.226, "Cellular Text Telephone Modem Description" |
| 1514 |
(CTM). |
| 1515 |
|
| 1516 |
[<a id="ref-8">8</a>] ITU-T Recommendation T.140, "Protocol for Multimedia |
| 1517 |
Application Text Conversation" (February 1998) and Addendum 1 |
| 1518 |
(February 2000). |
| 1519 |
|
| 1520 |
[<a id="ref-9">9</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session |
| 1521 |
Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006. |
| 1522 |
|
| 1523 |
[<a id="ref-10">10</a>] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating |
| 1524 |
User Agent Capabilities in the Session Initiation Protocol |
| 1525 |
(SIP)", <a href="./rfc3840">RFC 3840</a>, August 2004. |
| 1526 |
|
| 1527 |
[<a id="ref-11">11</a>] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller |
| 1528 |
Preferences for the Session Initiation Protocol (SIP)", <a href="./rfc3841">RFC</a> |
| 1529 |
<a href="./rfc3841">3841</a>, August 2004. |
| 1530 |
|
| 1531 |
[<a id="ref-12">12</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with |
| 1532 |
Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June 2002. |
| 1533 |
|
| 1534 |
[<a id="ref-13">13</a>] Camarillo, G., Burger, E., Schulzrinne, H., and A. van Wijk, |
| 1535 |
"Transcoding Services Invocation in the Session Initiation |
| 1536 |
Protocol (SIP) Using Third Party Call Control (3pcc)", <a href="./rfc4117">RFC</a> |
| 1537 |
<a href="./rfc4117">4117</a>, June 2005. |
| 1538 |
|
| 1539 |
[<a id="ref-14">14</a>] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD |
| 1540 |
63, <a href="./rfc3629">RFC 3629</a>, November 2003. |
| 1541 |
|
| 1542 |
[<a id="ref-15">15</a>] "XHTML 1.0: The Extensible HyperText Markup Language: A |
| 1543 |
Reformulation of HTML 4 in XML 1.0", W3C Recommendation, |
| 1544 |
Available at <a href="http://www.w3.org/TR/xhtml1">http://www.w3.org/TR/xhtml1</a>. |
| 1545 |
|
| 1546 |
[<a id="ref-16">16</a>] ITU-T Recommendation V.18, "Operational and Interworking |
| 1547 |
Requirements for DCEs operating in Text Telephone Mode", |
| 1548 |
November 2000. |
| 1549 |
|
| 1550 |
[<a id="ref-17">17</a>] TIA/EIA/IS-823-A, "TTY/TDD Extension to TIA/EIA-136-410 |
| 1551 |
Enhanced Full Rate Speech Codec (must used in conjunction with |
| 1552 |
TIA/EIA/IS-840)" |
| 1553 |
|
| 1554 |
[<a id="ref-18">18</a>] TIA/EIA/IS-127-2, "Enhanced Variable Rate Codec, Speech Service |
| 1555 |
Option 3 for Wideband Spread Spectrum Digital Systems, Addendum |
| 1556 |
2." |
| 1557 |
|
| 1558 |
[<a id="ref-19">19</a>] "IP Multimedia default codecs", 3GPP TS 26.235 |
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">van Wijk & Gybels Informational [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
[<a id="ref-20">20</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. |
| 1570 |
Norrman, "The Secure Real-time Transport Protocol (SRTP)", <a href="./rfc3711">RFC</a> |
| 1571 |
<a href="./rfc3711">3711</a>, March 2004. |
| 1572 |
|
| 1573 |
[<a id="ref-21">21</a>] ITU-T Recommendation F.700, "Framework Recommendation for |
| 1574 |
Multimedia Services", November 2000. |
| 1575 |
|
| 1576 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span> |
| 1577 |
|
| 1578 |
[<a id="ref-22">22</a>] Charlton, N., Gasson, M., Gybels, G., Spanner, M., and A. van |
| 1579 |
Wijk, "User Requirements for the Session Initiation Protocol |
| 1580 |
(SIP) in Support of Deaf, Hard of Hearing and Speech-impaired |
| 1581 |
Individuals", <a href="./rfc3351">RFC 3351</a>, August 2002. |
| 1582 |
|
| 1583 |
[<a id="ref-23">23</a>] Sinnreich, H., Ed., Lass, S., and C. Stredicke, "SIP Telephony |
| 1584 |
Device Requirements and Configuration", <a href="./rfc4504">RFC 4504</a>, May 2006. |
| 1585 |
|
| 1586 |
[<a id="ref-24">24</a>] European Telecommunications Standards Institute (ETSI), "Human |
| 1587 |
Factors (HF); Guidelines for Telecommunication Relay Services |
| 1588 |
for Text Telephones". TR 101 806, June 2000. |
| 1589 |
|
| 1590 |
[<a id="ref-25">25</a>] TIA/EIA/825 "A Frequency Shift Keyed Modem for Use on the |
| 1591 |
Public Switched Telephone Network." (The specification for |
| 1592 |
45.45 and 50 bit/s TTY modems.) |
| 1593 |
|
| 1594 |
[<a id="ref-26">26</a>] International Telecommunication Union (ITU), "300 bits per |
| 1595 |
second duplex modem standardized for use in the general |
| 1596 |
switched telephone network". ITU-T Recommendation V.21, |
| 1597 |
November 1988. |
| 1598 |
|
| 1599 |
[<a id="ref-27">27</a>] International Telecommunication Union (ITU), "600/1200-baud |
| 1600 |
modem standardized for use in the general switched telephone |
| 1601 |
network", ITU-T Recommendation V.23, November 1988. |
| 1602 |
|
| 1603 |
[<a id="ref-28">28</a>] Camarillo, G., "Framework for Transcoding with the Session |
| 1604 |
Initiation Protocol", Work in Progress, May 2006. |
| 1605 |
|
| 1606 |
[<a id="ref-29">29</a>] Camarillo, G., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22The+SIP+Conference+Bridge+Transcoding+Model%22'>"The SIP Conference Bridge Transcoding Model"</a>, |
| 1607 |
Work in Progress, January 2006. |
| 1608 |
|
| 1609 |
|
| 1610 |
|
| 1611 |
|
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">van Wijk & Gybels Informational [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
Authors' Addresses |
| 1626 |
|
| 1627 |
Guido Gybels |
| 1628 |
Department of New Technologies |
| 1629 |
RNID, 19-23 Featherstone Street |
| 1630 |
London EC1Y 8SL, UK |
| 1631 |
|
| 1632 |
Tel +44-20-7294 3713 |
| 1633 |
Txt +44-20-7296 8001 Ext 3713 |
| 1634 |
Fax +44-20-7296 8069 |
| 1635 |
EMail: [email protected] |
| 1636 |
<a href="http://www.ictrnid.org.uk">http://www.ictrnid.org.uk</a> |
| 1637 |
|
| 1638 |
|
| 1639 |
Arnoud A. T. van Wijk |
| 1640 |
Real-Time Text Taskforce (R3TF) |
| 1641 |
|
| 1642 |
EMail: [email protected] |
| 1643 |
<a href="http://www.realtimetext.org">http://www.realtimetext.org</a> |
| 1644 |
|
| 1645 |
|
| 1646 |
|
| 1647 |
|
| 1648 |
|
| 1649 |
|
| 1650 |
|
| 1651 |
|
| 1652 |
|
| 1653 |
|
| 1654 |
|
| 1655 |
|
| 1656 |
|
| 1657 |
|
| 1658 |
|
| 1659 |
|
| 1660 |
|
| 1661 |
|
| 1662 |
|
| 1663 |
|
| 1664 |
|
| 1665 |
|
| 1666 |
|
| 1667 |
|
| 1668 |
|
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">van Wijk & Gybels Informational [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc5194">RFC 5194</a> Framework for TOIP using SIP June 2008</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Full Copyright Statement |
| 1682 |
|
| 1683 |
Copyright (C) The IETF Trust (2008). |
| 1684 |
|
| 1685 |
This document is subject to the rights, licenses and restrictions |
| 1686 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 1687 |
retain all their rights. |
| 1688 |
|
| 1689 |
This document and the information contained herein are provided on an |
| 1690 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 1691 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND |
| 1692 |
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS |
| 1693 |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |
| 1694 |
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 1695 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1696 |
|
| 1697 |
Intellectual Property |
| 1698 |
|
| 1699 |
The IETF takes no position regarding the validity or scope of any |
| 1700 |
Intellectual Property Rights or other rights that might be claimed to |
| 1701 |
pertain to the implementation or use of the technology described in |
| 1702 |
this document or the extent to which any license under such rights |
| 1703 |
might or might not be available; nor does it represent that it has |
| 1704 |
made any independent effort to identify any such rights. Information |
| 1705 |
on the procedures with respect to rights in RFC documents can be |
| 1706 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 1707 |
|
| 1708 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 1709 |
assurances of licenses to be made available, or the result of an |
| 1710 |
attempt made to obtain a general license or permission for the use of |
| 1711 |
such proprietary rights by implementers or users of this |
| 1712 |
specification can be obtained from the IETF on-line IPR repository at |
| 1713 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 1714 |
|
| 1715 |
The IETF invites any interested party to bring to its attention any |
| 1716 |
copyrights, patents or patent applications, or other proprietary |
| 1717 |
rights that may cover technology that may be required to implement |
| 1718 |
this standard. Please address the information to the IETF at |
| 1719 |
[email protected]. |
| 1720 |
|
| 1721 |
|
| 1722 |
|
| 1723 |
|
| 1724 |
|
| 1725 |
|
| 1726 |
|
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
van Wijk & Gybels Informational [Page 31] |
| 1733 |
</pre> |