The above diagram illustrates the different systems involved when a message is sent through the API. An application developed using the API will call a method on the Vodafone Betavine API server. The API server will process the method call and convert it into a message which it will in turn pass to a messaging gateway. The messaging gateway determines which SMSC to send the message through. The SMSCs are connected to the mobile network and perform the finally delivery of the message to the handset.
The messaging gateway has multiple SMSC connections. This allows the API to distribute the load and cost of message delivery. Each SMSC behaviour is different and will only allow certain types of messages to be delivered.
The Vodafone ES SMSC will only allow messages less than 128 characters long and the originating number will be set to 'betavine'. The message text will contain the mobile number of the user accessing the API.
Vodafone UK SMSC will send messages as if they have been sent from the originating number, with no alteration in the message text.
For the latest information regarding the formatting of messages by the API ask in the Vodafone Betavine Forums