Skip to main content
The First Step
February 9, 2018
Question

RingOut problem - why did the "to" phone become the first leg and "from" phone the second leg?

We developed all features with RingOut API in sandbox for our web application. Yesterday it worked perfectly.Today strange things happened. When made call, somehow the "to" phone became first leg and "from" phone the second leg. The response after RingOut request was as something like

{
    "id": "Y3MxNjk2MTIzOTgyNDMyMTUyMDlAMTAuMjguMjAuMTEw",
    "uri": "https://platform.devtest.ringcentral.com/restapi/v1.0/account/~/extension/~/ringout/Y3MxNjk2MTIzOTgyNDMyMTUyMDlAMTAuMjguMjAuMTEw",
    "status": {
        "callStatus": "Invalid",
        "callerStatus": "Invalid",
        "calleeStatus": "Invalid"
    }
}Can someone let me know what went wrong?

22 replies

The First Step
February 21, 2018
Thx for the heads-up!  I was thinking that might happen.
New Participant
February 26, 2018
Is there any update on this from a RingCentral rep?  Our integration is working in reverse suddenly and I am hesitant to change the code if it is likely to be changed back.  An ETA on any potential fixes would be helpful in determining next steps for us.
The First Step
February 26, 2018
I reversed the to/from as someone mention higher in the forum.  It was working last week great.  RingCentral said they were going to push out a fix this weekend, which I would have thought would break it again after reversing the to/from, but our ringout tool is still working this morning - so not sure what if anything happened this weekend.
The First Step
February 26, 2018
Thanks for the update Brian.  Still working here too.  
New Participant
February 27, 2018
Reversing the to/from has no effect for me.  It's still calling the destination first and prompting them to "Press 1 to connect", and then ringing my RC phone only after the person I'm trying to call has pressed 1.  Exactly the opposite of what it had been doing.  I can't get it to function properly at all now.  Really frustrating, as this was working perfectly before.
New Participant
March 13, 2018
Is there an ETA for a fix on this?  The last update was a link back to this discussion.  Is it smart for me to reverse the parameters at this point?  That seems like an awful idea. If there is a fix coming soon I'd like to avoid that if possible.
The First Step
March 15, 2018
Appears the code may be back to the original now.  We are having issues again today with ring out. Getting ready to revert to original code on my end and will report back it that fixes it.
The First Step
March 15, 2018
Same here -  had to go back to old code as of Wednesday morning.
The First Step
March 15, 2018
Well it shifted back the other way this morning - not sure what is going on
The First Step
March 15, 2018
Yeah. I couldnt get it working last night when I reverted back to original code. Maybe Ill try the recent working code again today to see it works again.