France SMS Features and Restrictions
Alpha sender ID is recommended to ensure delivery for A2P traffic. Numeric sender ID is limited to short code or alternatively 2-way communication can be achieved by purchasing an LVN.
All transactional traffic will be delivered directly to carriers using 38XXX short codes or alphanumeric binds used specifically for this traffic type. To ensure the traffic is identified as such and delivered through the correct routes, contact your account manager or submit a support request.
Marketing or promotional content is limited to certain regulatory conditions. Any traffic not identified as transactional will automatically be subject to these regulatory conditions to avoid malfeasance.
Carriers will only accept delivery between 8:00 a.m. and 8:00 p.m. local time Monday to Saturday. Traffic sent outside these hours will be rejected.
Marketing traffic must add 'STOP au 36179' at the end of the SMS or messages will be rejected. Vonage will handle the reply to prevent further messages sent to this number.
To ensure your traffic is identified correctly and thus delivered through the correct routes, please contact your account manager or submit a support request.
French networks do not allow numeric Sender IDs that are not virtual numbers, to avoid spoofing of identities. For Lycamobile, all Sender IDs will be replaced with a local French Number.
Outbound messages from French Long Virtual Numbers are throttled at 1 SMS every 2 seconds. Vonage virtual numbers are available in the Numbers tab of the account Dashboard (only for P2P traffic for France).
LVNs must only be used for P2P traffic. Carriers will block excessive use of these LVNs, over approximately 500 SMS per LVN per day.
Other Features or Restrictions of Note
Currently we are unable to support machine to machine traffic via our french routes.
Unicode messages are supported over Orange, SFR, and Free networks. Bouygues Telecom only accepts some Unicode characters at this time.
DLRs are fully supported and considered reliable.
For more information, see the following articles:
Is it possible to bypass this restrictions? Let say we are in the case where the user is identified as not being a spammer and is the owner of the phone number sending the message.
Is there a supported encoding other than Unicode which allows accents (like iso-8859-1) ?
In Nexmo's RestAPI, French accents are supported in text mode when submitted through UTF-8 and URL encoding. Unicode is unfortunately not supported
Article is closed for comments.