NowWAP

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 Statistics Reports

The log files created by NowWAP are of a text format that follows the common log format for web servers. These log files are stored on the NowWAP server, with one log file created for each day, using a file naming convention of WAPGW-yyyymmdd.LOG, where yyyymmdd is the 4-digit year, 2-digit month and 2-digit day. NowWAP 2011 has optional functionality which can convert these log files into a...

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

Introducing NowWAP 2009

NowMobile is proud to introduce the latest version of the NowWAP Proxy/Gateway, NowWAP 2009. We’d like to take this opportunity to let you know what is new in NowWAP 2009. And if you missed our recent announcements regarding NowSMS 2009, the NowSMS MMSC, and NowSMS Lite, you can learn more at http://www.nowsms.com/nowsms2009. The most significant improvements in the NowWAP 2009 release are...

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

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

NowWAP in Fault Tolerant or Redundant Load Balanced Environment

For many configurations it is desirable to install NowWAP on multiple servers in order to achieve fault tolerance and/or improved throughput and performance. The only special consideration when running NowWAP in this type of clustered configuration is if NowWAP is configured to use RADIUS accounting to supply MSISDN information to one or more content servers, such as an MMSC. This document...

Read More

NowSMS Operator MMSC Considerations

The primary considerations for the NowSMS MMSC in an operator environment pertain to user provisioning and user identification. In the standard configuration for the MMSC, it is a requirement that each user be configured with a special MMS Message Server URL. The URL contains the username and password of the user account on the MMSC. In an operator environment, it is not practical to provision...

Read More