ANI/DID Routing

The ANI/DID Routing feature allows you to configure the DV2000/DV4 to route DID numbers to specific mailboxes, and/or take specific actions, based on the integration packet received from the PBX. It is integration dependent; that is, it can only route based on the data provided by the PBX.

Warning: DID translation is performed after the integration packet has been passed through the translation table. It is possible to use the ANI/DID routing table with extensions, but this is not recommended.

To edit the ANI/DID routing table, select Features | ANI/DID Routing from the main menu. This will open the ANI/DID Routing dialog, shown below.

Global Settings

Typically, an integration packet contains both a called party and a calling party. Either or both of these fields can be checked for DID translation. However, unexpected results may occur if both options are enabled.

Check called party

When an integration packet is received, the number of the called party will be checked against the Number field in the DID table (after passing through the translation table). By default, this field is enabled.

Check calling party

When an integration packet is received, the number of the calling party will be checked against the Number field in the DID table (after passing through the translation table). By default, this field is disabled.

Allow integration login

If this box is checked, the called party field is checked, and the integration says the call type is direct (mailbox login), then the call type will remain direct even if there is a DID translation for the given DID that is supposed to override the call type to force it to something else (such as RNA); in all other cases, this override would occur as expected.

If this option is not checked, then even if the integration says it is a direct call it will still be overridden by the entry in the DID table. By default, this option is enabled, to prevent an entry in the table from blocking a DID mailbox login.

DID Server

The DID server is an optional add-on you can purchase for hospitality systems. It allows a DID number to be assigned to a guest room at check-in and to be unassigned when the guest checks out. When automatic assignment is in use, the system will always select the least-recently-used DID number when making an assignment at check-in.

Note: The DID Server is an optional add-on feature. If you have not purchased this feature, the following two settings will be disabled and you will not be able to configure them. You will, however, still be able to make fixed DID assignments as outlined in the DID Table section below.

How to assign numbers for guest rooms

This setting determines how DID numbers are assigned to guest rooms at check-in, and can be used to block InnDesk clients from assigning DID numbers. There are four possible settings:

Default destination

If a DID number is found in the table, but has not been assigned a mailbox, then the call will be routed to the default destination mailbox. The default setting is zero (0), which means all unassigned DID numbers will be routed to the operator.

DID Table

The DID table is displayed in the lower half of the dialog, as shown in the figure above. Each row in the table represents the routing configuration for a single DID number, and contains the following eight settings:

Column

Description

Enabled

If checked, the DID is active; otherwise, it is disabled.

This allows you to take a DID number out of service without removing it from the table; when you are ready to put it back in service, simply check this box and click Apply to save the change.

Assignment

Limits how the DID number can be assigned.

Option	Description
Any	DID number can be manually assigned or auto-assigned.
Fixed	DID number can only be manually assigned.

Number

The DID number expected from the PBX.

Must exactly match what is received from your carrier, unless you are using the translation table (integration data is passed through the translation table before the DID table is consulted).

This number may be anywhere from 1 to 19 digits in length.

Mailbox

The mailbox assigned to the DID number.

If the assignment type is Fixed, enter the mailbox number you want assigned to this DID; otherwise, this field will reflect the mailbox number currently assigned by the DID Server.

Action to take

How to process a call from the DID number. There are four options:

Option	Description
Transfer	Transfers the call to the mailbox's extension number. If the mailbox field is blank and the DID server is active, then it will transfer to the Default Destination instead.
Execute	Executes the assigned mailbox. Useful for directing a DID call into a QA or system mailbox, or for directing a subscriber's cell phone into his or her mailbox to retrieve messages.
Record	Immediately records a message in the assigned mailbox.
Disconnect	Immediately disconnects the call.

Make call type

Overrides the call type indicated by the integration packet received from the PBX; it is only used if the Action to take field is set to Execute.

By changing the call type, you change how the call is routed by the system.

Valid settings include: N/A, Direct, RNA, Busy, and Forwarded.

The default setting is N/A. This means the call type is not changed.

Last assigned

Read-only. Indicates the date and time the DID number was last assigned to a mailbox via the DID server.

Database ID

Read-only. Used internally by the system. A negative value means the entry only exists in memory and has not yet been written to the database.

Testing and Diagnostics

The Integration and Setup log (viewed using the Trace Display application) will show exactly what actions are being taken by the integration and the ANI/DID routing system. The following example line shows a typical log statement:

This line indicates that the system received DID number 8899790; it's assigned mailbox is 530; and the assigned action was to transfer. So the caller would have been transferred to the extension for mailbox 530.

ANI Routing CallerID from [8899790] to [530] using action Execute call type set to direct.

In this second example, the received DID number 8899790 is still mapped to mailbox 530, but in this case the assigned action is to execute the mailbox after converting the call type to direct. This will place the caller in the subscriber menu for mailbox 530 without prompting for a password (unless direct login has been blocked by the global Allow mailbox login setting detailed above). This is best used only when the given DID number is that of the owner of the mailbox to which it has been assigned.