Document name Unified – Inbound DDI Call Routing Author  Simon Smith Publish Date 01/11/2018 Version  1.0 Reference  

 

 

1. Version Information

 

 

Date Author Update Information  Version 1/11/2018

Simon Smith

  1.0                

 

 

2. Document Purpose & History

 

This document describes the decision flow for an inbound DID call.

 

 

Inbound DDI

There are a number of different ways to route an inbound DDI call on a UCP/eMG80/vUCP. Some of these methods, such as iCLID work with other call routing methods, or override other methods. This document outlines the decision flow for an inbound DDI call, with CLI presented. This knowledge base is applicable to ISDN and SIP calls.

 

DDI Routing Overview

 

The general order of routing is:

  1. System Call Routing (251)
  2. MSN Routing (202)
  3. Flexible DID Conversion (231)
    1. iCLID routing
    2. Ring mode routing
  4. DISA/DID Destinations (168)

 

System Call Routing

The first configuration consulted is 251 System Call Routing Table. Scenarios are consulted to for a match. To be eligible for a match as a system call route, the scenario will need the following areas defined:

  • The scenario describing what calls match and when.
  • A priority, if there is more than one scenario match, the highest priority will be used.
  • Scenario Group should be 0.
  • The scenario should be active

 

System Call Routing Scenarios

The example would route calls to 01234567890, as long as there was not another active scenario defined with a higher priority, which matches the incoming call.

 

MSN Routing

 

After the System Routing table at the beginning of the flow, the system will check for an entry in the MSN table.

 

 

In the above example MSN table, calls to 01002003001 will follow the entry in the Flexible DID Conversion (231) table, and calls to 01234567890 will ring the MSN keys.

 

Flexible DID Routing

 

The vast majority of calls will be routed through the Flexible DID Conversion (231) table. The vast majority of calls will be routed to the Day/Night/Timed Ring destination. There are some important settings to consider when completing a row in this table.

  • ICM group controls which of Day/Night/Timed destination is followed.
  • iCLID Table Usage, whether to consult the iCLID table before using the ring mode destination.

There is a 4th ring mode an attendant can set (On Demand/Scenario, DND+5). The attendant selects the scenario group that will route the calls.

 

Scenario Routing

The above set of scenarios, would be activated by the Attendant for the ICM using DND + 5 + 001 (Scenario Group 1 above). The group routes DDIs 01234567891-3. However any call from 07777777777 will route to VSF 1 and hang up, typically used to reject nuisance calls. In this example, the calls from this number will only be rejected on these DDIs, however the caller can call other parts of the business (other DDIs).

 

DISA/DID Destinations

 

Should the system not find a match using the decision flow above, it will follow the error action defined in DISA/DID Destinations (168). The default behaviour is to reject the call, and generate error tone.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Regards,

 

Simon Smith

Tech support

Pragma – Unified Technology

 

t: +44 1903927101 e: 480900 simon.smith@wearepragma.co.uk w: www.wearepragma.co.uk

Follow us @wearepragma | LinkedIn | Check out our YouTube channel

 

Please use these links to access technical resources, some require login:

TeamSupport Ticket System:Click Here| Knowledge Base:Click Here

Software Library: Click Here| Documents and Manuals:Click Here

Training Courses & Webinars: Click Here| Tech Support Policy:Click Here  

“