| MSISDN how works in Now.WAP Proxy v2.50? |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Anibal Acosta New member Username: Aacosta Post Number: 7 Registered: 03-2004 |
I need that my MMSC receive the mobile number or the GSM IMSI from the Now.WAP but I don't know how to configure the Now.WAP, I am in the MSISDN Tab and I check the checkbox "Activate Radius accounting for MSISDN Collection" When I enable this, the port number and shared secret is enabled too, I asume that the that are values of my radius server? Also is enabled the Other three checkbox 1) Activate Simple Radius Authentication Server ... For what is used this? 2) Require MSISDN for all gateway connections .. For what is used this? 3)This I think that is the important for me, the forward of the MSISDN in the HTTP header, what I need to put in the "Content Domain to receive" TextBox? Thanks a lot | |||
| Kent Williams Moderator Username: Kent Post Number: 47 Registered: 10-2003 |
Hi, Setting up the RADIUS feed can be complicated. Most of the configuration occurs outside of Now.WAP. You need to configure your access servers (GGSN) to use RADIUS. When you configure the RADIUS in the access server, you are configuring the access server to use Now.WAP as a RADIUS Accounting server, and possibly also as a RADIUS authentication server. (Some access servers allow these roles to be defined separately, others only allow a role where RADIUS accounting and authentication are sent to a single RADIUS server.) Go ahead and activate the Simple RADIUS Authentication Server (if you do not use it, there will be no harm in having it enabled). By default, this server acts as a RADIUS Authentication server and accepts every connection request regardless of the username and password supplied. (This is usually normal in a mobile environment, as phones are not configured with unique user ids for connecting to the GPRS APN.) The tough part of troubleshooting a RADIUS setup is determining whether or not the access server is correctly forwarding the RADIUS requests to the Now.WAP proxy. To see this, you must enable the debug log in Now.WAP. Manually edit WAPGW.INI, and under the [WAPGW] section header, add Debug=Yes. Then restart the Now.WAP service. References to received RADIUS packets should appear in the WAPDEBUG.LOG. And if you have any questions about any of this information in the debug log, simply post a log excerpt here, or e-mail it to wap@now.co.uk. When RADIUS is working properly, the sequence of events is something like this: a.) User initiates connection to access server. Access server sends a RADIUS authentication packet to request access. b.) RADIUS authentication server replies with access accepted or access rejected. c.) If access accepted, access server sends a RADIUS accounting start packet to the RADIUS accounting server. This packet includes the phone number of the device that connected, and the IP address that has been assigned by the access server. d.) The RADIUS accounting server ackwnowledges receipt of the accounting packet. e.) When the sesssion is complete, the access server sends a RADIUS accounting stop packet to the RADIUS accounting server to indicate that the user has disconnected. Now.WAP uses this accounting information to be able to identify the phone number associated with requests that are coming in to the proxy over IP ... as there is nowhere in the WAP protocols itself where this information is provided. And it can generate a header in requests that are proxied (such as to the MMSC), so that these other servers can also determine the phone number of a connected user. To answer your other questions ...
This means that the proxy will reject any connections if it has not received proper RADIUS accounting information to identify the user. Any requests that are generated where this identification has not been received will return an error message.
To get started, just add a * character ... that means the header will be forwarded to all content servers. For privacy reasons, you may want to restrict this header to only be forwarded to content servers that you control. If you specify a name like "domain.com" in this list, it means that any requests that go to "mms.domain.com" or "www.domain.com" or "domain.com" will receive the MSISDN header in requests. Any host connections that do not match a domain name in this list will not receive the MSISDN header. -- Kent Williams Now Wireless Support | |||
