| Wap gateway restriction base on APN |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Ronald Ison New member Username: Isonronald Post Number: 3 Registered: 09-2010 |
We have a Now.WAP Proxy V2.59 I wish to escalate the concern of our customer. They wish to make restriction on Wap gateway based on specific APN users (specific APN range) to access specific website, please assist us on that matter. Is this possible and how? Your feedback is highly appreciated. Thank you | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2485 Registered: 08-2008 |
Hi Ronald, I think this link will explain the options: http://blog.nowsms.com/2008/07/one-wap-gateway-for-both-mms-and.html -- Des NowSMS Support | |||
| Ronald Ison New member Username: Isonronald Post Number: 5 Registered: 09-2010 |
Hi Des, Thanks for the reply Is this possible for Now.WAP Proxy V2.59 Can I ask for a support/quotation for this activity ? Can you give me details/procedures on how can I ask for a support from now.sms ? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7921 Registered: 10-2002 |
Hi Ronald, This requires NowWAP 2008 or later. (We changed the version numbers to be date based beginning in 2008.) If you need to discuss updating a maintenance contract, please contact our sales department, and they can explain procedures. Either call the telephone number (during UK business hours) on the Contact page at http://www.nowsms.com/contact.htm, or e-mail nowsms@nowsms.com, or fill out the contact form on the contact page. -bn Bryce Norwood NowSMS Support | |||
| Ronald Ison New member Username: Isonronald Post Number: 6 Registered: 09-2010 |
Thanks for the reply Would you mind if ask, is our Now.WAP Proxy V2.59 belongs to NowWAP 2008 or later ? OR NOT ? Just wanted to know. thanks again | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7923 Registered: 10-2002 |
No. Beginning in 2008, we changed the NowWAP version numbering to be date based. 2.59 is an earlier version that did not include this functionality. -bn | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 9 Registered: 09-2010 |
Hi Bryce, Thanks for the feedback, Could you please provides for each of the NowWAP2008 version and the latest one with the following point: 1.) the new features and improvements, compare to the our existing V2.59 version ? 2.) what is the minimum required in term of HW/platform and OS to run those versions ? 3.) what is the impact of this upgrade on the existing setup and configuration ? Appreciate your feedback Thank you ronald | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2500 Registered: 08-2008 |
Hi Ronald, We do not publish detailed change notes for NowWAP (unlike with the NowSMS MMSC for which we publish a detailed change history). The primary changes between v2.59 and 2008 was to add support for load balanced configurations and RADIUS forwarding. RADIUS support was also improved to fix a problem where RADIUS packets were being dropped under heavy load with user connections being rejected with the message "Error: Unable to determine phone number from dial-in server." The 2008 release also added support for limiting access for one or more APNs when servicing multiple APNs, as described here: http://blog.nowsms.com/2008/07/one-wap-gateway-for-both-mms-and.html The 2009 release added support for a 64-bit version that could handle a larger number of concurrent connections. There were also significant performance improvements for both 32-bit and 64-bit environments to improve performance and reduce overhead when processing a larger number of connections. The 2010 release added support for forwarding additional RADIUS headers as described at http://blog.nowsms.com/2010/04/operator-mmsc-accounting-detecting.html. The purpose of this support is to allow the MMSC to detect transactions being performed by roaming subscribers. (Additionally, some customers use these headers to differentiate between 2G and 3G data connections.) Each release also contains compatibility fixes based upon real world feedback and problem determination. There have been no changes to the hardware and OS requirements, except that a 64-bit Windows OS is required to run the 64-bit version. And 4GB memory is a recommended minimum amount of memory on that version. Specific hardware requirements depend too much on the number of concurrent users that need to be supported. All updates read the existing configuration from previous versions, and only a momentary restart (less than 5 minutes downtime) of the service is required to update. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2501 Registered: 08-2008 |
I couldn't find an article that talked about the reporting. The reports are fairly simplistic, but they are designed to allow you to extract some operational information. Here is a quick overview ... --- When usage reports are enabled, NowWAP will automatically generate daily and monthly usage reports. These reports are located in the REPORTS subdirectory of the NowWAP installation. REPORTS\LOGDB contains SQLite format databases with one database per month. REPORTS\TEXT contains text format summary reports of NowWAP usage. Daily reports have file names of YYYYMMDD.TXT and monthly reports have file names of YYYYMM.TXT. Every night at midnight, a new daily report and updated monthly report for the current month will be generated. The format of the text report will be similar to the following: NowWAP Usage Report: YYYYMMDD #### - Max Active Users #### - Max Active Requests #### - Total Unique MSISDN #### - Total Sessions #### - Total Requests Top Active Users #### - Phone Number 1 #### - Phone Number 2 etc... Top Content Domains #### - Domain 1 #### - Domain 2 etc... Top Content Servers #### - Server 1 #### - Server 2 etc... | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 10 Registered: 09-2010 |
Hi Des, Thanks for the feedback, Just a note, I wander if the last message is connected to your earlier reply? thanks mcronald | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2502 Registered: 08-2008 |
Hi Ronald, Yes, the second message was simply adding a bit of information on the reporting as I was going to point to a link that described it, but couldn't find a good existing link. -- Des NowSMS Support | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 11 Registered: 09-2010 |
Hi Support, We have renewed our maintenance contract, Can you give us procedure on how to upgrade/update/download the latest Now Wireless release ? Please reply, We need this as much as possible thank you for the usual assistance Ronald | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2542 Registered: 08-2008 |
Continued in the following thread: http://support.nowsms.com/discus/messages/1/60168.html | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 15 Registered: 09-2010 |
Dear nowsms/nowwap support, Thank you for the support we have successfully upgraded the WAPGW version. Going back to the original subject/message may I request for the procedure FOR THE RESTRICTION OF APN TO ACCESS SPECIFIC WEBSITE USING THE WAP Gateway (nowwap.proxy) We need to restrict the IP range 192.168.0.0/24 To access only our MMSC 10.30.1.1 and 10.20.2.2 AND TO access only our WAP portal http://10.40.4.4/mymain2.php | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2547 Registered: 08-2008 |
This is scenario 2 in the link that I referenced earlier. http://blog.nowsms.com/2008/07/one-wap-gateway-for-both-mms-and.html To specifically address your scenario: Manually edit the WAPGW.INI file (\Program Files\NowWAP is the default location) and under the [WAPGW] header add: IncludeMsisdnConnectOnlySourceIP=192.168.0.* This tells the WAP gateway that for any requests that come from clients in that IP address range, the gateway should only allow connections to domains/hosts in the "X-MSIDN" list. So you need to have the following entries configured on the "MSISDN" page of the NowWAP configuration, in the "Content domains to receive 'X-MSISDN' header" list: 10.30.1.1 10.20.2.2 10.40.4.4 If any of your clients are configured to access these servers by a local DNS host name instead of IP address, then this host name should also be added to the list. -- Des NowSMS Support | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 16 Registered: 09-2010 |
Hi Des/NowSMS support. Thank you for the prompt response Last question What will happen to the connections from other APN IP addresses (other than 192.168.0.* which I made restriction) ? thank you Ronald | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2551 Registered: 08-2008 |
Hi Ronald, For clients outside that IP range, all connections are allowed, but the X-MSISDN header is also inserted if the destination is in the list. Restrictions are only placed on connections from source IPs in the range of that additional setting. | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 17 Registered: 09-2010 |
Hi Des/NowSMS support, Thanks for the fast response Many tests have been performed regarding applying the restriction base on APN on the new Wap version, the method we used was to test first the restriction basing in one subscriber having the ip address defined in the range we want to do the restriction ,for that purpose we added IncludeMSISDNConnectOnlySourceIP=ip.addrsubscriber under the WaPGW.ini file , we then added the domain to restrict access in the "MSISDN" page as follow ,http://mmc.digicelhaiti.com/servlets/mms, http://172.16.3.136/mymain2.php , http://wap.mydigicellive.com/haiti, the issue is that this subscriber was not able to access neither the other web sites nor those including in the "MSISDN" page, furthermore the traffic was very affected because of other subscribers in the same range were not able to use the service. Is there any further parameters we must add under the WaPGW.ini file in order to have this specific subscriber reach only those specific domains ? Your urgent assistance is needed to complete the process. | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 18 Registered: 09-2010 |
Hi Des/NowSMS support, One more question to add, Is this possible with just single IP to be restrict? (for testing purpose) thanks ronald volubill | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2552 Registered: 08-2008 |
Please explain the exact configuration. DO NOT add URLs to this list. Host names and/or domain names are expected.. For example, instead of: http://wap.mydigicellive.com/haiti http://mmc.digicelhaiti.com/servlets/mms http://172.16.3.136/mymain2.php You would list: wap.mydigicellive.com mmc.digicelhaiti.com 172.16.3.136 Do not list URLs here, only host/domain names. Does that resolve the problem? One IP to restrict is fine. -- Des NowSMS Support | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 19 Registered: 09-2010 |
Hi Des/Now SMS support, another, For this case Do I need to put "check" in the MSISDN page configuration the []Require MSISDN for all gateway connections ? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2553 Registered: 08-2008 |
Yes | |||
| Ronald VBsupportPH New member Username: Isonronald Post Number: 20 Registered: 09-2010 |
this issue has been solved. Thank you very much Des/NOWSMS support for the assistance. salamat Ronald | |||
