Talkez h323

At the WC side. Display the video of the speaker among all the participants at the H323 EP side. If the H323 EP is itself the speaker among all the participants then display the video of the previous speaker among all the participants at that H323 EP. 6 The audio of the H323 End points will be sent to all other H323 End points except himself.H323CDEAdapter will mix the audio from the CDEMCU with the audio from all the H323 End Points and will send it back to CDE MCU. H323CDEAdapter will send the mixed audio of CDE MCU and the audio of all the H323 End Points except itself to each H323 End Point. 7 Following diagram describes the functional blocks for H323CDEAdapter and its interaction with CDEMCU: H323CDEAdapter CDEMCU Audio (Send/Receive) Video (Send/Receive) H323 MCU AV Client Protocol Entities 1 2 3 4 H323endpoint 8 In the implementation each of the H323 EP will have a audio buffer dictionary in which it will have audio buffer for each of the H323 EP except himself and an audio buffer for the CDE audio. We will also have a audio buffer dictionary for CDE MCU which will have audio buffer for every H323 EP. EP2 EP3 EP4 EP5 EP6 CDE EP1 EP2 EP1 EP3 EP4 EP5 EP6 CDE CDEMCU EP1 EP2 EP3 EP4 EP5 EP6 9 Implementation The classes that incorporate changes for the implementation of this requirement are: H323CAConferenceManager.cpp H323CAConnection.cpp H323CACDEConnection.cpp H323CAVideoBuffer.cpp 10 H323Connection* H323CAConferenceManager::CreateConnection (unsigned callRefValue){ //To check whether the no. of H323 EP logged in is less than six or not. If yes then // create a new connection for this H323 EP if( GetNoOfH323EP() iNoOfH323Login++; ssrc = dwH323SSRC & 0xff00ffff; // To generate the SSRC for the ssrc |= DWORD(iNoOfH323Login pH323Connection = new H323CAConnection(*this, callRefValue,ssrc); IncrNoOfH323EP(); // Increment the no. of H323 EP //logged in SetAnswerSend(false); } 11 BOOL H323CAConferenceManager::WriteH323Audio (const voidBOOL H323CAConferenceManager::WriteH323Audio (const void* buffer , PINDEX amount,const PString & thisToken,PString roomID, DWORD ssrc) { if ( DetectAudioLevel(buffer,amount) ) //If the audio packets coming are above audio // level Check the SSRC for H323 EP

List //Clear the H323 Audio count list and also the overall audio count list. // Clear the overall speaker video buffer and overall Previous Speaker // video buffer // Set the dOverallSpeakerSSRC and dOverallPrevSpeakerSSRC to zero. } void H323CAConferenceManager::SendReleaseComplete() { //Clear H323 EP list //Clear the H323 Audio count list and also the overall audio count list. } 18 void H323CAConferenceManager::AddH323Member(H323CAConnectionvoid H323CAConferenceManager::AddH323Member(H323CAConnection * newMember, DWORD ssrc) { // If this is the first entry in the room then create the room and video buffer and video position list // Add this H323 EP to the H323 EP list and add the audio count object for this end point in // H323AudioCountList and OverallAudioCountList. // Add the new member to every other H323 member // and every other H323 member to the new H323 member for (PINDEX i = 0; i PString token = H323EPList[i]; if (token != newToken) { H323CAConnection * conn = (H323CAConnection *) FindConnectionWithLock(token); if (conn != NULL) { conn->AddH323Member(newToken); newMember->AddH323Member(token); conn->Unlock(); } newMember->AddH323Member(CDEToken); // Add this H323 EP to the CDE 19 void H323CAConferenceManager::RemoveH323Member(H323CAConnectionvoid H323CAConferenceManager::RemoveH323Member(H323CAConnection * oldConn, DWORD ssrc) { //Clear the corner of the video window that the connection just vacated. // Remove the member from the other members // Remove the member from the CDE //Remove the audio count for this H323 EP from OverallAudioCountList //and H323AudioCountList // Check if the H323 EP that logs out is Overall Previous speaker and if yes // then set the // dOverallPrevSpeakerSSRC=0 // Remove the room if it becomes empty and call adapter logout request } 20 PINDEX H323CAConferenceManager::FindTokensVideoPosn(const PString &PINDEX H323CAConferenceManager::FindTokensVideoPosn(const PString & thisToken, PString roomID) { // To return the video Position of the H323 EP } BOOL H323CAConferenceManager::CheckH323EPSpeaker(DWORD SSRC) // To check the H323 Audio Packet for the speaker detection among the //H323 EP BOOL H323CAConferenceManager::CheckOverallSpeaker(DWORD SSRC) // to check the Audio Packet of either H323 EP or WC for the speaker //detection among the participants 21 BOOL H323CAConferenceManager::WriteVideo(const PString & thisToken,BOOL H323CAConferenceManager::WriteVideo(const PString & thisToken, const void * buffer, PINDEX amount, PString roomID, DWORD ssrc) { // This is called when video mode is

If the SIP server IP address or name is provided, you may have to specify the following parameters explicitly: Connection port (in case it is different from the standard 5060 port) Transport protocol used for sending media streams (UDP is selected by default). In such a case these parameters will be specified after the server address in the following way: :;transport=. Call string examples for SIP protocol: #sip:[email protected] #sip:[email protected]:5070 #sip:[email protected]:5070;transport=tcp #sip:james78 #sip:8001 #sip:@192.168.1.99 #sip:@192.168.1.99;transport=tcp #sip:@[fe80::805a:1cf9:12f9:def7] #tel:501 #tel:13478783263 # Calling mobile phones and landlines You can call a phone number using the dialer in the address book. For more information about this feature, please read the TrueConf client applications user guide. # Calling H.323 endpoints Use the following call string formats for calling an H.323 endpoint: #h323:@, where: is the IP address of an H.323 gatekeeper. #h323:@[], where: is the IPv6 address of an H.323 gatekeeper #h323:@, where: is the IP address of an H.323 gatekeeper or an MCU is an ID of a user or a device registered on an H.323 gatekeeper with an IP address specified in parameter. #h323:@[], where: is the IPv6 address of an H.323 gatekeeper or an MCU is an ID of a user or a device registered on an H.323 gatekeeper with an IP address specified in parameter. #h323:\e\@, where: is the IP address of an H.323 gatekeeper or an MCU is an E.164 format number of a user or device registered on an H.323 gatekeeper with an IP address specified in parameter. #h323:@, where: is the IP address of an H.323 gatekeeper. #h323:\e\@, where: — is an E.164 format number of an H.323 gatekeeper. If the IP address of the H.323 gatekeeper or MCU is included, it may be necessary to specify the connection port in an explicit way (when this port is different from the standard 1720 port). In this case it has to be specified after the IP address in the following way: #h323:@: Call string examples for H.323 protocol: #h323:@192.168.1.99 #h323:@192.168.1.99:1730 #h323:[email protected] #h323:@[fe80::805a:1cf9:12f9:def7] #h323:james78 #h323:\e\8001 # Calling RTSP endpoints To display an RTSP stream in the layout, add the video source as a participant to a group conference or a point-to-point call using the RTSP call string. In this way, you can access the video from an IP camera or another conference streamed over RTSP. The call string format may differ depending on the vendor or camera model. You need to

Presentation on theme: "H323 MCU Functionality."— Presentation transcript: 1 H323 MCU Functionality 2 Overview: Current version CDE allows single H323 End Point to join the audio/video conference using H323CDEAdapter Release The new version of CDE will allow creation/termination of an audio/video conference room in which multiple H323 End Points are able to join using H323CDEAdapter. In both the cases H323CDEAdapter will be considered as a single logical Web Client by the CDE MCU. 3 Operational Concepts and Scenarios:The AV Client is responsible for handling audio and video for a web client. Communication between CDEMCU and H323CDEAdapter is based on a protocol provided by NECST. The purpose of this protocol is to manage communication between CDEMCU and H323CDEAdapter. CDEMCU will send multiple audio buffers in a single stream; H323CDEAdapter will detect the speaker among the web clients. H323CDEAdapter will also detect the speaker among the H323 End Points The video display will depend upon the type of the video mode. There are basically two video modes: Mixed Video Mode Single Video Mode 4 In the mixed video mode the video display will be as : a) Mixed Video Mode In the mixed video mode the video display will be as : H323CDEAdapter will display quadrant image at the H323 End Point side. . First Quadrant Second Quadrant Third Quadrant Fourth Quadrant The image of the Web Client speaker will always be shown in the first quadrant. The image of the speaker among the H323 End Points will be shown at the second quadrant. The image of any two H323 end points other than the speaker will be switched between third and fourth quadrants. If H323 End Point, who was speaker and whose image was being displayed in the second quadrant logs out, then any of the H323 End Point image will be displayed in the second quadrant. In case there is no Web client present in the conference, the first quadrant will display gray screen. Same 4 quadrant image will be sent to CDE MCU server. 5 b) Single video mode Display the video of the speaker among the H323 EP