[Spce-user] Spce-user Digest, Vol 35, Issue 4
Edo
edo.ekunwe at gmail.com
Mon May 9 14:16:10 EDT 2022
Yes, they are prepaid subscribers -- still testing at this time. I
understand that they may show up zero cost but the subscriber balance does
not reduce by the amount of the call.
I will try to set the subscriber as postpaid and see if that makes a
difference. I do need them to be postpaid and bill generated afterwards
just currently testing out a scenario where I can control a postpaid
carrier using prepaid amount limit to ensure that calls are rejected after
a certain level of risk exposure.
Thanks
On Mon, May 9, 2022 at 1:09 PM Leighton Brennan <leightonbrennan at gmail.com>
wrote:
> The alerts are saying prepaid subscribers and carriers.
> Are you using prepaid or postpaid?
>
> We don’t use prepaid subscribers so do t know if calls show as in CDR but
> it’s possible that they may show up with 0 cost as they have already paid
> for the calls.
>
> Best Regards
> Leighton Brennan
>
> On 9 May 2022, at 18:21, Edo <edo.ekunwe at gmail.com> wrote:
>
>
> Thanks for the response Leighton.
>
> Updates:
> 1. Rate-o-mat was unstable giving some errors about routes not having any
> rate assigned. I resolved that and it has been stable ever since -- 12+hrs .
> 2. I have added non-zero rates to all routes but calls still not billing
> -- see the "warning" received below
> WARNING: No duplication db credentials, disabled.
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING:
> source_carrier_provider is prepaid
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING:
> source_reseller_provider is prepaid
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING: no prepaid
> cost record found for call ID 6N8MsrLUAlBqiIIYbLeg1A.., applying calculated
> costs
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING:
> source_carrier_provider is prepaid
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING:
> source_reseller_provider is prepaid
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING: no prepaid
> cost record found for call ID XpUtGjlbgwuEVHulYflw9A.., applying calculated
> costs
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING:
> source_carrier_provider is prepaid
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING:
> source_reseller_provider is prepaid
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING: no prepaid
> cost record found for call ID 0gN01wwAdMYVUGrholUvng.., applying calculated
> costs
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING: No
> duplication db credentials, disabled.
>
> May 9 00:08:21 spce (info) ngcp-rate-o-mat[130258]: WARNING: No
> duplication db credentials, disabled.
>
>
> browsing to the call details per the subscriber still shows cost = 0.00 I
> am trying to troubleshoot why this is currently. I understand that there is
> "no prepaid cost record found" but do not know which record it is actually
> bricking at.
>
>
> Any pointers will be greatly appreciated.
>
>
> Thanks
>
>
> On Mon, May 9, 2022 at 2:06 AM Leighton Brennan <leightonbrennan at gmail.com>
> wrote:
>
>> If you run the following command
>> tail -f /var/log/ngcp/rate-o-mat
>>
>> Make a call and check what outputs. I believe that the call will only
>> show in the call log for the customer after the rating process has taken
>> place so it seems it has been rated, do you have any 0 charge destinations
>> entered.
>>
>> Best Regards
>> Leighton Brennan
>>
>> On 9 May 2022, at 01:16, Rene Krenn <rkrenn at sipwise.com> wrote:
>>
>>
>>
>> We need to see something in rateomat.log.
>>
>> pls check if the rate-o-mat service is enabled&running properly.
>>
>>
>>
>> br
>>
>>
>>
>> *Von:* Edo [mailto:edo.ekunwe at gmail.com]
>> *Gesendet:* Sonntag, 8. Mai 2022 23:12
>> *An:* Leighton Brennan <leightonbrennan at gmail.com>
>> *Cc:* Spce-user at lists.sipwise.com
>> *Betreff:* Re: [Spce-user] Spce-user Digest, Vol 35, Issue 4
>>
>>
>>
>> Hi Leighton,
>>
>>
>>
>> I checked the rate-o-mat.log and it has no information (0 bytes). Is it
>> possible that I have not set the rate engine correctly? the cdr.log shows
>> information and apparently calls being billed but no call-ID information.
>> see below
>>
>>
>>
>> sudo cat cdr.log
>>
>> May 8 00:24:05 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 2 callids and generating 2 CDRs was 61015 us.
>>
>> May 8 00:24:05 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 32.778825 CDR/sec
>>
>> May 8 00:25:08 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 66345 us.
>>
>> May 8 00:25:08 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 15.072726 CDR/sec
>>
>> May 8 00:25:11 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2982 us.
>>
>> May 8 00:25:11 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:25:21 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2911 us.
>>
>> May 8 00:25:21 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:25:31 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3282 us.
>>
>> May 8 00:25:31 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:25:41 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2536 us.
>>
>> May 8 00:25:41 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:25:51 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3074 us.
>>
>> May 8 00:25:51 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:26:01 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2667 us.
>>
>> May 8 00:26:01 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:26:11 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 50406 us.
>>
>> May 8 00:26:11 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 19.838908 CDR/sec
>>
>> May 8 00:26:14 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3211 us.
>>
>> May 8 00:26:14 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:26:24 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2285 us.
>>
>> May 8 00:26:24 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:26:34 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2981 us.
>>
>> May 8 00:26:34 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:26:44 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3276 us.
>>
>> May 8 00:26:44 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 00:26:54 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 43391 us.
>>
>> May 8 00:26:54 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 23.046254 CDR/sec
>>
>> May 8 15:53:02 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 34636 us.
>>
>> May 8 15:53:02 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 28.871694 CDR/sec
>>
>> May 8 15:55:25 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 49914 us.
>>
>> May 8 15:55:25 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 20.034459 CDR/sec
>>
>> May 8 15:56:38 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 36547 us.
>>
>> May 8 15:56:38 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 27.362027 CDR/sec
>>
>> May 8 15:58:51 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 45959 us.
>>
>> May 8 15:58:51 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 21.758524 CDR/sec
>>
>> May 8 15:59:24 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 2 callids and generating 2 CDRs was 50023 us.
>>
>> May 8 15:59:24 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 39.981608 CDR/sec
>>
>> May 8 15:59:57 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 51488 us.
>>
>> May 8 15:59:57 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 19.422001 CDR/sec
>>
>> May 8 16:01:00 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3491 us.
>>
>> May 8 16:01:00 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 16:01:10 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 66117 us.
>>
>> May 8 16:01:10 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 15.124703 CDR/sec
>>
>> May 8 16:01:13 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 2571 us.
>>
>> May 8 16:01:13 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 16:01:23 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3085 us.
>>
>> May 8 16:01:23 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 16:01:33 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 0 CDRs was 3012 us.
>>
>> May 8 16:01:33 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 0.000000 CDR/sec
>>
>> May 8 16:01:43 spce (info) mediator[1442]: mediator.c:447 [main]:
>> Runtime for loop processing 1 callids and generating 1 CDRs was 209343 us.
>>
>> May 8 16:01:43 spce (info) mediator[1442]: mediator.c:449 [main]: Total
>> CDR creation rate 4.776849 CDR/sec
>>
>> $
>>
>>
>>
>> Back <https://192.168.1.39:1443/back>
>>
>> [Show all calls \/]
>>
>> Show [5 \/] entries
>>
>> From Date: [ ]To Date: [ ]Search:
>>
>>
>>
>> *#*
>>
>> *Caller*
>>
>> *Callee*
>>
>> *CLIR*
>>
>> *Billing zone*
>>
>> *Status*
>>
>> *Start Time*
>>
>> *Duration*
>>
>> *MOS avg*
>>
>> *MOS packetloss*
>>
>> *MOS jitter*
>>
>> *MOS roundtrip*
>>
>> *Call-ID*
>>
>> *Cost*
>>
>> Total
>>
>> 0:40:38.659
>>
>> 0.00
>>
>> 173
>>
>> 1XXXXXXXXXX
>>
>> XXXXXXXXXX5777
>>
>> 0
>>
>> ok
>>
>> 2022-05-08 16:00:56.381
>>
>> 0:00:39.928
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 0.0
>>
>> 3DSBYkqxuq8TAhsH-CM-Sw..
>>
>> 0.00
>>
>>
>>
>> Thanks
>>
>>
>>
>> On Sun, May 8, 2022 at 2:36 PM Leighton Brennan <
>> leightonbrennan at gmail.com> wrote:
>>
>> If you check the rate-o-mat log it should tell you what the reason for
>> this is.
>>
>> Most likely the rates you have created don’t match the number in the CDR.
>>
>> Rate-o-mat logs are stored in /var/log/ngcp/
>>
>>
>>
>> It will tell you in this log file what the number is so you can correct
>> your billing fee.
>>
>> Best Regards
>>
>> Leighton Brennan
>>
>>
>>
>> On 8 May 2022, at 20:28, Edo <edo.ekunwe at gmail.com> wrote:
>>
>>
>>
>> Thanks Matthias,
>>
>>
>>
>> I have set up the billing profile, billing network and added the rates to
>> it. However, I cannot get it to actually bill against a call.
>>
>>
>>
>> I have a subscriber that is under a reseller and domain, the reseller has
>> a contact, billing profile and contract. When I make calls from the
>> subscriber, I route the calls through a peer (I would also like to bill
>> peers as well). After the call is complete, when I check the CDR, I see the
>> calls but the cost of the call is always showing 0.00. My problem is how to
>> tie the rate to the subscriber or peer as needed so that the balance on the
>> reseller/subscriber can be reduced based on the calls completed.
>>
>>
>>
>> Thoughts?
>>
>>
>>
>> On Sun, May 8, 2022 at 11:00 AM <spce-user-request at lists.sipwise.com>
>> wrote:
>>
>> Send Spce-user mailing list submissions to
>> spce-user at lists.sipwise.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>
>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>> or, via email, send a message with subject or body 'help' to
>> spce-user-request at lists.sipwise.com
>>
>> You can reach the person managing the list at
>> spce-user-owner at lists.sipwise.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Spce-user digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Help with Setting up Billing on CE (Edo)
>> 2. Re: Help with Setting up Billing on CE (Matthias Hohl)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sun, 8 May 2022 00:37:12 -0500
>> From: Edo <edo.ekunwe at gmail.com>
>> To: spce-user at lists.sipwise.com
>> Subject: [Spce-user] Help with Setting up Billing on CE
>> Message-ID:
>> <CAFkRdGvQxoPO-LQRij9FE9G_EFyuWD4ynXj=
>> 6+vinBNo_3oDaQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi All,
>>
>> I have been fumbling with setting up billing on sipwise CE and have been
>> unsuccessful.
>>
>> Please can someone mentor me? The documentation is not very clear as to
>> how
>> to actually achieve this.
>>
>> Thanks
>>
>> --
>> -----
>> Ekunwe
>> Tel: 601.497.3932
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220508/41e9cd3f/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 8 May 2022 17:14:12 +0200 (CEST)
>> From: Matthias Hohl <matthias.hohl at telematica.at>
>> To: 'Edo' <edo.ekunwe at gmail.com>, spce-user at lists.sipwise.com
>> Subject: Re: [Spce-user] Help with Setting up Billing on CE
>> Message-ID: <1585704095.1958400.1652022852261.JavaMail.zimbra at mx>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Ifyou could descripe me in detail where you need some help, I could try
>> if I can help you ?
>>
>>
>>
>> Normally it is very simple.
>>
>> Create a Billing Profile via the GUI and upload your billing profile
>> entries via CSV file.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Von: Edo <edo.ekunwe at gmail.com>
>> Gesendet: Sonntag, 8. Mai 2022 07:37
>> An: spce-user at lists.sipwise.com
>> Betreff: [Spce-user] Help with Setting up Billing on CE
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I have been fumbling with setting up billing on sipwise CE and have been
>> unsuccessful.
>>
>>
>>
>> Please can someone mentor me? The documentation is not very clear as to
>> how to actually achieve this.
>>
>>
>>
>> Thanks
>>
>>
>>
>>
>> --
>>
>> -----
>>
>> Ekunwe
>> Tel: 601.497.3932
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220508/9edf7b59/attachment-0001.html
>> >
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: smime.p7s
>> Type: application/pkcs7-signature
>> Size: 5022 bytes
>> Desc: not available
>> URL: <
>> http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220508/9edf7b59/attachment-0001.p7s
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>
>>
>> ------------------------------
>>
>> End of Spce-user Digest, Vol 35, Issue 4
>> ****************************************
>>
>>
>>
>>
>> --
>>
>> -----
>>
>> Ekunwe
>> EDO Network Services, Inc.
>> Tel: 601.497.3932
>> Fax: 601.979.5931
>>
>> --
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>
>>
>>
>>
>> --
>>
>> -----
>>
>> Ekunwe
>> EDO Network Services, Inc.
>> Tel: 601.497.3932
>> Fax: 601.979.5931
>>
>>
>
> --
> -----
> Ekunwe
> EDO Network Services, Inc.
> Tel: 601.497.3932
> Fax: 601.979.5931
>
>
--
-----
Ekunwe
EDO Network Services, Inc.
Tel: 601.497.3932
Fax: 601.979.5931
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220509/bb4d6211/attachment-0002.html>
More information about the Spce-user
mailing list