Ringing does not work if call created on server side

[KestasVenslauskas]

Ringing does not work if a call is created on a server side using REST.

Call contains all members. But if another user tries to call ring() it says no users to ring

Example code on flutter (note that call has already been created in the backend):

  final call = StreamVideo.instance.makeCall(
        callType: StreamCallType.custom('appointment'),
        id: callId,
      );

      await call.getOrCreate(
        memberIds: [_sessionRepository.userId!, patientId],
        ringing: true,
        video: true,
      );

      final members = await call.queryMembers();
      final memberIds = members.getDataOrNull()?.members.keys.toList() ?? [];
      logger.w('call $memberIds');

      await call
          .ring(userIds: memberIds, video: true)
          .then((list) => logger.d('Ringing result: $list'))
          .catchError((error, stackTrace) {
            logger.e('Error ringing call: $error');
          });

Ringing result: Result.Failure{error: VideoErrorWithCause{message: {"code":4,"message":"RingCall failed with error: \"no users to ring\"","StatusCode":400,"duration":"0.00ms","more_info":"https://getstream.io/chat/docs/api_errors_response","details":[]}, exception: ApiException 400: {"code":4,"message":"RingCall failed with error: \"no users to ring\"","StatusCode":400,"duration":"0.00ms","more_info":"https://getstream.io/chat/docs/api_errors_response","details":[]}, stackTrace: #0 ProductvideoApi.ringCall (package:stream_video/open_api/video/coordinator/api/productvideo_api.dart:2262:7)

If I would change the callId with different one that does not already exist the ringing would work.

[KestasVenslauskas]

Sorry looks like I found the hidden behaviour.
If a user is not a creator of a video call he is not able to ring the others. Is that right?

[Brazol]

Hey @KestasVenslauskas sorry for the delayed response. It shouldn’t be limited to just the creator being able to ring others. Most likely, the SendEvent permission is required for any call member to trigger ringing.

From the error you shared, it seems more likely that the patientId was invalid (e.g., referencing a non-existent user) or that the user was already in a call. Are you still experiencing this issue?

[KestasVenslauskas]

@Brazol Just double checked user role permissions on getstream dashboard, and both roles have SendEvent permission granted.
While I was testing both users did exist and I was not in the call with the call owner at that moment. I think this should be reproducible on your side.

Our call room is created on our backend using REST api with A & B users set as participants and user B is the owner.
This way user B is able to rint to user A but user A is not able to ring user B. This should be reproducible on your side I just don't have any public repo to share for now.