I successfully created and am using the High Volume App on number xxx-xxx-1306
APP ID 0BeUP9IIQCSuO-LdU9dXQw
I then created another app to use regular SMS, I was trying to attach that number xxx-xxx-7873 or better yet our main 800#
APP ID 9TlxXxTiSf6n7qed0fX3uQ
When I try to login to the regular SMS production app with 7873, it does not work, but I can login to the online portal, so it is not a password problem. I cannot login with the 800# either, when I use the password reset for the 800#, it says it will send email to my email, but I never get an email. Also I dont see our 800# listed as a number in the users, and 7873 is the super user that I use to administer the account. I assume you cannot login as the 800#
Does something have to be done to allow me to use 7873 in the regular SMS app?
thanks for the reply
1. the error when logging in with # 7873 is
"error" : "invalid_grant", "errors" : [ { "errorCode" : "OAU-140", "message" : "Invalid resource owner credentials"
but I can login with that user/pass to ringcentral, I am extension 101 and have tried with and without the extension
2 I am using the client id, client secret, username, password AND extension number, just like I was in the sandbox, of course I am now using the production ID and Secret
$SessionUser = "+15555557873" $SessionPassword = "xxxxxxxxxxx" $ClientID = "xxxxxxxxxxxxx" $ClientSecret = "hyGxxxxxxxxxnQ" $sessionExtension = "101"
3. I created a request for the TF number
thanks
"just like I was in the sandbox", did you really change the client id and client secret for your production app? Did you change the server url to point to the production server? I fully trust this error "Invalid resource owner credentials" and I am 100% sure it's a mistake in your params.
Something has changed in the backend, now I am getting a OAU-143
when I search for that in the forum, I get 0 results.
{ "error" : "invalid_request", "errors" : [ { "errorCode" : "OAU-143", "message" : "Resource Owner credentials are incomplete" } ], "error_description" : "Resource Owner credentials are incomplete" }
I appreciate your concerns , here is my code for the production app
$SessionUser = "+1xxxxxx7873" $SessionPassword = "$xxxxxx!" $ClientID = "9Tlxxxxxxx3uQ" $ClientSecret = "hyG_xxxxxxxxx_mjjnQ" $sessionExtension = "101" $AuthAPI = @{"endpoint" = 'https://platform.ringcentral.com/' "url" = 'restapi/oauth/token' }
and here is the code for the sandbox
$SessionUser = "+1xxxxxx2434" $SessionPassword = "j7MxxxxxxxxxAxf" $ClientID = "VRbXxxxxxxxxxKM_1Q" $ClientSecret = "L4XAKxxxxxxxVY9g" $sessionExtension = "101" $AuthAPI = @{"endpoint" = 'https://platform.devtest.ringcentral.com/' "url" = 'restapi/oauth/token' }
as you can see I have changed everything to use the production app
could you please verify that #7873 is configured to use this APP thanks for your time
There is nothing wrong with your app. Since you login using the direct number, can you just drop the extension number param.
BTW, not sure how you finally call the endpoint, but your name for the AuthAPI is not correct. url or server_url should be "https://platform.ringcentral.com" and the endpoint is some endpoint such as "restapi/oauth/token".
I dont think there is anything wrong with my code, it is the same code that works in the sandbox, here again is my code, I just removed the extension
Function Get-RingCentralAuthentication { $SessionUser = "+1800xxx5041" $SessionPassword = "$xxxxxxxxt" $ClientID = "9TlxxxxxX3uQ" $ClientSecret = "hyG_xxxxxxxmjjnQ" $ClientCredsPlainText = $ClientID + ":" + $ClientSecret $ClientCredsBase64 = [System.Convert]::ToBase64String( [System.Text.Encoding]::UTF8.GetBytes($ClientCredsPlainText)) $AuthHeader = @{"Content-Type" = 'application/x-www-form-urlencoded' "accept" = 'application/json' "authorization" = "Basic $ClientCredsBase64" } $AuthAPI = @{"endpoint" = 'https://platform.ringcentral.com/' "url" = 'restapi/oauth/token' } $AuthBody = @{"grant_type" = 'password' "username" = $SessionUser "password" = $SessionPassword } $uri = $AuthAPI.endpoint + $AuthAPI.url $request = Invoke-RestMethod -Method POST -Uri $uri -Headers $AuthHeader -Body $AuthBody return $request }
Earlier you showed that you were using the direct number, and that was why I asked you to remove the extension number '101'
$SessionUser = "+1xxxxxx7873"
Now you removed it and changed to use the main company number. Why?
$SessionUser = "+1800xxx5041"
I have been trying eveything, I sent a request to get the main 800# working and they sent this back
"Invalid resource owner credentials" error usually occurs when the credentials are incorrect. Please try logging in to Service web (service.ringcentral.com) using the same credentials (username, Extension and password) you are using to authorize the application to make API calls. If your password is incorrect, you can reset it yourself by clicking the Forgot password link. You can go ahead and do that by clicking on the Forgot Password link. Also if your application is in production, you need to switch all your credentials from sandbox to production.
then after a few hours the error changed on the #7873 from
"Resource Owner credentials are incomplete"
to
"Resource Owner credentials are incomplete"
so I tried the 800#, now both the 800# and #7873 get the same
"Resource Owner credentials are incomplete" error
I think there is something not configured correctly with main number
should this app work on all the extensions, except those set for the Bulk sms?
It should not be the problem with the app.
After all of this, reset password etc., could you still login the service web with the same username and password?
Or can you login this RC app https://app.ringcentral.com using the direct number of the extension 101?
yes, I just test the RC app and logged in with these
800xxx5041 with no extension
800xxx5041 with extension 101
831xxx7873 with no extension
831xxx7873 with extension 101
I also tested with a non-main line number
805xxx4050 with extension 102
805xxx4050 with no extension
all of them worked.
and I have tried all of these in the API
If I use 805xxx4050 with extension 102 I get
"error" : "invalid_grant", "errors" : [ { "errorCode" : "OAU-140", "message" : "Invalid resource owner credentials"
If I use 800xx5041 or 831xxx7873 with or without an extension I get this different error
"error" : "invalid_request", "errors" : [ { "errorCode" : "OAU-143", "message" : "Resource Owner credentials are incomplete"
I really dont think this is a password error. If I switch back to the sandbox, it works fine, so I dont think its a coding error
May this be in your case as I see the $ sign in the password?
thats a good catch, but It didnt fix the problem
ok, I changed the password here are the results
with the 800 number with no extension
$SessionUser = "+1800xxx5041" $SessionPassword = "hYcxxxxxxajtc" $ClientID = "9TlxXxxxxX3uQ" $ClientSecret = "hyG_xxxxx_mjjnQ"
"errorCode" : "FeatureNotAvailable", "message" : "Phone number doesn't belong to extension", "errors" : [ { "errorCode" : "MSG-304", "message" : "Phone number doesn't belong to extension"
with the 831xxx7873 with no extension
$SessionUser = "+1831xxx7873" $SessionPassword = "hYcxxxxxajtc" $ClientID = "9TlxXxxxxxX3uQ" $ClientSecret = "hyG_xxxxxT_mjjnQ"
"errorCode":"FeatureNotAvailable", "message":"Phone number doesn't belong to extension", "errorCode" : "MSG-304",
"errorCode":"FeatureNotAvailable", "message":"Phone number doesn't belong to extension", "errorCode" : "MSG-304",
What do you mean it did not fix the problem? The new error proves that you could login with the new password. The error says that you are trying to send SMS messages using the "from" number which does not belong to the logged in user.
See our example code, we recommend developers to read the phone number to find the right numbers a user can use for the "from"
async function read_extension_phone_number(){ try { var resp = await platform.get("/restapi/v1.0/account/~/extension/~/phone-number") var jsonObj = await resp.json() for (var record of jsonObj.records){ for (feature of record.features){ if (feature == "SmsSender"){ return send_sms(record.phoneNumber) } } } } catch(e) { console.log(e.message) process.exit(1) } }
https://developers.ringcentral.com/guide/messaging/quick-start#javascript
ok, you are right, I have been trying so many things, when I change the from number #7873 it all worked.. Thanks for you perseverance in helping me. Now If I could get support to let me use the 800# everything would be perfect.
I can't be wrong LOL.
Remember that the #800 is your main company number. You need (if not yet) to set it via the IVR settings to round Fax/SMS messages to the "101" extension in order to send and receive messages from the main company number.
I cant find any setting for SMS in the IVR setting, we have a basic single level IVR
I found your answer to someone else
https://community.ringcentral.com/questions/102801/cannot-send-sms-from-main-company-number.html and tried that, I changed the Operator Extension to 101, but it doesnt allow to use the 800 as the from
Your TF number is not yet provisioned for SMS. Have you submitted a request?
Im trying, this is my last reply, hopefully they understand what I asking
From: Ken Nye Sent: Wednesday, January 19, 2022 3:09 PM To: Dev Platform Support Subject: RE: RingCentral [ ref:_00D80aRUX._5002H1MnLio:ref ] I worked with Phong Vu and he helped me get the code working correctly with 831xxx7873 I would like to be able to be use the FROM number to be our main 800xxx5041 Can that be added? Thank you Ken Nye
Actually there is a better way to send a request. Open this link and follow the instructions.
If you do this, you can cancel your previous support ticket.
I did this, it talked about paying for each SMS, I understand the High Volume SMS is extra, but I thought regular SMS is part of the service we already pay for.
No, the regular TF SMS is not free. Same pricing as HV SMS. TF SMS is regulated for non-consumer text messaging. Read this article to learn more.
for some reason even thought it says I have 300 characters left if would not let me post the full post, here is the rest
If I add the extension to 7873
$SessionUser = "+1831xxx7873" $SessionPassword = "hYcZxxxxajtc" $ClientID = "9TlxXxxx0fX3uQ" $ClientSecret = "hyG_HxxxxxGqT_mjjnQ" $sessionExtension = "101"
"error":"invalid_grant", "errorCode" : "OAU-140", "message" : "Invalid resource owner credentials"
If I add the extension to the 800 number
$SessionUser = "+1800xxx5041" $SessionPassword = "hYxxxxxjtc" $ClientID = "9Tlxxxxx3uQ" $ClientSecret = "hyG_xxxx_mjjnQ" $sessionExtension = "101"
"error" : "invalid_grant", "errors" : [ { "errorCode" : "OAU-140", "message" : "Invalid resource owner credentials"
"When I try to login to the regular SMS production app with 7873, it does not work, but I can login to the online portal, so it is not a password problem"
1. "It doesn't work": how and what is the error?
2. "it is not a password problem": to login, you need the app client id, client secret, username, password AND extension number (if using the main company number). Any wrong the param will fail, NOT just the password.
Your 800 is a main company number and it's a TF number. TF number is not provisioned for SMS unless you create a request to enable for standard TF SMS feature.
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