I see this issue in another thread and I don't know if I'm supposed to place at the bottom of it or a new thread. I didn't see the issue resolved however. I am having the same issue. I graduated form development to production today. I changed my URLs to the
platform.ringcentral.com address. I changed my key & secret codes to production values and immediately received a 304 error. After reading your post on the previous thread, I checked with my RingCentral account and tried changing my credentials to the phone number, extension & password of the operator's extension to no avail. I also tried changing them to my credentials(super admin), again to no avail. I'm at a loss.
Still getting the error, I tried switching back to the development server and works fine. Back to production and get the error. I am logging in with number 18778897640 (operator) and sending with number 18883931083.
Oh, this is very simple: RingCentral does not currently support sending SMS from toll-free numbers. This limitation is primarily because inability of some carriers to route inbound SMS to toll free numbers.
I suspect that if you try any local company number (if you have one) it will work.
OK, I changed my send from number to 16788841809, one of our local numbers. I am still getting my token logged in as our operator as required (18778897640), I am still getting a 304 error. Do I have to change my operator number to a local number as well?
Bob, according to what I can see, 16788841809 is mapped to ext.124 while your operator extension is 113. Even if you are logged as an operator, you cannot send SMS from other users' direct numbers. In your particular scenario, to be able to send from 16788841809 you need:
- either authenticate as ext.124
- or unassign 16788841809 from ext.124 and make it additional company number