Assigning Trunk Groups/Sip Accounts; Allocating Routing Codes - Aastra OpenCom 510 User Manual

Multi-Company Variant Configuring the Multi-Company Variant
When setting up a new User group (in the User Manager menu), you will find
that the default company is predefined; another company can be assigned as long
as no other companies have been set up.

16.1.4 Assigning Trunk Groups/SIP Accounts

Connections of the same type and in the same direction are arranged in a trunk
group (e.g. S multi-terminal connections). To be able to correctly transfer
0
incoming calls to the members of the configured companies (the users) via the
lines of a certain trunk group of the OpenCom 510, each of the available trunk
groups must be assigned to one of the companies. This is necessary to be able to
transfer incoming external calls to the correct company exchange in cases where
the called internal subscriber cannot be reached ("Connection to Operator"), for
example. SIP accounts can also be assigned to a company.
The assignment of trunk groups to companies is done in the PBX Configuration:
Trunks: Bundle menu. The assignment of trunk groups to companies is done in
the PBX Configuration: SIP: SIP accounts.
For outgoing external calls which users set up via the lines of their company's
trunk group/SIP account, the assignment of the trunk group to the company is
irrelevant: the charges are assigned according to the "source" principle.
Charges are billed to the company to which the user belongs who set up the con-
nection. The OpenCom 510 recognises this on the basis of the assignment
between user groups and companies and on the basis of the routing code with
which a line of the trunk group/SIP account was seized. For more information,
please see the following section.

16.1.5 Allocating Routing Codes

Routes are used for automatic and selective seizure of trunk groups or connec-
tions for external calls. It is possible to seize a route by predialling a code.
In the PBX Configuration: Trunks: Route menu, you can define which company
can seize each route. An individual code for the seizure is allocated per route for
each company. The OpenCom 510 ensures that during configuration no seizure
code is allocated twice (for two different routes) for each company. If during confi-
guration of a route no code is allocated for one of the configured companies, the
route concerned cannot be seized by the members (user groups) of this company.
167