Product Guide A5000 R5.4 Multi-company Services - CONTENTS -

Transcription

1 - CONTENTS MULTI-COMPANY SERVICES MULTI-COMPANY APPLICATION IN AN IP NETWORK ABBREVIATED NUMBERS PER "COMPANY-DEPARTMENT" ENTITY NUMBERS BARRED FOR SPECIFIC "COMPANY-DEPARTMENT" ENTITIES DEDICATED AND SHARED OPERATOR CONSOLE NIGHT FORWARDING AND GENERAL BELL PER COMPANY-DEPARTMENT" ENTITY ON-HOLD-MUSIC PER "COMPANY-DEPARTMENT" ENTITY DAY-NIGHT CALENDAR PER "COMPANY-DEPARTMENT" ENTITY RESERVED "OUTGOING" TRUNKS INDIVIDUALS IN A COMPANY SPECIFIC COMPANY WITH CALL BARRING INDIVIDUALS IN A COMPANY SIZING OF FUNCTIONS FOR EACH "COMPANY-DEPARTMENT" ENTITY... 6 BPS0121AENAA01 Page 1/6

2 23. MULTI-COMPANY SERVICES The Aastra 5000 software provides a multi-company application which allows for dedicated groups of subscribers either the sharing or the customisation of some resources of the Aastra 5000 solution (Aastra X Series, Aastra 500 gateways and Aastra 5000 Server). Based on this application, users can share the Aastra 5000 software and its integrated functions, including the voice mail, the charging ticket buffer (billing), the operator network infrastructure, the directory, the telephone numbering plan (in terms of length and features). Furthermore, it is also possible to share applications such as: UCP unified messaging services Or charging and traffic analysis application. Subscriber groups are organised as companies and sub-divided into individual departments. Each subscriber is assigned to a company-department entity. There are no restrictions regarding the subscriber s number of a company-department entity. The subscribers of a company-department entity can be distributed over several sites. Some functions or resources are programmed depending on the company-department entity assigned to the user. It is also possible to allow or forbid calls between companies. In this case, internal calls are only allowed between the subscribers of a specific company or between the subscribers of a company and those of the company defined as the manager of the Aastra 5000 solution (also referred to as "company 0"). The following operations between companies are therefore not allowed: direct call broadcast call call pick-up (interception) message deposit parking forwarding to another subscriber than the ones from its own company and/or Company 0 (reminder: for external call some rights have to be assigned to the users) directory Restrictions : Restrictions on the numbering plan and multi-company: The Aastra 5000 numbering plan is unique for all companies managed: its length is unique and facilities are the same for all companies. The same local number can be assigned to only one user (2 users of 2 different companies can t have the same number). Restrictions on the Aastra 5000 directory and multi-company: The Aastra 5000 directory is not multi-company: all users see the entire directory. call by name: research is accomplished on all companies, it can not be accomplished on a particular one. Contact management is not multi-company. Consultation of the http directory server on A5000 provides access to all records regardless of company BPS0121AENAA01 Page 2/6

3 Note: it is possible with the TWP Browser to take into account the user rights in the directory or external databases consultation, in order to work only with records that the user has read access rights. See the TWP chapter. However this access is not available to SIP terminals Multi-company application in an IP network Subscribers of companies can be equipped with IP or SIP terminals or Softphones. Thus, all companies share the same Aastra 5000 platform and the same resources, and all terminals support the same features (Call Distribution, abbreviated numbers, on-hold messages, voic , etc.). Be aware that an Aastra X Series does not dedicate VoIP resource per company. Vocoder resources of the Aastra X Series are shared by all companies. If companies also share the same LAN infrastructure, sub-networks and DHCP servers, the multicompany aspect has no specific impact on parameters for the definition of telephony over IP. To manage multi-company, the IP network must be a single private and homogeneous IP network. This limit is linked to the impossibility of deporting IP terminals through routing equipment doing NAT. If companies share the same telecommunication infrastructure, but not the same LAN, routing equipment must be provided in addition to their LAN equipment. This complementary routing equipment must be programmed in such a way that it filters the flows towards the different subnetworks of the individual companies. Each company can have its own DHCP server. Each company can have a Voice VLAN number in order to ensure service quality. BPS0121AENAA01 Page 3/6

4 23.2 Abbreviated numbers per "company-department" entity The Aastra 5000 software supports several lists of abbreviated numbers. The management of the assignment of these lists can be adjusted easily. Depending on each customer s requirements, each list can be assigned to a specific department, group of departments or company. This approach ensures that each company and/or department can use both customised and shared lists Numbers barred for specific "company-department" entities As with abbreviated numbers, several lists of barred or screened or forbidden numbers can be composed, and each list can be assigned to different departments Dedicated and shared operator console The Aastra 5000 software can assign operator consoles only to some specific companies in addition to the operator consoles attached to a particular building. When the attendant/operator assigned to a company is absent (i.e. the last attendant console has been deactivated), the general attendant consoles of the building take over the tasks of the company attendant. This characteristic allows the company to delegate the task from the operator console to the attendant console belonging to the building during off-peak hours or while its own operators are absent then to dedicate employees to the operator console s job only during peak hours. This approach provides a significant cost saving when compared to full time attendant service by dedicated operators from each company Night forwarding and general bell per company-department" entity You can define specific night forwarding extensions or general bells (common bells) either for each entity or group of entity. This feature provides answering machines at night time dedicated to small companies or to specific departments On-hold-music per "company-department" entity Each department or group of departments can have specific on-hold music to customise the telephone answering service. Furthermore, it is also possible to customise ACD s messages and on-hold music Day-night calendar per "company-department" entity The Aastra 5000 software supports several calendars for switching between day and night modes. Each calendar contains a maximum of four daily ranges and can be programmed differently for each day of the week. For each department, the day/night switchover calendar can be defined for sets and the day/night switchover calendar for operator groups. BPS0121AENAA01 Page 4/6

5 23.8 Reserved "outgoing" trunks It is also possible to define "outgoing" trunks for a specific company, a group of departments, or a dedicated department with heavier traffic than the rest of the installed system. If the reserved trunk becomes saturated, overflow can be authorised on the general trunk group. Trunk resources can be of ISDN or IP/SIP type Individuals in a company In a single company configuration you can define groups of people who cannot call each other (internal calls). When installing the system, or on request from the user, calls set up by the operator or by a subscriber in the main company (company 0) can be authorised or forbidden. This feature is often requested for a hospital or hotel configuration Specific company with call barring Individuals in a company This particular configuration is designed for exhibition halls and rented individual offices. Regarding some country s laws (depending on the country) internal calls between companies sharing the same network infrastructure are forbidden. Calls must be done through the public network (PSTN). All these telephone sets are declared in a company/department referred as a specific company of individuals (Company X/Department 90 to 94). The Aastra software prevents calls between the different extensions of this company, but authorises calls with the central managing company in the building (referred to as Company 0). This allows the central managing company to provide common office services such as voic or e- mail, secretariat, an administration PC, distribution of internal calls, external call fallback, greeting messages, etc.). These services can be accessed through the Aastra software. BPS0121AENAA01 Page 5/6

6 23.11 Sizing of functions for each "company-department" entity From Aastra 5000 R5.2, capacities in terms of the number of company/department pairs (1000 pairs instead of 256) and answering services (1000 answering services instead of 256) have been enhanced. Capacities in terms of number of available messages and music have also been increased in architectures with carrier connection in IP trunk. The number of available company/department pairs is summarised in the table below: Company/department operating mode Aastra X Series or Aastra 500 ipbx 32 companies 32 departments Aastra 5000 Server (integrated Media Server) 32 companies 32 departments Number of companies Number of services Number of departments per company Total number of company/department entities Number of answering services (ACD) 1000 In R5.1 or R5.2 interoperability : limited to 255 Number of answering services per company/service Number of calendars Number of different announcements in TDM operator connection Number of different announcements in IP carrier connection (SIP) 250 ; 170 customizable 250 ; 170 customizable 250 ;170 customizable, expandable to 1500 in multi-site configuration 250 ;170 customizable, expandable to 1500 in multisite configuration For large networks in which it is necessary to define more than 16 calendars, it is possible to deploy some calendars via the Aastra Communication Portal answering service solution (and to deactivate the Aastra 5000 calendar by forcing it to day mode, no matter the time of the day). For more information on sizing, please refer to Chapter 10 of the Product Guide. BPS0121AENAA01 Page 6/6