SIM Configuration Guide. February 2015 Version 1 Document Reference: 8127

Size: px

Start display at page:

Download "SIM Configuration Guide. February 2015 Version 1 Document Reference: 8127"

Eugene Lyons
8 years ago
Views:

1 SIM Configuration Guide February 2015 Version 1 Document Reference: 8127

2 Contents 1 SIM APN Settings SIM MMS Settings SIM Settings SIM SMS Settings SIM SMS Charging Eseye Mobile Originated Eseye Mobile Terminated Non Eseye Mobile Terminated API SMS Receive API SMS Terminate Mobile Transmit Examples Server SMS Gateway Settings Server MMS Gateway Settings

.. 6 5.3 Non Eseye Mobile Terminated... 6 5.4 API SMS Receive... 6 5.5 API SMS Terminate Mobile Transmit.

3 1 SIM APN SETTINGS Eseye operate a private APN that is accessible from its SIM cards. APN: eseye.com Username: Your_Company_Name Password: Pass Device authentication at the APN is done using the SIM number. The username and password are not actually used for authentication and so you can set these fields to anything. We recommend setting the username to your company name as it helps the Eseye support team assist you. Figure 1: APN Settings Example 2 SIM MMS SETTINGS Eseye operate an MMSC that is accessible from its SIM cards. The MMSC is accessible through the Eseye WAP gateway using the standard eseye.com APN. Gateway IP: Port: 80 MMSC URL: 3

The username and password are not actually used for authentication and so you can set these fields to anything.

The default option is for the server to generate a unique web link for the MMS content and SMS or email the link to the intended destination.

4 The default option is for the server to generate a unique web link for the MMS content and SMS or the link to the intended destination. This method provides the lowest cost and most compatible delivery mechanism for devices that need to route MMS. The cost of sending an MMS through this mechanism is the cost of the GPRS data to the MMSC and an SMS message. These are charged to the SIM at standard rates. Figure 2: MMS Settings Example 3 SIM SETTINGS Eseye operate an SMTP mail relay that is accessible from its SIM cards, so that SIM cards can send s. SMTP Relay: Port: 25 The external IP address for the mail relay resolves to eseye.net so it is recommended to set the from address in your device to be from the eseye.net domain to allow it to successfully negotiate some SPAM filters. Figure 3: SMTP Settings Example 4

The cost of sending an MMS through this mechanism is the cost of the GPRS data to the MMSC and an SMS message. These are charged to the SIM at standard rates.

4 SIM SMS SETTINGS All the Eseye SIMs can be configured to send and receive SMS messages. By default these services are barred. Eseye operate an UDP to SMS service accessible from its SIM cards.

5 4 SIM SMS SETTINGS All the Eseye SIMs can be configured to send and receive SMS messages. By default these services are barred. Eseye operate an UDP to SMS service accessible from its SIM cards. The gateway will take the IP packet and convert it to an SMS. Please refer to document 8063 Serval UDP to SMS Service for more information. This method provides the lowest cost method of sending SMS messages from the SIM, particularly relevant if the SIM is abroad. You only pay for the low cost GPRS packet and the outbound bulk SMS. 5 SIM SMS CHARGING SMS can be a cost effective protocol for delivering data, however it can also turn out to be a very expensive route, understanding how the SMS charges are built up is essential for managing these costs. 5.1 Eseye Mobile Originated SIM Eseye Mobile Originated The Eseye Mobile Originated transaction is for an Eseye SIM originating an SMS message and it being delivered to the Eseye. The charges associated with this element depend on the mobile network the Eseye SIM is currently operating within. 5

This method provides the lowest cost method of sending SMS messages from the SIM, particularly relevant if the SIM is abroad. You only pay for the low cost GPRS packet and the outbound bulk SMS.

6 5.2 Eseye Mobile Terminated SIM Eseye Mobile Terminated The Eseye Mobile Terminated transaction is for an SMS message being delivered to an Eseye SIM from the Eseye. There is no charge associated with this transaction. 5.3 Non Eseye Mobile Terminated NON SIM Non Eseye Mobile Terminated The Non Eseye Mobile Terminated transaction is for an SMS message being delivered to a Non- Eseye SIM from the Eseye. The charges associated with this element depend on the mobile network the target SIM is a subscriber of. 5.4 API SMS Receive HTTP API API SMS Receive The API SMS Receive transaction is when an SMS is delivered from the Eseye to a customer s server using the HTTP API. There is no charge associated with this transaction. 6

3 Non Eseye Mobile Terminated NON SIM Non Eseye Mobile Terminated The Non Eseye Mobile Terminated transaction is for an SMS message being delivered to a Non- Eseye SIM from the

5.5 API SMS Terminate Mobile Transmit HTTP API API SMS Transmit The API SMS Transmit transaction is when a customer s server sends and SMS to the Eseye for delivery to a mobile SIM card.

7 5.5 API SMS Terminate Mobile Transmit HTTP API API SMS Transmit The API SMS Transmit transaction is when a customer s server sends and SMS to the Eseye for delivery to a mobile SIM card. There is a fixed SMS transmit charge associated with this transaction. 5.6 Examples Source Destination Components Comment Eseye SIM Customer Server Eseye Mobile Originated API SMS Receive Eseye SIM Non Eseye SIM Eseye Mobile Originated Non Eseye Mobile Terminated Lowest cost solution for receiving SMS from an Eseye SIM Normal SMS operation, two international charges are incurred. Non Eseye SIM Eseye SIM Eseye Mobile Terminated No additional Eseye charges Customer Server Eseye SIM API SMS Transmit Eseye Mobile Terminated Customer Server Non Eseye SIM API SMS Transmit Non Eseye Mobile Terminated Lowest cost solution for transmitting SMS to an Eseye SIM Outbound SMS gateway service. 7

6 Examples Source Destination Components Comment Eseye SIM Customer Server Eseye Mobile Originated API SMS Receive Eseye SIM Non Eseye SIM Eseye Mobile Originated Non Eseye Mobile Terminated Lowest

6 SERVER SMS GATEWAY SETTINGS Eseye operate an for application servers to send SMS s to users or their SIM cards. Applications can send SMSs via HTTP or Email APIs SMS gateway: http://messaging.eseye.

8 6 SERVER SMS GATEWAY SETTINGS Eseye operate an for application servers to send SMS s to users or their SIM cards. Applications can send SMSs via HTTP or APIs SMS gateway: You will be allocated a username and password when you sign up for this service. PHP Example: $message = "PhoneNumber=".urlencode($phonenumber); // Number to send to $message.= "&Text=".urlencode($text); // The message $message.= "&Sender=".urlencode($sender); // Sender phone number $url = " $post = $url."?".$message; $ch = curl_init($post); curl_setopt($ch, CURLOPT_USERPWD, "UserName:Password"); curl_setopt($ch, CURLOPT_HEADER, 0); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); $retval = curl_exec($ch); curl_close($ch); The Eseye can also be used to receive SMS messages, these can be routed to your own software / servers using HTTP You will be allocated a keyword when you sign up for this service. PHP Example: <? header ("Content-Type: text/plain"); if (!isset($_request['sender'])) echo "No Sender Phone Number"; if (!isset($_request['text'])) echo "No SMS Text"; if (!isset($_request['date'])) echo "No SMS Date Defined"; if (!isset($_request['time'])) echo "No SMS Time Defined"; 8

urlencode($text); // The message $message.= "&

9 ?> ASP Example: <% Response.ContentType = "text/plain" If Request.QueryString("Sender") = "" Then Response.Write ("No Sender Phone Number") End If If (Request.QueryString("Text") = "") Then Response.Write ("No SMS Text") End If If (Request.QueryString("Date") = "") Then Response.Write ("No SMS Date Defined") End If If (Request.QueryString("Time") = "") Then Response.Write ("No SMS Time Defined") End If %> 6.1 Server MMS Gateway Settings Eseye operate an MMSC for application servers to send MMS s to users. Applications can send MMSs via HTTP or APIs SMS gateway: You will be allocated a username and password when you sign up for this service. 9

QueryString("Time") = "") Then Response.Write ("No SMS Time Defined") End If %> 6.

POP3 Connector for Exchange - Configuration

Eclarsys PopGrabber POP3 Connector for Exchange - Configuration PopGrabber is an excellent replacement for the POP3 connector included in Windows SBS 2000 and 2003. It also works, of course, with Exchange