DID Pool

DID Pool is a feature that allows you to configure DID (Direct Inward Dialing) numbers.  DID numbers can be forwarded to the system via DID gateway or specialized DID provider.

Any change you make related to Rates, Routes, Destination Sets, Tariffs, DID numbers, DID Charging Groups and Routing Groups may not be applied immediately. You need to wait at least 1 minute so that the system can update its internal "cache".  For example; if you update a heavy bulk of multiple destination sets at once, you may have to wait more than 1 minute for the system to update.  Read more...

Each DID number has the following parameters:

  • DID: this is the "canonic" E.164 number that will be used by the system for billing and accounting purposes. Calls from Accounts to DID numbers should be made through a CLD that matches the number in the DID field. The incoming_DID/CLD is only for authentication of incoming traffic
  • Incoming DID/CLD: this is the number as it comes from the DID gateway or DID provider.  The number might be the same as the DID, but sometimes it could be different due to the presence of local or technical prefixes
  • CLI Translation Rule: the regular expression used to translate incoming CLI numbers into canonic E.164 form. Translation Rules are important particularly for the Callback application, where the system needs to call the CLI back. The Translation Rule can be left blank in cases where the DID comes in form of E.164, or CLI already or when E.164 CLI is not important/relevant
  • Assigned to:  setting that reflects the IVR Application that will handle calls coming through the DID, or the specific Account that should ring when a call comes in through the DID. The DID can be unassigned, in which case the system will not perform any specific processing; the calls will be subject to the regular incoming call AAA procedure
  • Charging group: Charging group is used to charge DIDs with some additional fee.  You can create multiple DID groups, for example, local DIDs which can cost "x" fee and toll-free DIDs which can cost a higher price. When used, charging groups will affect call costs by applying surcharges. Charging groups are also useful for IVR applications. If used with IVR applications such as Calling Card or Conferencing, they will result in a higher end-user charge.   Available from 2.1
  • Forward DID #: Without this feature, an incoming call to a UA would be sent with a CLD equal to the Account ID. This feature allows the Account UA assigned with the DID to see the DID number used for the call.  Test your UA before relying on this feature, as it might not be supported by the UA.  If 'Forward DID #' is enabled, the value from the'DID' field is forwarded.  Available from version 2.1

Case - DID number assigned to account:
How to activate the Forward DID# option:

Two ways of DID call routing if Account is tied to a DID number:

1) If On-Net Routing is set to "Default" in the Account's Routing Group, Sippy forwards incoming DID calls to the registered Account;

2) If On-Net Routing is set to "Disabled" in the Account's Routing Group, Sippy forwards incoming DID calls to the list of Vendors using the Routing Group of the Account.


Sippy Softswitch 1.9