<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>I'm doing tests over that, but not using the cdr client ... but integrating the real-time evapi, so far, so good till now. Still some scenarios not working, but trying to figureout why and fixing them.<br></div><div><br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>De: </b>"Barry Flanagan" <barry@flanagan.ie><br><b>Para: </b>"Raúl Alexis Betancor Santana" <rabs@dimension-virtual.com><br><b>CC: </b>spce-user@lists.sipwise.com<br><b>Enviados: </b>Jueves, 2 de Febrero 2017 15:59:57<br><b>Asunto: </b>Re: [Spce-user] Billing Plan fallback on missing fee<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature">On 2 February 2017 at 15:33, Raúl Alexis Betancor Santana <span dir="ltr"><<a href="mailto:rabs@dimension-virtual.com" target="_blank">rabs@dimension-virtual.com</a>></span> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><div>Are you using the Kamailio evapi ? as the cGRates tutorial suggest, or other way to create the CDRs?<br></div></div></div></blockquote><br><div>No because that would require more customization to SP than we wish to do. So far we have just used the cdr client cdrc to inject them. </div><br><div>As I say, at this point we are just at the proof of concept stage. Lacking in manpower right now to push it further - cgrates itself is a steep learning curve. Hopefully some time this year we will run the two in parallel as a further test and see how it goes.</div><br><div>-Barry</div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><br><div>Best regards<br></div><br><hr id="m_-1970757655220384388zwchr"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>De: </b>"Barry Flanagan" <<a href="mailto:barry@flanagan.ie" target="_blank">barry@flanagan.ie</a>><br><b>Para: </b>"Oleg" <<a href="mailto:spce@irg-x.net" target="_blank">spce@irg-x.net</a>><br><b>CC: </b><a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a><br><b>Enviados: </b>Jueves, 2 de Febrero 2017 15:47:59<br><b>Asunto: </b>Re: [Spce-user] Billing Plan fallback on missing fee<br></blockquote></div><div><div class="h5"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div dir="ltr"><div class="gmail_extra"><div><div class="m_-1970757655220384388gmail_signature">On 2 February 2017 at 15:34, Oleg <span dir="ltr"><<a href="mailto:spce@irg-x.net" target="_blank">spce@irg-x.net</a>></span> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Interesting, I would have bet you'd be modifing kamailio-proxy.cfg to add routes with cgrates acc code.<br></blockquote><br><div>No - I think that might be a step too far for the good people at Sipwise Support :-) </div><br><div>-Barry</div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> Thanks<br> <br> Oleg<div><div class="m_-1970757655220384388h5"><br> <br> On 2017-02-02 16:24, Barry Flanagan wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-1970757655220384388h5">On 2 February 2017 at 14:53, Oleg <<a href="mailto:spce@irg-x.net" target="_blank">spce@irg-x.net</a>> wrote:<br> <br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for Your comment. Indeed, I too have to update 10 or 30<br> Billing Plans every time my upstream providers change rates. It's<br> somewhat cumbersome to maintain and repeat same fees across all the<br> billing plans all the time.<br> <br> Your idea with CGRates sounds interesting. Any pointers for<br> integration between sipwise and cgrates?<br></blockquote><br> We would just intend to replace rate-o-mat with a daemon to feed in<br> the CDR to cgrates then mark them as rated in SP. Our invoicing system<br> then takes in its rated CDR from cgrates instead of SP.<br> <br> We have already decoupled our front-end rate management system from<br> SP. Instead of writing the rates directly to SP it gets written to a<br> separate system, which can then populate the rates in either/both SP<br> and cgrates.<br> <br> So far we have successfully exported the same rate card to both<br> systems and have sent sample SP CDR to cgrates and confirmed they were<br> correctly rated. Still a lot of work to do though.<br> <br> -Barry<br> <br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-1970757655220384388h5">Thanks.<br> <br> Oleg.<br> <br> On 2017-02-02 14:48, Barry Flanagan wrote:<br> <br> On 2 February 2017 at 13:01, Oleg <<a href="mailto:spce@irg-x.net" target="_blank">spce@irg-x.net</a>> wrote:<br> <br> Hello,<br> <br> Just wandering if there is a way to tell SPCE to fallback to an<br> alternative billing_plan if rate-o-mat does not find a Fee in the<br> current plan (on Customer's billing plan missing Fee, apply<br> Reseller' billing plan fee for the given destination, if present).<br> <br> No, not possible at the moment. Pity. It would be great if you<br> could<br> assign a "fallthrough" rate card to a customer. So, you could have<br> your standard rate card as base, and then for customer A you can<br> have<br> a rate card with just a few (say UK) rates. A call from this<br> customer<br> would first check their rate card and if not found, check the<br> fallthrough one.<br> <br> This would mean that instead of having to maintain full separate<br> rate<br> cards for every customer where there is a slight difference, you<br> just<br> maintain the standard rates and then the smaller individual rate<br> cards<br> per customer.<br> <br> This and the lack of multiple Free Time "buckets" are my biggest<br> gripes with SP (I am on Pro).<br> <br> We are actually investigating cgrates as an alternative rating<br> engine<br> (we don't use the invoicing built in to SP)<br> <br> -Barry Flanagan<br> <br> Example.<br> <br> - 'DefaultResellerBillingPlan' contains all the destinations<br> - 'ClientsOfferPlan' contains one destination Fee only (ex.: 5%<br> discount calculated for fees to US<br> '^1,on_peak_init_rate,on_peak_init_interval,...')<br> <br> A user with 'ClientsOfferPlan' assigned is billed through<br> DefaultResekkerBillingPlan for all the destination (therein<br> present), except for one Fee ('^1'), which is billed through<br> 'ClientsOfferPlan'.<br> <br> In other words, I'd like sipwise to rate (and include in Invoice)<br> 'accounting.cdr.source_reseller_cost' (if > 0) when<br> accounting.cdr.source_customer_cost=0.<br> <br> Is this possible?<br> <br> Thank You<br> <br> Oleg<br> _______________________________________________<br> Spce-user mailing list<br> <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br></div></div><a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a> [1] [1]<br> <br> Links:<br> ------<br> [1] <a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a> [1]<br></blockquote><span> <br> <br> <br> Links:<br> ------<br> [1] <a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br> </span></blockquote><br></blockquote></div><br></div></div><br>_______________________________________________<br>Spce-user mailing list<br><a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br><a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br></blockquote></div></div></div></div></div><br>_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
<br></blockquote></div></div></div><br></blockquote></div></div></body></html>