Toggle sidebar Toggle sidebar

Twilio Alphanumeric Sender ID configuration for 3CX

Status
Not open for further replies.
HARVINDER SINGH

HARVINDER SINGH

SMB User
Basic Certified
Joined
Jul 28, 2022
Messages
40
Reaction score
1
Hi Team ,
Is Twilio Alphanumeric Sender ID compatible with 3CX ?
 
Hi, SMS handling for incoming alphanumeric Sender ID is compatible in v18 sp8, see the detailed change log here
 
Hi @Alejandro_3CX dose it also work to sent SMS from 3cx app, I mean it will show Alphanumeric ID when SMS sent from 3cx app. if yes is there any configuration guide as it is not workign for me.
 
@TheodorosG_3CX yes I configured the SMS same way , but on receving end it is showing mobile number insted of Alphanumeric Sender ID
 
HARVINDER SINGH said:
Hi @Alejandro_3CX dose it also work to sent SMS from 3cx app, I mean it will show Alphanumeric ID when SMS sent from 3cx app. if yes is there any configuration guide as it is not workign for me.
Click to expand...
Hi, Im afraid that this is only for incoming SMS in the 3CX not for outgoing.
 
As there is no way to auto-respond to WhatsApp-Messages, we only can answer by SMS after the 24h-Period of Meta. It is so important for us to send SMS by Twilio with alphanumeric Sender-ID (which is available in Germany without registration) to prevent customers answers by SMS (without "re-open" the WhatsApp Chat) or - worst case - call us at the Twilio's Overseas Number.

From the twilio console, we can send SMS with alphanumeric Sender-ID but not from 3CX. This is the code shown in the twilio console (to protect private data some characters are replaced with asterisks):

curl 'https://api.twilio.com/2010-04-01/Accounts/ACa5ce3af9b632417724becda2********/Messages.json' -X POST \
--data-urlencode 'To=+4917610777***' \
--data-urlencode 'MessagingServiceSid=MG65a294485da5473a1e15d63ccac80***' \
--data-urlencode 'Body=Text Message with Sender type Messaging Service...' \
-u ACa5ce3af9b632417724becda2********:[AuthToken]

That's all. I wonder, if we can bring 3CX to just add this 3rd line (MessagingServiceSid) when posting to Twilio, then our problem would be solved. For now, all SMS sent out from 3CX are received with the numeric number we want hide to the receiver.

Any idea?
 
Last edited:
LH74 said:
As there is no way to auto-respond to WhatsApp-Messages, we only can answer by SMS after the 24h-Period of Meta. It is so important for us to send SMS by Twilio with alphanumeric Sender-ID (which is available in Germany without registration) to prevent customers answers by SMS (without "re-open" the WhatsApp Chat) or - worst case - call us at the Twilio's Overseas Number.

From the twilio console, we can send SMS with alphanumeric Sender-ID but not from 3CX. This is the code shown in the twilio console (to protect private data some characters are replaced with asterisks):

curl 'https://api.twilio.com/2010-04-01/Accounts/ACa5ce3af9b632417724becda2********/Messages.json' -X POST \
--data-urlencode 'To=+4917610777***' \
--data-urlencode 'MessagingServiceSid=MG65a294485da5473a1e15d63ccac80***' \
--data-urlencode 'Body=Text Message with Sender type Messaging Service...' \
-u ACa5ce3af9b632417724becda2********:[AuthToken]

That's all. I wonder, if we can bring 3CX to just add this 3rd line (MessagingServiceSid) when posting to Twilio, then our problem would be solved. For now, all SMS sent out from 3CX are received with the numeric number we want hide to the receiver.

Any idea?
Click to expand...
Export the Twilio provider, adjust the SMS section where the URL is, then import the provider and redo the routing.
 
That's really a great Idea! But for my understanding I can only adjust the URL. There seems to be no way to adjust the content posted to the twilio server and add this line needed in order to send from Alphanumeric SID:

--data-urlencode 'MessagingServiceSid=MG65a294485da5473a1e15d63ccac80***' \

Neither in provider.pv (from export Trunk & Chat):

<sms>
<variable name="MESSAGING_SID">
<option>ACa5ce3af9b632417724becda2b*******</option>
</variable>
<field name="Enabled">1</field>
<field name="OptionalProvider">1</field>
<field name="ProviderType">twilio</field>
<field name="OutboundRouting">1</field>
<field name="ProviderName">Twilio</field>
<field name="MessagingUrl">https://api.twilio.com/2010-04-01/Accounts/{MESSAGING_SID}/Messages.json</field>
</sms>

nor twilio.pv.xml (from Admin Console Advanced / Templates / Provider-Templates):

<sms>
<variable name="MESSAGING_SID">
<title>ACCOUNT_SID</title>
<option name="Messaging Account SID" required="true" maxlength="60" type="textbox"></option>
</variable>
<variable name="MESSAGING_TOKEN">
<title>AUTH_TOKEN</title>
<option name="Auth token" secure="true" required="true" maxlength="100" type="password"></option>
</variable>
<field name="MessagingUrl" status="readonly">https://api.twilio.com/2010-04-01/Accounts/{MESSAGING_SID}/Messages.json</field>
<field name="ProviderName" status="readonly">Twilio</field>
<field name="OptionalProvider" status="readonly">1</field>
<field name="ProviderType" status="readonly">twilio</field>
<field name="OutboundRouting" status="readonly">1</field>
<field name="HasWebhook" status="readonly">1</field>
</sms>

Maybe I do not see the wood for the trees...
 
Data-UrlEncode is simply a GET parameter.

{URL}/messages.json?MessagingServiceSid=yourSIDhere
 
LH74 said:
That's really a great Idea! But for my understanding I can only adjust the URL. There seems to be no way to adjust the content posted to the twilio server and add this line needed tho send from Alphanumeric SID:

--data-urlencode 'MessagingServiceSid=MG65a294485da5473a1e15d63ccac80***' \

Neither in provider.pv (from export Trunk & Chat):

<sms>
<variable name="MESSAGING_SID">
<option>ACa5ce3af9b632417724becda2b*******</option>
</variable>
<field name="Enabled">1</field>
<field name="OptionalProvider">1</field>
<field name="ProviderType">twilio</field>
<field name="OutboundRouting">1</field>
<field name="ProviderName">Twilio</field>
<field name="MessagingUrl">https://api.twilio.com/2010-04-01/Accounts/{MESSAGING_SID}/Messages.json</field>
</sms>

nor twilio.pv.xml (from Admin Console Advanced / Templates / Provider-Templates):

<sms>
<variable name="MESSAGING_SID">
<title>ACCOUNT_SID</title>
<option name="Messaging Account SID" required="true" maxlength="60" type="textbox"></option>
</variable>
<variable name="MESSAGING_TOKEN">
<title>AUTH_TOKEN</title>
<option name="Auth token" secure="true" required="true" maxlength="100" type="password"></option>
</variable>
<field name="MessagingUrl" status="readonly">https://api.twilio.com/2010-04-01/Accounts/{MESSAGING_SID}/Messages.json</field>
<field name="ProviderName" status="readonly">Twilio</field>
<field name="OptionalProvider" status="readonly">1</field>
<field name="ProviderType" status="readonly">twilio</field>
<field name="OutboundRouting" status="readonly">1</field>
<field name="HasWebhook" status="readonly">1</field>
</sms>

Maybe I do not see the wood for the trees...
Click to expand...

ConceptsWeb said:
Data-UrlEncode is simply a GET parameter.

{URL}/messages.json?MessagingServiceSid=yourSIDhere
Click to expand...

Thank you so much showing me the way I have to take but I'm sorry, for being stupid to implement the GET parameter.
  1. Where do I have to adjust the XML-Settings?
    In the Trunk & Chat Section?
    I'm able to export the settings, but unable to import the edited XML-File (there seems to be no option)
    In the Advanced / Templates / Provider-Templates Section?
    I'm see the Content of XML-File selected, but when just copy&paste the unchanged content and save as XML-file and import this file I get the error "Provider template file has incorrect structure - header / template - Value is required"

  2. How to edit the XML-File?
    Just replace:
    <field name="MessagingUrl">https://api.twilio.com/2010-04-01/Accounts/{MESSAGING_SID}/Messages.json</field>
    with:
    <field name="MessagingUrl">https://api.twilio.com/2010-04-01/Accounts/{MESSAGING_SID}/Messages.json?MessagingServiceSid=MG65a294485da5473a1e15d63ccac80***</field>
Thank you in advance!
 
Alejandro_3CX said:
Hi, Im afraid that this is only for incoming SMS in the 3CX not for outgoing.
Click to expand...
1723659132652.png

Sending one-way SMS with alphanumeric sender ID (which should work as described above, see https://www.3cx.com/live-chat/business-text/) is so important for us. Twilio does support Alphanumeric Sender ID (it works from Twilio Console) and there is only the MessagingServiceSid parameter missing which has to be come from 3CX, see described https://www.3cx.com/community/threa...r-id-configuration-for-3cx.122926/post-608292

Are there any plans for an 3CX-Update supporting this parameter?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,953
Messages
589,914
Members
164,849
Latest member
BillyAkansel
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom