Saibabu Malisetti

First of all thanks a lot for your response @shawnmcknight . We have an existing Monolithic App that is written in Typescript, GraphQL based on NestJS and Type ORM. So...

Thanks for this thread and it kind of gives options for us to similar issue we are aiming to resolve. The only thing we like to know is how can...

@ujwal-setlur and @teezzan we managed to get it working by using "Flow-2" approach as per my message above and I presume you also must have used Flow-2. If by any...

thanks @ujwal-setlur for confirming this. Your confirmation aligns with our implementation of Flow-2, cheers

Hello i am having similar issue, can you pls. check if you can help the issue https://github.com/HenningM/express-ws/issues/116 please?

the other approach is to listen for "incomingMessage" and "outgoingMessage" events as per the JITSI documentation [here](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-iframe-events#incomingmessage) by using the API object created for each conference on on participant side.,...

Following up further, i have done some more research and here are my findings.... 1. Removed all JITSI/* docker images from my local docker registry. 2. then i executed steps...

> i just took a look at `https://github.com/jitsi/jitsi-meet/blob/master/config.js` but i don't see any property like `recordingSharingUrl ` for us to configure through `configOverwrite` option.

Ok, thanks @damencho for insights. SO let me put my understanding.... 1. the `recordingLinkAvailable` event as mentioned [here ](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-iframe-events#recordinglinkavailable) will get triggered only if we start the conference using JaaS...

ok we tried the option of naming our JITSI Tenant as JaaS one as follows... also we registered event Listener for `recordingLinkAvailable ` With the below configuration we tried both...