Voip Terminology & Concepts: Real-Time Transport Protocol, Session Initiation Protocol, IP Multimedia Subsystem, Session Border Controller

Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 31. Chapters: Real-time Transport Protocol, Session Initiation Protocol, IP Multimedia Subsystem, Session border controller, Lawful interception, STUN, Media Gateway Control Protocol, Wideband audio, PacketCable, Call Agent, Vishing, Multimedia Telephony, Traversal Using Relay NAT, VoIP VPN, Comfort noise, SIP Trunking, Voice chat, SIP connection, Softphone, Anti-tromboning, VoIP spam, Host Media Processing, Signaling gateway, Internet telephony service provider, Back-to-back user agent, Packet loss concealment, Voice engine, WebCall, White, black and grey routes, International gateway, Talkspurt, Voice peering, Chatter bug, Hookflash, Purple minutes, Call origination, Trunking gateway, Survivable Branch Appliance, Mouth-to-ear delay. Excerpt: The IP Multimedia Subsystem (IMS) is an architectural framework for delivering Internet Protocol (IP) multimedia services. It was originally designed by the wireless standards body 3rd Generation Partnership Project (3GPP), as a part of the vision for evolving mobile networks beyond GSM. Its original formulation (3GPP R5) represented an approach to delivering Internet services over GPRS. This vision was later updated by 3GPP, 3GPP2 and TISPAN by requiring support of networks other than GPRS, such as Wireless LAN, CDMA2000 and fixed line. To ease the integration with the Internet, IMS uses IETF protocols wherever possible, e.g. Session Initiation Protocol (SIP). According to the 3GPP, IMS is not intended to standardize applications but rather to aid the access of multimedia and voice applications from wireless and wireline terminals, i.e. create a form of fixed-mobile convergence (FMC). This is done by having a horizontal control layer that isolates the access network from the service layer. From a logical architecture perspective, services need not have their own control functions, as the...