© Aastra AMC and AMC+ 2.0 Functions Overview Quick Overview over AMC and AMC+ Functions

© Aastra Aastra Mobile Client (AMC) 2.0 Solution Overview Aastra Mobile Client (AMC) Mobile Extension Integration (MEX) Direct integration of mobile phones with call manager as extensions No AMC Controller needed Features handled directly by call manager Mobile number configured as an extension in the system Mobile LCR Travel SIM Mobile OS supported Android, BlackBerry, Symbian Aastra Mobile Client plus (AMC+) Mobile Integration (SIP user) Connects to call manager via AMC Controller Seen as SIP extension by the system Features handled by AMCC towards call manager Mobile LCR Travel SIM Dual mode (Mobile/Wi-Fi) Directory search Secure VoIP (TLS / SRTP) for Wi-Fi/3.5G calls AMC Controller options (AMCC) Software only options VM Ware AMCC-30 (for 30 AMC+ users) – for SME AMCC-125 (for 125 AMC+ users) Mobile OS supported iPhone, Android, BlackBerry, Symbian ASE/MXO/PLM/0221/0/1 EN

© Aastra AMC Single Mode – Functions AMC Single mode The AMC mobile client is combined with a patented feature in the PBX called Mobile Extension, which enables a mobile to be handled as a normal extension in the system. Operator supported routing In certain markets, a service is available from the mobile operator to ”connect” groups of mobile numbers to a specific customer PBX. In this case, all calls to and from the mobile are automatically routed to the PBX system except for emergency numbers. This significantly reduces the call setup time. Calling card or client based routing In this case, the client routes the call via a pre-defined access number into the PBX system. Also called “client-based routing “(unlike the operator supported routing). Call setup time with client based routing can be variable depending on the number of digits (1). Exemption numberWhen using calling card all calls are routed through the PBX. With an Exemption Number one number or several telephone numbers can be defined to be routed as mobile calls (not through the PBX system). In call servicesAvailable services during a call, such as inquiry, toggle, conference, call back and call forward. The number of services offered depend on what the PBX system allows for mobile connections. Call profilesControl how the PBX handles the call flow for a specific user via activity profiles enabled from AMC Absence informationControl own absence or activity status via AMC Https call-back/Mobile LCR To control the call route of a mobile call for saving cost e.g. International telephone calls. The license is called ”mobile LCR” and support Https based callback in MX-ONE and / Aastra 700 platform. In this case, the data channel is used to transmit the call setup information to the PBX. Travel SIMWith Travel SIM you can use a local SIM card e.g. when abroad. AMC then tells the PBX exchange that the extension number shall be directed to the mobile local number. (1) When operator supported dialing is not available, DTMF is used as the method to transmit the dialed digits during call setup at a rate of 2 digits per second. This can take up to 15 seconds, depending on the number of dialed digits. ASE/MXO/PLM/0221/0/1 EN

© Aastra AMC Single Mode – Smartphones (1): Android does not yet offer an API to enable support of DTMF-tones from an application during a call, therefore, mid-call services are disabled when using the Android OS version of the client. (2): The iPhone OS is only supported with the AMC+ version of the client AMC Single modeSymbian (S60 3rd, 5th ed & Symbian ^3 & Anna) BlackBerry (RIM OS v4.x, 5, 6) Android (v ) iPhone (2) Calling card Exemption number In-call (mid-call) services Call profiles Absence information Https call-back Travel SIM (1) ASE/MXO/PLM/0221/0/1 EN

© Aastra AMC+/Dual Mode – Functions AMC+ Basic functionAll functions included in AMC single mode and functions listed below. The Mobile Extension feature in the PBX is not required in this scenario. Mobile connect SIP integration The mobile phone extension is managed as a SIP extension in the PBX system. There is no difference in functionality compared to a normal mobile extension user. AMC+ requires an ”AMC Controller” that is handling the data -signaling through the mobile network. AMC Controllers are available in 2 sizes (max 30 / 125 AMC+ users) as well as software for commissioning on the server for larger customers. Call setup time can be variable depending on the type of mobile data service available and the OS used (1). Dual modeAMC+ can work as SIP client for VoWLAN (voice-over-WLAN) alt. over the mobile network (3.5G) with automatic hand-over. The system decide if VoIP is possible depending on parameters that is measuring call quality. VoIP SecurityEncryptions of VoIP call through SRTP and TLS. Prevent eaves dropping. Directory SearchAMC+ can search in the PBX enterprise register through LDAP, e.g. one exchange-server The caller ID and name is presented on incoming calls (provided that the person can be found in directory) as well as A-number presentation over the mobile data network. Basic Mobile PresenceThrough the AMC see an user presence status. Requires a presence-server (XMPP alt SIP Simple) Mobile IMInstant Messaging (chat) through AMC Requires presence/chat-server (XMPP alt SIP Simple) (1) Best results for call setup are achieved using a 3G data channel for signaling the destination number in the call setup. DTMF is used as a fall back method for call setup if the data channel is not available, however, this can take up to 15 seconds or more, depending on the number of dialed digits. ASE/MXO/PLM/0221/0/1 EN

© Aastra AMC+ 2.0 – Smartphones AMC+Symbian (S60 3rd, 5th ed & Symbian ^3 & Anna) BlackBerry (RIM OS v5, 6 & 7) Android (v ) iPhone (IOS v4 & v5) Calling card Exemption number In-call services (1) Call profiles Absence Information Https call-back Travel SIM Dual mode VoIP Security (2) Directory Search Basic Mobile Presence Mobile IM (1): In-call (mid-call) services with Android and iPhone telephones requires a 3G or Wi-Fi data connection,as DTMF is not supported during an active call with these OSs. However, in-call services can be activated via DTMF tones for Symbian and BlackBerry terminals if no 3G or Wi-Fi connection is available. (2): Use of Bluetooth headsets cannot guarantee a secure call during a VoIP/VoWLAN call (3): AMC+ UC feature support for the Android OS version of the client is not yet supported (4): AMC+ for iPhone only support seamless handover from Cellular network to Wi-Fi (2) (3) ASE/MXO/PLM/0221/0/1 EN (4)

© Aastra FMC Solution Challengers to Consider New smart phone types/models are released every week. To avoid solution complexity, it is recommended to implement a mobile phone policy in the company to standardize on a limited amount of phone models to ease management. A smart phone is like a computer. You have to reboot them now and then to ensure consistent behavior (The recommendation is once a day on average). AMC+ is a powerful application and if you have all features turned on AMC+ as well as the data connections, it can consume ~30% more battery (depending on phone type, OS version & network). If dual-mode is part of the solution, you must make sure the Wi-Fi network is “VoIP ready”. AMC+ call setup time is slightly longer than the a standard mobile call due to that the call is setup via the call manager in the enterprise. Mobile phone OS specific limitations: When roaming outside their “home” network, iPhone and Android OS phone users have to manually answer the “https call back” request during the call setup. iPhones can only do automatic VoIP call hand over from GSM to Wi-Fi. However, Wi-Fi to GSM hand-over is automatic. This is only a limitation with this phone OS, not others. iPhones do not provide an API to enable AMC+ to detect roaming automatically, so this feature has to be manually activated in the AMC+ in the “About/Status” menu when users roam outside their “home” mobile network. ASE/FMC/PLM/ 0002 / EN

© Aastra Thank you! ASE/MXO/PLM/0221/0/1 EN