[Spce-user] Billing and peer costs

[Anar Agayarov]

Thank you for the clarification, Daniel.
It means I should separate billing profiles?

At least 2 different profiles should be. For clients and for peers?



On Mon, Jun 15, 2020 at 13:26 Daniel Grotti <dgrotti at sipwise.com> wrote:

> Hi,
> the relation between peering server and billing fees is done via the
> menu "Resellers and Peering Contracts".
> When you create the peering contract, you will be asked to assign a
> billing profile.
> That billing profile should contain the FEES with your provider prices
> (15 cents).
>
> While, when you create a customer contracts, it will be associated to a
> billing profile with the FEES on 20cents.
>
>
> Cheers,
>
>
> Daniel Grotti
>
> Head of Customer Support                     Sipwise GmbH
> e: dgrotti at sipwise.com                     Europaring F15
> t: +43(0)130120332                A-2345 Brunn Am Gebirge
> w: www.sipwise.com   FN: 305595f   FG: LG Wiener Neustadt
>
> On 6/12/20 6:30 PM, Anar Agayarov wrote:
> > Dear list members.
> >
> > I hope you are doing well.
> >
> > I have 50 peer providers and each provider has around 100 prefixes.
> >
> > I can not find how I should setup a billing scheme.
> >
> > My task is very simple:
> >
> > Provider A is selling 9955552X prefix for 15 cents/minute, Provider B
> > selling 9955553X for 15 cents/minute, I am selling these prefixes to my
> > customer 20 cents.
> >
> > But nowhere I can not build billing fee and peering group relationships.
> >
> > P.S. It is not related LCR. Because I should reroute the exact call to
> > the exact provider.
> >
> > Looking forward to your help.
> > --
> >
> > Best Regards
> > Anar Agayarov
> >
> >
> >
>
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
-- 

Best Regards
Anar Agayarov

+994555644152
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200615/229fdfbe/attachment-0002.html>