News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Search
Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Sandbox unexpectedly gets "The number you dialed is not in service at this time." - is there a limit to the number of times we can call our sandbox account?
Tags: sandbox
Jan 18, 2016 at 7:45am   •   8 replies  •  0 likes
polar-operations

I have set up a private app that I'm testing in the sandbox. While testing, I suddenly get the following message when I dial the sandbox phone number:


"The number you dialed is not in service at this time. Thank you for calling. Goodbye"


Is there a limit to how many times we can call our sandbox account per day? I am able to send text messages to the number and I get them via the subscription API programatically.


I had just figured out how to subscribe to events and was making great progress on our internal app when this happened.


Thanks!

--Ed

8 Answers
answered on Jan 29, 2016 at 1:31am  

Hi Ed,

Perhaps there was a setting configuration that was not enabled on the Number and we have got this issue resolved now.

Kindly continue with the development activities and if you have any concerns feel free to reach out to us via email or submitting a support ticket.


 0
answered on Jan 27, 2016 at 5:01am  
Benjamin,

I opened a ticket over a week ago and they still haven't resolved the issue or helped identify why my main number on the sandbox account now gets a "no longer in service" message. Regardless of extension configurations, I would think the main line would still ring when we call it.

We need to validate the APIs can meet our needs soon or we'll be forced to look at other VoIP solutions. We've been a RingCentral customer for almost two years and I'd rather not move but tying our phones into our back office systems is a requirement as we grow.

--Ed

 0
answered on Jan 18, 2016 at 12:38pm  
Hey Ed,

I'm not sure what is causing that issue. You'll want to submit a support ticket to get the core team to help diagnose.

Thanks for sharing the bad href in that link, I've submitted a ticket for fixing.

 0
answered on Jan 18, 2016 at 11:57am  
No luck. I've set up an extension with a softphone as outlined in your tutorial.  I can make outgoing calls without a problem but get the same error message when I try an incoming call.

--Ed

BTW: You've got a bad link in that tutorial. In the " Configure Sandbox Account" section you show " Go to https://service.devtest.ringcentral.com" but the underlying link is to platform.devtest.ringcentral.com)

 0
answered on Jan 18, 2016 at 10:57am  
I'm guessing that the one user in your Sandbox account is an admin (typically this is extension 101)?

Could you click on the Phones & Devices for that user, and make sure you have added a phone (under 'phones', click on "Add Phone", then enter a physical device number in there which you own). I think that's what's causing the issue (if you haven't added a phone for that user yet). Let me know if that works. :)

 0
answered on Jan 18, 2016 at 10:02am  
I am pretty sure everything is set up properly.  This shows the sandbox application:

When I click on the "Web Dashboard" app, here's the Application Credentials:

and the Account Information:
 

You can see the number I am dialing that I'm reporting:

I have dialed this from two phones that are not Ring Central lines, both resulting in the same error.

I did log into the https://service.devtest.ringcentral.com/ site and created a virtual phone number for the primary user (802) 448-8980 since one wasn't there:

That doesn't appear to change anything. (and I get the same not in service message for that number as well)

Thanks again for your assistance.

--Ed

 0
answered on Jan 18, 2016 at 8:39am  
Hey Benjamin,

I am using the number that RingCentral assigned to the developer account. This worked on Friday and this morning but stopped working about an 90 minutes ago. When I say worked, I dialed the number and got the attendant. I was unable to programmatically get any events until about an hour ago but was able to use the API Explorer on Friday and query the "Call Log".

--Ed

 0
answered on Jan 18, 2016 at 8:32am  
Hey Ed,

Have you configured a device for that line? I've not received this message myself before, but thought this might be a good place to start.

 0



A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

PRODUCTS
RingEX
Message
Video
Phone
OPEN ECOSYSTEM
Developer Platform
APIs
Integrated Apps
App Gallery
Developer support
Games and rewards

RESOURCES
Resource center
Blog
Product Releases
Accessibility
QUICK LINKS
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us