Closed pfeifel closed 7 years ago
So, found the problem in my code. thanks anyway.
@pfeifel
Glad to hear the problem was resolved. One thing to be aware of is that if the bot performs any "blocking" operations within its AudioSocket.AudioSendStatusChanged event, that will prevent other events, such as AudioMediaReceived, from being raised. The bot's code must ensure all handlers for media platform events execute quickly and do not block. Thanks.
Hi Stephen,
Thanks for the info. It seems to be working even without waiting for the send status to become active.
Eyal.
On Thu, Aug 17, 2017 at 8:42 PM, Stephen Sulzer [MSFT] < notifications@github.com> wrote:
@pfeifel https://github.com/pfeifel
Glad to hear the problem was resolved. One thing to be aware of is that if the bot performs any "blocking" operations within its AudioSocket.AudioSendStatusChanged event, that will prevent other events, such as AudioMediaReceived, from being raised. The bot's code must ensure all handlers for media platform events execute quickly and do not block. Thanks.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/BotBuilder-RealTimeMediaCalling/issues/27#issuecomment-323144155, or mute the thread https://github.com/notifications/unsubscribe-auth/AGNhueiZH5KvCmnqVxXyGKSxDmWK1RrIks5sZHuRgaJpZM4O56TC .
Is there a limitation on sending and receiving at the same time, from multiple threads? I have a solution that works if I am only receiving media, but when I start sending, it stops receiving messages.