Ant-Media-Server
Ant-Media-Server copied to clipboard
ant-media
proprietary encryption in payload
Hi, We use Ant Media APIs to implement a proprietary conference call application client, from the development point of view all required API support is available except in the case if we try to encrypt the video and chat using our proprietary encryption. Could you advise us on how we can encrypt the video and data (chat content) using our algorithms?
We installed Ant Media on the customer's private server.
Hi @daosmeet ,
Thank you for asking this question.
Technically, yes it's possible to use your proprietary encryption in WebRTC. Practically, you just need get the WebRTC stack and change encryption algorithm there and build the WebRTC stack again. https://webrtc.googlesource.com/
You need to do this for every SDKs. For instance if you use android SDK or iOS SDK, you also need to build the WebRTC stack for Android and iOS with your proprietary encryption. I think a kind of roadmap below is OK to proceed.
- Change the WebRTC stack and use your proprietary encryption
- Run the sample applications in WebRTC stack that uses your proprietary encryption
After you confirm that, we can share the Ant Media's patch for WebRTC stack and instructions to build the WebRTC stack for the server side.
Is that ok for you?
Hi,
The idea is End-to-End encryption and the server shouldn't make any decryption/encryption processes only endpoints have access to do that. Does your change proposal support the idea (End-to-End encryption) of what we are looking for?
Regards, Mostafa
Hi Mostafa,
I understand your requirement.
My idea is not the End-to-End encryption. Server need to decrypt the video/audio in order to record or any other operations.
In order to support End-to-End encyrption, we need to make some important changes on the server side. We're starting to work on WebRTC stack side. We can analyze E2E encyrption feasibility on our end. I think it takes a least a few weeks to confirm if it's feasible or not.
Btw, how's your timeline? Is this an urgent issue for you?
Hi Yash,
We have start integration to test WebRTC soon with application latest on middle of Jun. So, I need to know latest on 17th of Jun the result that can go with your WebRTC or not. The End-to-End encryption is essential in our use case, the server should be as a bridge and should not involve in any circumstance to manipulated user Video/Voice/Data, just forward and as signalling services. Is it possible to get the feasibility study latest on 17th of Jun? Can you implement this feature, If the feasibility study results is that it is possible to do this feature?
Regards, CTO Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 23. May 2022, at 10.51, Ahmet Oğuz Mermerkaya @.@.>> wrote:
Hi Mostafa,
I understand your requirement.
My idea is not the End-to-End encryption. Server need to decrypt the video/audio in order to record or any other operations.
In order to support End-to-End encyrption, we need to make some important changes on the server side. We're starting to work on WebRTC stack side. We can analyze E2E encyrption feasibility on our end. I think it takes a least a few weeks to confirm if it's feasible or not.
Btw, how's your timeline? Is this an urgent issue for you?
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1134308590, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC3Z7BKDY3JWQPZ7PJGDVLM2GJANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Hi @daosmeet ,
Thank you for your response
Is it possible to get the feasibility study latest on 17th of Jun?
Yes, it's possible to get the feasbility study on 17th of Jun.
Can you implement this feature, If the feasibility study results is that it is possible to do this feature?
Yes, if it seems feasible, we can implement this feature. It's something that adds value to the product.
We'll make the feasibility in the scope of this issue https://github.com/ant-media/Ant-Media-Server/issues/3076
Hi Ahmet!
Any news regarding End-to-End video, voice and data channel encryption possibility functionality development progressing?
Regards, CTO Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 23. May 2022, at 13.58, Ahmet Oğuz Mermerkaya @.@.>> wrote:
Hi @daosmeethttps://github.com/daosmeet ,
Thank you for your response
Is it possible to get the feasibility study latest on 17th of Jun?
Yes, it's possible to get the feasbility study on 17th of Jun.
Can you implement this feature, If the feasibility study results is that it is possible to do this feature?
Yes, if it seems feasible, we can implement this feature. It's something that adds value to the product.
We'll make the feasibility in the scope of this issue #3076https://github.com/ant-media/Ant-Media-Server/issues/3076
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1134523767, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC32XZ5XLFOL6STTRZWDVLNQEBANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Hi @daosmeet ,
Thank you for follow up. I plan to give something in this week. There were some unexpected issues that steal my time. Sorry for that
Hi @daosmeet,
Late is better than never. Sorry for that. I just have change to work with these issues.
Fortunately, interface supports custom encryption and decryption. You can set custom encryptor and decryptor
Even if interface supports that native implementation is required for that
Do you have expertise in these kind of implementations?
Hi Ahmet,
In our use case the purpose is to implement native iOS, Android mobile app as well as separate applications for Windows and Mac. My question is that how Ant Media Api and SDK can be use and apply to in implement proprietary encryption using SDK in case of Mobile native App and laptops?
Do you provide also SDK to support proprietary encryption for Video, Data channel?
Regards, CTO Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 4. Jul 2022, at 17.09, Ahmet Oğuz Mermerkaya @.@.>> wrote:
Hi @daosmeethttps://github.com/daosmeet,
Late is better than never. I just have change to work with these issues.
Fortunately, interface supports custom encryption and decryption. You can set custom encryptorhttps://github.com/ant-media/Ant-Media-Server/blob/master/src/main/java/org/webrtc/RtpSender.java#L97 and decryptorhttps://github.com/ant-media/Ant-Media-Server/blob/master/src/main/java/org/webrtc/RtpReceiver.java#L77
Even if interface supports that native implementation is required for thathttps://github.com/ant-media/Ant-Media-Server/blob/master/src/main/java/org/webrtc/FrameEncryptor.java
Do you have expertise in these kind of implementations?
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1173866003, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC33K325XH5DJEGJZZZTVSLWDJANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Hi Mostafa @daosmeet ,
It seems that SDK supports the custom encryption however there should be native side of the custom encryption. It requires good level of understanding the native codes. Currently, we don't support this function. Fortunately, any developer having the expertise can make it.
There is an also insertable-streams option on the table. I'm not fully familiar with them. It provides E2E encryption in this sample. Check this out I'm just getting familiar with these things and I may provide some more information later.
If you would like to be part of it or you don't wait for me, you can also make some googling and we can discuss together.
Hi Ahmet!
What you mean by " Currently, we don't support this function”? Do you mean that And Media SDK doesn’t support E2E encryption?
Regards, CTO Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 6. Jul 2022, at 13.43, Ahmet Oğuz Mermerkaya @.@.>> wrote:
Hi Mostafa @daosmeethttps://github.com/daosmeet ,
It seems that SDK supports the custom encryption however there should be native side of the custom encryption. It requires good level of understanding the native codes. Currently, we don't support this function. Fortunately, any developer having the expertise can make it.
There is an also insertable-streams option on the table. I'm not fully familiar with them. It provides E2E encryption in this sample. Check this outhttps://webrtc.github.io/samples/src/content/insertable-streams/endtoend-encryption/ I'm just getting familiar with these things and I may provide some more information later.
If you would like to be part of it or you don't wait for me, you can also make some googling and we can discuss together.
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1176069086, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC33W4XXWTJYED6XGMMLVSVPL3ANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
In order to function properly, the SDK and server side should support. Currently SDK supports but Server side does not have support. Sorry.
Hi Ahmet,
This case already known on May when I ask you the same question and you told that it requires to modify server and SDK/API to support End-To-End Video, Voice and Data channel encryption nothing has been changed from May when got the same message. Then on the lates of May you told me you can make changes to and provide me this solution latest on middle of Jun and know we are on July with same situation. My team was expecting to get you WebRTC solution as part of in-house WebRTC with proprietary End-To-End encryption now we lost 2 month even you knew that this is situation on May and promised to provide me this solution. It’s almost 2 months we was waiting you to provide us solution. This proposal came from you that you can modify and provide us functional solution. I am really disappointed to hear that why you promised even you didn’t wanted to do that?
Regards, CTO Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 18. Jul 2022, at 20.40, Ahmet Oğuz Mermerkaya @.@.>> wrote:
In order to function properly, the SDK and server side should support. Currently SDK supports but Server side does not have support. Sorry.
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1187905127, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC3ZNHS4DHB5QUQHMLSDVUWJHPANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Hi Ahmet!
Asioiden selventämiseksi ja ymmärtämiseksi haluaisin tietää, riittääkö iOS-, Android-, Window- ja Mac-sovellusten kehittämiseen SDK:n käyttö päästä päähän -salauksen tekemiseen vai tarvitseeko myös palvelinta muokata niin, että se tukee pääte-salausta. salaus loppuun asti.
Tarkoituksenamme on kehittää WebRTC-konferenssipuheluasiakassovellus iOS:lle, Androidille, Macille ja Windows 10/11:lle. Tekeekö nykyinen SDK-tuki päästä päähän -salausta muuttamatta palvelimen ohjelmistoa?
On tärkeää tietää, miten saamme asian toimimaan, jos SDK tukee päästä päähän -salausta koskematta palvelinohjelmistoon. Joka tapauksessa palvelin, joka käyttää välitys NAT:ia” (TURN) sallii asiakkaiden lähettää ja vastaanottaa dataa välipalvelimen kautta tai STUN-muodossa saadakseen selville asiakkaan julkisen osoitteen, jos niin miksi meidän pitää vaihtaa palvelinohjelmistoa?
Regards, CTO, Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 18. Jul 2022, at 20.40, Ahmet Oğuz Mermerkaya @.@.>> wrote:
In order to function properly, the SDK and server side should support. Currently SDK supports but Server side does not have support. Sorry.
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1187905127, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC3ZNHS4DHB5QUQHMLSDVUWJHPANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Hi Ahmet!
Sorry wrong language!
To clarify and understand things better, I would like to know if we use of SDK to develop iOS, Android, Window and Mac apps are enough to make end-to-end encryption or do you also need to modify the server to support end-to-end encryption. Our purpose is to develop the WebRTC Conference call client for iOS, Android, Mac, and Windows10/11. Does current SDK support make End-To-End encryption without changing the server SW? It is important to know how we can make the thing works if SDK supports the end-to-end encryption without touching server SW. Anyway server using relay NAT” (TURN) allows clients to send and receive data through an intermediary server or as STUN to find out the client's public address if so why do we need to change serve SW?
Regards, CTO Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 20. Jul 2022, at 8.50, Mostafa Hanifi @.@.>> wrote:
Hi Ahmet!
Asioiden selventämiseksi ja ymmärtämiseksi haluaisin tietää, riittääkö iOS-, Android-, Window- ja Mac-sovellusten kehittämiseen SDK:n käyttö päästä päähän -salauksen tekemiseen vai tarvitseeko myös palvelinta muokata niin, että se tukee pääte-salausta. salaus loppuun asti.
Tarkoituksenamme on kehittää WebRTC-konferenssipuheluasiakassovellus iOS:lle, Androidille, Macille ja Windows 10/11:lle. Tekeekö nykyinen SDK-tuki päästä päähän -salausta muuttamatta palvelimen ohjelmistoa?
On tärkeää tietää, miten saamme asian toimimaan, jos SDK tukee päästä päähän -salausta koskematta palvelinohjelmistoon. Joka tapauksessa palvelin, joka käyttää välitys NAT:ia” (TURN) sallii asiakkaiden lähettää ja vastaanottaa dataa välipalvelimen kautta tai STUN-muodossa saadakseen selville asiakkaan julkisen osoitteen, jos niin miksi meidän pitää vaihtaa palvelinohjelmistoa?
Regards, CTO, Mostafa Hanifi @.@.> https://daosmeet.com
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
On 18. Jul 2022, at 20.40, Ahmet Oğuz Mermerkaya @.@.>> wrote:
In order to function properly, the SDK and server side should support. Currently SDK supports but Server side does not have support. Sorry.
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1187905127, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC3ZNHS4DHB5QUQHMLSDVUWJHPANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Hi Mostafa,
Please take it easy. I don't want to defend myself against you. Let's have a better communication, understand the status and think of what we can do for the solution.
In May, we only know that E2E is not supported, today we know SDK supports E2E and there are some methods already available in the server side and client side to have custom encryption. I am sorry for your time. Please let me express myself, I didn't give my word to support E2E in this time frame. I just take a look at the feasibility. Sorry for the misunderstanding. Please also keep in mind that we're under pressure for the workload and there are some tasks having a higher priority. I think you probably know and feel what I meant to say.
To clarify and understand things better, I would like to know if we use of SDK to develop iOS, Android, Window and Mac apps are enough to make end-to-end encryption or do you also need to modify the server to support end-to-end encryption. Our purpose is to develop the WebRTC Conference call client for iOS, Android, Mac, and Windows10/11. Does current SDK support make End-To-End encryption without changing the server SW? It is important to know how we can make the thing works if SDK supports the end-to-end encryption without touching server SW. Anyway server using relay NAT” (TURN) allows clients to send and receive data through an intermediary server or as STUN to find out the client's public address if so why do we need to change serve SW?
If you use Peer to Peer mode (mesh networking), SDK supports End-to-End encryption. It's likely that this is not your case. You likely need to have a scalable solution so that the server needs to support E2E encryption for the client side. Because data is relayed through server.
Let's talk about the solution, even if it's challenging to say for me, we currently work on webrtc stack upgrade to support AV1 and in the second phase of this work, we can support E2E encryption. I think it will also increase the performance of the server indirectly. ETA for this work is the end of this year. Please believe me, I really wish to give solution right now with my full heart to you. On the other hand, you know there are resources, commitments as you have.
My recommendation for you is that let's start the conference call implementation on your end and you'll have E2E at the end of this year. You will just change some simple things on the client side to enable E2E.
Have a great day.
Regards, A. Oguz
Hi Ahmet,
Could you kindly keep me up to dated, when you could possibly during this year provide end-to-end encryption?
Regards, CTO, Mostafa Hanifi @.@.> https://daosmeet.comhttps://daosmeet.com/
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
Sent from my iPhone
On 20. Jul 2022, at 10.12, Ahmet Oğuz Mermerkaya @.***> wrote:
Hi Mostafa,
Please take it easy. I don't want to defend myself against you. Let's have a better communication, understand the status and think of what we can do for the solution.
In May, we only know that E2E is not supported, today we know SDK supports E2E and there are some methods already available in the server side and client side to have custom encryption. I am sorry for your time. Please let me express myself, I didn't give my word to support E2E in this time frame. I just take a look at the feasibility. Sorry for the misunderstanding. Please also keep in mind that we're under pressure for the workload and there are some tasks having a higher priority. I think you probably know and feel what I meant to say.
To clarify and understand things better, I would like to know if we use of SDK to develop iOS, Android, Window and Mac apps are enough to make end-to-end encryption or do you also need to modify the server to support end-to-end encryption. Our purpose is to develop the WebRTC Conference call client for iOS, Android, Mac, and Windows10/11. Does current SDK support make End-To-End encryption without changing the server SW? It is important to know how we can make the thing works if SDK supports the end-to-end encryption without touching server SW. Anyway server using relay NAT” (TURN) allows clients to send and receive data through an intermediary server or as STUN to find out the client's public address if so why do we need to change serve SW?
If you use Peer to Peer mode (mesh networking), SDK supports End-to-End encryption. It's likely that this is not your case. You likely need to have a scalable solution so that the server needs to support E2E encryption for the client side. Because data is relayed through server.
Let's talk about the solution, even if it's challenging to say for me, we currently work on webrtc stack upgrade to support AV1 and in the second phase of this work, we can support E2E encryption. I think it will also increase the performance of the server indirectly. ETA for this work is the end of this year. Please believe me, I really wish to give solution right now with my full heart to you. On the other hand, you know there are resources, commitments as you have.
My recommendation for you is that let's start the conference call implementation on your end and you'll have E2E at the end of this year. You will just change some simple things on the client side to enable E2E.
Have a great day.
Regards, A. Oguz
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1189912907, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC37DIVEMX5SIT6LK7YLVU6REBANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>
Thank you Ahmed!
Regards, CTO, Mostafa Hanifi @.@.> https://daosmeet.comhttps://daosmeet.com/
Daosmeet Oy Ltd A Head Office of Daosmeet Oy Ltd, a limited company registered in Finland and whose registered address is Huopalahdentie 24, 00350 Helsinki, Finland. This email (including any attachments) is private and confidential, and may be privileged. It is for the exclusive use of the intended recipient(s). If you have received this email in error, please inform the sender immediately and then delete this email. Unless you have been given specific permission to do so, please do not distribute or copy this email or its contents.
Unless the text of this email specifically states that it is a contractual offer or acceptance, the sender does not intend to create a legal relationship and this email shall not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Daosmeet Oy Ltd.
Sent from my iPhone
On 19. Aug 2022, at 14.28, Ahmet Oğuz Mermerkaya @.***> wrote:
Hi Mostafa, ETA is the end of this year for this feature.
Regards, A. Oguz
— Reply to this email directly, view it on GitHubhttps://github.com/ant-media/Ant-Media-Server/issues/4173#issuecomment-1220561683, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBOC3YDCNN76ITLXPUB6GDVZ5VUZANCNFSM5VHUPTZA. You are receiving this because you were mentioned.Message ID: @.***>