| Missing X-MSISDN Header |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ |
◄ ► |
| Author | Message | |||
| Fino New member Username: Fino Post Number: 1 Registered: 11-2008 |
Hi, We are using Nowwap to serve our CDMA 1xRTT customers in the last couple of years. Currently, we encounter a problem in our WAPGW, and expect to get helpful support from you. The issue is related to MSISDN forwarding where our Nowwap often doesn't get the MSISDN header properly to be forwarded to the destination address. This has caused some of our applications not working properly, as they rely on the MSISDN value in WAP headers for authentication. This has been going on in the last one month or so. Most of the time, the MSISDN (or IMSI in CDMA) is provided correctly. But increasingly it is not. Please note, in the Nowwap configuration, we have enabled the following options: - Forward X-MSISDN header in content server requests - Require MSISDN for all gateway connection Please help how we should trace the problem and solve the issue. Is there any configuration that we missed? Or is it a bug in Nowwap that requires an update or patch? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 234 Registered: 08-2008 |
Hi, It sounds like you could be encountering the problem referenced here: http://blog.nowsms.com/2008/10/nowwap-radius-accounting-and-msisdn.html If you are experiencing an increase in data traffic on your system, I would especially guess that this is the issue. -- Des NowSMS Support | |||
