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
Related
I'm having trouble understanding the bigcomerece api documentation.
I cant find where it explains how to mark and order as shipped ,update with tracking number and initiate a customer ship notification email.
can someone help me with a link to this documentation?
https://developer.bigcommerce.com/api/orders
You need to Create an Order Shipment:
https://developer.bigcommerce.com/api/stores/v2/orders/shipments
There you can specify a "tracking_number" etc...
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).
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
I'v implemented the GCM, but have some points it seems I didn't follow understand.
GCM have a concept of Canonical Ids, in which if the client registers two or more times, and you from the server sends messages to these Google will return a (the) canonical id of the last registered regId ?? When I test this by deliberately not unregister the device it still successfully sends multiple messages to the same device. Have I misunderstood what the canonical id is? Are you suppose to be able to register the device several times ?
Yes you can register the same app/device multiple times, and canonical Ids are designed to help you fix that problem when it arrives. Your server will need to prune your registration ID list when you receive a response with a canonical Id. You can see a response I wrote here: android GCM get original id of canonical id That describes the format and what to do.
This post also contains good information about canonical Ids: GCM and id handling
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?