Sippy Softswitch 2020 introduces changes into authentication and charging procedures for a DID.

Authentication

The DID Authentication Rule has received two new fields: 'Incoming CLI' and 'Type'.

Incoming CLI

This attribute is now also considered during authentication of a call. The CLI supports an exact match only, no wildcard symbols are supported.

DID Authentication Type

In earlier versions of Sippy Softswitch, only Remote Authentication Rules could be configured, which applied when a call initially arrived at the softswitch. However, there is an additional configuration, known as Late DID Recognition, that occurs after the call has already been authenticated using methods like Digest Authentication, Account Authentication Rule, or Remote DID Authentication. By using the Late DID Authentication Rule, administrators gain more flexibility in managing call routing based on DIDs after the initial authentication stage.

How Late DID Recognition Works

Once a call is authenticated, Sippy applies translations at the account level. If the call is On-Net, the system performs an extra check to see if the CLD matches any DID number (NOT Incoming DID number). If a match is found, the call is routed to the corresponding DID, following the assigned Customer or Account.

Introducing the "Late" DID Authentication Rule

To provide control over this Late DID Recognition process, Sippy introduced a new type of DID Authentication Rule, called "Late".

  • When a DID is configured with the Late rule, the Late DID Recognition process is allowed, which reflects the behavior seen in older versions of Sippy.
  • If the Late rule is removed from the DID’s list of authentication rules, the system will no longer identify that DID through the Late DID Recognition procedure.

Important Considerations

  • None of the configuration options for the Authentication Rule apply to the Late type, e.g. Incoming DID, Incoming CLI, CLI Translation, Vendor, Connection, Buying Charging Group
  • Late DID Recognition is not supported for configuration with DID is assigned to an IVR application


Changes to DID charging

Selling DID Charging Group

The Selling DID Charging Group has lost the Per-Minute charge parameters such as Interval 1, Interval N, Price 1, Price N, etc and instead it has received a new attribute: an Incoming Tariff. 

For smooth transition for previously configured Selling DID charging Groups with Per-Minute charge parameters, new Tariff of type = Incoming with name that matches DID Charging Group is created with all charges inherited, and gets linked as Incoming Tariff to existing group.

Incoming Tariff

In order to charge an incoming DID call based on the CLI a new type of a Tariff has been introduced. It resembles the usual Tariff but does not contain many attributes such as Local Calling, Loss Protection, etc. 

New filter - Type - was added to Tariffs list page.

Incoming Tariff may contain many Incoming Rates. They are matched using a standard prefix match. There is a special prefix 'default' which matches when no other prefix has matched. Even if there is no 'default' Incoming Rate in the Incoming Tariff it is still considered to be present and have zero price.