Unreferenced stub auto yes date December 2009 An H.323 Gatekeeper serves the purpose of Call Admission Control and translation services from E.164 IDs commonly a phone number to IP addresses in an H.323 telephony network. Gatekeepers can be combined with a gateway function to proxy H.323 calls and are sometimes referred to as Session Border Controllers. A gatekeeper can also deny access or limit the number of simultaneous connections to prevent network congestion . H.323 endpoints are not required to register with a gatekeeper to be able to place point to point calls, but they are essential for any serious H.323 network to control call prefix routing and link capacities among other functions. A typical H323 Gatekeeper call flow for a successful call may look like Endpoint A Endpoint B 1234 1123 Endpoint A dials 1123 from the system. Endpoint A sends ARQ Admission Request to the Gatekeeper. Gatekeeper returns ACF Admission Confirmation with IP address of endpoint B. Endpoint A sends Q.931 call setup messages to endpoint B. Endpoint B sends the Gatekeeper an ARQ, asking if it can answer call. Gatekeeper returns an ACF with IP address of endpoint A. Endpoint B answers and sends Q.931 call setup messages to endpoint A. IRR sent to Gatekeeper from both endpoints. Either endpoint disconnects the call by sending a DRQ Disconnect Request to the Gatekeeper. Gatekeeper sends a DCF Disconnect Confirmation to both endpoints. The gatekeeper allows calls to be placed either Directly between endpoints Direct Endpoint Model , or Route the call signaling through itself Gatekeeper Routed Model . See also GNU Gatekeeper GNU Gatekeeper GnuGK Cisco Cisco IOS IOS release version 11.3 2 NA and 12.0 3 T Cisco Multimedia Conference Manager MCM Emblaze VCON Media Exchange Manager MXM TANDBERG Video Communication Server VCS Category ITU T recommendations Category Videotelephony Network software stub fr Gatekeeper ru H.323 ... more details
Unreferenced date October 2008 TransNexus , founded in 1997, is a commercial company providing software products for managing peering among VoIP networks. VoIP Peering is a concept that has grown from the practice of peering IP data networks. Evolution of VoIP Peering In the beginning of the Internet, IP networks interconnected through public peering points such as Metropolitan Area Ethernet MAE East located on Washington DC or MAE West located in San Francisco. These public peering points soon became overwhelmed by the growing amount of data traffic being exchanged between IP networks. To address this problem, private data network operators began to privately interconnect peer their networks. As VoIP technology developed, it was first deployed as a technology to bypass toll charges of the long distance telephone networks or Public Switched Telephone Network PSTN . VoIP networks were stand alone networks interconnected only with the PSTN. VoIP peering, however, is the growing practice of directly interconnecting VoIP networks. TransNexus, along with Cisco , 3Com and others was the creator of the ETSI Open settlement protocol OSP . The OSP protocol is global standard for enabling secure peer to peer VoIP routing and accounting without the need of an intermediary device, such as a proxy, session border controller or Back to Back User Agent B2BUA , in the VoIP signaling path. OSP peering is a general technique which may be used for any VoIP protocol i.e. H323, SIP or IAX and other IP communication transactions such as video, file sharing or short messaging. External links http www.transnexus.com Official website Category Networking companies of the United States ... more details
Orphan date February 2009 openCU is a cross platform, open source implementation of CU SeeMe , a video conferencing protocol, written in C . While the Session Initiation Protocol SIP and H323 needs human intervention, it is not really recommended for large conferences. openCU is made to close the gap between Multipoint Control Unit based expensive hardware solutions and proprietary, web based subscription solutions like Adobe breeze Macromedia Breeze or Webex from Cisco. The project, was initiated in October 2008 after Roozbeh joined the project. The goal is to create a self configuring, scalable, interactive, social , streaming platform for all operating systems. openCU employs a conference control protocol that has proven to be quite robust and allows for the expression of detailed state regarding the relations of each conference participant to each other participant. In conjunction with a reflector software it allows for customized distribution of conference media, so that nothing is transmitted unless it is used. The protocol is limited in the size of the conference it can serve, but our Who date November 2009 investigations have shown that this can be extended. The video is encoded in an ad hoc format that was designed for a particular family of desktop machines that were widespread in the past. What it lacks in mathematical elegance, it makes up for in quickness. http ipsix.org dundee4.pdf Comparison of Radvision Hardware MCU and CUSeeMe Networks Software MCU Citation needed date November 2009 The client software has alpha status and binary packages for Windows XP are available. The software is double licensed under the Affero General Public License Agpl . Recently added compressed media communication Xvid Speex encoding beside Raw format Gray16 PCM . Currently When date November 2010 working on text chat, x264 Advanced Audio Coding and porting to Linux BSD OSX. References http sattlers.org mickey CU SeeMe internetTVwithCUSeeMe index.html Internet TV with CU S ... more details
ITU Telecommunication Standardization Sector ITU T Recommendation Q.931 is the ITU standard Integrated Services Digital Network ISDN connection control Signaling telecommunications signalling Communications protocol protocol , forming part of Digital Subscriber Signalling System No. 1 . ref http www.itu.int rec T REC Q.931 en ITU T Recommendation Q.931 Digital subscriber Signalling System No. 1 ISDN user network interface layer 3 specification for basic call control ref Unlike connectionless systems like Internet Protocol TCP IP , ISDN is connection oriented and uses explicit signalling to manage call state Q.931. Q.931 typically does not carry user data. Q.931 does not have a direct equivalent in the Internet Protocol stack, but can be compared to Session Initiation Protocol SIP . Q.931 does not provide flow control or perform retransmission, since the underlying OSI model layers are assumed to be reliable and the Telecommunication circuit circuit oriented nature of ISDN allocates Bandwidth computing bandwidth in fixed increments of 64 Kilobit per second kbit s . Amongst other things, Q.931 manages connection setup and breakdown. Like Transmission Control Protocol TCP , Q.931 documents both the protocol itself and a protocol Finite state machine state machine . Q.931 was designed for ISDN call establishment, maintenance, and release of network connections between two DTEs on the ISDN D channel. Q.931 has more recently been used as part of the VoIP H323 H.323 protocol stack see H.225.0 and in modified form in some mobile phone transmission systems ref such as in GSM, where it is used for circuit switched call control between User equipment UE and Mobile Switching Center MSC ref and in Q.2931 ATM . A Q.931 frame contains the following elements Protocol discriminator PD Specifies which signaling protocol is used for the connection e.g. PD 8 for DSS1 Call reference value CR Addresses different connections which can exist simultaneously. The value is valid only during t ... more details
Cleanup date December 2007 Unreferenced date December 2007 In a telecommunications system, a Call Agent is a Media Gateway Controller MGC when used in the context of MGCP . It is concerned with the handling of specific services to users. MGCP is a server client protocol developed by Cisco, to make Industry Standard. MGCP is the only Server Client Voice communication protocol in existence. Other protocols SIP and H323 are called as Peer to Peer Protocols. MGCP being Open Standard any one can use it and Create their own Call agent for example http www.cisco.com en US products sw voicesw ps556 index.html Cisco Call Manager , other type of Call agent Examples are AVAYA IP EPABX, Nortel CS1000E etc, these are not using MGCP or SCCP, but some proprietary signalling pattern between the call agents and End points. Call Agent controls the signalling communication between Phones, Media Gateways like Routers on which PRI lines Terminate, ex Cisco 28xx Series Routers Now New versions of Cisco Voice Routers are released 29xx and 39xx , Media Gateways like Analog Extensions Also called as FXS in Cisco devices context like Cisco VG224 and VG248, VG202 and VG204 and Analog Trunks Also called as FXO in Cisco Device Context . Call Agent is responsible to register the end devices like phone and Media Gateways which act as dump terminals. After we have Dump extension registered to the call agent, when end device phone instrument handset headphone or speaker is picked up, the phone sends signal to call agent and informs that the phone handset has been picked up what to do, Call agent instructs the phone to give the dial tone. After the user listens to the dialtone, user enters the destination number to which they want to dial. Phone will send each digit immediately that is dialed by user one by one ie. First digit will be send first to call agent immediately it is dialed then second and so on . Call Agent receives the digits dialed by the phone. Call Agent identify that to which destina ... more details
port item type path nowiki code h323 Used with H.323 multimedia communications RFC 3508 code nowiki h323 user host port parameters nowiki code http HyperText Transfer Protocol HTTP resources RFC 1738 ... more details
Encyclopedia
top
