[Spce-user] Using an external billing system
Skyler
skchopperguy at gmail.com
Wed Aug 21 12:50:41 EDT 2013
Oren,
Exactly, we all want a serious user/admin portal with billing and
provisioning.
Our discussion a few months ago is a perfect example. There were 9 of
us willing to be a part of the provisioner.net style integration...which
unfortunately didn't go anywhere.
Keeping with that example, one could create a blesta module designed
from provisioner.net and make that module for sale on blesta market
place. Could be for $50,$100,$150 per download. Or, just make the module
open and available on GIT with sipwise. So anyone can contribute.
I agree that, there needs to be a 'bounty' or 'fund' of some sort.
Otherwise this whole discussion is dead within 1 week.
I will commit $250 USD right now towards a complete user/admin portal
with billing and provisioning. I will commit my assistance in anyway I
can to plan development. I will also commit to contributing more $$'s
once the project is started and there is evidence of a solid foundation.
Anyone willing to commit also? Cash, coding, planning?
-Skyler
On 08/21/2013 09:38 AM, Oren Yehezkely wrote:
> Skyler,
>
> I bet that we all want these features and more.
> However this is much more than billing. this is a complete front end
> development, including a portal, billing and provisioning
> (we did have a short discussion a few months ago about Provisioner.net...).
>
> I don't assume that anybody will do this for us for free.
>
> We need to organize to raise the needed funds and develop this together.
>
> If any of you is interested in participating, feel free to PM me.
>
> Oren
>
>
> On Wed, Aug 21, 2013 at 12:25 PM, Skyler <skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>> wrote:
>
> Oren, I definitely agree that the end solution needs to be done in a
> serious way and be open to adding/customizing for anyone.
>
> What we should do here is have everyone pitch-in to create a list of
> specific objectives or needs that the billing solution must have.
> Then both projects can use those same objectives.
>
> New User signup:
> - A form that creates new accounts and services in billing and sipwise.
>
> End-user panel:
>
> - Secure login
> - Overview of account
> - Ability to pay invoices
> - Ability to view/download/email past paid invoices
> - Ability to create support tickets
> - Ability to edit billing address
> - Ability to edit e911 service address if different
> - Ability to buy DID's and add service(s)
> - Ability to manage phones and/or adapters
> - Ability to auto-suspend service(s)
> - Ability to view/search/download CDR for account and/or per DID
> - Ability to view/listen/download/delete voicemail
> - Ability to create call-forwarding or ring-group(s)
> - Ability to ...
>
> Admin Panel:
>
> - View and control all end-user(s) functions
> - View and control all sipwise functions
> - Accounting ...
>
>
> Skyler
>
>
> On 08/21/2013 09:06 AM, Oren Yehezkely wrote:
>
> Skyler,
>
> I agree with Gavin regarding forking jBilling (from version 2.0)
> if we
> can get the programmers to do that.
> As I mentioned I am willing to contribute if this is done
> seriously. If
> there is a programmer in the list who is able and willing to do
> such work,
> please feel free to PM me.
> I am willing to try a general solution like Blesta, but the
> nature of
> these products is that they are too general and I did not find
> any of
> them that will fit for telecom needs.
> Most of those products target ISPs, domain and email providers.
> None of
> them would even look at VoIP.
>
> jBilling is the first one I have seem that got it right (or at least
> very close ;) )
>
> Oren
>
>
> On Wed, Aug 21, 2013 at 11:17 AM, Skyler <skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>> wrote:
>
> Gavin, that is actually the power of sipwise. It can have
> anything
> available via API so if you want some complicated data, it
> can be
> exposed rather easily.
>
> A solution like Blesta could quickly take advantage of any
> functions exposed. Limits really seem endless. One example (of
> hundreds) is device management. Users could manage or at
> least have
> access to specific settings for any device via the Blesta
> customer
> area...and any changes could be self-administered to some
> extent.
>
> I understand that jbilling can pull cdr's and create
> billing. The
> goal is world domination, I just don't see JBilling being
> able to
> handle that without forking $24,000/yr.
>
>
>
> On 08/21/2013 08:04 AM, Gavin Sweet wrote:
>
> If you *have* to use the API, then its going to be
> expensive
> these days,
> certainly compared to free ;-)
>
> The other option is to do things in batch, but this
> limits you
> to a specific
> architecture, and also really prevents you from doing
> pre-pay.
>
> (Or, you go back to using version 2, which still
> includes the
> API, and fork
> the software from there).
>
> I don't really know Blesta, but I'd be interested to
> know what
> kind of
> volumes of CDR's you can scale to there. I guess a lot
> of people
> on this
> group will only do their mediation and rating in
> sipwise, so its
> not really
> an issue, you can inherit all the values directly from
> the CDR
> files. If
> however you want to apply any kind of alternative/mixed
> rating
> schemas with
> logic other than that supported by sipwise (e.g.
> bundles, e.g.
> other CDR
> suppliers, e.g. etc etc) then you need a mediation and
> rating
> engine in your
> billing system (or find another open source) and you do
> need it
> to scale
> once you're getting into the millions of records.
>
> Cheers
> Gavin
>
>
>
> -----Original Message-----
> From: spce-user-bounces at lists.__sipw__ise.com
> <http://sipwise.com>
> <mailto:spce-user-bounces at __lists.sipwise.com
> <mailto:spce-user-bounces at lists.sipwise.com>>
> [mailto:spce-user- <mailto:spce-user->
> <mailto:spce-user- <mailto:spce-user->>
> bounces at lists.sipwise.com <mailto:bounces at lists.sipwise.com>
> <mailto:bounces at lists.sipwise.__com
> <mailto:bounces at lists.sipwise.com>>] On Behalf Of Skyler
> Sent: 21 August 2013 15:51
> To: Barry Flanagan
> Cc: spce-user
> Subject: Re: [Spce-user] Using an external billing
> system
>
> Thanks Barry, that's what I understood as well. The
> JBilling
> API and
> any customization access is _only_ available for the
> Enterprise or
> Telco
> version(s) as of v3. So it is really useless to any
> of us
> ... unless
> your willing to shell out $2k/mth.
>
> I've been looking around for months..years even. Blesta
> really is the
> only option I could find that would accommodate
> every need
> while being
> 100% front-end (admin/users) for spce. Takes
> programming and
> time, I am
> talking with the creators right now and will know a
> cost
> soon. I'm
> thinking the module(s)/plugins(s) can be hosted
> with sipwise
> so we can
> simply D/L into Blesta any time.
>
> --Skyler
>
>
> On 08/21/2013 04:36 AM, Barry Flanagan wrote:
>
> On 21 August 2013 05:01, Oren Yehezkely
> <orenyny at gmail.com <mailto:orenyny at gmail.com>
> <mailto:orenyny at gmail.com <mailto:orenyny at gmail.com>>
> <mailto:orenyny at gmail.com
> <mailto:orenyny at gmail.com> <mailto:orenyny at gmail.com
> <mailto:orenyny at gmail.com>>>>
>
> wrote:
>
> Skyler,
>
> I also thought at the beginning that
> (jBilling) CE
> is locked
>
> down.
>
> But on a second look I am not sure about
> it anymore.
>
> I think we should give it a chance,
> especially if
> we have some
> people here in the list who are experts
> for jBilling.
>
>
> The problem with the CE version of jBilling is
> there is
> no API at all
> - they took it out when going from v2 -> v3.
> Makes it
> fairly useless
> as it can't be integrated easily with anything
> else.
>
> -Barry
>
>
> I am willing to participate significantly
> in a
> bounty for
>
> jBilling
>
> integration.
>
> I have also been following Blesta for several
> years now. Not sure
>
> if
>
> this is a product for telco services, but
> I am
> willing to listen
>
> and
>
> may be willing to contribute for a bounty to
> integrate Blesta as
>
> well.
>
>
> I prefer to stay in this list. IMHO - a
> forum is
> more efficient
>
> that
>
> a mailing list but this could be a
> different issue
> all together.
>
> Thanks,
>
> Oren
>
>
> On Tue, Aug 20, 2013 at 9:46 AM,
> <skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>__>> wrote:
>
> Wow.
>
>
>
> ------------------------------____----------------------------__--__-
>
>
> -----------
>
> *From:* "Jeremie Chism"
> <jchism2 at gmail.com <mailto:jchism2 at gmail.com>
> <mailto:jchism2 at gmail.com
> <mailto:jchism2 at gmail.com>>
> <mailto:jchism2 at gmail.com
> <mailto:jchism2 at gmail.com>
>
> <mailto:jchism2 at gmail.com
> <mailto:jchism2 at gmail.com>>>>
> *To:* "Barry Flanagan"
> <barry at flanagan.ie <mailto:barry at flanagan.ie>
> <mailto:barry at flanagan.ie
> <mailto:barry at flanagan.ie>>
> <mailto:barry at flanagan.ie
> <mailto:barry at flanagan.ie>
>
> <mailto:barry at flanagan.ie
> <mailto:barry at flanagan.ie>>>>
> *CC:* "Skyler"
> <skchopperguy at gmail.com <mailto:skchopperguy at gmail.com>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>__>>, "spce-
>
> user at lists.sipwise.com <mailto:user at lists.sipwise.com>
> <mailto:user at lists.sipwise.com <mailto:user at lists.sipwise.com>__>
>
> <mailto:spce-user at lists.
> <mailto:spce-user at lists.>__sipw__ise.com <http://sipwise.com>
> <mailto:spce-user at lists.__sipwise.com
> <mailto:spce-user at lists.sipwise.com>>>"
> <spce-user at lists.sipwise.com
> <mailto:spce-user at lists.sipwise.com>
> <mailto:spce-user at lists.__sipwise.com
> <mailto:spce-user at lists.sipwise.com>> <mailto:spce- <mailto:spce->
> <mailto:spce- <mailto:spce->>
>
> user at lists.sipwise.com <mailto:user at lists.sipwise.com>
> <mailto:user at lists.sipwise.com <mailto:user at lists.sipwise.com>__>>>
>
>
> *Sent:* August 20, 2013 6:36 AM
>
>
> *Subject:* Re: [Spce-user] Using an
> external
> billing system
>
> Telco version of jbilling is 2000.00
> US per month.
>
> Sent from my iPhone
>
> On Aug 20, 2013, at 4:30 AM, Barry
> Flanagan
>
> <barry at flanagan.ie <mailto:barry at flanagan.ie>
> <mailto:barry at flanagan.ie <mailto:barry at flanagan.ie>>
>
> <mailto:barry at flanagan.ie
> <mailto:barry at flanagan.ie>
>
> <mailto:barry at flanagan.ie
> <mailto:barry at flanagan.ie>>>> wrote:
>
> On 20 August 2013 09:51, Skyler
> <skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>
>
> <mailto:skchopperguy at gmail.com
> <mailto:skchopperguy at gmail.com>__>__>> wrote:
>
> On 08/20/2013 01:41 AM, Barry
> Flanagan
> wrote:
>
>
> @List Admins: Any chance
> there
> could be a mailing
>
> list
>
> created like
> spce-integration or
> spce-billing
> for such
>
> discussions?
>
> It could be
> useful and would help
> keep this
> list on topic.
>
> -Barry
>
>
> wouldn't that be a request for
> jbilling? I know Blesta
>
> has
>
> a dev area that would fit us
> all nice
> and tidy...I just
> bought a license and they gave me
> access ;)
>
>
> No, I was suggesting a list for the
> discussion of general
>
> SPCE
>
> integration issues relating to
> third party
> apps (jbilling
> blesta, SugarCRM, whatever) - not
> specifically jbilling or
> any other systems
>
> -Barry
>
>
>
>
>
> _____________________________________________________
>
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> <mailto:Spce-user at lists.__sipwise.com
> <mailto:Spce-user at lists.sipwise.com>>
> <mailto:Spce-user at lists.
> <mailto:Spce-user at lists.>__sipw__ise.com <http://sipwise.com>
> <mailto:Spce-user at lists.__sipwise.com
> <mailto:Spce-user at lists.sipwise.com>>>
> http://lists.sipwise.com/______listinfo/spce-user
> <http://lists.sipwise.com/____listinfo/spce-user>
>
> <http://lists.sipwise.com/____listinfo/spce-user
> <http://lists.sipwise.com/__listinfo/spce-user>>
>
>
> <http://lists.sipwise.com/____listinfo/spce-user
> <http://lists.sipwise.com/__listinfo/spce-user>
>
> <http://lists.sipwise.com/__listinfo/spce-user
> <http://lists.sipwise.com/listinfo/spce-user>>>
>
>
>
>
>
> ___________________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> <mailto:Spce-user at lists.__sipwise.com
> <mailto:Spce-user at lists.sipwise.com>> <mailto:Spce- <mailto:Spce->
> <mailto:Spce- <mailto:Spce->>
>
> user at lists.sipwise.com <mailto:user at lists.sipwise.com>
> <mailto:user at lists.sipwise.com <mailto:user at lists.sipwise.com>__>>
>
> http://lists.sipwise.com/____listinfo/spce-user
> <http://lists.sipwise.com/__listinfo/spce-user>
>
> <http://lists.sipwise.com/__listinfo/spce-user
> <http://lists.sipwise.com/listinfo/spce-user>>
>
>
>
>
> ___________________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> <mailto:Spce-user at lists.__sipwise.com
> <mailto:Spce-user at lists.sipwise.com>> <mailto:Spce- <mailto:Spce->
> <mailto:Spce- <mailto:Spce->>
>
> user at lists.sipwise.com <mailto:user at lists.sipwise.com>
> <mailto:user at lists.sipwise.com <mailto:user at lists.sipwise.com>__>>
>
> http://lists.sipwise.com/____listinfo/spce-user
> <http://lists.sipwise.com/__listinfo/spce-user>
> <http://lists.sipwise.com/__listinfo/spce-user
> <http://lists.sipwise.com/listinfo/spce-user>>
>
>
>
>
>
> ___________________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> <mailto:Spce-user at lists.__sipwise.com
> <mailto:Spce-user at lists.sipwise.com>>
> http://lists.sipwise.com/____listinfo/spce-user
> <http://lists.sipwise.com/__listinfo/spce-user>
> <http://lists.sipwise.com/__listinfo/spce-user
> <http://lists.sipwise.com/listinfo/spce-user>>
> -----
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> <http://www.avg.com>
>
> Version: 2013.0.3392 / Virus Database: 3211/6569 -
> Release Date:
> 08/11/13 Internal Virus Database is out of date.
>
>
>
> ___________________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> <mailto:Spce-user at lists.__sipwise.com
> <mailto:Spce-user at lists.sipwise.com>>
> http://lists.sipwise.com/____listinfo/spce-user
> <http://lists.sipwise.com/__listinfo/spce-user>
> <http://lists.sipwise.com/__listinfo/spce-user
> <http://lists.sipwise.com/listinfo/spce-user>>
>
>
>
More information about the Spce-user
mailing list