[FIX] Livechat-jitsi-call #22678
[FIX] Livechat-jitsi-call #22678
Conversation
| @@ -33,9 +32,6 @@ API.v1.addRoute('livechat/video.call/:token', { | |||
| throw new Meteor.Error('invalid-livechat-config'); | |||
| } | |||
|
|
|||
| Messages.createWithTypeRoomIdMessageAndUser('livechat_video_call', room._id, '', guest, { | |||
There was a problem hiding this comment.
If you are removing this message creation function, then how will the agent know whether a jitsi call is initiated or not.
There was a problem hiding this comment.
And also are you allowing visitor to initiate Jitsi call?
There was a problem hiding this comment.
If you click on phone icon button, the agent will be redirected to new tab or the call will start on same tab depend on jitsi configuration done by administrator. The function I remove is responsible for join call button action that will appear in chat. I agree current solution is not correct solution, as by remove this function will remove the functionality of join call button which can be use in case agent by mistake close the call window. So I am working on that. But I think the error is in this function Messages.createWithTypeRoomIdMessageAndUser only because as I remove this function api is working fine. I am able to get responses as shown in the above image at widget side.
No, I am not allowing visitors to initiate the call. Above response I got from api after the visitor clicks on the accept button at widget side and then response will be used for generating a link for jitsi at widget side.
murtaza98
force-pushed
the
livechat-calls
branch
from
118373c to
01a3f00
Compare
murtaza98
force-pushed
the
livechat-calls
branch
2 times, most recently
from
a272f80 to
8085535
Compare
Current if you make get request http://localhost:3000/api/v1/livechat/video.call/: token with Livechat.videoCall() at widget side, it was showing bad request because there was some error at rc-core server file. But after doing changes at rc-core server side and making an api call with Livechat.videoCall , now I am getting the expected result at widget side as shown in the image below.
