- Joined
- Sep 23, 2021
- Messages
- 9
- Reaction score
- 1
We have a generic SIP trunk that we have been using for voice for several years.
We have also had the same DIDs' SMS hosted at Twilio for years.
i.e. +19201234567 voice calls are delivered to SIPCo and then to 3CX, but an SMS sent to +19201234567 is delivered to Twilio and then wherever we tell Twilio to route it.
This has worked for years. We now want to look to bring SMS messaging for *some* DIDs into 3CX. SIPCo does not support SMS in a way that makes sense for us, so we do not want to have SMS on these DIDs hosted by SIPCo. SMS needs to continue to be hosted by Twilio.
I thought we could make this work by enabling SMS on the SIPCo SIP trunk and then using this config to use Twilio:
Provider URL: https://api.twilio.com/2010-04-01/Accounts/[ACCOUNTSID]/SMS/Messages -OR-
Provider URL: https://api.twilio.com/2010-04-01/Accounts/[ACCOUNTSID]/Messages.json
For the API key, I've tried the Account SID, the token, an API key, the API secret, AccountSID:Token, APIKey:Secret, and a few other variations. The logs show failed authentication, so I obviously don't have it quite right. I've also tried encoding the user/pass a few ways without success.
Any suggestions?
We have also had the same DIDs' SMS hosted at Twilio for years.
i.e. +19201234567 voice calls are delivered to SIPCo and then to 3CX, but an SMS sent to +19201234567 is delivered to Twilio and then wherever we tell Twilio to route it.
This has worked for years. We now want to look to bring SMS messaging for *some* DIDs into 3CX. SIPCo does not support SMS in a way that makes sense for us, so we do not want to have SMS on these DIDs hosted by SIPCo. SMS needs to continue to be hosted by Twilio.
I thought we could make this work by enabling SMS on the SIPCo SIP trunk and then using this config to use Twilio:
Provider URL: https://api.twilio.com/2010-04-01/Accounts/[ACCOUNTSID]/SMS/Messages -OR-
Provider URL: https://api.twilio.com/2010-04-01/Accounts/[ACCOUNTSID]/Messages.json
For the API key, I've tried the Account SID, the token, an API key, the API secret, AccountSID:Token, APIKey:Secret, and a few other variations. The logs show failed authentication, so I obviously don't have it quite right. I've also tried encoding the user/pass a few ways without success.
Any suggestions?