Hello,
a credit control module using diameter and not bound to ims sounds quite
useful. There are many providers relying now on radius that consider
upgrading to diameter, but it is unlikely to deploy ims platform for
their telephony services. Having it will create the playground for those
considering diameter as their next AAA system.
I don't know how much shared code is going to be between existing module
and the new one, if it is a lot, then a new internal library can be
created (or the shared code added to an existing one).
Cheers,
Daniel
On 17/02/15 22:54, Shane Harrison wrote:
Hi all,
As you will have seen from my posts, I have adapted the ims_charging module to work with
usrloc module i.e. outside ims environment.
I am interested in whether others see a use in having a Diameter Credit Control module
that is standalone. There are already a number of Credit Control modules other than the
ims one e.g. cncxx and I am not sure if the community sees a need for YACC.
If there is interest then need to consider further how best to approach accommodating
both ims dependence and standalone operation.
Cheers
Shane
Shane Harrison
Senior Software Engineer
Imagination Technologies NZ Limited
Level 2
1 Market Grove
Lower Hutt, 5010
New Zealand
PO Box 30-449
Lower Hutt, 5040
New Zealand
Phone: +64 4 890-3681 ext 3361
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany -
http://www.kamailioworld.com