You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am using the following code to send an sms, numbers masked for privacy reasons
constclient=sipgateIO({ tokenId, token });createSMSModule(client).send({// this number is assigned to my account from employer:from: '+49157XXXXXXXX',message: 'Test SMS',to: 'some other number',})
I am getting the following error
Error: Number is not registered as a sender ID in your account
Why do I have to register the sender ID if the mobile number is already assigned to my account?
I can register the number on the Website if I try to send an sms manually, but is it possible to achieve this programmatically?
Looking at the API specs: https://api.sipgate.com/v2/doc#/sms
it seems that this should be possible, however, it was unclear to me how to achieve this with sipgate-node library.
Do I have to do requests to the API directly without the client?
I suppose I would need to do a request for verification to the number, get the verification code from the sms of the number, and then do a post to verify?
Hello, I am using the following code to send an sms, numbers masked for privacy reasons
I am getting the following error
Why do I have to register the sender ID if the mobile number is already assigned to my account?
I can register the number on the Website if I try to send an sms manually, but is it possible to achieve this programmatically?
Looking at the API specs:
https://api.sipgate.com/v2/doc#/sms
it seems that this should be possible, however, it was unclear to me how to achieve this with
sipgate-node
library.The sms module only exports these two functions
Do I have to do requests to the API directly without the client?
I suppose I would need to do a request for verification to the number, get the verification code from the sms of the number, and then do a post to verify?
Thank you.
Related #18
The text was updated successfully, but these errors were encountered: