http://debianws.lexgopc.com/wiki143/index.php?action=history&feed=atom&title=Telephony_application_server 2026-10-26T16:19:11Z Revision history for this page on the wiki MediaWiki 1.43.1 http://debianws.lexgopc.com/wiki143/index.php?title=Telephony_application_server&diff=3103879&oldid=prev 2024-12-11T20:36:22Z

<p>chg unref. to one source tag; ► Wikipedia:WikiProject Unreferenced articles; <a href="/wiki143/index.php?title=WP:URA&amp;action=edit&amp;redlink=1" class="new" title="WP:URA (page does not exist)">you can help!</a> ●</p> <p><b>New page</b></p><div>{{One source|date=December 2024}}<br /> <br /> The term &#039;&#039;&#039;telephony application server&#039;&#039;&#039;&lt;ref&gt;{{cite web |title=What is Telephony Application Server (TAS)? |url=https://www.dialogic.com/glossary/telephony-application-server-tas |website=dialogic.com |access-date=11 December 2024}}&lt;/ref&gt; refers to an entity in a [[telephone network]] that carries out functions that are not directly related to the routing of messages through the network.<br /> <br /> Such functions can include in-network [[answering machine]]s, 800 ([[freephone]]) numbers, automatic [[call forwarding]], [[conference call|conference]] bridges and many other types of application. In integrated telephone networks, these are mostly implemented as functions in the [[telephone exchange]], but in more open networks such as [[IP telephony]] networks based on the [[Session Initiation Protocol|SIP]] protocol, these are often separate [[computer]]s.<br /> <br /> In contexts where it is obvious that one is talking about telephony, such as RFC 3057, one often just calls them &quot;application servers&quot;; this is also common in the context of SIP (for instance in RFC 4240), because proponents argue that SIP is applicable to a much wider range of applications than just telephony.<br /> <br /> The application server provides call-termination or subscriber-independent applications. These include such capabilities as local number portability, [[free-call]] routing resolution, conference bridge services, and [[unified messaging]]. The [[PSTN]] versions of these applications are frequently known as 800 numbers in North America. The subscriber has to explicitly place a call to the application server.<br /> <br /> Application server applications are of two general types, those that are signaling only, and those that involve media manipulation. The former are often related to routing resolution—local number portability, free-call routing, and other services where the dialed number must be translated to a routable address. An example involving media manipulation would be conference bridge applications, something with which most business people are very familiar. The call steps include<br /> <br /> *Each user calls in on a pre-published number. <br /> *The dialed number is translated into an IP address and named the endpoint of the application server, and the call is routed there. <br /> *The application server connects to the media server, instructing it to play a greeting and collect the conference number. <br /> *The media server returns and conference number, and the application server instructs the media server to play a prompt to collect the authorization number. <br /> *If the digits collected are correct, the application server tells the media server to move this call to a particular conference bridge.<br /> <br /> ==References==<br /> {{reflist}}<br /> <br /> [[Category:Telephony]]</div>

imported>JoeNMLC