Sippy Software, Inc.

Hi there,

In New Zealand we have two toll free prefixes (64800 and 64508). When a call comes into these numbers, we need to charge the owner of the number the following: CLI is National (64), charge $0.05/minute CLI is Mobile (642), charge $0.25/minute.

I looked at: https://support.sippysoft.com/support/solutions/articles/77881-charging-on-net-account-to-account-calls

However the "Accessibility Surcharges" only allow 1 rate per DID. We need two based on the CLI calling in.

It would be ideal if we can add prefixes the same as the Minute Plans. Or maybe a new "Reverse Charge" section. I'm sure you have many customers that require this type of rating.

In the meantime, I have to send all these calls to an Asterisk system which appends digits based on the CLI, then returns them to Sippy which can then rate the calls. It's a very messy solution.

We'd love for a proper way to do this.

Hi Juan,

As you know, On-Net Routing is Sippy's feature that empowers Account to Account calling without routing the traffic to your upstream destination providers. It empowers free calling among your customers or a special charge that you wish to apply with the Onnet_<out/in> rate. It turns out that with the example used, where the caller's Incoming CLI is Anonymous, is not the regular case with On-Net calls. If this is the case with your calls, there is an originating UA that is passing calls without CLI to your switch.

If calls are being authorized through the Authentication Rules method, the Incoming CLI field can be used to identify the region of the caller rather than the use of the Local Calling feature. The Advanced Parameters field can then be used to select a specific Tariff relating to your caller's region and bill with the special Onnet_<out/in> prefix. If you wish for Anonymous calls to be authenticated and charged accordingly, an additional rule can be set with "Anonymous" in the Incoming CLI field.

Let me know your progress and if you require more detail in an email.

Kind regards,

Kevin King

Client Success Manager - Sales & Marketing

System Configuration, Training & Optimization

Skype: Kevin.Sippy

Email: Kevin.King@Sippysoft.com

 

Hi Kevin,

Incoming calls show up as on_net though. So we can't set billing for those:

Incoming CLI	anonymous
Prefix	onnet_in

We can create a cost for all onnet_in, however that will charge all calls rather than the actual prefix.

Please advise how we'd do CLI-based billing using the Local Calling region, as I can't see a way.

Regards,

Juan

Hi Juan and Ferry,

Thank you for your feedback and comments. This is a call rating and billing scenario that is becoming more frequently requested throughout North America with their Inter/Intrastate requirements as stated by Ferry, with the ANZ market as highlighted by Juan, and with the growing A-Numbering or ORB billing discipline in Europe. Telecommunications companies such as Belgacom (Proximus Group) lead the sophisticated charging model to challenge your billing solution.

An existing feature of the Sippy Softswitch that has originally been developed for the US-based numbering plans is the "Local Calling" feature. When enabled, Sippy inspects the CLI of each call and checks it against a group of destinations that are within the local calling area. If the CLI and CLD are found within the same origination area, a Local Calling rate will be billed for the call, if supported by the vendor.

For example, if a call is made to CLD 13256427891 from CLI 14328813622, an area of TX applying to the state of Texas can be configured and each of the prefixes of these numbers will be included within the Local Calling area. Therefore, Local Calling billing will be applied to the caller's Account, billed at the intrastate rate of your choice. If your rates are based on your suppliers providing an origination-based rating, the same will apply to the vendor-facing configurations on your Sippy Softswitch, rating calls accurately based on the CLI's local calling region. Interderminate rating and billing or denial of calls can also be configured through the use of Authentication Rules for calls that do not have a correct CLI.

For more information, please visit our Local Calling online document.

We have a keen interest in refining this feature for the evolving billing requirements of this scenario so please, do not hesitate to reach out for more feedback after your investigation of the feature.

Kind regards,

Kevin King

Client Success Manager - Sales & Marketing

System Configuration, Training & Optimization

Skype: Kevin.Sippy

Email: Kevin.King@Sippysoft.com

This is the same for USA actually with their interstate and intrastate charging of calls. Would be great to have ORB billing (originated based billing) based in CLI indeed.
We now do this manually after the call has been made but this way LCR does not get to work proactively.

Regards,

Ferry