Trunk Route Separation

| | | | | |

Тел. : (495) 730-4022 |

Trunk Route Separation

Functional description
This function enables trunks generated in the system to be separated and operated independently from the tenant. The following service can be separated and applied.

When service application should be differently operated due to a different protocol.

When different initialization timing should be assigned to the local board because the connected remote station is different even though the protocol is same.

When the different Allow/Deny Trunk Outgoing Digit option should be selected.

When the different incoming should be assigned in time of abnormal trunk incoming occurrence.

When usage of trunk-related service should be differently operated.

When call limit in time of trunk outgoing should be differently operated.

Operating procedure
Service conditions

A route can be separated up to eight routes for each system.

Depending on service for each route, connection can be allowed or denied (in time of direct call, call forwarding by the extension subscriber or transmit by the attendant subscriber)

Data generation
Trunk route separation

[4.1 Trunk Information ⇒ Trunk Route]

[4.7 Trunk Route Assign]

Allow/Deny Outgoing Digit Table by Subscriber Class in Time of Trunk Outgoing for each Route

[3.3 Allow/Deny Outgoing Digit Table by Class]

Service Assign per Day/Night Mode for Abnormal IC trunk Call

[4.10 Trunk Route Base IC Day/Night Option]

Assign Call Time Limit by Route

[4.13 Trunk O/G Call Duration Restriction ⇒ Allow Time]

Interactions