Knowledge Base » SMS Gateway » WAP Pushes
- Knowledge Base
- What types of WAP Pushes are supported? 
- What is a Service Indication? 
- What is a Service Loader? 
- How can I ensure that a user receives content? 
- Should I use WAP Pushes in the US? 
- How many characters are allowed for the push_siname and push_href parameters? 
We support two types of WAP Push:
A Service Indication is essentially a title with parameter push_siname, and a URL with parameter push_href, as detailed here.
The way that Service indications are displayed varies considerably from handset to handset. Some handsets display the URL, others do not. All handsets that support WAP pushes display the push_siname however.
A Service Loader is designed to push the user to a given URL automatically. This type of WAP Push is quite outmoded, and not supported by many modern handsets. Their use is discouraged, and we strongly recommend using the Service Indication type of WAP Push instead.
More information about Service Loaders can be found here.
Unfortunately, some modern handsets (particularly the PDA type) do not support WAP Pushes, and will silently discard any push messages received. In order to ensure that a user receives WAP content, we advise sending a Service Indication WAP Push followed by a plain-text SMS with the URL included. Most modern handsets will automatically detect the URL and display it as a hyperlink, allowing a user to access your WAP site with minimal fuss, even if the handset does not support WAP Pushes.
It is generally inadvisable to use WAP Pushes in the US, as they are not very well supported by carriers and handsets, and users in North America are generally not familiar with them. Instead, you can simply include a URL in a plain-text SMS, where almost all modern handsets will turn them into clickable hyperlinks to perform the same function as a WAP push.
In order to use WAP Pushes, the shortcode that you use must be binary-enabled. Please contact our sales team at email@example.com for more information.
Unfortunately, there is no specific answer to this question. A WAP push consists of a header which is followed by the SI name and target URL. In addition to being compressed, certain parts of the URL may be tokenized. This means that determining the length of a WAP push is complex.
We have found that the maximum practical length of the "push_href" parameter is about 80 characters, and it is generally a good idea to keep the URL as short as possible. The length of the "push_siname" parameter is dependent on all the above factors (namely the size of the URL, the size of the header including compression information), so the best way to determine the maximum length in practice is simply by testing.