| VASP - Diameter initiation. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 14, 2015 ⬆ |
◄ ► |
| Author | Message | |||
| No Name New member Username: Ncblx Post Number: 11 Registered: 02-2014 |
Hello. We have a VASP account for MM7. While sending MMS MM7 is not generated Diameter Accounting Request. How can we configure VASP account to connect from VASP MM7 while sending MMS received Diameter Accounting Request? And how can we limit the list to send MMS to subscribers for VASP MM7 Thanks. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5088 Registered: 08-2008 |
Hi, I can confirm that this is true. DIAMETER is only used for local MM1 subscribers, as that is what most charging systems are prepared to accept. We rely on accounting callbacks for charging on other interfaces. I discussed this with members of our engineering team, and the general consensus is that we would need guidance to consider options to extend this interface to VASP accounts. One of the basic underlying issues is that the VASP sender does not necessarily correlate 1-to-1 with a VASP account, and we're not sure how to best handle this. -- Des NowSMS Support | |||
| No Name New member Username: Ncblx Post Number: 12 Registered: 02-2014 |
Hi. How soon will you be able to make the necessary changes? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5091 Registered: 08-2008 |
I do not know. It requires guidance for how the DIAMETER parameters should be handled in a VASP scenario. Specifically the issue of how to specify VASP account name in DIAMETER request. -- Des NowSMS Support | |||
| No Name New member Username: Ncblx Post Number: 13 Registered: 02-2014 |
Hi Des, no need to indicate VASP account name on DIAMETER request. You can put A and B number (short number) on specific AVP just like as you do it on MM1 | |||
| No Name New member Username: Ncblx Post Number: 14 Registered: 02-2014 |
Hello Des. Any news? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5097 Registered: 08-2008 |
It is being looked into, but it is more a question of weeks than days. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5098 Registered: 08-2008 |
It is being looked into, but it is more a question of weeks than days. | |||
| No Name New member Username: Ncblx Post Number: 19 Registered: 02-2014 |
Hello Des. Any news? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5122 Registered: 08-2008 |
Hi, This issue is addressed in the following update: http://www.nowsms.com/download/nowsms20141122.zip -- Des NowSMS Support | |||
| No Name New member Username: Ncblx Post Number: 23 Registered: 02-2014 |
During sending a MMS. with there is no the proceeding traffic Diameter | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5136 Registered: 08-2008 |
For normal MM1 requests? Or only for MM7? By default, MM7 (or any VASP submissions) submission do not generate Diameter requests, only MM1 submissions from local users. In this update, a setting was added. It is described in the release notes (changes.txt), and I have copied below. * DIAMETER: Add support for DIAMETER callbacks for message submissions from VASP accounts via MM1, EAIF and MM7. By default, only MM1 submissions from MMSC user accounts trigger DIAMETER. To also use DIAMETER for VASP requests, add DiameterChargeVASP=Yes to the [MM9Diameter] section of MMSC.INI. | |||
