Academia.eduAcademia.edu

Figure 1 – uploaded by Emre Dandıl

See full PDFdownloadDownload figure
Fig. 1. System architecture and infrastructure of the proposed video conference application developed mobile application was programmed ir the Android Studio [14] environment with the Javz programming language. Detailed information about other libraries and databases used in the study is presented in Table 1. 2.1 The Jitsi Meet Platform

Figure 1 System architecture and infrastructure of the proposed video conference application developed mobile application was programmed ir the Android Studio [14] environment with the Javz programming language. Detailed information about other libraries and databases used in the study is presented in Table 1. 2.1 The Jitsi Meet Platform

Related Figures (8)

Table 1. Detailed information about the libraries and databases used in the study
Table 1. Detailed information about the libraries and databases used in the study
Fig. 2. Jitsi components and architecture diagram [11] 3 The Developed Video Conferencing Mobile Application
Fig. 2. Jitsi components and architecture diagram [11] 3 The Developed Video Conferencing Mobile Application
Fig 3. Login and registration form interfaces of the developed mobile application
Fig 3. Login and registration form interfaces of the developed mobile application
The FCM service is based on sending incoming messages on the server to the relevant client and managing this sending process in a convenient way. In the application developed in this study, an FCM token is created for each user. This token is created at login and deleted when logged out. In the application, when the session is re-opened, a new updated token is registered in the database. The Retrofit library checks whether users are online by listening to user tokens in a created service database. Thanks to the token, users can send and receive call requests (push notification) among themselves. The creation of the token with FCM and the initiation ofa meeting invitation with the generated token are shown in Fig. 7 and Fig. 8, respectively.
The FCM service is based on sending incoming messages on the server to the relevant client and managing this sending process in a convenient way. In the application developed in this study, an FCM token is created for each user. This token is created at login and deleted when logged out. In the application, when the session is re-opened, a new updated token is registered in the database. The Retrofit library checks whether users are online by listening to user tokens in a created service database. Thanks to the token, users can send and receive call requests (push notification) among themselves. The creation of the token with FCM and the initiation ofa meeting invitation with the generated token are shown in Fig. 7 and Fig. 8, respectively.
Fig 5. Sending invitation and receiving invitation processes for conversation between two users in the application
Fig 5. Sending invitation and receiving invitation processes for conversation between two users in the application
Fig 9. Implementation of voice call with the developed mobile application In Fig. 10, screenshots of a video call in the mobile application environment developed with Jitsi Meet
Fig 9. Implementation of voice call with the developed mobile application In Fig. 10, screenshots of a video call in the mobile application environment developed with Jitsi Meet
In Fig. 9, the visuals of a voice call between two users in the developed mobile application interface are presented. Here, when the user approves the voice call request with the help of the FCM token, the FCM token notifies the sender that the invitation was approved and a conversation was started with the Jitsi Meet infrastructure. In voice call, Jitsi Meet uses encryption during transmission from user to server. Communication is encrypted before leaving the device and decrypted when it reaches the server. After processing, it is re-encrypted when leaving the server to be sent to the recipient. Thus, a secure voice call is provided between two users.
In Fig. 9, the visuals of a voice call between two users in the developed mobile application interface are presented. Here, when the user approves the voice call request with the help of the FCM token, the FCM token notifies the sender that the invitation was approved and a conversation was started with the Jitsi Meet infrastructure. In voice call, Jitsi Meet uses encryption during transmission from user to server. Communication is encrypted before leaving the device and decrypted when it reaches the server. After processing, it is re-encrypted when leaving the server to be sent to the recipient. Thus, a secure voice call is provided between two users.
infrastructure are denoted. In the video call, the process is operated as in the voice call. 4 Conclusion
infrastructure are denoted. In the video call, the process is operated as in the voice call. 4 Conclusion
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved