<div dir="ltr">Hi Jon<div><br></div><div style>Thanks. Mmm, for some reason I assumed that it would do that, probably based on the fact that one puts a billing profile/contract ID in the peering details. I guess I could work with:</div><div style><br></div><div style><span style="font-size:13px">In case you add billing profiles to the peers using direction outbound marks</span><br style="font-size:13px"><span style="font-size:13px">your cost when seding calls to the peer. You can put there the cost and use</span><br style="font-size:13px"><span style="font-size:13px">"incoming" direction and you'll get the value when the call ends in one of your</span><br style="font-size:13px"><span style="font-size:13px">subscribers.</span><br></div><div style><span style="font-size:13px"><br></span></div><div style>But it would then show the cost in the cdr records of the end user when the look at their CDRs? Am I correct? That would be problematic as well. </div><div style><br></div><div style>Seeing that this has become a critical component for us now I really hope that sipwise can do it in some way....</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 8, 2015 at 5:12 PM, Jon Bonilla (Manwe) <span dir="ltr"><<a href="mailto:manwe@sipdoc.net" target="_blank">manwe@sipdoc.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">El Fri, 8 May 2015 16:33:50 +0200<br>
Theo <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>> escribió:<br>
<span class=""><br>
> Hi<br>
><br>
> I am finally having a look at the billing side of things. Still getting my<br>
> head around most of it and will come up with more questions no doubt, but<br>
> the first one is this:<br>
><br>
> At this point I am not worried about billing our clients - I need to rate<br>
> the calls coming in from a peer as they are meant to pay us an interconnect<br>
> fee. I am struggling to grasp how this is done. From the 2.8 handbook:<br>
><br>
><br>
</span>> - *source*: The source pattern. This is a POSIX regular expression<br>
<span class="">> matching the complete source URI (e.g. ^.*@sip\.example\.org$ or<br>
> ^someone@sip\.sipwise\.com$ or just . to match everything). If you leave<br>
> this field empty, the default pattern . matching everything will be set<br>
> implicitely. Internally, this pattern will be matched against the<br>
> <source_cli>@<source_domain> fields of the CDR.<br>
</span>> - *destination*: The destination pattern. This is a POSIX regular<br>
<span class="">> expression matching the complete destination URI (e.g. someone@sip<br>
> \.example\.org or ^43). This field must be set.<br>
</span>> - *direction*: Outbound for standard origination fees (applies to<br>
<span class="">> callers placing a call and getting billed for that) or Inbound for<br>
> termination fees (applies to callees if you want to charge them for<br>
</span>> receiving various calls, e.g. for 800-numbers). *If in doubt, use<br>
> Outbound*. If you upload fees via CSV files, useout or in, respectively.<br>
<span class="">><br>
> Source - understand<br>
> Destination - there wouldn't be one. I merely need to rate the calls from a<br>
> peer. The wouldn't just go to one destination, they go all over the<br>
> platform. What is meant to go there?<br>
> Direction - Inbound I would imagine, but it must not apply to the callee,<br>
> but rather to the peer?<br>
><br>
> Any input appreciated.<br>
<br>
<br>
</span>The spce system is prepared to charge subscribers only. Not peers. When you use<br>
direction "incoming" in the billing profile assigned to your subscriber that<br>
means that you charge the subscriber for receiving calls.<br>
<br>
In case you add billing profiles to the peers using direction outbound marks<br>
your cost when seding calls to the peer. You can put there the cost and use<br>
"incoming" direction and you'll get the value when the call ends in one of your<br>
subscribers.<br>
<br>
Peer-to-peer calls cannot be rated properly AFAIK.<br>
<br>
<br>_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">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>
<br></blockquote></div><br></div>