| Accounting Extra Headers for Roaming |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Alma Muñoz |
We have the MMSC version 2008. We currently do not received any parameter that allows us to charge and identify MMS originated in a roaming partner network. Our WAP gateway is Ericsson and I would like to know if with our current MMS version we are able to receive the AccountingExtraHeaders? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2531 Registered: 08-2008 |
Hi, According to the article that describes this capability: http://blog.nowsms.com/2010/04/operator-mmsc-accounting-detecting.html It requires NowWAP 2010 and NowSMS 2009 (or later). It also requires that your RADIUS accounting feed includes the 3GPP SGSN-MCC-MNC and SGSN-ADDRESS attributes. -- Des NowSMS Support | |||
| Alma Muñoz New member Username: Acmu Post Number: 2 Registered: 10-2006 |
We purshased the Upgrade for NowSMS 2009. How we should proceed with the installation? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2532 Registered: 08-2008 |
Hi, Note that it also requires NowWAP 2010, as described in the link that I referenced above, as the processing flow goes from RADIUS accounting, to NowWAP, to the MMSC, to the accounting callbacks. If you have an upgrade authorisation for 2009, but not 2010, I can send you NowSMS 2009 via e-mail (it is not available for download). Send an e-mail message to nowsms@nowsms.com with "Attention: Des" in the subject line. Please include a screen capture of the "Serial #" page of your NowSMS installation, and company details, so that I can verify this before sending you the file. -- Des NowSMS Support | |||
| Alma Muñoz New member Username: Acmu Post Number: 3 Registered: 10-2006 |
We do not use NowWAP as we have an Ericsson WAP Gateway. I will send you the upgrade authorisation. I'm not sure if its for the 2009 or 2010 version. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2533 Registered: 08-2008 |
Hi Alma, I'm happy to send you the file once I have your information, but it is not going to work unless there is some way that the Ericsson WAP Gateway can be configured to pass additional HTTP headers to provide this information. We do not require the headers to be generated by NowWAP. Please refer again to the article that I referenced, and I will explain how it works in a little more detail. The MMSC (beginning with 2009 version) has a feature where it can extract additional HTTP headers that are passed to the MMSC accounting callbacks. One example of how this can be useful is detecting transactions from roaming subscribers. However, in order to use this capability, the WAP gateway must insert whatever headers are of interest, just as the WAP gateway currently provides identification of the user's MSISDN to the MMSC. The MMSC can be configured to inspect any HTTP headers and forward the content of these headers to the accounting callback. NowWAP 2010 automatically checks for the 3GPP SGSN-MCC-MNC and SGSN-ADDRESS attributes, and when NowWAP processes a request, the forwarded HTTP request will include "X-WAP-3GPP-SGSN-MMC-MNC:" and "X-WAP-3GPP-SGSN-ADDRESS:" headers with the associated values. The example in the link that I keep referencing configures the MMSC to look for those headers and include them in the MMS accounting callbacks, so that you can detect if the subscriber is roaming. If you are using a different WAP gateway, then you need to check to see if that WAP gateway can include any headers that can be useful to you in this way. Regarding the update ... If you have 2010 authorisation, you can download the trial version of NowSMS from this web site as an update. The trial version will not revert to a trial license, it is also used to update your system. If it detects an older license that does not have an updates agreement, it will simply refuse to install the update, and the existing installation will not be modified. -- Des NowSMS Support | |||
| Alma Muñoz New member Username: Acmu Post Number: 4 Registered: 10-2006 |
Hello, We have already done the upgrade to 2010 version. We recently installed a new Ericsson WAP Gateway and instead of the SGSN address, it sends the GGSN address. In this case what is the accounting extra header we should configure on the MMSC.ini file? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2735 Registered: 08-2008 |
Hi Alma, I cannot tell you how the Ericsson WAP gateway works. If the Ericsson WAP gateway forwards this information in an HTTP header, then you can configure the MMSC to forward the content of this HTTP header to your accounting callback. If you refer back to the link that I posted earlier in this thread, it describes how NowWAP generates these headers, and the NowSMS MMSC is configured to parse them and forward them to your accounting callback. I will explain this in a little more detail, so you can understand how you could interface with another WAP gateway. However, you will need to figure out how the other WAP gateway encodes this information. In the case of NowWAP, NowWAP inserts the following HTTP headers: X-WAP-3GPP-SGSN-MCC-MNC: xxxxx X-WAP-3GPP-SGSN-ADDRESS: a.b.c.d You then tell the MMSC to look for these headers by editing MMSC.INI, and under the [MMSC] header, adding: AccountingExtraHeaders=X-WAP-3GPP-SGSN-MCC-MNC,X-WAP-3GPP-SGSN-ADDRESS When this parameter is present, the MMSC looks for any of the HTTP headers in this comma delimited list and includes them in the MMS accounting callback if they are present. They are appended to the accounting callback URL like this: &X-WAP-3GPP-SGSN-MCC-MNC=xxxxx&X-WAP-3GPP-SGSN-ADDRESS=a.b.c.d So if the Ericsson gateway uses some other HTTP header(s), you would insert the name of these header(s) into the AccountingExtraHeaders= parameter in MMSC.INI. And the MMSC would forward the values for those headers in the HTTP request that is sent to the accounting callback. I do not have any information about what HTTP headers might be used for this purpose on an Ericsson WAP gateway. All this said, I do have a concern that if the gateway can only provide you with the GGSN address, this will be of no value in determining whether or not a subscriber is roaming. It is my understanding that the GGSN would always be within your home network. The SGSN could be on a roaming network. -- Des NowSMS Support | |||
| Alma Muñoz New member Username: Acmu Post Number: 5 Registered: 10-2006 |
Hi Des, We have made the changes on our WAP Gateway and now the SGSN IP Address is sent in the HTTP Header. I have added the line in the MMSC.ini config file: AccountingExtraHeaders=X-WAP-3GPP-SGSN-MCC-MNC,X-WAP-3GPP-SGSN-ADDRESS But I don't see that the IP Adddress is sent in the accounting call back. Could you check this? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3044 Registered: 08-2008 |
Hi Alma, I'd need to see a trace to confirm that the headers are present and the format is as expected. Either a Wireshark trace, or MMSCDEBUG.LOG. -- Des NowSMS Support | |||
