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 server, which enables content server, such as an MMSC to identify the subscriber.
On extremely busy systems, NowWAP was not processing Radius requests quickly enough, which could cause some packets to be lost, resulting in rejected connections.
This problem was corrected in the 2008.06.03 release of NowWAP, which is currently available for download at http://www.nowwap.com/.
More information about how to configure NowWAP and the NowSMS MMSC to use a Radius accounting feed can be found at http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm.
Additional information about configuring a Radius accounting feed in a fault tolerant and/or load balanced installation of multiple NowWAP servers can be found at http://www.nowsms.com/nowwap-in-fault-tolerant-or-redundant-load-balanced-environment.
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...