You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 44.201.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 23:54, 31 July 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪AntiCompositeNumber‬. The reason given is Open proxy/Webhost: Visit the FAQ if you are affected .
- Start of block: 13:55, 18 August 2022
- Expiry of block: 13:55, 18 April 2025
Your current IP address is 44.201.28.123. The blocked range is 44.201.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((refimprove|date=August 2022))
'''Text over IP''' (or '''ToIP''') is a means of providing a [[real-time text]] (RTT) service that operates over IP-based networks.<ref>((Cite web |title=What is IP texting? |url=https://high-tech-guide.com/article/what-is-ip-texting |access-date=2022-08-06 |website=high-tech-guide.com))</ref> It complements Voice over IP ([[VoIP]]) and Video over IP.

Real-time text is streaming text that is transmitted as it is produced, allowing text to be used conversationally.<ref>((Cite web |date=2016-12-20 |title=Real-Time Text |url=https://www.fcc.gov/real-time-text |access-date=2022-08-06 |website=Federal Communications Commission |language=en))</ref> Real-time text is defined in ITU-T Multimedia Recommendation F.700 2.1.2.1 . Real-time text is designed for conversational use where people interactively converse with each other. To achieve this, particular user requirements have been specified for the delay of each character and the character loss rate (see F.700 Annex A.3).

Real-time Text over IP can be used:
*in conjunction with voice or video in a multimedia communication or on its own, on fixed or mobile accesses,
* by people who want a fast and really interactive means of conversing,
* in noisy environments where it may be hard to hear,
* in environments where other people are nearby but where communications privacy is required,
* to transfer information (e.g., numbers, addresses, etc.) where exactness is necessary,
* by people with hearing loss or speech impairments to communicate with non-disabled and deaf or hard of hearing or speech impaired people.
* to provide real time captioning of a voice conversation for people with a hearing loss. See also captioned telephony in [[Telecommunications Relay Service]]
* to provide all voice callers with a convenient means to accurately pass numbers, addresses and other detailed information in text.

== Features==
ToIP is designed around the ITU-T T.140 real-time text presentation layer protocol (defined for H.32x multimedia services).  T.140 allows real-time editing of text e.g. by using 'backspace' and retyping. T.140 is based on the [[Universal Coded Character Set|ISO 10646-1 character set]] that is used by most IP text specifications and uses the UTF-8 format. 

Transport of ToIP uses the same [[Real-time Transport Protocol]] (RTP) as [[VoIP]] and Video-over-IP. The text is encoded according to IETF RFC 4103 "RTP Payload for Text Conversation".  

RFC&nbsp;4103 supports an optional forward error correction scheme based on redundant transmission (using RFC 2198). This results in a very low end-to-end packet loss across IP transmission links that have moderately high packet loss. To improve efficiency, text can be buffered for 0.3–0.5 seconds before it is sent whilst still meeting the delay requirements. 

RTP is usually transported over the [[User Datagram Protocol]] (UDP). However, because 2.5G mobile networks supported the [[Transmission Control Protocol]] (TCP) but did not consistently support UDP, some implementations of ToIP over mobile networks use TCP internally. 3G mobile networks can support UDP. 

The protocol stack for a ToIP medium is: 

{| class="wikitable"
|   T.140
|-
| RFC 4103
|-
| RTP
|-
| UDP (TCP)
|-
| IP
|-
|}

Very fast typing (30 characters per second) results in a two kilobit per second traffic load (including overheads for RFC&nbsp;4103 with the maximum level of redundancy, RTP, UDP and IP).

Control of ToIP sessions has been defined using the standard [[Session Initiation Protocol]] (SIP) (RFC 3261) and the [[Session Description Protocol]] (SDP) (RFC 4566) protocols. 
* SIP is used without any alteration.
* Real-time text encoding is identified by using the SDP media definition 'm=text'.
* The 3GPP IMS defines the features of SDP that ToIP uses in 3GPP TS 26.114 v7.4.0 A5

See IETF '''RFC 5194''' "Framework for real-time text over IP using the Session Initiation Protocol (SIP)" and IETF '''RFC 4504''' "SIP Telephony Device Requirements and Configuration" Section 2.9 for more information.

==Deployment==
[[Next Generation Networking]] (NGNs) is a concept developed by telecommunication service providers and their suppliers. It aims to create a true multi-service network based in IP technology. 

ToIP has been specified for inclusion in the 3GPP [[IP Multimedia Subsystem]] (IMS) (in 3GPP TS 26.114 v2.0.0 "IMS, Multimedia Telephony, Media handling and interaction"). IMS is being used to implement NGNs in many fixed and mobile networks. 

Support of ToIP is being considered in multimedia Emergency [[Public-safety answering point]] (PSAPs) in Europe and USA. The ECRIT IETF working group defines ToIP as one form of access to Emergency Services. 

ToIP can provide a 'low impact' solution to meeting national regulatory requirements to provide 'equivalent service' to the telephone service for people who have hearing or speech impairments. 

A typical terminal on a fixed line access is a home computer that supports multimedia communications - Voice and Video and real-time Text over IP. See External links for information about ToIP equipment and software.

==Use by deaf and hard-of-hearing people==
[[Telecommunications device for the deaf]] (TDD) or TTYs (also called Textphone or minicoms) were designed to transport real-time text over the [[Public switched telephone network|PSTN]]. TDDs use a range of modem technologies.
  
Text-over-IP has been designed as a replacement for TDDs when using the IP-based networks  but also to be of use to mainstream voice call users. It has less service restrictions compared with TDDs, is designed to be used as a mainstream service and can be used on standard computers or mobile terminals. Proper alerting systems for incoming calls need to be included as well as user interfaces, both hardware and software, that meet the needs of deaf people, and people with hearing or speech impairments. This can best be achieved with input from end-users in the development stages.

Interworking between TDDs and ToIP has been implemented using gateways by T-Meeting, Omnitor, Trace R& D, RNID, Center, Voiceriver, and AnnieS. '''RFC 5194''' "Framework for real-time text over IP using the Session Initiation Protocol (SIP)" provides an overview of interworking issues. Work is being proposed in the IETF SIPPING work group on more detailed interworking based on a range of call scenarios.

==See also==
* [[Real-Time Text]]
* [[Timed Text]]
* [[Total Conversation]]
* [[ipTTY]]

== References ==
((reflist))


== External links ==
* http://www.annies.nl/  AnnieS ToIP software for 2.5G GSM and 3G mobile terminals (in Dutch).
* https://archive.today/20130506213226/http://www.ictrnid.org.uk/talkbytext.html  RNID’s TalkByText software for mobile, web and PC based accesses
* https://archive.today/20130102005154/http://www.aupix.com/  Aupix AP-100 and AP-200 [[videophone]] with video, real-time text and voice
* http://www.ives.fr/ develops a web softphone with video, real-time text and voice including T.140 support based on eConf technology.
* http://sourceforge.net/projects/tipcon1/  Trace/Omnitor SIPCon1 open-source PC software with video, real-time text and voice
* http://asterisk.org  Asterisk open source IP multimedia exchange version 1.8.0 supports T.140 natively
* http://www.nextalk.com IP network based PBX and call center systems using ToIP to telephony gateways for TTY interoperability over [[PSTN]].
* http://www.packetizer.com/ipmc/diagnostics/cercalc.html Character Error Calculator for ToIP
* http://www.accessaphone.com/iptty/ Tenacity's [[ipTTY]] which is a SIP soft phone that supports TTY over IP.
* http://www.textspeak.com/ Text to Speech TTS in 24 languages over Ethernet, WiFi and TCP/IP
* http://realjabber.org - XMPP-based real-time text protocol based on XEP-0301

[[Category:IMS services]]
[[Category:Internet protocols]]
[[Category:Assistive technology]]

Pages transcluded onto the current version of this page (help):

Text over IP (edit)
Template:Ambox (view source) (template editor protected)
Template:Cite web (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Refimprove (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Text over IP.

Retrieved from "https://en.wikipedia.org/wiki/Text_over_IP"