NEW FEATURES FOR ENTERPRISE

QUESCOM GATEWAY - VERSION 5.2

February 2010

Copyright Notice

Copyright

1998-2010 Copyright QuesCom BP 327, 06906 Sophia-Antipolis Cedex, FRANCE Edited in France, February 2010 All rights reserved. This product and its related documentation are protected by copyright and distributed under QuesCom licenses to its authorized users only. Authorized users who have purchased one or more QuesCom products described herein can download and print a copy of this publication. No part of this product or its related documentation may be reproduced, adapted or translated without prior written authorization of QuesCom. The information contained herein is subject to change without prior notice.

Contact

QuesCom BP 327 06906 Sophia-Antipolis Cedex FRANCE Phone: Fax: URL: E-mail: +33 4 97 23 48 48 +33 4 97 23 48 49 http://www.quescom.com info@quescom.com

QuesCom

Page 2/48

Trademarks

Trademarks

QuesCom, NextBX and SmartIAD are registered trademarks of QuesCom SA. Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. All other products mentioned herein may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.

QuesCom

Page 3/48

Disclaimer

Disclaimer

Information contained herein supersedes preliminary specifications or data sheets of the product as well as earlier versions of this publication, if any. While every effort has been made to ensure the accuracy of this publication, QuesCom assumes no liability for omissions or editorial errors contained herein. QuesCom reserves the right to revise the information herein at any time without prior notice. Changes and improvements will be incorporated into the new version of this publication. THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND. QUESCOM HEREBY DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND THOSE ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. IN NO EVENT SHALL QUESCOM BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL OR INCIDENTAL DAMAGES, INCLUDING BUT NOT LIMITED TO, ALL DAMAGES RESULTING FROM LOSS OF USE, DATA OR PROFITS ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

QuesCom

Page 4/48

Contents
Contents 1. 2. Profile New features description
2.1. SNMP 2.1.1. ISDN trunks 2.1.2. GSM trunks 2.1.3. IP trunks 2.1.4. Virtual SIP Phone LDAP synchronization & user import file 2.2.1. QPortal User Synchronization menu 2.2.2. Configuration wizard Virtual SIP Phone 2.3.1. Overview 2.3.2. VSP configuration 2.3.3. VSP routing QWAdmin support for VSP Mobile Reachability Detection T.37 support for fax and SMS sending 2.6.1. For Email to Fax 2.6.2. For Email to SMS New CDR format

5 6 7
7 8 9 11 12 13 14 22 24 24 25 28 30 32 34 34 35 36

2.2. 2.3.

2.4. 2.5. 2.6. 2.7.

3.

Customer Service

48

QuesCom

Page 5/48

Contents

1.

Profile

Overview

This document describes new features for QuesCom gateway for Enterprise, introduced in the software version 5.2. QuesCom Gateway 200 QuesCom Gateway 300 QuesCom Gateway 400

QuesCom Product

System Release

IAD05.20

QuesCom

Page 6/48

Contents

2.
2.1.

New features description

SNMP

Overview

In this new software release, the SNMP support is improved to provide a real-time view of communications on the QuesCom gateway. New counters have been added to relate communications established on each trunks (IP, GSM and ISDN). Also, on these trunks, new traps are generated on main events.

Note The QuesCom MIB is saved into the QuesCom gateway in the folder d:\QuesCom\Pilot\quescom.mib To enable SNMP traps, run into a telnet session on the QuesCom gateway the program config /snmp and enter the IP address of the destination of traps.

QuesCom

Page 7/48

Contents

2.1.1.

ISDN trunks

Counters description

The table below describes all OID that monitor ISDN ports: OID path 1.3.6.1.4.1.9622.11.1 1.3.6.1.4.1.9622.11.1.1 1.3.6.1.4.1.9622.11.1.2 1.3.6.1.4.1.9622.11.1.2.1 1.3.6.1.4.1.9622.11.1.2.1.1 1.3.6.1.4.1.9622.11.1.2.1.2 1.3.6.1.4.1.9622.11.1.2.1.3 1.3.6.1.4.1.9622.11.1.2.1.4 1.3.6.1.4.1.9622.11.1.2.1.5 1.3.6.1.4.1.9622.11.1.2.1.6 1.3.6.1.4.1.9622.11.1.2.1.7 1.3.6.1.4.1.9622.11.1.2.1.8 1.3.6.1.4.1.9622.11.1.2.1.9 1.3.6.1.4.1.9622.11.1.2.1.10 1.3.6.1.4.1.9622.11.1.2.1.11 1.3.6.1.4.1.9622.11.1.2.1.12 1.3.6.1.4.1.9622.11.1.2.1.13 1.3.6.1.4.1.9622.11.1.2.1.14 isdn isdnNumber isdnComponentsTable isdnComponentsEntry isdnIndex isdnGwName isdnSlot isdnPort isdnType isdnMode isdnStatus isdnUsedChannels isdnUsedChannelsVoiceIn isdnUsedChannelsVoiceOut isdnUsedChannelsFaxIn isdnUsedChannelsFaxOut isdnUsedChannelsT38In isdnUsedChannelsT38Out SmartIad Slot number board Trunk number PRI or BRI type NT or TE mode Status Up or Down Number of non idle channels on the slot/port Number of channels with SWI status (ISDN incoming calls) Number of channels with SWO status (ISDN outgoing calls) Number of channels with FAXI status (Incoming fax) Number of channels with FAXO status (Outgoing fax) Number of channels with RTFI status (Real Time Incoming fax) Number of channels with RTFO status (Real Time Outgoing fax) Number of ISDN ports. Sequence of isdnEntry index isdnIndex Name Explanation and possible values

Traps description

The table below describes traps related to ISDN links. OID path 1.3.6.1.4.1.9622.12 1.3.6.1.4.1.9622.12.1 1.3.6.1.4.1.9622.12.2 Name trunksTraps isdnLinkUp isdnLinkDown Value are isdnIndex and isdnStatus Value are isdnIndex and isdnStatus Explanation and possible values

QuesCom

Page 8/48

Contents

2.1.2.

GSM trunks

GSM Counter description

The table below describes all OID that monitor ISDN ports: OID path 1.3.6.1.4.1.9622.11.2 1.3.6.1.4.1.9622.11.2.1 1.3.6.1.4.1.9622.11.2.2 1.3.6.1.4.1.9622.11.2.3 1.3.6.1.4.1.9622.11.2.4 1.3.6.1.4.1.9622.11.2.5 1.3.6.1.4.1.9622.11.2.6 gsm gsmNumber gsmSimMissingPorts gsmSimPukPorts gsmSimRegisteredPorts gsmUsedPorts gsmUsedPortsIn Number of GSM channels, including master & relay Number of GSM without SIM cards Number of GSM ports with SIM PUK Number of SIM registered Number of established calls since last reboot. Number incoming reboot of calls established since last Name Explanation and possible values

1.3.6.1.4.1.9622.11.2.7 1.3.6.1.4.1.9622.11.2.8 1.3.6.1.4.1.9622.11.2.8.1 1.3.6.1.4.1.9622.11.2.8.1.1 1.3.6.1.4.1.9622.11.2.8.1.2 1.3.6.1.4.1.9622.11.2.8.1.3 1.3.6.1.4.1.9622.11.2.8.1.4

gsmUsedPortsOut gsmComponentsTable gsmComponentsEntry gsmIndex gsmGwName gsmPort gsmType

Number of established outgoing calls since last reboot Sequence of gsmEntry Index gsmIndex

SmartIAD GSM port number on the gateway Possible choice are: Dual band or tri band US or tri band EU or quad band UMTS EU or quad band UMTS world Possible status are SIM missing, registered, call out, call in. Name of the operator. GSM Signal level Half rate, full rate, Enhanced Full Rate, AMR Half Rate or AMR Full Rate. Blank if no call established Blank if no call established Number of HR calls since startup

1.3.6.1.4.1.9622.11.2.8.1.5 1.3.6.1.4.1.9622.11.2.8.1.6 1.3.6.1.4.1.9622.11.2.8.1.7 1.3.6.1.4.1.9622.11.2.8.1.8

gsmStatus gsmOperator gsmSignalReceivingLevel gsmMode

1.3.6.1.4.1.9622.11.2.8.1.9 1.3.6.1.4.1.9622.11.2.8.1.10 1.3.6.1.4.1.9622.11.2.8.1.11

gsmCallingNumber gsmCalledNumber gsmNbHRCalls

QuesCom

Page 9/48

Contents

GSM counter description (suite)

OID path 1.3.6.1.4.1.9622.11.2.8.1.12 1.3.6.1.4.1.9622.11.2.8.1.13 1.3.6.1.4.1.9622.11.2.8.1.14 1.3.6.1.4.1.9622.11.2.8.1.15 1.3.6.1.4.1.9622.11.2.8.1.16 1.3.6.1.4.1.9622.11.2.8.1.17 1.3.6.1.4.1.9622.11.2.8.1.18 1.3.6.1.4.1.9622.11.2.8.1.19

Name gsmNbCellLACChanged gsmNbNetworkCongestion gsmNbCallsPlaced gsmNbCallsEstablishedOut gsmNbCallsReceived gsmNbCallsEstablishedIn gsmNbSmsSent gsmNbSmsReceived

Explanation values

and

possible

Number of Cell/LAC changes since startup. Number of No Dial tone or No Carrier messages Number of GSM outgoing call placed Number of GSM outgoing calls connected. Number of GSM incoming call received. Number of incoming calls connected Number of SMS sent. Number of SMS received.

Traps description

The table below describes traps related to GSM links. OID path 1.3.6.1.4.1.9622.12.3 1.3.6.1.4.1.9622.12.4 Name gsmLinkUp gsmLinkDown Explanation and possible values Values sent are gsmIndex and gsmStatus when a SIM is registered Values sent are gsmIndex and gsmStatus when a SIM is deregistered.

QuesCom

Page 10/48

Contents

2.1.3.

IP trunks

Counters description

The table below describes all OID that monitor IP trunks: OID path 1.3.6.1.4.1.9622.11.3 1.3.6.1.4.1.9622.11.3.1 1.3.6.1.4.1.9622.11.3.2 1.3.6.1.4.1.9622.11.3.2.1 1.3.6.1.4.1.9622.11.3.2.1.1 1.3.6.1.4.1.9622.11.3.2.1.2 1.3.6.1.4.1.9622.11.3.2.1.3 1.3.6.1.4.1.9622.11.3.2.1.4 1.3.6.1.4.1.9622.11.3.2.1.5 1.3.6.1.4.1.9622.11.3.2.1.6 1.3.6.1.4.1.9622.11.3.2.1.7 1.3.6.1.4.1.9622.11.3.2.1.8 voip voipNumber voipComponentsTable voipComponentsEntry voipIndex voipName voipType voipProtocole voipStatus voipUsedSessions voipUsedSessionsIn voipUsedSesssionsOut VoIP Trunk name Possible type are trunk or VoIP device SIP or H323 Possible status are up or down Number of connected VoIP calls Number of incoming calls Number of outgoing calls Name Explanation and possible values VoIP branch Number of SIP and H323 trunks Sequence of voipEntry index voipIndex

Traps description

The table below describes traps related to VoIP trunks: OID path 1.3.6.1.4.1.9622.12.5 1.3.6.1.4.1.9622.12.6 Name voipLinkUp voipLinkDown Explanation and possible values Values sent are voipIndex and voipStatus when the IP link is up. Values sent are voipIndex and voipStatus when the IP link is down.

QuesCom

Page 11/48

Contents

2.1.4.

Virtual SIP Phone

Counters description

Note Refer to the section 2.3 for the Virtual SIP Phone (VSP) description.

The table below describes all OID that monitor Virtual SIP Phones: OID path 1.3.6.1.4.1.9622.11.4 1.3.6.1.4.1.9622.11.4.1 1.3.6.1.4.1.9622.11.4.2 1.3.6.1.4.1.9622.11.4.2.1 1.3.6.1.4.1.9622.11.4.2.1.1 1.3.6.1.4.1.9622.11.4.2.1.2 1.3.6.1.4.1.9622.11.4.2.1.3 vsp vspNumber vspComponentsTable vspComponentsEntry vspIndex vspCallerId vspStatus Caller Id associated to VSP Inactive/active not registered/active registered Name Explanation and possible values Vitual SIP Phone branch Number of VSP Sequence of vspEntry index vspIndex

Traps description

The table below describes traps related to Virtual SIP Phone: OID path 1.3.6.1.4.1.9622.12.7 1.3.6.1.4.1.9622.12.8 Name vspLinkUp vspLinkDown Explanation and possible values Values sent are vspIndex and vspStatus when the VSP is registered. Values sent are vspIndex and vspStatus when the VPS deregistered.

QuesCom

Page 12/48

Contents

2.2.

LDAP synchronization & user import file

Overview

This new software release introduces the synchronisation of user information with external database. Only fields mandatory for user creation in QPortal are synchronised: QPortal login, Fax and SMS sending/receiving.

Synchronization method

Two synchronisation methods are available: synchronization by import of a CSV file or synchronization with a LDAP server Note The administrator account can never be altered by synchronization by CSV or LDAP.

Synchronize and import

The user synchronization can be performed: at the end of the Configuration Wizard from QPortal > User & Mobility > User synchronization menu

QuesCom

Page 13/48

Contents

2.2.1.

QPortal User Synchronization menu

Overview

In the section Users & Mobility, the menu User Synchronization allows the synchronization of user information by import of a CSV file and by synchronization with a LDAP server.

Select the synchronization method

Select first the synchronization method by clicking either on the CSV button or on the LDAP button:

QuesCom

Page 14/48

Contents

2.2.1.1.

Synchronization by import of a CSV file

Overview

The user information is saved into a file with a specific format, the CSV file. During the synchronization process, this file is loaded on the QuesCom gateway and users are created into the embedded QuesCom database.

CSV file format overview

The format of a CSV file is: One record per line All lines are CR/LF terminated All fields are coma separated (,)

Fields description

Each line of the CSV file must be composed of all these fields: Field Value Login User login (for QPUser), must be unique. Password User password cannot be empty. LastName User last name, cannot be empty FirstName User first name, cannot be empty EmailAddress User email address for the reception of faxes, voice box messages and SMS, cannot be empty UserLanguage Enter FRE or ENG or GER. Mobility Enter YES to enable Mobility Pro features for this user. NO means no Mobility and Mobility Pro access. Voicebox Enter YES or NO to grant access or not to VoiceBox services Fax Enter YES or NO to grant access or not to fax sending/receiving services SMS Enter YES or NO to grant access or not to SMS sending/receiving services. Caller ID Caller ID of the user. Several caller ID can be added, separated by a coma.

Example

jsmith , pwd , john, smith, jsmith@qc.com, ENG, Yes,Yes,Yes, Yes, 0641106674 rcold , pwd , robert, cold, rcold@qc.com, ENG, Yes,Yes,Yes, Yes, 0641106675,2345

QuesCom

Page 15/48

Contents

Synchronization by CSV

To start the synchronization of user information by import of a CSV file, follow the procedure described below: Step 1 2 Action Click Browse and select the CSV file you want import. Select update options: Options Explanation Add new users To create in the QuesCom database users not already present but listed into the CSV file. Update existing To update information of users already created users into the QuesCom database by information present into the CSV file. Note that username, password and language fields are not updated. Delete users not To delete users from the QuesCom database if listed in CSV file they are not present in the CSV file. Click Import.

QuesCom

Page 16/48

New features description

2.2.1.2. Synchronization with LDAP server

Overview

Use this option to synchronize user information with a LDAP server (like Active Directory). The configuration of the synchronization with a LDAP server is performed in three steps: Step Description 1 Server Parameter: Configure the access to the LDAP server (IP address, login/password, base location) and synchronization interval. 2 Fields Mapping: Configure the mapping between LDAP user information record (like sAMAccountName) and QuesCom QPortal user fields name (like User Name). 3 Caller ID Mapping: Configure the mapping between LDAP user phone information (like telephoneNumber) and QuesCom Caller ID. All these steps are described below.

QuesCom

Page 17/48

New features description

Synchronization with LDAP, server parameters

The table below describes Server Parameters for user synchronization by LDAP: Parameter Explanation IP address of Enter here the LDAP server IP address or enter the FQDN (Fully LDAP server Qualified Domain Name) Port Enter the LDAP server default port. The default port is 389. User name Administrator name allowing the connection to the LDAP server Password Administrator password Base location Enter the base name (branch of the tree where user information is stored). Ex: To import users from a LADP server named LDAP.quescom.com, use CN=Users,DC=LDAP,DC=quescom,DC=com Scope The LDAP search scope indicates the set of entries at or below the search base DN that may be considered potential matches for a search operation. Possible values are: BASE The search operation is only performed against the entry specified as the search base DN. No entries below it will be considered. ONELEVEL The search operation is only performed against entries that are immediate subordinates of the entry specified as the search base DN. The base entry itself is not included. SUBTREE The search operation is performed against the entry specified as the search base and all of its subordinates to any depth. Filter Enter a filter sentence here to retrieve only a set of users. Ex: If users are member of a group named GW users the filter is: (memberOf=CN=GW Users,CN=Users,DC=quescom,DC=com) Enter the maximum number of LDAP entries returned by the LDAP server in a single results page. Once that all entries of the page are processed, the QuesCom gateway will request the next page from the LDAP server. The default value is 100 and the maximum value is 10000. Enter the synchronization timing in minutes. The value can be 0, so the synchronization will be done only when manually requested. Click Test LDAP to tests server settings. A file is generated for checking. Click Sync LDAP now to force the synchronization now.

Page Size

Synchronization interval (min) Test LDAP Sync LDAP now

QuesCom

Page 18/48

New features description

Field mappings

The Field Mappings page allows the definition of the mapping between LDAP record name and QPortal user field name. Settings LDAP fields Explanation For QuesCom QPortal user fields that have an equivalent in LDAP, enter the LDAP record name. Example for an Active Directory server: sAMAccountName for User Name, Sn for Last Name, givenName for First Name, Mail for E-mail If there is no LDAP field linked to QuesCom field (field not specified or specified field not present on the server) a default value can be forced. Example: Password can be forced to the LDAP field Sn or, the same password can be set to all users by entering a default password in the text box. User Language can be selected from a combo box, Mobility and Voice Box can be checked or not Check the box if you want the value is updated every time the synchronization is run (and set LDAP field or Default value) Do not check the box if the value in the QuesCom system must never be updated. LDAP field/Default value will be used only when a new user is created.

Default value

Updateable

QuesCom

Page 19/48

New features description

Caller ID Mappings

Define the computation of Caller ID from LDAP information in this page. The table below explains the caller ID computation from Caller ID Mapping settings: Procedure to compute a caller ID Search of a specific Attribute in the LDAP user record. (Ex: telephoneNumber or facsimileTeletphoneNumber) IF THEN The attribute is found with a particular Prefix (Ex: +33) apply the Rule to create the Caller ID. (Ex: the rule -1:3 +1:0 to transform +33497239348 to the Caller ID 0497239348) and Create the Caller ID with the result of : o the Rule and o the Fax/SMS Send /Receive attribute.

Note: Rules and wildcards are described below.

The snapshot below shows the Caller ID Mappings panel:

QuesCom

Page 20/48

New features description

Rules & wildcard

Rules operations possible: To add digits x digits in y position, the rule is +y :x To remove x digits in y position the rule is -y :x The wildcards * can be used. This wildcard replace a sequence of digit Examples : 234 : Match any called number starting with 234 234* : same as 234

Process

To configure the Caller ID Mappings, follow the procedure described below: Step 1 2 Action Set Attribute, Prefix, Rule and FAX/SMS Send / Receive parameters Click Add. Note Several Caller IDs can be created from the same Attribute and the same Prefix. See the example below.

Example

In this example, for all users, we create 2 Caller ID from the LDAP Attribute telephoneNumber: To create a Caller ID: with a Long distance format number from the international format number: +33 4 97 23 4848 with a short number from international format number: +33 4 97 23 4848 Set the Prefix +33 +33 Set the Rule -1:3 +1:0 -1:8 Result 0497234848 48 48

QuesCom

Page 21/48

New features description 2.2.2. Configuration wizard

New optional step in the configuration wizard

Since the version 5.10, the installation and the configuration of QuesCom gateways is performed through wizards. The software release 5.20 extends the configuration wizard with new steps for user synchronisation. The user import or synchronisation at the end of the configuration wizard is optional and can be skipped. A new menu in QPortal > Users > User Synchronisation allows also configuring an import and a synchronisation. The first step of the user synchronization wizard consist in selecting the method: For import from CSV file select Import users from a file For synchronization with a LDAP server, select Establish users synchronization with LDAP directory

First step, select the method

Upload CSV file

Click Browse button and select your CSV file. Then, To create in the QuesCom database users not already present but listed into the CSV file, click Add new users. To update information of users already created into the QuesCom database by information present into the CSV file click Update existing users To delete users into the QuesCom database those are not present into the CSV file, click Delete users not listed in CSV file.

QuesCom

Page 22/48

New features description

Confirmation

On clicking Next, a Summary displays administrator settings. Back button can be used to modify these settings. The load starts when the Finish button is clicked.

LDAP synchronization

If the LDAP synchronization method is selected, some mandatory parameters must be filled: Parameter Explanation IP address of Enter here the IP address of the LDAP server. LDAP server User name Administrator name that allows the connection to the LDAP server Password Administrator password Base Enter the base name (branch of the tree where user information is stored). Ex: To import users from LADP server named LDAP.quescom.com, use CN=Users,DC=LDAP,DC=quescom,DC=com Filter Enter a filter sentence here to retrieve only a set of users. Ex: If users are member of a group named GW users the filter shoulf be: (memberOf=CN=GW Users,CN=Users,DC=quescom,DC=com)

Confirmation

On clicking Next, a Summary displays administrator settings. Back button can be used to modify these settings. The synchronization starts when the Finish button is clicked.

QuesCom

Page 23/48

New features description

2.3.
2.3.1.

Virtual SIP Phone

Overview

Overview

The new feature Virtual SIP Phone simplifies the configuration of Mobility users for iPBX. Now, for the IPBX point of view, Mobility users are only registered SIP phones and for the QuesCom gateway point of view, Mobility users are Virtual SIP Phones.

Benefits

By this way, adding a Mobility user in the telephone environment consist in the declaration of a new SIP phone in the iPBX. Natively, basic features including line supervision, boss/secretary relation, online/busy status etc. are available exactly like with a physical SIP phone. Call transfer is done by the SIP REFER method. Benefits are: VoIP internal resources on both iPBX and QuesCom gateway are freed The Mobility user that initiated the transfer can be joined again Message Waiting Indication and messages sent by iPBX can be forwarded to the mobile user using his phone device capabilities (i.e. SMS on a mobile phone) Available soon. Virtual SIP phone can be registered/unregistered depending on mobile user status identified by the gateway (See the Mobile Reachability Detection feature)

QuesCom

Page 24/48

New features description 2.3.2. VSP configuration

Overview

Several steps are required to configure Virtual SIP Phones (VSP) in QuesCom gateway. The table below list all these steps while sections below describe them in details: Step Action Required/optional 1 Run config /vsp to configure VSP IP address Optional and ports 2 Create a Foreign Gatekeeper SIP Required 3 Configure VSP for each users in QPortal > Required Users & Mobility > Users 4 Add VSP to a device group Required 5 Configure call route between the device Required group and Mobility Note Only one VSP is authorized per user The Called ID associated to the VSP must be the users One Number.

VSP IP addresses and ports

This action is optional. For some iPBX (like Aastra5000) a secondary IP address for VSP is necessary. Also, each VSP must be reachable on a specific port. (This is the port announced in contact header during the SIP registration). To configure the second IP address and VSP port, follow the procedure described below: Step Action 1 Connect to the QuesCom gateway be a telnet session. 2 Run config /vsp 3 The following questions will be asked: Enter the secondary Gateway IP Address [192.168.196.35]: Enter here the secondary IP address for VSP. The default value is the IP address of the QuesCom gateway plus 1. Enter VSP SIP port pool start [12000]: Enter here the first port number of the VSP pool. The default value is 12000. Enter VSP SIP port pool size [100]: Enter here the number of VSP. The default value is 100. 4 Enter 1 to confirm parameters and Y to restart the QuesCom gateway.

QuesCom

Page 25/48

New features description

Create FGK SIP

As Virtual SIP Phone are associated to a Foreign Gatekeeper SIP (the iPBX), the Foreign Gatekeeper object must be created into the QuesCom gateway. Follow the procedure below to create the Foreign Gatekeeper: Step Action 1 Connect to the QPortal: http://Gateway_IP_@:8000 2 Click Objects > Foreign Gatekeeper > ADD RECORD. 3 In the Foreign Gatekeeper panel, enter: ID = If the QuesCom gateway needs to register to the iPBX, enter the gateway registration name. If not, enter the name of the iPBX. Name = Enter the name of the iPBX Gatekeeper type = SIP VoIP Profile = NOOPT_SIP (if the QuesCom gateway does not need to register to the iPBX) 4 Click SAVE.

QuesCom

Page 26/48

New features description

Create VSP

To create a user with a Virtual SIP phone or to add a Virtual SIP Phone to a user, follow the procedure described below: Step Action 1 Connect to the QPortal: http://Gateway_IP_@:8000 2 Click Objects > Users & Mobility > Users > ADD RECORD. 3 In the User creation panel, Under User Identity enter the user Last Name, First Name, Email address and Language. Under Authorised services, enter the user login and password. Check Mobility Pro. Under Caller ID, enter a Caller ID and click Add. Under Phones, enter a Phone Name, select Phone Type = VSP and enter the Phone Calling ID. Under VSP, enter the mandatory parameter Trunk ID = the name of the iPBX. User Name is the SIP user name declared into the IPBX. Password is optional. 4 Click SAVE. The snapshot below shows the section Phones > Main:

The snapshot below shows the section Phones > VSP:

QuesCom

Page 27/48

New features description 2.3.3. VSP routing

Route calls from the IPBX to Mobility

To configure a call route from VSP registered on the IPBX to Mobility, follow the procedure described below: Step Action 1 Connect to the QPortal: http://Gateway_IP_@:8000 2 Open Services > Service > ADD Record 3 In the Service panel, enter: Origin type = Foreign GK Origin = IPBX Call type = Foreign Gatekeeper Called Prefix number = * Service Type = CTI application Destination = Mobility 4 Click Save. The snapshot below shows the service form:

QuesCom

Page 28/48

New features description

Route calls from Mobility to the IPBX

To configure a call route from Mobility to VSP, follow the procedure described below: Step Action 1 Connect to the QPortal: http://Gateway_IP_@:8000 2 Open Services > Service > ADD Record 3 In the Service panel, enter: Origin type = CTI application Origin = Mobility Called Prefix number = * Call type = CTI application Service Type = VoIP Destination Type = Foreign Gatekeeper Destination = IPBX 4 Click Save. The snapshot below shows the service form:

QuesCom

Page 29/48

New features description

2.4.

QWAdmin support for VSP

Overview

This new software release supports the display, the monitoring and the activation of VSP in the QuesCom Management Console: QWAdmin. The QWAdmin version must be 4.50.013 or higher. Note To know the version of your QuesCom Management Console, in the top menu, select Help > About Management Console and the version will be displayed.

Location

VSP are located in the QWAdmin tree view under the folder Virtual SIP Phone.

Status

VSP color icons differs depending on the VSP status: Color Red Orange Green Explanation The VSP is inactive The VSP is active but not registered The VSP is active and registered

QuesCom

Page 30/48

New features description

Right pane information

For each VSP the right pane displays: Parameter Host Name IP address Manufacturer Product Name Product Type Explanation Caller Identifier of the VSP declared in QPortal > Users & Mobility > Users > Phones > Main > Phone Calling ID. IP address of the Virtual SIP phone or IPBX address QuesCom The Caller ID is displayed Always Virtual SIP Phone

Actions on right-click

Possible actions on the right click menu on the VSP are: Activate (Activate the VSP) De Activate (Unregister and deactivate the VSP)

QuesCom

Page 31/48

New features description

2.5.

Mobile Reachability Detection

Overview

This new software release introduces the Mobile Reachability Detection feature, which monitors the mobile phone reachability of Mobility pro users (with MobiQ installed). This monitoring is made with no pre-requisite from the GSM network, except supporting SMS reception with delivery receipt. Depending on the mobile phone status, reachable or not (i.e. registered or not in the GSM network), different actions can be taken to change the routing of the calls that should be forwarded to this mobile phone. This feature brings a value added for multi ring configurations for instance: Without this feature, if the user has configured the dual ring for its office phone and its mobile phone and if the mobile phone is off (or out of GSM coverage), the communication will be directly redirected to the mobile voice mail. With Mobile Reachability Detection feature, only the office phone will ring and a redirection on no response configured in QPUser or in the PBX/iPBX can handle the call (ex: on no response during lunch time, redirect the call to the reception). The configuration of global parameters of the Mobile Reachability Detection feature is performed it the section Users & Mobility > Mobility > Server. Two global parameters can be set: Parameter Explanation Reachability The default value is 25 seconds. If between this delay the Validation QuesCom gateway does not receive a response from the mobile Delay (s) phone, the mobile is declared as Un reachable and no more call will be redirected to this mobile phone. The default value is 24 hours. If during this duration, there is no Max Max response from the mobile phone, the new mobile phone status Unreachability duration (hours) will be set to Assumed Reachable and new tests about its reachability will be performed.

Benefits

Global parameters

QuesCom

Page 32/48

New features description

User Parameters

To enable this feature for a user, follow the procedure described below: Step Action 1 Connect to the QPortal: http://Gateway_IP_@:8000 2 Open Users & Mobility > User > ADD Record or Edit a Record ( 3

In Authorised Services section, check Mobility Pro. In Phone > Mobile section, check: o Replace Caller ID by SMS and o Mobile Reachability detection. In Phone > Reachability section, configure actions depending on the Reachability status. o On an unreachability status detected, choose to unregister or not the VSP select a QPuser profile to active o On a reachability status detected, Select a QPuser profile to active Click Save.

The snapshot below shows the Mobile section:

The snapshot below shows the Reachability actions section:

QuesCom

Page 33/48

New features description

2.6.

T.37 support for fax and SMS sending

Overview

This new software release support the T.37 format for Email to Fax or Email to SMS.

2.6.1.

For Email to Fax

Send Fax as an email

The user can send a fax from any email client (like Outlook) with: T.37 address in the To field The fax content in attachment in the .tiff format.

To format

T.37 address can have a format like below: FAX=+334xxxxx@domain FAX=04xxxxx@domain +334xxxxx@fax.domain 04xxxxx@fax.domain FAX=+334xxxx@192.168.1.1 FAX=04xxxxx@192.168.1.1

Where domain or fax.domain must be resolved by a DNS server to the IP address of the QuesCom Gateway.

QuesCom

Page 34/48

New features description 2.6.2. For Email to SMS

Send SMS as an email

The user can send a SMS from any email client (like Outlook) with: T.37 address in the To field The SMS text into the body of the email.

To format

T.37 address can have a format like below: SMS=+334xxxxx@domain SMS=04xxxxx@domain +336xxxxx@sms.domain 06xxxxx@sms.domain SMS=+336xxxxx@192.168.1.1 SMS=06xxxxx@192.168.1.1

Where domain or sms.domain must be resolved by a DNS server to the IP address of the QuesCom Gateway. Flash SMS support Emails with the importance flag set to high will deliver as Flash SMS.

QuesCom

Page 35/48

New features description

2.7.

New CDR format

Overview

This software release introduces the Call Detail Record (CDR) version 1.32.

Note CDR management (file size, folder storage, backup path, backup period, and the sent of CDR by email) can be configure by the command: config /cdr

The table below describes the new CDR format:

Type String Num. Num. String Num. Num. Num. String Num. Num. Num. Num. String String Num. String String Num. Num.

Field Version Transac Number Caller Device Type Caller Device Name Caller Slot Caller Port Called Device Type Called Device Name Called Slot Called Port Call Type Service Type Start Date LOC Start Time LOC Duration Caller Number Called Number Ringing Duration Number

Explanation Ticket Version Number gives the ticket structure. Here 1.32 Call Id. Type of Caller device (See table1) Name of Caller device Slot eventually used on the caller device Port eventually used on the caller device Type of Called device (See table1) Name of called device Slot eventually used on the called device Port eventually used on the called device QuesCom Call Type (See table 2) QuesCom Service Type (See table 3 and 6) Local Date of call start Local Time of call start Call Duration ( seconds) Caller Number Called Number Ringing Duration. for SMS : number of characters for Fax : number of pages For other calls value = 0 See call type to know if it is SMS or fax. 1 means that call has failed 0 means that call was successful

Max Size Example (Characters) 4 1.32 10 2 64 2 2 2 64 2 2 3 3 8 6 10 32 32 10 10 125631 1 88 1 0 2 88 0 0 2 5 20030617 142655 35 016523874 5 049723484 8 0 25

Num.

Failure

This table continues in the next page

QuesCom

Page 36/48

New features description

Type HEXA

Field Q931-1

Explanation Q931 field 1, for GSM calls over Siemens modules Location ID returned by AT+CEER command, otherwise Q931 Cause Location (See table 4) Q931 field 2, for GSM calls over Siemens modules Reason returned by AT+CEER command, otherwise Q931 Cause Reason QuesCom 400 failure cause IMSI of the SIM used to place the call (if applicable) Specify the codec used for this call (see table 5) GSM Provider code after number portability check Delay between the arrival of the call in the system and the call start ringing. (in seconds) RTP/SDP IP address Call Duration ( seconds) including minimum and step call charge IMEI of the GSM port used to place the call (if applicable) IMSI of the SIM that received the call Channel mode for GSM calls established, as returned by AT^MONI command: S_HR: Half Rate, S_FR: Full Rate, S_EFR: Enhanced Full Rate, A_HR: AMR Half Rate, A_FR: AMR Full Rate, otherwise not significant Receiving signal level for GSM calls in dBm, as returned by AT+CSQ command, otherwise not significant 0: -113 dBm or less 1: -111 dBm 230: -109 -53 dBm 31: -51 dBm or greater 99: not known or not detectable Bit Error Rate for GSM calls, as returned by AT+CSQ command: 0-7 as defined in the RXQUAL table of GSM 05.08, 99: not known or not detectable otherwise not significant Response of ATD command for GSM calls: 0: OK, 1: NO DAIL TONE, 2: NO CARRIER, 3: BUSY, 4: NO ANSWER otherwise not significant Return and New Line

Max Size Example (Characters) 2 91

HEXA

Q931-2

87

HEXA String String Num Num String Num. String String String

INTERNAL CAUSE IMSI Codec Used Destination Operator Code Post Dial Delay IP address Billed Duration IMEI Incoming IMSI Channel Mode

8 15 10 8 8 15 10 15 15 6

E2010009 123456789 012345 G711A G711U 20810 12 192.168.19 8.201 60 123456789 012345 123456789 012345 S_FR

Num.

Signal Level

Num.

Bit Error Rate

Num.

ATD Response

CR LF

QuesCom

Page 37/48

New features description

Table description

Table 1- Caller Device Type ID 0 1 2 3 Device Type QuesCom Gateway VoIP Device Foreign Gatekeeper CTI Application

Table 2 Call Type List ID 1 5 6 7 10 11 12 15 16 17 20 21 24 25 100 101 102 103 110 151 152 Label Local ISDN H323 Outgoing VoIP Outgoing Fax Outgoing Email to Fax Fax Real Time GSM Incoming Local ISDN Data H323 Foreign Gatekeeper Local ISDN Fax 2/3 Local ISDN Fax gr4 Email to SMS SMS Outgoing Back UP 1 Back UP 2 VOIP OutGoing1 VOIP OutGoing2 CTI Application FAX LOG SMS LOG

Table 3 Service Type List ID 1 2 3 4 5 6 7 8 9 10 12 16 17 Label CTI Application VoIP Fax Real Time Fax Store & Forward Switch Fax To Send Voice Msg H323 Voice Fax Remote Access Service Message Waiting Indicator SMS Store & Forward SMS To Send

Table 5 GSM codec list G711A G711U G711A56 G711U56 G723 G729 G729A G729B G729AB GSM

Table 6 - FAX/ SMS Mode If call type is FAX LOG (151) or SMS LOG (152) then Service Type field is not service type but fax mode or SMS mode: ID Label 101 Fax to file 102 Fax to fax 104 Email to fax 105 Fax Real Time 106 SMS to File 107 SMS to Email 108 SMS to Fax 109 SMS to SMS 110 Email to SMS

QuesCom

Page 38/48

New features description

Q931-1 Location ID, for GSM calls

Table 4 Q931-1 Location ID for GSM calls. ID Description 0 No error (default) 1 SIEMENS L2 cause 2 GSM cause for L3 Radio Resource Sublayer (GSM 04.08 annex F) (See table 4.2) 3 SIEMENS cause for L3 Radio Resource Sublayer (See table 4.3) 4 GSM cause for L3 Mobility Management (GSM 04.08 annex G) (See table 4.4) 5 SIEMENS cause for L3 Mobility Management (See table 4.5) 6 GSM cause for L3 Mobility Management via MMR-SAP (GSM 04.08 annex G) 7 SIEMENS cause for L3 Mobility Management via MMR-SAP 8 GSM cause for L3 Call Control (GSM 04.08 10.5.4.11 and annex H) (table 4.6) 9 SIEMENS cause for L3 Call Control (See table 4.7) 11 SIEMENS cause for L3 Advice of Charge Entity (See table 4.8) 12 GSM cause for L3 SMS CP Entity 13 SIEMENS cause for L3 SMS CP Entity 14 GSM cause for L3 SMS RL Entity 15 SIEMENS cause for L3 SMS RL Entity 16 GSM cause for L3 SMS TL Entity 17 SIEMENS cause for L3 SMS TL Entity 18 SIEMENS cause for DSM Entity 21 GSM cause for L3 Call-related Supplementary Services (See table 4.9) 22 SIEMENS cause for L3 Call-related Supplementary Services (See table 4.10) 32 SIEMENS cause for Supplementary Services Entity 33 SIEMENS cause for Supplementary Services Manager 34 Network cause for Supplementary Services (GSM 04.08 10.5.4.11 and annex H) 35 Supplementary Services network error (GSM 04.80 3.6.6) 48 GSM cause for GPRS Mobility Management (GSM 04.08 annex G.6) 49 SIEMENS cause for GPRS Mobility Management 50 GSM cause for Session Management (GSM 04.08 annex I) 51 SIEMENS cause for Session Management (See table 4.11) 127 SIEMENS cause for protocol module or other local cause (See table 4.12) 128 Supplementary Services general problem (GSM 04.80 3.6.7) 129 Supplementary Services invoke problem (GSM 04.80 3.6.7) 130 Supplementary Services result problem (GSM 04.80 3.6.7) 131 Supplementary Services error problem (GSM 04.80 3.6.7) 241 SIEMENS cause for GPRS API 242 SIEMENS cause for Link Management 243 SIEMENS cause for PPP/IP-Stack

QuesCom

Page 39/48

New features description

Q931-2 causes GSM release cause for L3 Radio Resource (RR)

Tables below describe Q931-2 cause ID for GSM calls, corresponding to locations described in the table 4. Table 4.2 GSM release cause for L3 Radio Resource Number Description 0 Normal event 1 Abnormal release, unspecified 2 Abnormal release, channel unacceptable 3 Abnormal release, timer expired 4 Abnormal release, no activity on the radio path 5 Pre-emptive release 8 Handover impossible, timing advance out of range 9 Channel mode unacceptable 10 Frequency not implemented 65 Call already cleared 95 Semantically incorrect message 96 Invalid mandatory information 97 Message type non-existent or not implemented 98 Message type not compatible with protocol state 100 Conditional information element error 101 No cell allocation available 111 Protocol error unspecified

SIEMENS release cause for L3 Radio Resource (RR)

Table 4.3 - SIEMENS release cause for L3 Radio Resource Number 1 2 3 4 5 6 7 8 9 Description Racchs not answered Racchs rejected Access class of the SIM is barred by the network provider SABM failure Radio link counter expiry or PerformAbnormalRelease Confirm ABORT of the MM Respond to DEACT REQ Loss of coverage Reestablishment not possible

QuesCom

Page 40/48

New features description

GSM release cause for Mobility Management (MM) or Session Management (SM)

Table 4.4 - GSM release cause for Mobility Management (MM) or Session Management (SM) Number Description Causes related to MS identification 2 IMSI unknown in HLR 3 Illegal MS 4 IMSI unknown in VLR 5 IMEI not accepted 6 Illegal ME Cause related to subscription options 11 PLMN not allowed 12 Location Area not allowed 13 Roaming not allowed in this location area Causes related to PLMN specific network failures and congestion 17 Network failure 22 Congestion Causes related to nature of request 25 PDP context is deactivated because of a LLC or SNDCP failure 32 Service option not supported 33 Requested service option not subscribed 34 Service option temporarily out of order 36 Regular PDP context deactivation 38 Call cannot be identified Causes related to invalid messages 95 Semantically incorrect message 96 Invalid mandatory information 97 Message type non-existent or not implemented 98 Message not compatible with protocol state 99 Information element non-existent or not implemented 100 Conditional information element error 101 Messages not compatible with protocol state 111 Protocol error unspecified Causes related to GPRS 7 GPRS services not allowed 8 GPRS services not allowed in combination with non-GPRS services 9 MS identity cannot be identified by the network 10 Implicitly detached 14 GPRS services not allowed in current PLMN 16 MSC temporarily unreachable

QuesCom

Page 41/48

New features description

SIEMENS release cause for L3 Mobility Management (MM)

Table 4.5 Number 1 8 9 11 17 18 19 20 21 22 23 24 25

SIEMENS release cause for L3 Mobility Management (MM) Description No SIM available No MM connection Authentication failure MM performs detach Registration failed and will be re-attempted in a short term CM connection establishment failed Registration failed and will be re-attempted in a long term RR connection is released MS tries to register SPLMN is not available An MTC is in progress A PLMN scan is in progress The MM is detached the MS is in MS class C GPRS only

QuesCom

Page 42/48

New features description

GSM release cause for L3 Call Control (CC)

Table 4.6 - GSM release cause for L3 Call Control Number Description 0 No error Normal class 1 Unassigned (unallocated) number 3 No route to destination 6 Channel unacceptable 8 Operator determined barring 16 Normal call clearing 17 User busy 18 No user responding 19 User alerting no answer 21 Call rejected 22 Number changed 25 Pre-emption 26 Non-selected user clearing 27 Destination out of order 28 Invalid number format (incomplete number) 29 Facility rejected 30 Response to STATUS ENQUIRY 31 Normal unspecified Resource unavailable class 34 No circuit/channel available 38 Network out of order 41 Temporary failure 42 Switching equipment congestion 43 Access information discarded 44 Requested circuit/channel not available 47 Resource unavailable unspecified Service or option not available class 49 Quality of service unavailable 50 Requested facility not subscribed 55 Incoming calls barred within the CUG 57 Bearer capability not authorized 58 Bearer capability not presently available 63 Service or option not available unspecified Service or option not implemented 65 Bearer service not implemented 68 ACM equal or greater than ACMmax 69 Requested facility not implemented 70 Only restricted digital information bearer capability is available 79 service or option not implemented unspecified Invalid message (e.g. parameter out of range) class 81 Invalid transaction identifier value This table continues in the next page

QuesCom

Page 43/48

New features description

GSM release cause for L3 Call Control (CC) (Suite)

Table 4.6 - GSM release cause for L3 Call Control (CC) (Suite) Number Description 87 User not member of CUG 88 Incompatible destination 91 Invalid transit network selection 95 Semantically incorrect message Protocol error (e.g. unknown message) class 96 Invalid mandatory information 97 Message type non-existent or not implemented 98 Message type not compatible with protocol state 99 Information element non-existent or not implemented 100 Conditional information element error 101 Message not compatible with protocol 102 Recovery on timer expiry 111 Protocol error unspecified Interworking class 127 Interworking unspecified

SIEMENS release cause for L3 Call Control (CC)

Table 4.7 - SIEMENS release cause for L3 Call Control Number 1 2 3 4 5 6 7 Description Call dropped Service not available Hold procedure not available Temporary no service previous procedure not yet finished No speech service available Call reestablishment procedure active Mobile received a release (complete) message during a modify procedure (modify reject) 8 Call clearing because loss of radio connection if no reestablishment is allowed (call not active) 10 Number not included in FDN list Notifications 300 Called party barred incoming call

SIEMENS release cause for L3 Advice of Charge (AOC)

Table 4.8 SIEMENS release cause for L3 Advice of Charge Number 1 2 3 4 5 Description SIM data not available SIM does not support AOC SIM data access error ACM limit almost reached ACM range overflow ACM range overflow

QuesCom

Page 44/48

New features description

GSM Release cause for Supplementary Service Call

Table 4.9 - GSM Release cause for Supplementary Service Call Number Description 0 No error (default) 1 UnknownSubscriber 9 IllegalSubscriber 10 BearerServiceNotProvisioned 11 TeleserviceNotProvisioned 12 IllegalEquipment 13 CallBarred 15 CUGReject 16 IllegalSSOperation 17 SSErrorStatus 18 SSNotAvailable 19 SSSubscriptionViolation 20 SSIncompatibility 21 FacilityNotSupported 27 AbsentSubscriber 29 ShortTermDenial 30 LongTermDenial 34 SystemFailure 35 DataMissing 36 UnexpectedDataValue 37 PWRegistrationFailure 38 NegativePWCheck 43 NumberOfPWAttemptsViolation 71 UnknownAlphabet 72 USSDBusy 126 MaxNumsOfMPTYCallsExceeded 127 ResourcesNotAvailable General Problem Codes 300 Unrecognized Component 301 Mistyped Component 302 Badly Structured Component Invoke Problem Codes 303 Duplicate Invoke ID 304 Unrecognized Operation 305 Mistyped Parameter 306 Resource Limitation 307 Initiating Release 308 Unrecognized Linked ID 309 Linked Response Unexpected 310 Unexpected Linked Operation This table continues in the next page

QuesCom

Page 45/48

New features description

GSM Release cause for Supplementary Service Call (Suite)

Table 4.9 - GSM Release cause for Supplementary Service Call Number Description Return Result Problem Codes 311 Unrecognize Invoke ID 312 Return Result Unexpected 313 Mistyped Parameter Return Error Problem Codes 314 Unrecognized Invoke ID 315 Return Error Unexpected 316 Unrecognized Error 317 Unexpected Error 318 Mistyped Parameter

SIEMENS release cause for Call-related Supplementary Services (CRSS)

Table 4.10 - SIEMENS release cause for Call-related Supplementary Services Number Description 0 ECT procedure failed (timer expired) 1 Call has been cleared without receiving an answer to ECT request 2 Initial conditions not fulfilled (one active - one held call) 3 Received "return error" 4 Call has been cleared without receiving an answer to CCBS request 5 Initial conditions for CCBS not fulfilled (Idle CRSS) Causes related to nature of request 25 LLC or SNDCP failure 26 Insufficient resources 27 Unknown or missing access point name 28 Unknown PDP address or PDP type 29 User authentification failed 30 Activation rejected by GGSN 31 Activation rejected unspecified 32 Service option not supported 33 Requested service option not subscribed 34 Service option temporarily out of order 35 NSAPI already used 36 Regular PDP context deactivation 37 QoS not accepted 38 Network failure 39 Reactivation requested 40 Feature not supported Causes related to invalid messages 81 Invalid transaction identifier value 95 Semantically incorrect message 96 Invalid mandatory information 97 Message type non-existant or not implemented 98 Message type not comaptible with protocol state 99 Information element non-existent or not implemented 100 Conditional information element error 101 Message not compatible with protocol 111 Protocol error unspecified

QuesCom

Page 46/48

New features description

SIEMENS release cause for Session Management (SM)

Table 4.11 - SIEMENS release cause for Session Management (SM) Number Description 3 The MS has not got any answer to the ACTIVATE PDP CONTEXT request message sent five times to the network 4 A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated 5 A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated. The activation request is rejected by the SM sending the cause 'insufficient resources' to the network because the SM was not able to perform the necessary comparisons for a static PDP address collision detection. 6 A MT PDP context which is active or in the activation process is deactivated because another MT PDP context with the same TI is requested by the network to be activated. As a static PDP address collision with an MO activating PDP context has been detected by the SM the SM discards the activation request 7 A MT PDP context request has been indicated but could not be processed in time. The activation request is rejected by the SM sending the cause 'insufficient resources' to the network.

GSM cause for L3 Protocol module or other local cause

Table 4.12 GSM cause for L3 Protocol module or other local cause Number Description 2 No detailed cause

QuesCom

Page 47/48

Customer Service

3.

Customer Service

Contact

Phone - Fax: E-mail: URL:

+33 (0) 820 20 38 46 support@quescom.com http://support.quescom.com/

QuesCom

Page 48/48