Support forum
Add Reply
Add Topic11:12 am
May 28, 2013
Offline
QuoteSorry for the late response. You are correct, the username has to be the exact phone number otherwise Twilio will not accept it.
It is possible to change the number format (or replace the username with another number completely) with an HTTP callback script. But in order to do this, the HTTP callbacks must be enabled and you have to make a customized C# script. This is probably a bit overkill for your configuration.
Regards, Henk
4:40 pm
Never mind! I got it to work with the web connector. I discovered the username has to exactly match the full phone number preceded with the + and country code.
6:24 pm
OK, I tried creating a user in the web connector where the username and full name both matches the sending number, but the texts still are sourced from the primary number of the Twilio HTTP connector instead of the secondary one I'm trying to use. Maybe I'm misunderstanding or doing something wrong. That number works fine with the SQL connector.
6:15 pm
Henk Helmantel said
The browser application of the Web Connector does not have an option to let the user change the sender address, it always uses the login name as the 'from' address. The HTTP API of the Web Connector *does* have an option to set the sender address to any value.You can set the login name for each user to the sender address that you want to use. But be aware that the web application was designed mainly to give employees within a company an easy way to send SMS messages, it is not designed with external customers in mind.
Ah, ok. I see. I think this will work. I was just looking for a quick solution to allow some employees to be able to send text messages from a specific number until we have our final solution in place. I will test this making a user account as the number I'm sending from and let you know if I have any more questions.
Thank you for your help!
10:42 am
May 28, 2013
Offline
The browser application of the Web Connector does not have an option to let the user change the sender address, it always uses the login name as the 'from' address. The HTTP API of the Web Connector *does* have an option to set the sender address to any value.
You can set the login name for each user to the sender address that you want to use. But be aware that the web application was designed mainly to give employees within a company an easy way to send SMS messages, it is not designed with external customers in mind.
Vinny Abello said
Also, speaking of HTTP callback... is there a way to enable TLS and bind a certificate for the HTTP callback? It seems odd that it must remain unencrypted when most everything else can use TLS 1.2.
This is possible but it requires a small modification to the (Twilio) script of the HTTP Gateway. If you set the 'ShowAdvancedOptions' propery in the advanced settings of the Twilio HTTP Gateway to 'True', a new "Edit 'Twilio' script" link will appear in the 'Twilio' settings. You can click on this link to open the script editor.
On lines 46 and 47 of the Twilio script, you can set the full path- and filename for the .PFX certificate file and the password of the file. After you have done that, the Twilio HTTP webhook requires an HTTPS connection.
Regards, Henk
4:00 pm
Also, speaking of HTTP callback... is there a way to enable TLS and bind a certificate for the HTTP callback? It seems odd that it must remain unencrypted when most everything else can use TLS 1.2.
3:58 pm
Thanks for the response, Henk.
I suspected that was the case. I'm likewise looking at doing something similar with a web connector, but I want the users of the web connector to be tied to a specific hosted number with Twilio. I found the SQL connector lets me specify any sending number that is authorized which works as expected when inserting records, but didn't see a way to do that with the web connector. In the short term, I'd like to have a user be able to login to the web connector and send texts out using a specific number so the replies also go back to that number. Currently, it's just defaulting to the first number in the From address list on the gateway properties. Would I need to create another Twilio gateway with that number only, and use the same account SID and auth token, tying that back to the web connector? I feel like that's overcomplicating things and there's a better way, since it's so simple with the SQL connector. In the long term, we'll have a custom built application that just interacts with the SQL table but it will take us a little time.
Thanks again.
3:28 pm
May 28, 2013
Offline
Hello Vinny,
If you set up the Email Connector to forward each received SMS message from a specific connector to email, it will do so for all of the received SMS messages. The Email Connector does not have a way to forward only specific SMS messages to email but you can use multiple Twilio HTTP Gateways and let Diafaan SMS Server only route received SMS messages from one of the gateways to the Email Connector.
If you want to use a single Twilio HTTP Gateway then there are two ways in Diafaan SMS Server that you can do this, but both ways require a customized script.
The easiest method is to use a Scripting Connector with a small C# script that forwards only specific SMS messages to email. A script to convert the message to an email message is not difficult to make but it requires some experience in C# programming.
Another method is to use the HTTP Callback functionality of Diafaan SMS Server to route the received SMS messages only to the desired connector(s). This also requires a small script in C# (or PHP).
Regards, Henk
10:44 pm
Hello. We are testing Diafaan SMS Server basic edition coupled with Twilio as our gateway. We have a single SQL Connector which is working as expected. I was investigating the email connector and was trying to figure out if there is a way to forward received SMS messages to email, only for a specific receiving number. I'm trying to see if I can only send emails to a specific group mailbox when a text is received from Twilio for a specific hosted SMS number of ours for that group. I wasn't sure the best approach for this, be it scripting, some native functionality in the connector, or multiple Twilio Gateways with different service ID's and numbers tied to each.
Thanks for any pointers.
Most Users Ever Online: 529
Currently Online:
5 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Member Stats:
Guest Posters: 672
Members: 0
Moderators: 0
Admins: 1
Forum Stats:
Groups: 2
Forums: 3
Topics: 1141
Posts: 3899
Newest Members:
, Henk HelmantelAdministrators: Henk Helmantel: 1488