I was able to make RingOut using the SDK on sandbox. My app just got approved on prod. I was able to authenticate the request, received both access token and refresh token. However, when I actually make the call, my VOIP phone never rang. The result from the RingOut request was:
{
"id" : "s-a7180ed0b0ee7z1875cd4e581zc192470000",
"status" : {
"callStatus" : "InProgress",
"callerStatus" : "InProgress",
"calleeStatus" : "InProgress"
}
}
Can you clarify this "my VOIP phone"?
1. What is that phone?
2. Can you make a ring-out call manually from that phone?
3. Can you login the RC app or the RingCentral soft phone app and make a ring-out call manually, and also from your app to ring that phone?
My VOIP phone is the RingCentral app. I am able to make outgoing call using the RingCentral app. When I use the Sandbox URL and creds, my RIngCentral softphone app would ring making the "ring-out" API call and I was connected to the destination after answering that call.
The RingCentral softphone never rang when I use Production URL and creds to make the "ring-out" API call.
The analytic on the developer site is showing successful calls from last Friday when I ran the tests. However, neither did my softphone nor the destination number (my mobile phone) ever rang when I ran the tests.
I don't think that it's the ring-out API issue. It seems some extension or phone settings issue. Can you put the "from" and "to" number to your mobile numbers?
This is a screenshot of my call history from the Ring Central app. The call in the red box was made using the Sandbox URL and creds. The calls in the blue box was made using production URL and creds. The ringout requests were identical using the same outgoing and origination numbers. However, the one using Sandbox was an incoming call to my RingCentral number. Those calls using Production were outgoing calls but neither the "from" or the "to" numbers ever rang.
BTW, those outgoing calls that never rang had the opposite detail call info compares to calls that worked.
Sorry for the delayed response. But in this case, I think you should submit a support case so someone will look into your account and troubleshoot the issue.
7 People are following this question.
