App ID: Sf_MHvJ_RSCNbASqY4hw-g~yH9spVm3RZSAmcwoDLI7hg
App Name: Xima CCaaS
App Link: https://ai-developer.ringcentral.com/administration.html#/application/Sf_MHvJ_RSCNbASqY4hw-g~yH9spVm3RZSAmcwoDLI7hg
Env: Production

I have also created a support ticket. case number 15233463

We have a call that comes into our SIP handset. TelephonySessionId=s-a0dd87208502fz180a94f0c42z16963390000

Then with our sip handset we make the call to an agent. TelephonySessionId=s-a0dd8651384ccz180a94f70a2z8549130000

Once that agent is talking we finish the Attended Tranfser.

According to the SIP messages that we see on our end the AttendedTransfer completed. So our system thinks the agent (Crystal Geiger extension 686) has answered the call and the REFER message got an OK response.

The API says that the transfer went through but then never sends the DISCONNECT event on the s-a0dd8651384ccz180a94f70a2z8549130000 call id. We do see a single DISCONNECT on the second call Id s-a0dd87208502fz180a94f0c42z16963390000.

The Call Logs in the RingCentral system say that the agent missed the call but it lasted 10 minutes. Is that expected? Is there a bug on your end?

We did end up hitting the call log API and it shows the call was there for the 10 minutes as we see afterwards with the 10 minute missed call. Our customer is complaining that the agent was stuck tied to this call for 10 minutes when from their end it seemed the call was over and they should be available.