Thank you for the update. I am still having issues with the author not logging correct when the call is to a call queue setup inside ringcentral. I think the user mapping might be why, as it used to work correctly before the user mapping feature.

Here is an example call log. When the call is made, it instantly logs as the admin account as 0 seconds. This call was answered by someone in the queue.

​@sburton The team is aware of this issue and will look into it upon their return from holiday in China. What is interesting is that this worked properly when you were NOT using server-side call logging, is that correct? 

I am wondering though - should we prevent calls being received by call queues from being logged? Keep in mind that when you have a call queue, and that call queue connects a caller to an agent, the call will still be logged by the agent. In this scenario, logging the call when it arrives as the call queue may actually be undesirable. Thoughts?

I believe the author worked correctly using server side logging before the user mapping feature, but I don’t think it ever worked with branch ring groups. In the same way, the RingCentral mobile app would not ring for an end user in a branch ring group, but would work if they were in a call queue. As call queues treat the call as if it was a direct call to the agent when answered (I think that is the proper way of looking at it).

Yes, having the call logged when the agent answers the call in a call queue would be the desirable option. That way, the call log shows the agent as the author.