MMS Charging with E// CS 5.0

MMS Charging with E// CS 5.0 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 19, 2016 » MMS Charging with E// CS 5.0 « Previous || Next »
Author Message
DAVID AYMERIC
New member
Username: Davidaymeric

Post Number: 1
Registered: 01-2015
Posted on Monday, January 12, 2015 - 06:19 pm:   

Hello support,

We are using NowMMS 2010.11.26 and we would like to charge MMS using Diameter CCR messages with Ericsson Charging System 5.0 plateform.

Does our current NowMMS version support MMS Diameter CCR Charging ?
If not then what would it take to do so ?
If yes then how can we configure this functionality ?

Other question :
Does NowMMS Diameter Charging functionality manage MMS with multiple recipients ? How ?

Thanks for your help.

David AYMERIC
Digicel FWI –VAS Engineer
Immeuble Oasis Quartier Bois Rouge, 97224 Ducos, Martinique
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5161
Registered: 08-2008
Posted on Tuesday, January 13, 2015 - 01:13 am:   

Hi David,

Customers have connected NowMMS to Ericsson Charging Systems using both SCAPv2 and SCAPv1. I do not know what version of the Charging System supports which SCAP version. SCAPv2 is newer and preferable. (Generic Diameter can also be used.)

Detailed information on this implementation can be found here: http://www.nowsms.com/mmsc-diameter-mm9-implementation

Support was added starting with version 2013.04.01, so it would requite an upgrade.

--
Des
NowSMS Support
DAVID AYMERIC
New member
Username: Davidaymeric

Post Number: 2
Registered: 01-2015
Posted on Tuesday, January 13, 2015 - 05:38 pm:   

Hi Des,

Thanks a lot for this quick answer.

Could you tell me what it takes to upgrade our Now SMS MMS Gateway version (compatibility ? cost ?) ?

Besides, could you tell me if NowMMS manages MMS charging when there are several recipients (one to many MMS which should be charged many times) ?

Finally could you tell me if NowMMS MM9 can be linked to severals Charging Systems (one C.S. per country) and if we can implement msisdn based routing rules ?

Thanks again
Regards
David
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5168
Registered: 08-2008
Posted on Friday, January 16, 2015 - 07:32 pm:   

Hi David,

Apologies for the delay in response this time.

I have forwarded your message to a sales colleague to email you about upgrade information. Compatibility should not be a concern.


quote:

Besides, could you tell me if NowMMS manages MMS charging when there are several recipients (one to many MMS which should be charged many times) ?




Yes.

By default, the MMSC issues a separate charge for each recipient.

There is a configuration setting for an alternative technique where a single charge is made, with the unit charge set to the number of recipients.


quote:

Finally could you tell me if NowMMS MM9 can be linked to severals Charging Systems (one C.S. per country) and if we can implement msisdn based routing rules ?




Multiple Diameter servers can be configured in the MMSC.

An HTTP based accounting callback is required to tell the MMSC which Diameter server to send the charge to.

Basically, the MMSC issues an HTTP request to a script you need to provide. The parameters tell the sender and recipient, and the response from the script tells the MMSC which Diameter server should receive the charge.

--
Des
NowSMS Support
DAVID AYMERIC
New member
Username: Davidaymeric

Post Number: 3
Registered: 01-2015
Posted on Wednesday, May 13, 2015 - 09:29 pm:   

Hi support,

I have successfully upgraded Now SMS MMS Gateway version.

I have successfully implemented and tested MM9 Diameter SCAPv2 charging towards multiple Diameter servers and with a subscribers white list (using PreAuth Callbacs).


Now, I have a last thing to set. I would like to put the MCCMNC and the SGSN IP address on the Diameters messages in order to charge roaming traffic properly.

On MMSC.INI, I have set extra headers under [MMSC] to have this information available. But I don't know how to set these extra header variables under [MM9Diameter].

Could you tell me what is the right syntax for these variables ?

The following does NOT work :

[MMSC]
AccountingExtraHeaders=X-WAP-3GPP-SGSN-MCC-MNC,X-WAP-3GPP-SGSN-ADDRESS

[MM9Diameter].
Subscription-Id-Location=@@X-WAP-3GPP-SGSN-MCC-MNC@@
SGSN-MCC-MNC=@@X-WAP-3GPP-SGSN-MCC-MNC@@
SGSN-Address=@@X-WAP-3GPP-SGSN-ADDRESS@@

Thanks for your help
Regards
David
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8109
Registered: 10-2002
Posted on Thursday, May 14, 2015 - 12:29 pm:   

Hi David,

It depends on how you want to include those parameters in the Diameter packet.

For Ericsson SCAPv2, I believe the expected behavior is to encode the SGSN MCC MNC as the Subscription-Id-Location.

To enable this with the default Diameter templates, use these MMSC.INI settings:

SupportedExtensionSets=SCAP
Subscription-Id-Location=@@SGSNMCCMNC@@

It is also possible to encode 3GPP-SGSN-MCC-MNC and SGSN-ADDRESS as per their definition in 3GPP TS 32.299, but I don't think Ericsson supports this. This is enabled via the SupportedExtensionSets=3GPPSGSN setting. (Or SupportedExtensionSets=SCAP,3GPPSGSN to enable both SCAP and these parameters.)

Start with just the SCAP extension set, as I believe that is what Ericsson expects.

For more custom requirements, the diameter-credit-control.xml template can be edited, but you should not need to do that unless you have extra required parameters on your system.

-bn

Bryce Norwood
Now SMS/MMS Support
DAVID AYMERIC
New member
Username: Davidaymeric

Post Number: 4
Registered: 01-2015
Posted on Thursday, May 14, 2015 - 08:59 pm:   

Hi Bryce,

Thanks for your answer.

Indeed, only the Subscription-Id-Location AVP is supported by E//.

I cannot manage to set the @@SGSNMCCMNC@@ variable for this AVP.
Yet it works well if I set a fixed value ('hello' value for example) on this AVP or if I set any other variable (variable @@SGSNADDRESS@@ works well on this AVP for example but this is not what we want...).

There must be an issue with this variable. I have noticed that both 3GPP AVP 18 and SCAPv2 AVP 1074 are missing (see WhireShark trace attached).

I have also attached the MMSC.INI and the dictionnary



Have you been told about any issue on the @@SGSNMCCMNC@@ variable ?



Thanks for you help
Regards
David
David
application/octet-streamWhireSharkTrace
MMS-Diameter-Trace.pcapng (95.4 k)
application/octet-streamMMSC.INI
MMSC.INI (6.3 k)
text/xmldictionnary
diameter-credit-control.xml (5.9 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8111
Registered: 10-2002
Posted on Thursday, May 14, 2015 - 09:49 pm:   

Hi David,

OK...I see what you mean. I thought this bug had been fixed, but it has not.

I found a reference to this problem in another thread http://support.nowsms.com/discus/messages/485/71497.html (December 23, 2013 post).

The solution is to add the following to the [MM9Diameter] section of MMSC.INI:

SGSNMCCMNCHeader=X-WAP-3GPP-SGSN-MCC-MNC

It appears that we never fixed that problem, and have been using this work-around when needed.

Note that you will need to create this section as this particular setting is global, not server specific. (It tells the MMSC which HTTP header has the MCC-MNC value, as the default header is being handled wrong). So just add this:

[MM9Diameter]
SGSNMCCMNCHeader=X-WAP-3GPP-SGSN-MCC-MNC

-bn

Bryce Norwood
Now SMS/MMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics