Assigning A Bundle/Sip Trunk; Allocating Routing Codes - Aastra OpenCom 100 Series Mounting And Commissioning User Manual

Multi-Company Variant

Assigning a Bundle/SIP Trunk

Connections of the same type and in the same direction are arranged in a bundle (e.g.
S multi-terminal connections). To be able to correctly transfer incoming calls to the
0
members of the configured companies (the users) via the lines of a certain bundle of
the OpenCom 100, each of the available bundles must be assigned to one of the com-
panies. 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 trunks can also be assigned to a
company.
The assignment of bundles to companies is done in the Telephony: Trunks: Trunk
group menu. The assignment of SIP accounts to companies is done in the Telephony:
Trunks: SIP trunks menu.
Note
A bundle configured as a System access can however also be used jointly by multi-
ple companies. Available direct dialling-in numbers of the system access can be as-
signed to the internal company call numbers via the Telephony: Call Distribution:
Incoming DDI menu.
For outgoing external calls which users set up via the lines of their company's bundle/
SIP trunk, the assignment of the bundle 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 100 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 bundle/SIP trunk was seized. For more information, please see the following
section.

Allocating Routing Codes

Routes are used for automatic and selective seizure of bundles or connections for
external calls. It is possible to seize a route by predialling a code.
In the Telephony: 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 100 ensures that during configuration no seizure code is allocated
twice (for two different routes) for each company. If during configuration of a route no
213