Technical Specifications
All you need is an application connected to the internet. mcharge will manage the connection with mobile operators.
To send Premium SMS. Your application will need to initiate requests to the mcharge servers.
To receive Premium SMS. After receiving your SMS from the mobile operator, mcharge will send a request to your servers on a URL you define (and an open port; by default mcharge will use Port 80). Your application needs to interpret the requests via scripts that you developed and host on your servers.
Connection Protocols
| HTTP GET | Basic command used for internet-based applications, extremely easy to implement. | Download our HTTP technical specifications |
|---|---|---|
| XML | Provides excellent interoperability amongst heterogeneous systems and is, of course, language independent. | Download our XML technical specifications |
| SOAP | Is also extensively used for web services, and can now be used to communicate with mpulses’ SMS gateway. | Download our SOAP technical specifications |
| SMPP | Protocol made for mobile specialists that are used to working with protocols specific to the mobile industry. It is the most common protocol for direct communication with a mobile operator’s SMS-C. mpulse supports a subset of the protocol, meaning we support only certain functionalities. | Download our SMPP technical specifications |
| Enjoy the functionalities offered by our gateway product, without the complexity of other implementation methods. It’s as easy as sending and receiving email! Benefit exclusive usage of your dedicated short code or access one of mpulse’s shared short code, obtain delivery reports, and much more… | Contact us to find out how it works |
France supporting documents
For SMS in France, your application needs to follow particular workflows to handle market specific technical constraints.
- For pay-per-download (one single billing transaction per SMS):
Download our France Premium MO factsheet
- For subscription services (after subscribing users pay weekly or monthly for example):
Download our France Premium MT factsheet
Supported features
| Feature | HTTP | XML | SOAP | SMPP | |
|---|---|---|---|---|---|
| SMS MO | Yes | Yes | Yes | Yes | Yes |
| SMS MT | Yes | Yes | Yes | Yes | Yes |
| WAP-Push | Possible | Yes | Yes | Yes | Yes |
| Delivery reports | Possible | Yes | Yes | Yes | Yes |
| Long-number | Yes | Yes | Yes | Yes | Yes |
| Sessions | Yes | Yes | Yes | Yes | Yes |
| Dynamic keywords | Yes | Yes | Yes | Yes | Yes |
| Concatenated SMS | no | Yes | Yes | Yes | Yes |
| MNO indicated on SMS MO and DLR | No | Yes | Yes | Yes | Yes* |
| Determine TTL** | No | No | Yes | No | Yes |
* Optional network operator field not part of the standard SMPP 3.4 protocol ** When supported by mobile operator. TTL means « time to live », ie. period of time during which the mobile operator will try to deliver an SMS.
Gateway Technical Environment
Security
Your connection to mcharge
- Access protection by username/password
- Authentication via originating IP address check (optional)
- Messages can be exchanged over the HTTPS protocol (rates upon request)
- VPN connection (rates upon request)
mcharge
- VPN connection with mobile operators
- Site protected from deliberate or unintended damage: anti-theft infrared motion detection alarm, video surveillance, personnel access policy, anti-fire oxygen evacuation, and back-up power supply
Environment
- Direct and indirect mobile operator connections
- Redundant national and international backbone connections
- Physical location in Luxembourg (EBRC building)
Platform
- Hosted on redundant virtualized bi-quad-core machines
- Running Red Hat Enterprise Linux 5, JBoss Application Server 4.2 and MySQL Enterprise 5
Watchguard Firewall
