Read on for the answers to the questions asked most frequently about Aerialink services.
Yes. Delivery receipts - referred to as DLR - provide visibility to the greatest level of delivery confirmation in countries and with carriers who support DLR. For more information, check out the full article on Carrier Delivery Receipts as well as details about other types of message status acknowledgement.
HTTP & SMPP Connection Messaging Limits
- P2P (Person to Person) long codes: 1 msg/second per Long Code
- A2P (Dedicated short codes): 10 msg/second per Short Code
- A2P (Shared short codes): 5 msg/second per Short Code
HTTP (JSON and XML), SMPP (3.3 and 3.4), MM4 (SMTP), SMTP, FTP.
Aerialink is connected to over 900+ carriers worldwide.
Choose a reach list based on your sender ID type and country to see the carriers that code can message.
Absolutely! Live support is included with all of our plans.
Just fill out the form for a trial.
A sales rep will reach out to you.
Aerialink provides a monthly pay-as-you-go model. There are no long-term contract commitments.
We love listening to customer needs and ideas.
Don’t be shy - existing customers can request a feature right in the Platform. Don’t have a Platform account but still curious about what we can do for you? Our sales team would be happy to hear from you.**
Although it is on our roadmap for the future, Aerialink does not currently offer bulk sends through our API.
Aerialink is a number sponsor which allows you to lease a number in a matter of minutes.
Dedicated short code numbers require registration with the Common Short Code Association (CSCA) and cross-carrier certification with all wireless carriers. Aerialink will guide you through the steps regardless of what type of number you need.
We also support special location-neutral long codes that do not resolve to a known area code.
Yes, provided that porting is supported for the long code, which is true of most (but not all) cases.
The business that leases the numbers manages this aspect.
This is similar to leasing numbers from a telephone or VOIP carrier/service provider for your voice lines.
Voice network number translation matches numbers progressively while mobile messaging matches numbers exactly.
In other words, the actual “number” that we text is only that first ten digits (plus the country code!), and any additional digits entered will make the number unrecognizable to your mobile device.
When sending A2P traffic internationally, what “from” number or name will be displayed on a device receiving an SMS from my application?
This varies by country.
The displayed “from” address could be a fixed, Aerialink-leased long code, a short code or a customized alpha/alphanumeric (e.g, your company name). In some countries, the original sender ID may get overwritten by a local ID to avoid carrier blocking. Please enquire for specific country restricitons.
Short codes are country-specific
Message delivery from a U.S. short code is intended for U.S. destination numbers operating on U.S. carrier networks. Non-U.S. numbers will not receive messages sent from U.S. short codes. U.S. end-users with American handset devices and numbers roaming on international networks may be able to successfully receive messages, but this cannot be guaranteed.
Their base requirements are the same, but additional expectations differ.
While all mobile programs must uphold the guidelines set out by the regulating body for their country (CTIA for the U.S., CWTA for Canada), carriers each have their own, additional set of expectations which must be fulfilled by mobile programs wishing to send to that carrier’s mobile subscribers.
I do not see [x] in the CTIA guidelines, yet Aerialink lists it as a requirement. Does Aerialink have its own, additional requirements?
Aerialink has no self-generated, additional requirements for compliance.
Short code certification is subject not only to following the CTIA guidelines but to meeting carrier requirements which are applied in addition to what is recommended in the CTIA. Aerialink’s certification team stays up-to-date on the latest industry standards, best-practices and carrier requirements and has compiled these all together for your perusal in the Compliance section.
Compliance expectations vary not only by carrier, but by carrier employee.
Not only do carrier expectations change frequently and often go unpublished, they vary depending upon whose desk your program brief has landed on. It is very possible that your message flow was rejected based on either a new, unpublished requirement, or because the carrier-employed individual who reviewed your program brief has interpreted those requirements in manner differing from what Aerialink has encountered in the past.
Still curious after reading our Leasing & Aquisitions articles? Let us answer your questions.
The time of migration varies by carrier.
No. Most carriers migrate at their own rate and require no formal migration date.
Two carriers—Sprint and T-Mobile—do set migration dates, however no action is required by you, the customer. Aerialink will notify you of when your carriers have migrated.
There is no standard order by which the carriers migrate.
Each one will review, approve and migrate your code at their leisure.
The length of migration varies primarily on how busy the carrier is.
Once your program brief is submitted to the carriers, it is up to each carrier to review and approve your short code. If their compliance and certification teams are very busy, it may take longer to review and approve your code.
Migration time varies for Tier 1’s and Tier 4’s alike.
Tier 1 carriers typically take longer to approve and migrate a short code to the fact that they have more programs to review at a single time. However, if they are not busy, Tier 1 carriers can migrate just as quickly as any others. Aerialink has seen Tier 1 carriers migrate first, last and everywhere in between.
Aerialink will provide regular status updates throughout the migration process.
When a carrier has migrated your code, Aerialink will notify you via email.
Traffic will switch prior to carrier migration for MO’s; after migration for MT’s.
MT’s will continue to go through your old aggregator until migration is complete.
Does Aerialink provide an option for those who cannot use their short code while it is being migrated?
Aerialink can provide you with a temporary long-code number.
The temporary LCN may be used for traffic or testing while migration is occurring.
Aerialink will confirm when each carrier has migrated and is ready to be tested.
Aerialink will proactively test your code on Tier 1 carriers in addition to your own testing.
This page was last updated 1550081819471