16. MULTI-SITE SERVICES WITH MOVACS SIGNALLING...

- CONTENTS - 16. MULTI-SITE SERVICES WITH MOVACS SIGNALLING... 2 16.1 GLOBAL OFFER POSITIONING AND NETWORKING... 4 16.2 AASTRA - MOVACS MULTI-SITE SOLUTION... 5 16.2.1 Transparency of services... 5 16.2.2 Centralisation of network access... 5 16.2.3 Centralisation of resources... 6 16.2.4 Administration... 7 16.3 MOVACS MULTI-SITE SERVICES - AVAILABLE FROM R5.2... 8 16.3.1 Remote digital subscriber (Virtual TDM)... 8 16.3.2 Associated multi-site terminals... 9 16.3.3 Hunting groups and multi-site... 11 16.3.4 Free seating and multi-site... 11 16.3.5 Virtual TDM and architecture... 11 16.4 R5.2 - R5.3 - R5.4 INTERWORKING... 12 16.5 QSIG MCDN... 14 16.5.1 Telephone features... 14 16.5.2 Centralisation of resources... 14 16.5.3 Management... 15 16.5.4 QSIG MCDN networking... 15 16.6 SIP INTER-SITE LINKS... 16 BPS0121AENAA01 Page 1/17

16. MULTI-SITE SERVICES WITH MOVACS SIGNALLING This chapter describes the service s level of different network connexion. For a detailed description of this specific networking please refer to chapter 17. From a terminological point of view, a distinction should be made between simple networking and a multi-site configuration. A multi-site configuration provides users with the dialling options and features of a single virtual ipbx, whereas simple networking by classical tie lines, (which has been used for years by private telephony systems) does not provide these advantages. Aastra solutions provide both possibilities due to their latest-generation open architecture. For end users, a multi-site solution provides many benefits, such as: Cost optimisation : Intersite communications are routed over private links, Use of Least Cost Routing mechanisms to make a local call instead of a long-distance call Optimization of the carriers links (centralized accesses, traffic distribution) Centralisation of servers such as voicemail systems, phone answering services such as attendant consoles Joint billing and traffic analysis. The same level of service for all sites : Homogeneous numbering plan Subscribers moving without changing their telephone number. Telephony collaboration services: filtering, supervision, written messages, call distribution to hunt groups, call by name ) Distributed call center agents. Ergonomy and common traditional facilities: call transfer, call forwarding, call back Automatic location of the subscriber (login-logout of the subscriber, DECT roaming) and management of emergency numbers Security services: dual homing, SRTP encryption of communications. A homogeneous service: one single entry point for a customer calling the company, Simplified company management: on each site, users have access to the same telephony features, which increases user flexibility. DECT solution (roaming / handover) or IP/SIP subscribers are part of the multi-site solution. Furthermore, users can keep their personal number when moving from one site to another. This feature is interesting for campuses architecture where trunk and network accesses are centralised. The Aastra multi-site network includes the Aastra 5000 range R5.4, R5.3 and R5.2: Aastra XS, Aastra XL, Aastra XD and Aastra 500 (from R5.3 SP1) gateways, the Aastra 5000 Communication Server Telephony over IP solution. Interworking provides only the features from the lowest release on the whole multi-site network. On a site with release N interoperating with a site with release N-1, the features of release N are not available on the sites with release N-1. Some features of release N can be available on sites with release N. For a heterogeneous release R5.4 network with release R5.2, only release R5.2 functions are available on all sites. BPS0121AENAA01 Page 2/17

The services available in a multi-site network do not depend on the type of ipbx used in the different network nodes; this is due to the Aastra 5000 specific software, which is common to all ipbx. A company using this type of solution is thus equipped with the best in class tool that helps to boost its organisation capacities and optimize costs. For more information, please read paragraph «R5.2, R5.3, and R5.4 interworking». BPS0121AENAA01 Page 3/17

16.1 Global Offer Positioning and Networking Aastra has enhanced its key point s networking offer and structured it to meet the requirements of its users. The aim of this solution is to offer a soft migration to the enhanced services of the Aastra multisite solution which takes into account the existing situation: Heterogeneous ipbx systems: Protection of investment, Site configuration. Sometimes a leased line may not be profitable. In this context, Aastra has developed an interconnection solution which is based on IP signalling and voice flow over ISDN. The voice flow can be compressed to allow the passage of several voice calls simultaneously on one and the same ISDN B channel. Aastra defined its offer according to the type of ipbx/call Server to be interconnected, as shown in the diagram below: One of the following connections will be chosen, depending on the capacity of each platform and the type of required upgrade: An ISDN connection offering services like calling party number display and forwarding, A connection based on: Circuit lines - tie lines providing internal dialling and transfer services This offer is described in section 18 Heterogeneous Interconnection: SIP, QSIG, A QSIG (Q interface SIGnalling) connection. This offer is described in section 18 Heterogeneous Interconnection: SIP, QSIG, A QSIG MCDN - MOVACS ENTRY connection, which is the entry ticket to our multi-site service MOVACS (Multi switch Original Virtual Addressing Communication System) A SIP connection. This offer is described in chapter 18 Heterogeneous Interconnection: SIP, QSIG, A multi-site service offering a single, virtual ipbx spanning several ipbx/call Server thanks to our MOVACS protocol. This offer is currently available on standard circuit interfaces, but from software release R1.2 it is available on the IP data and routing infrastructure (Intranet) too. BPS0121AENAA01 Page 4/17

16.2 Aastra - MOVACS Multi-site Solution 16.2.1 Transparency of services Subscribers are granted with two types of telephony features. Some are not related to the multi-site structure of the network. Others are related to the multi-site functionality. For example, this is case for the call forwarding feature: It may be interesting to be able to forward one user s call to another site. Aastra provides the possibility to use these features in a multi-site with a total transparency of services. A very small number of these features can only be operated in single site mode. Examples of mono-site features: Network intercom (monitoring in intercom mode of an external trunk line), Broadcast call, Associated and tandem sets (a subscription associated dynamically or statically - to several terminals), Broadcast of synchronous messages and announcements, Hunt groups: only the super-group overrides this restriction, just like virtual TDM function (for digital terminals only). Note: ACP-Contact Centre does not rely on this feature. Parking function: Set A puts a caller on hold; resuming this call on a Set B connected to another ipbx is not possible; the parked call must be resumed by a set which is connected to the same ipbx as Set A. The list of mono-site and multi-site features is described in chapter 10 item 7 «Features» - columns «A5000 Server» and «Aastra X Series». The list of multi-site facilities is described in chapter 10 item 7 «Features» - column «Multi-site MOVACS». 16.2.2 Centralisation of network access One of the benefits of deploying a multi-site is the centralisation of operator accesses (PSTN carriers). It allows the optimization of the connection s costs and the use of these accesses as well as the return on investments (operator/carrier subscription, specific PSTN card). In addition, sometimes accessing to PSTN networks from other sites is advised, either for security or for cost-saving reasons (Least Cost Routing mechanisms). BPS0121AENAA01 Page 5/17

16.2.3 Centralisation of resources Centralisation of servers In order to avoid too many hardware resources and to ease the multi-site network(s management, it is possible to centralise the internal (Aastra Call Server) or external servers (Application s servers) of IP multi-site Internal servers: Telephone number translation server (STT): Centralisation of rerouting and Least Cost routing (LCR) services, Server for call distribution to attendants (SRT), centralisation of available attendant consoles, LDAP server: in a multi-site network, the LDAP directory can be copied in the network to increase the security of the directory (if a directory fails, the information is available on another directory server of the network) and the number of available accesses, and therefore to reduce the directory access time. Call Admission Control (CAC) server: restriction of VoIP & ToIP calls between users, Call ticket server and call ticket buffer (Billing and call statistics). External servers: It is also possible to centralise the external servers of associated applications such as: AS7900 Alarm server. transmission of alarm messages on a DECT terminal, Server for operation via a hotel front office, Billing and traffic observation (centralisation of billing tickets), Voice mail system such as UCP, Contact Centre: ACP, CTI gateway / unified communications such as TWP or ACP, Interactive voice servers, Conference bridge: ACP-IP conference bridge, Paging, Network administration: AM7450 Monitoring of network (with alarm) ipbx s operation logbook Homogeneous management of subscribers Numbering plan management (internal, DID, feature...) Management of LDAP directory Management of common abbreviated numbers Multi-site relocation. Billing Traffic analysis Centralisation of attendants Attendants can be centralised and organised by services. An attendant service is a group of attendants processing the same traffic. For security reasons, or in order to process calls on the closest public network access point, it can be interesting to distribute the attendant s services on different sites. It is possible, in particular in a multi-site configuration, to set up ipbx subunits each of which has its own attendant functions and its own inbound trunks. Homogeneous dialling A multi-site configuration allows the user to overcome geographical dispersion and to find the same services again after relocation; as well as a homogeneous single numbering plan at network level. Aastra 5000 solution accepts a local numbering plan from 2 to 6 digits. BPS0121AENAA01 Page 6/17

16.2.4 Administration The administrator of a multi-site network can query and modify the whole multi-site network from any point of the network. Management can be centralised, with the administrator connecting to each site one after the other. Furthermore, the alarm centralisation mechanism allows the user to visualise all alarms from different network sites on the same console. Furthermore, Aastra includes an administration function which consists of 2 solutions complementing each other: The Aastra Management Portal is a single-site administration solution which is integrated into the Aastra X Series and Aastra 5000 Server. It has a Web interface, which avoids having to install and maintain a client s software. The Aastra Management 7450 allows the user to manage a group of Aastra platforms in a multi-site, stand-alone or park management s configuration with the same or a different software version. This application is Web-based, too. Depending on the model and their options, these solutions include centralised features complementing each other, in accordance with the OSI model: Fault management, Configuration management, Directory management, User s rights management, Performance management. But these servers also provide features such as consultation of directories on Intranet or time sheets on Intranet. The servers can be located freely on any site of the network, and communicate through a data connection. Access to the server can be decentralised (for more details refer to the chapters on the administration of these solutions). For more information about AM 7450, refer to the chapter Aastra Management 7450 in the Product Guide. For more information about AMP, refer to the chapter Aastra Management Portal in the Product Guide. BPS0121AENAA01 Page 7/17

16.3 MOVACS multi-site services - available from R5.2 16.3.1 Remote digital subscriber (Virtual TDM) Centralising subscriptions makes it possible in nominal mode to manage subscribers on the Aastra 5000 call server and the physical device (digital terminal) on an Aastra X Series gateway. Therefore, in addition to IP, SIP, IP DECT, TDM DECT terminals, users of digital terminals can be declared on Aastra 5000 Server. This centralisation facilitates subscriber management via AMP and brings in multi-site features, also for digital TDM terminals. In addition these digital terminals benefits Aastra 5000 Server redundancy solutions: duplex A5000 solution or security solutions via VMware virtualization. Moreover, a notion of Dual homing now exists for these digital terminals. Their backup site is the site to which they are physically connected. This means that: Main site = Call server (Virtual TDM license for the subscription). Back-up site = Aastra X Series gateway with the physical connexion for terminals 5300, M7xx, 6750. A license is needed: Virtual TDM It concerns the following terminals: Aastra 5300 / 6750 / M7xx BPS0121AENAA01 Page 8/17

Note: From release R5.2, the Virtual TDM function is available in multi-centre MOVACS. Subscriptions on the call server side using remote TDM terminals can be set to Dual homing with the gateway (backup site) on which the physical terminals are connected. In this case, the signalling link between the call server and gateway is supervised (this supervision is necessary to solve possible defence problems). This function is not available for analogue terminals, ISDN terminals and the attendant console. Licensing: Virtual TDM licenses must be defined on the Call Server. The license also includes a Dual homing license. The backup site for Dual homing is declared on the Call Server. Neither the Dual homing license, nor the virtual TDM license is required on the backup site. The notion of local TDM license does not exist. Only the virtual TDM license is defined. The associated physical devices of one specific gateway on some local subscriptions of this gateway are not in any way subject to the virtual TDM license defined on this gateway. 16.3.2 Associated multi-site terminals Up till release < R5.2, in a multi-site configuration, the assignment of a physical terminal (TDM) was only authorised on a subscription declared on the same site as the terminal. The software has been modified to take into account the new MMIs as well as the processing of the authorisation to remotely assign a physical terminal to a subscription. The MMI menus have been enhanced to take into account: The site number when a physical equipment is assigned to a subscription The display of subscription number on the site on which the physical terminal is located, in the display menus. The display of remote site number in the subscriptions display menus. The association of an IP DECT terminal (more generally an IP terminal) and a digital terminal was not possible in R5.1 if the digital terminal was not connected to the site to which the IP DECT terminal was connected. This is now possible from release R5.2, thanks to the virtual TDM function. This assignment can be performed either by the administrator (via the AMP/AM7450 management tools) or by the user (login). BPS0121AENAA01 Page 9/17

Here are some examples: In association mode, with Dual homing, backup can only take place on a single gateway for all the terminals from each association. Only the terminals capable of connect to the backup gateway will access this service: Main site = Call Server Backup site = one and only one gateway BPS0121AENAA01 Page 10/17

New rules to be respected Note that this new function implies some new rules that must be respected, such as: The new virtual TDM license must be provisioned on the Call Server. The association between an equipment and the subscription may be made in different ways, either through AMP, through AM7450, or manually. In all cases, this assignment between the subscription and the equipment may only be done if MOVACS signalling are set up between the different ipbx concerned. No creation/modification/deletion will be active until the signalling is set up. 16.3.3 Hunting groups and multi-site Functionally, it is now possible to create a hunting group including some digital TDM terminals physically distributed over several different gateways. The head of the hunt group and subscribers must be defined on the same site. Moreover, the subscribers physical equipments may be on remote sites. 16.3.4 Free seating and multi-site It is possible to move about and find your services by logging on to a digital TDM terminal, even if this equipment is connected to another site from the multi-site. In fact, if the user logs on to the terminal, the association between the terminal and the remote subscription is possible, provided a virtual TDM license is available on the subscription site. Reminder: free seating is possible on wired terminals 5300, 5300ip, 6750, 6700i (except 6751i), M7xx, i7xx; it is also possible to change from one terminal type to the other. 16.3.5 Virtual TDM and architecture The bandwidth required for signalling between Call Server and gateway to ensure the Virtual TDM function is as follows: Aastra 5300 TDM: bandwidth = 11 kbits/s Aastra 6750 TDM: bandwidth = 10 kbits/s M7xx TDM: bandwidth = 8 kbits/s Case of system defence: Cases of defence are automatically managed by the call server and gateway pair, in order to solve some cases of inconsistencies which may arise between the call server data and gateway data. These inconsistencies may occur in the following cases: Data backup / restore (CS or GW). This is the most probable case. Login / logout operation by MMI terminal or AMP. This is supposed to be an unlikely case. However, it is managed by the system. These defence cases also apply when Dual homing is active (that is: when the call server and backup gateway are active). BPS0121AENAA01 Page 11/17

16.4 R5.2 - R5.3 - R5.4 interworking Description and specific cases: Multi-site networking (MOVACS) is possible with the different systems in releases R5.4, R5.3 and R5.2 (A5000 Server, Aastra X Series (XS/XL/XD), Aastra 500). From release R5.4, the system behaves like the previous release, regardless of whether it is used on a homogeneous network (Aastra 5000) or in a heterogeneous architecture (MOVACS, tie line, QSIG, SIP, etc.). The basic rule on an Aastra 5000 multisite network is to apply descending compatibility. This means that when there are two releases N and N-1, and in case of interoperation between these 2 systems, the functions of N -1 are available on the 2 sites. For a heterogeneous network R5.4 with R5.2, only release R5.2 functions are available on all sites. However, a few exceptions do exist: Dual homing: the node on which the subscriber is declared and the backup node must have the same release. The SIP terminal (6739i) is only supported as from release R5.2. The new terminals 5361 and 5361i are only supported as from release R5.3. The Aastra 5000 LDAP directory must be located on a R5.2, R5.3 or R5.4 site or on AM 7450 V2.3 min. The new numbering plan (LDAP) available from R5.2 is only available in a multi-site R5.2-R5.4. When the Aastra 5000 LDAP directory is stored on the AM 7450 V2.3, there may be replications on R5.3, on R5.2 (if R5.4 features are not used). The new features are: from R5.2: the numbering plan, PNIA; from R5.3: pictures service. from R5.4 : UTF-8 characters for names and first names. The 6739i with photos can be used from R5.2 on sites with the R5.3 directory. When the LDAP directory of Aastra 5000 is on AM 7450 R2.4, replication is only available on R5.4 sites. Aastra 5000 LDAP directory: LDAP directory synchronisation with other directories is available if this LDAP directory is installed on the AM 7450 server R2.4. Site management in R5.4 can only be done with an AM 7450 R2.4 AM 7450 forwarding management: to supervise the active/inactive forwarding status in a manager/assistant filtering configuration, the system must be in R5.2 min. TMA: the TMA module of AM 7450 can manage (create, modify, delete) IP terminals on a multi-site network, no matter the ipbx software release Labels: The length of the field "labels" in the AMP must be compatible with the oldest PBX version. This concerns the field "pickup group" and the text "Company / Department. LDAP-directory-based numbering plan is not available on a heterogeneous network. Pickup Group: in heterogeneous multi-site, only the first 252 pickup groups can have a global reach or a reach that includes the sites <R5.3. Free seating particular case with an Aastra terminal 5300ip: the terminal is connected with the profile of an R5.2 user. If another user (whose profile is on another ipbx release R5.4) activates the free seating function on this terminal, the IP terminal restarts by loading the new profile. Why does this terminal reboot? There is a terminal firmware inconsistency between release R5.2 and release R5.4. IP terminal 5300ip loads the firmware corresponding to the ipbx release of the user concerned. Note: if the terminal is configured to make encryptions in TLS mode, a user with an R5.2 subscription is not authorised to log on to this terminal. BPS0121AENAA01 Page 12/17

Reminder: the free seating function for Aastra 6700i terminals exists from R5.2 (log on and log out manually). This means that manual login with Aastra 6700i will be rejected from a subscription declared on a site below R5.2. The Squat function: it is not available in a heterogeneous multi-site environment (except when the subscription and the terminal used are on R5.4 ipbxs). Support of the codec G722: only available between sites in version >= R5.3 and if the CAC server is declared on a >=R5.3 system. "Power saving" function for virtual terminals (Virtual TDM). To benefit from this functional improvement, the user subscription and the gateway to which he is connected must be both in version >=R5.3. SIP trunk: R543 new features are available if the version of the site is R5.4. Note: a SIP trunk connection between two sites is possible if one is in R5.4 and the other in R5.3 or R5.2. The level of service shall be that the site where the software version is the oldest. Improvements in the multi-site emergency services (free seating and IP DECT mobility in centralised carrier architecture) are only available from version R5.3. BPS0121AENAA01 Page 13/17

16.5 QSIG MCDN The QSIG MCDN networking service is the equivalent of an enhanced QSIG service (which is able to manage certain advanced functions such as forwarding ). This service offer is intended for Aastra platforms. It is especially attractive for remote sites such as agency types interacting with a central site. It provides the possibility to interface with other ipbx than Aastra 5000. 16.5.1 Telephone features This service provides users with: Basic call and number identification, Name transport: caller, notified terminal (the set is ringing with call on hold), busy terminal and answering terminal, Forwarding (immediate, on busy and on no answer), Call transfer (with connection), Automatic callback on set busy or on no answer 16.5.2 Centralisation of resources Furthermore, this solution allows the sharing of resources such as: Centralised DID: the central site routes inbound calls from different operator networks. Outbound operator trunks: The central site can play the role of front end Least Cost Routing. It chooses the lowest cost operator for outbound calls anywhere in the network. Centralization of external voice mail that are voice messaging or unified (UCP): Direct call from the messaging system, Possibility to leave messages in a voice mailbox after the call has been forwarded to the called party s voice mailbox, Notification about messages left in a voice mailbox and messages read by a voice mailbox (on the display of a digital terminal by a message lamp, on a digital or analogue terminal by a voice message when the handset is lifted). Assistance between attendant services: attendant services located on several sites can use an assistance mechanism. Each new call arriving at an attendant service will be processed directly by the site assistance service if the hold time exceeds a set timeout, or according to a programmable schedule. Aastra recommends the deployment of attendant services on two ipbxs rather than carrying out an elaborate engineering study of call flow. BPS0121AENAA01 Page 14/17

16.5.3 Management The AM 7450 administration tool allows the management of a large number of services in the network, such as: Subscriber management LDAP directory management and its optional synchronisation to a company s directory. Remote configuration (either graphical MMI Interface) Error management (managing alarms, including notification by e-mail) Log and event management Management of voice mailbox and of integrated voice services Retrieval of call tickets for external billing and traffic analysis applications Network inventory (hardware and software) Real-time programming and supervision of individual tasks or groups of tasks Access rights management for different administrators For more information about AM 7450, refer to the chapter Aastra Management 7450 in the Product Guide. 16.5.4 QSIG MCDN networking QSIG MCDN networking provides the most important services of the Aastra software, and at the same time optimises communication costs. Networking (voice and signals) is performed on ISDN T0 or T2 fixed links. BPS0121AENAA01 Page 15/17

16.6 SIP inter-site links The Aastra SIP offer is enhanced and proposes: The SIP option integrated into all Aastra, for a smooth migration to open Telephony over IP The possibility to interconnect MOVACS multi-sites in order to provide large IP networks with 100 to 1000 sites and up to 150,000 users (IP or TDM); then SIP networking can be implemented between the multi-site MOVACS. The possibility of dialogue with various SIP servers (refer to chapter Heterogeneous interconnection: SIP, QSIG of the Product Guide ): dialogue with a third-party ipbx via a direct RTP/UDP/IP flow dialogue with multimedia servers The possibility to choose an SIP operator (refer to chapter Heterogeneous interconnection: SIP, QSIG of the Product Guide): thanks to the operator SIP connection Least Cost Routing (ISDN, SIP) Standard services according to SIP RFC. The SIP proxy is integrated into Aastra: On Aastra XS, XL, XD from R5.1 and on Aastra 500 from R5.3 SP1, the SIP proxy is integrated into the motherboard. On Aastra 5000 Server from R5.1, it is the integrated SIP proxy which manages SIP accesses. SIP trunk for interconnection of Aastra or of multi-site Aastra: A SIP gateway is required on each multi-site configuration. BPS0121AENAA01 Page 16/17

Services available in SIP interconnection of multi-site Aastra: Basic IP call (direct call between terminals) Vocal, video, fax call Codec negotiation among those available on A5000, Caller name and number display Display s Restriction of calling party number DTMF (info message or RFC 2833) Call transfer Forwarding Least Cost Routing Outbound call setup Incoming call with: Transport of caller number (CLIP) or of installation Transport of called number CPID (on the model with screen) Call on hold Call transfer Double call Three-parties conference On Hold, trace DTMF Call-back on free phone Call-back on busy phone Monitoring of long calls Call forwarding on busy, immediately or on no answer phone Cascade forwarding Voice mail forwarding Voice mail forwarding to the mailbox of first number called Transmission of caller and called number to voice mailbox Transmission of status of called set to voice mailbox For more functional details, please refer to chapter «Carriers networks services» of the Product Guide. The AM7450 can perform the administration of Aastra sites and of Aastra multi-sites. For this, IP access must be available on the Aastra sites and Aastra multi-sites. Maximum SIP capacities: Platform SIP subscribers (max) simultaneous SIP calls (max) Aastra XS, XL, XD 500 200 Aastra 5000 Server 15,000 1,900 Aastra 500 R5.3 SP1 (per rack) 500 200 For more details on SIP trunk, refer to chapter «Carriers networks services» of the Product Guide. BPS0121AENAA01 Page 17/17