Sandbox vs Production weird behaviors Active Calls not available

  • 1
  • Problem
  • Updated 1 year ago
So in sandbox when we initiate a call it will appear in the active call response and after we ended the call when we query the active calls the last call will be listed and some details into it such as call duration etc. But in the production environment it seems that when we ended the call there are no more active calls available. Is it an api issue or are there any settings in the admin portal that affects this behavior? 
Photo of Bryan Bojorque

Bryan Bojorque

  • 310 Points 250 badge 2x thumb

Posted 1 year ago

  • 1
Photo of Bryan Bojorque

Bryan Bojorque

  • 310 Points 250 badge 2x thumb
https://devcommunity.ringcentral.com/ringcentraldev/topics/active-calls-question

Active call logs API not only keeps the track of Active calls but also keeps the track of most recent calls. The recent calls stays in the Active calls for 20-40 min.
While it takes sometime for the most recent call to appear in the call-logs generated by call log API, Active Call API  allows the look up for the most recent call as well as the on going call data.  
Photo of Benjamin Dean

Benjamin Dean

  • 8,602 Points 5k badge 2x thumb
That community response may be out of date (since it is a couple of years old). It should be 3-5 minutes for the duration that Active Calls are available once completed.

Could you retest using the metric that I have indicated, and confirm 3-5 minutes is the correct duration in which closed calls are visible in Active Calls API requests please?
Photo of Bryan Bojorque

Bryan Bojorque

  • 310 Points 250 badge 2x thumb
I did test it sir immediately query get active calls after the call was ended and it seems like the latest ended call is not being listed. Not unlike the sandbox api.
Photo of Benjamin Dean

Benjamin Dean

  • 8,602 Points 5k badge 2x thumb
Could you please provide the following information to help me diagnose if this needs escalated to our Engineering team for review:

1. The full API request (headers, body, footers) being used to request your ActiveCalls data.
2. The full response from the previous request (with headers, body, footers)
3. A screenshot of your call in the softphone being made (to support the request data being returned)