Gateways are the mechanisms for sending messages. You can define SYNC gateways, UDP gateways, and SMTP gateways. In most cases, you can also use a device tracker gateway that automatically decides which gateway to use.
Device tracker gateway When you use the device tracker gateway, the address in your push request is the MobiLink user name of the Listener.
Device tracking allows automatic management of remote device address changes. When using device tracking, the SYNC gateway is attempted first, with fallback to the UDP and then the SMTP gateways if they are enabled.
Use of the device tracker gateway is recommended. If you do not use device tracking, your request_cursor must include a UDP or SMTP gateway name and address, and, for each push request, only that gateway becomes tried.
SYNC gateway The SYNC gateway can use the same protocol as you use for synchronization. The connection is persistent, and is used for all Listener communication (notifications, confirmation, and device tracking). If you are using SYNC, you may not need to make any changes to the default gateway settings.
UDP gateway This gateway allows you to send push requests to remote listeners using UDP. If you are using UDP, you may not need to make any changes to the default gateway settings.
SMTP gateway You can use the SMTP gateway to send messages to SMS listeners via a wireless carrier's email-to-SMS service. For SMTP, you need to configure an SMTP gateway and carrier.
When you use an SMTP gateway, you configure carriers to store information about the public wireless carriers that you want to use. Carrier information is used to create SMS email addresses from device tracking information that is sent up from Listeners.
Configuring gateways and carriers
| Send feedback about this page via email or DocCommentXchange | Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0 |