I am a bit confused conerning the services of the SMS Provider MessageBird; their API permits to include an "Originator", which is used as the sender of the SMS. On one hand, the documentation
https://developers.messagebird.com/
states that in some countries the originator is not used and refers to a list of country-specific information. On the other hand, this list
http://support.messagebird.com/hc/en-us/sections/202017565-Country-Info-Restrictions?page=1#articles
does not include an entry for Denmark. The specific problem is that using the same account, the originator is used for Germany, but apparently doesn't work for Denmark. Does anyone have any experience with this or any information which might be helpful? If so, I would appreciate any comment.
The originator as you said it is going to be used as the sender of the SMS.
But there are restrictions as you noted on the docs. For example when you are sending messages to the US you cannot use alphanumeric originators like "Codor LLC". You need to use a numeric phone number.
If you are trying to send an SMS to Denmark from a german originator number it should work. No restrictions apply here.
Something else can be broken. Please contact support (support#messagebird.com) and we'll help you out (I work at MessageBird).
Related
I am using "ConvertPlus Default" Checkout Theme in 2Checkout to accept international payments from my customers across the world. I generated the Buy Link and integrated with my store.
My issue is that the Checkout Form is not showing fields to input Address and City for many countries including Mexico, Japan etc. Refer screenshot below:
How do I enable the option to accept Complete Address information for all countries across the world?
Buy Link looks like this:
https://secure.2checkout.com/checkout/buy/?merchant=\[MerchantID\]&prod=\[ProductID\]&qty=1&tpl=default
You should add the tangible parameter
Send tangible=TRUE or tangible=1 for products that require physical delivery.
As of 10/01/2019 the parameter you will need to enable shipping is
li_#_tangible
The documentation says this.
Specifies if the corresponding li_#type is a tangible or intangible.
( Must be Upper Case, ‘Y’ or ‘N’, if li#_type is ‘shipping’ forced to
‘Y’.)
Where # is the parameter number. Because you can send multile items in the same POST so it will appear as multiple items in the 2CO cart.
Here is the full documentation about parameters,
https://www.2checkout.com/documentation/checkout/parameters/
Hope this helps someone.
Cheers.
I'm using vatlayer API for getting company information by put in the vat number. https://vatlayer.com/documentation
Now I want split address info in the state, zipcode, addressline and address number.
I get the address info: BREDABAAN 13052900 SCHOTEN.
The address number and zipcode stands against each other without spacing. (1305number and 2900 zipcode).
Is there another API for working with the vies database where i can split these information? Or an work around for this bug?
VatLayer don't support the split atm.
I get the address information by:
$("#organisation_address_line_1").val(json.company_address);
Thanks in advance,
There's quite a lot of API's to handle VAT validation but the ones that provide information about the trader essentially all rely on the official API at http://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl . It connects directly to the VIES system. Perhaps the values returned there are a bit different: it's worth trying your validation that way as well.
Unfortunately, since VIES does not return structured addresses (except for approximate matches, but only Spain supports them at the moment) and does not specify a common format for the free text addresses, you're going to have to deal with whatever format the country has chosen to provide, which means manual parsing.
I reckon 3rd party wrapping API's could handle guessing the format and splitting the formats on their own but I am not aware of any that would do it.
My kannel works great in smpp, deliver SMS postback me DLR for updating status.
When I send a SMS to my customer, i would like to know on which operator (Orange, Bouygues, ...) i sent the SMS.
I work with a SMSC called Highconnexion (in France) and according to its technical support, Highconnexion send me the op_id into an optional field in DELIVER_SM. The field is referenced by the value 0x1402.
He tells me that he think that kannel can get this information but don't know how because he is not a kannel specialist.
I try to find how to get this op_id, but impossible to find a response on google search.
Is someone can help me ?
You now know TLV code (0x1402). What you also need is TLV length and type — these you have to ask from the SMSC owner.
After that please refer to kannel docs here: http://www.kannel.org/download/1.5.0/userguide-1.5.0/userguide.html#META-DATA
And this conversation here:
http://www.kannel.org/pipermail/users/2010-October/013995.html
I have created an application that that sends error notifications to some mobile numbers located inside and outside of the United States via Twilio.
Inside the United states I get the expected results. The message shows that it is coming from my Twilio assigned phone number. However, when I test to an international destination; the results are unpredictable.
Sometimes I receive the message "from" a long number that is almost never the same twice. Other times I receive the message "from" a meaningless and sometimes strange "short code" that changes frequently as well.
How can I prevent this unwanted, unpredictable behavior?
Twilio Customer Support here - this is not really a stack overflow question as its to do with the way carriers send SMS in certain markets, but if you write into the help#twilio.com we'll explain in more detail.
Different countries actually have different policies about sender IDs. In some countries you are able to deliver A2P traffic only from alpha senders, for example. In other countries you might be able to send messages only from a local longode sender ID or from a shortcode like in USA. There are also often different routes available which may support different features. If you would like to test out features of the route your current SMS supplier has, you can send test SMS messages on mobile test numbers of telqtest.com
this question is a tad more on the technical side, but I hope it can be easilly solved.
You see, my problem here is the following:
I have a Gateway for sending SMS, however, I want those SMS to show a name instead of the number (company/Bank name for instance) like some Banks/providers have over here.
However I can't seem to find any sort of documentation on how to achieve this.
Is there any sort of way to achieve what I want?