WAP Gateway

Operator MMSC without a WAP Gateway (ICAP)

When implementing an MMSC for a mobile operator network, one of the most confusing concepts is how user authentication is usually performed in conjunction with a WAP Gateway. MMS uses the MM1 Protocol (OMA MMS Encapsulation) for transactions between a mobile device and the MMSC. This protocol does not define how the MMSC identifies and authenticates the subscriber when the MMS client on a mobile...

Read More

NowWAP: Enabling Cookies for HTTP Header Enrichment

NowWAP HTTP Header Enrichment (HHE) is described in more detail in the following article:  http://www.nowsms.com/nowwap-and-http-header-enrichment In addition to the HHE issues discussed in that article, we frequently receive questions about using HTTP Cookie headers for identifying the MSISDN. These questions are usually asked for the following reasons: Customers migrating from or augmenting...

Read More

NowWAP and HTTP Header Enrichment (HHE)

The HTTP Header Enrichment (HHE) capability provides solutions for a content provider to identify a subscriber. Basic HHE allows the subscriber to be identified by their MSISDN. Aliased HHE allows the subscriber to be identified without divulging the subscriber’s MSISDN. A standard feature of the NowWAP Proxy is to provide Basic HTTP Header Enrichment to facilitate operator billing for...

Read More

WAP Gateway Blocks BlackBerry App World

WAP Gateway Blocks BlackBerry App World

It has come to our attention that the default configuration setting for the NowWAP WAP Gateway blocks users from connecting to BlackBerry App World. The reason for this seems to be some unusual communication patterns between the handset and the App World server. The handset attempts to created a tunneled connection to the HTTP port (80) of the BlackBerry App World server. Symptoms of the problem...

Read More

NowWAP, Radius Accounting and MSISDN headers

NowWAP was recently updated over the summer months to address an issue on heavily loaded systems where Radius packets could be lost. NowWAP uses these Radius accounting packets in order to determine the identity (phone number or MSISDN) associated with the device that is making a request. NowWAP includes the phone number in an X-MSISDN header when forwarding the request to a downstream content...

Read More

One WAP Gateway for both MMS and Browser Data

Smaller mobile operators often ask us how to deploy a single WAP Gateway (or WAP Proxy if you prefer that terminology, as our marketing folks seem to prefer) to deploy both MMS traffic and general browser traffic. Of course, technically there is no reason that a single WAP Gateway can’t support both types of traffic. So if you’re not a mobile operator, you’re probably wondering...

Read More

Migrating to a Multiple Server MMSC, WAP Gateway, or NowSMS Gateway

The recent postings about multiple server redundant NowSMS or NowWAP configurations have generated a lot of questions from existing customers about how to migrate an existing installation to a multiple server configuration. Migrating an existing NowWAP installation to a multiple server configuration is the easiest task to explain. That’s because there is no shared data storage requirement,...

Read More