MC Solution Technical-training

MC Solution Technical Training
A introduction through the concepts and the installation of the MC Solution

©Comdasys 2011 All rights reserved

Introduction

• • • • •

Comdasys was founded in 2004, Private held company Products for branch connectivity (SBC …) 2007 launched first vendor independent FMC solution Development based in Munich, Germany Main Product: MC Solution – Mobile Phone Integration into Premise based and Hosted PBX

• Business & Technology Partners: Aastra, Avaya, Broadsoft, Mitel, MailVision, nfon, NEC-United, Seltatel, ShoreTel, Siemens, Teles

©Comdasys 2011 All rights reserved

2

The Market Leading FMC/UC Solution
The Frost & Sullivan Award for Market Leadership is presented to Comdasys which has demonstrated excellence in capturing the highest market share within its industry. The Award recognizes the company's leadership position within the industry in terms of revenues or units, as specified. Note: report available upon request

©Comdasys 2011 All rights reserved

3

Today‘s Business Challenges We enable you to master today‘s business challenges with our comprehensive unified-communications product: The MC Solution.

Integrate PBX Reduce Communication Costs Unify Communications Leverage Wi-Fi Infrastructure

©Comdasys 2011 All rights reserved

4

Mobile Phone Integration
Deskphone: 354 PBX

PSTN Trunk

Mobile users 355 356 357 358 … WIFI AP

Deskphone: 353

MC Client: 357

MC Client: 355 MC Controller Mobile Network Internet

MC Client: 358

Home/ Hotspot
MC Client: 356

©Comdasys 2011 All rights reserved

5

Mobile Phone Integration

• Controller integrates like a “normal” SIP desk phone • PBX side requires only the configuration of normal SIP UA and an optional SIP-trunk for routing inbound/outbound cellular calls • • • • • • Mobile Phone becomes part of the PBX – full featured PBX extension Mobile Phone rings whenever office extension is dialed Mobile Phone can dial extensions of the PBX Features of PBX can be used by the mobile No mobility support required by PBX PBX agnostic solution

©Comdasys 2011 All rights reserved

6

Mobile Phone Integration for legacy SIP PBX
• New method since controller version 10684.14 • Controller is connected via SIP-trunk only • No user agent support for PBX required

©Comdasys 2011 All rights reserved

7

Client Support
Nokia S60 3rd & 5th & ^3

Blackberry

iPhone

Android

©Comdasys 2011 All rights reserved

8

Controller Options
MC Controller 1800 2800 3800 5000 Up to 7 or 15 Users Up to 50 Users Up to 250 Users 250 to 2000 Users Installation on high-end servers such as Blade Servers allows much higher scaling
9

Enterprise

©Comdasys 2011 All rights reserved

Benefits / Features

©Comdasys 2011 All rights reserved

10

Mobile Phone Integration – enhanced More than “mobile twinning” + web-client
• • • • Client integrates into mobile phone Client UI offers telephony and UC features VoIP calling capabilities via WIFI and 3G networks Faster call setup in mobile networks using signalization via data channel for the cellular call • Flexible call models (WIFI, Call through, Callback) with automatic preselection of most appropriate call type • Cost saving potentials through Mobile LCR

©Comdasys 2011 All rights reserved

11

Benefits

• Centralized routing / billing in the PBX • Single number reach: one office number (instead of office/mobile/private number) • • • • Desk phone can be replaced by mobile PBX voicemail can be used (single voicemail) + MWI on client Leverage WIFI networks and save mobile costs Use PBX for national / international calls at lower cost

©Comdasys 2011 All rights reserved

12

Cost –Saving-Potential Examples of Cost-Optimization Options
Feature
Call-Through Call-Back Call-Back combined with Travel SIM Making use of WiFi hotspots TOTAL

Use Case
GSM to landline calls inside home country calls to foreign countries Calls made from foreign countries to the home country Using a local SIM card when making calls in foreign countries to the home country, or other destinations

Savings in %
90% on a call 50% on a call 70% on a call

Using a local SIM card when making calls in foreign countries to the home country, or other destinations

25% (on overall bill, on top of the above)

Up to 80% savings on overall bill

©Comdasys 2011 All rights reserved

13

Features

• Extension dialing • PBX features (transfer, conference, forwarding, hunt-groups, pickup …) can be used on mobile • Keyset phone (secretary) can monitor the call-status of the mobile • Features can also used with packet data channel (or pure cellular mode) • Seamless handover between WIFI and GSM • TLS/SRTP for securing WIFI / Vo3G calls • Easy deployment / configuration using integrated deployment tool

©Comdasys 2011 All rights reserved

14

Call Scenarios

©Comdasys 2011 All rights reserved

15

SIP IP Telephony SIP Registration of Mobile users

Ext2 Ext1 PBX

PSTN GW Mobile Network Mobile Phone A

REGISTER Ext3 Ext4 Ext5 …

AP MC Client Ext3

MC Controller

©Comdasys 2011 All rights reserved

16

WLAN Call

4 Ext2 Ext1 PBX 3 1

PSTN GW

Ext3 Ext4 Ext5 …

AP MC Client Ext3

MC Controller

2

©Comdasys 2011 All rights reserved

17

WLAN Call from remote office/internet
4 Ext2 Ext1 PBX 3 Ext3 Ext4 Ext5 … AP MC Client Ext3

PSTN GW

MC Controller 1 2 MC Client Ext4 AP

©Comdasys 2011 All rights reserved

18

Cellular Integration

PSTN Ext2 Ext1 PBX

PSTN GW Mobile Network MC Client Ext5

Ext3 Ext4 Ext5 … AP MC Client Ext3

MC Controller

©Comdasys 2011 All rights reserved

19

Call from Client (Cellular Mode) Call through
1 4 Ext2 Ext1 PBX 2 Mobile Network MC Client Ext5 Ext3 Ext4 Ext5 … AP MC Client Ext3 3

PSTN GW

MC Controller

©Comdasys 2011 All rights reserved

20

Call from Client (Cellular Mode) Call through - benefits

• Call routed though PBX network • Cost savings for local -> international calls • Cost savings for internal calls

©Comdasys 2011 All rights reserved

21

Call to Client (Cellular Mode) (Static Roaming)
4 1 Ext2 Ext1 3 PBX

PSTN GW Mobile Network MC Client Ext5

Ext3 Ext4 Ext5 …

2

AP MC Client Ext3

MC Controller

©Comdasys 2011 All rights reserved

22

Handover
Handover Call

7

4 Ext2 Ext1 PBX 6 3

PSTN GW Mobile Network

Ext3 Ext4 Ext5 … AP MC Client Ext3 5 Handover Request 1 MC Controller

MC Client Ext4 AP
©Comdasys 2011 All rights reserved

2

23

Handover Android
IMS Handover Call

4 5 Ext2 Ext1 PBX 6 Mobile Network Ext3 Ext4 Ext5 … MC Client Ext3 AP 3

PSTN GW

MC Controller 1 MC Client Ext4 AP
©Comdasys 2011 All rights reserved

2

24

Packet Data Channel
1 4 Ext2 Ext1 PBX 2 Mobile Network MC Client Ext5 Ext3 Ext4 Ext5 … AP 5 Data Channel MC Controller MC Client Ext3 3

PSTN GW

©Comdasys 2011 All rights reserved

25

VOIP Call via 3G data channel

Ext2 Ext1 PBX

PSTN GW Mobile Network MC Client Ext5

Ext3 Ext4 Ext5 … AP MC Client Ext3

MC Controller

©Comdasys 2011 All rights reserved

26

HTTPS Callback

3

5 Ext2 Ext1 2 PBX 4

PSTN GW Mobile Network MC Client Ext5

Ext3 Ext4 Ext5 … AP MC Client Ext3

1 Callback request MC Controller

©Comdasys 2011 All rights reserved

27

Cellular Callback
1 7 5 Ext2 Ext1 4 PBX 2 Mobile Network MC Client Ext5 Ext3 Ext4 Ext5 … 3 AP MC Client Ext3 6

PSTN GW

MC Controller

©Comdasys 2011 All rights reserved

28

Callback benefits

• Call routed though PBX network • Cost savings for calls when roaming

©Comdasys 2011 All rights reserved

29

SIM - Switch
1

Ext2 Ext1 PBX 2 Mobile Network MC Client Ext5 Ext3 Ext4 Ext5 … 3 AP MC Client Ext3

PSTN GW

Home Network MC Controller Roaming Network 4

roaming network SIM card activated

©Comdasys 2011 All rights reserved

30

Call reverse

1 4 Ext2 6 5 7 Mobile Network MC Client Ext5 Ext3 Ext4 Ext5 … 2 Ext1 3 PBX

PSTN GW

AP MC Client Ext3

MC Controller

©Comdasys 2011 All rights reserved

31

Network Configuration

©Comdasys 2011 All rights reserved

32

Network Configuration Basics
• Controller is equipped with at least one LAN interface and one WAN interface • Other Interfaces LANB / DMZ remain for special use and should not be used unless there is a special reason • LAN interface should connect to PBX network (trusted network) • WAN interface allows only access from clients through integrated SBC port 5062

©Comdasys 2011 All rights reserved

33

Network Configuration Public IP via WAN interface
MC Controller

• Public IP configured on WAN Interface e.g. 82.11.22.33 • Integrated Firewall allows only access to FMC SBC and Client interface • recommended setup • Optional: configure a hostroute on your internal LAN router to optimize traffic flow
Linux router example: ip route add 82.11.22.33/32 via 10.1.1.10
©Comdasys 2011 All rights reserved

LAN-IP: 10.1.1.10 PBX

LAN

WAN WAN-IP: 82.11.22.33

L

Switch

34

Network Configuration NAT Scenario - Port forwarding
MC Controller

• Only LAN interface used • Public IP configured on WAN router forward traffic to LAN IP • Public IP must be static / no DHCP • External IP for NAT (82.11.22.33) must be configured in SIP settings of MC Controller

LAN-IP: 10.1.1.10 PBX

LAN External IP for NAT: 82.11.22.33

L

Switch

Router LAN IP: 10.1.1.1

NAT Router for Public IP 82.11.22.33 Forwards client ports TCP: 5061/5062/448 UDP: 5062/35000-65000 to 10.1.1.10

©Comdasys 2011 All rights reserved

35

Network Configuration NAT Scenario - Port forwarding

• External IP for NAT (82.11.22.33) must be configured in SIP settings of MC Controller • Leave address empty if you use the first (WAN) scenario

©Comdasys 2011 All rights reserved

36

Network Configuration DMZ Configuration
MC Controller

• DMZ Firewall allows only traffic between PBX, Controller and Phones • If PBX makes no media termination, make sure that RTP media is allowed between the Controller and all phones / Media GWs in the network • Caution: Well understanding of VOIP network required for DMZ setup – port ranges will be different on each PBX
©Comdasys 2011 All rights reserved

LAN-IP: 10.1.1.10 PBX

L

DMZ Firewall

LAN

WAN

DMZ
WAN-IP: 82.11.22.33

Ports used between MC Controller & PBX: UDP: 5060 / 11000 -11999 SIP Trunks UDP: 12000 - 12999 SIP Registration UDP: 16384 - 32786 RTP Media Outgoing connections controller: UDP: 53 for DNS TCP: 5222 for XMPP IM/Presence TCP: 389 LDAP for Corp. Directory TCP: 80 for redirect deployment (internet) TCP: 2195 for Apple Push notification (internet) Incoming connections: TCP: 22/443 SSH and WEBGUI

37

Network Configuration Client Side

• The Client is configured to connect to the WAN address • The Client must connect the SBC port 5062 for: • Connecting from Public internet (NAT traversal) • TCP/TLS support • DNS domain names can be used to connect to the controller

©Comdasys 2011 All rights reserved

38

Network Configuration Using domain names with the client
• DNS can be configured that the client resolves the controller LAN-A IP inside the LAN/WIFI, while in the public network the WAN IP address is resolved. E.g.: • Internal DNS server has fmc.example.com -> 10.10.25.124 (LAN) • Public DNS server has fmc.example.com -> 82.11.22.33 (WAN) • Caution: Use low TTL for the DNS records since phones usually cache the DNS records and could use old records after transition from packet data network <-> WIFI

©Comdasys 2011 All rights reserved

39

Network Configuration Using domain names with the client
• Setup the DNS used by the client as “FMC User Domain” on the controller

©Comdasys 2011 All rights reserved

40

Integration Approach – review

©Comdasys 2011 All rights reserved

41

Integration Approach Requirements
• SIP PBX / registrar / Soft-Switch • One subscriber account (SIP-UserAgent) per MC user on PBX • At least one public DID number for mobile-integration “Special FMC numbers” (used for calls from handset in cellular mode -> Controller) • Required for most PBX: trunk interface between PBX (for placing calls from controller -> handset in cellular mode) • One public IP address for supporting public WIFI / packet data channel

©Comdasys 2011 All rights reserved

42

Integration Approach Requirements Example
• Example: 30 new mobile subscribers should connected to you PBX • 30 user accounts (SIP-UserAgent) configured on your PBX • 3 Public DID numbers on you PBX or GW routed via trunk to the controller (special FMC Number for call through/celluar handover/callback) • Trunk for placing outbound calls to the subscriber mobile • public IP address for supporting public WIFI / packet data channel • Controller MC2800 (Up to 50 users) , 30 MC Client licenses

©Comdasys 2011 All rights reserved

43

Basic Setup

©Comdasys 2011 All rights reserved

44

Basic Setup Configuration Methods

• GUI (Web browser) • Used for graphical configuration • CLI (serial / SSH) • Used for initial setup ( e.g. setup IP Addresses and routing) • Used for network troubleshooting • Strongly customized configurations additionally possible via CLI (experts only)

©Comdasys 2011 All rights reserved

45

Basic Setup Default Configuration
• Default IP: 10.0.0.205 / 24 • HTTPS WebGUI port 443 • Username: admin / Password: sesam • https://10.0.0.205 • CLI login (serial or ssh) • Username: root / Password: sesam

©Comdasys 2011 All rights reserved

46

Basic Setup Serial CLI
• For basic system configuration connect to the serial console with a RS232 serial NULL-modem cable. • Use a Terminal program like MS Hyper Terminal, PuTTY for Windows or minicom (Linux). Use the following settings: • 9600 8N1 • Baud rate: 9600 • 8 data bits • No parity bits • 1 stop bit

©Comdasys 2011 All rights reserved

47

Basic Setup CLI Menu

• Configure Network interfaces and routing • Apply configuration to activate/restart networking and services • Run shell for network troubleshooting, e.g. ping

©Comdasys 2011 All rights reserved

48

Basic Setup WebGUI

• Connect to WebGUI using https://10.0.0.205 while using default address

Model Type System Version

©Comdasys 2011 All rights reserved

49

Basic Setup WebGUI

• Configuration divided into sections • Most system and network configurations require to press “Apply Configuration” to restart the networking and system services • After system changes the “Apply Configuration” will be highlighted: • Telephony settings (new user etc.) don’t require this, hence the “Apply Configuration” will not be highlighted
©Comdasys 2011 All rights reserved

50

Basic Setup WebGUI status

Use “Home” to enter the status page. Check service status and restart individual services Service Status Green: OK Gray: not configured Red: not running / configuration problem

©Comdasys 2011 All rights reserved

51

Basic Setup Network - LAN

• Configure LAN address • press save

©Comdasys 2011 All rights reserved

52

Basic Setup Network - Routing

• Configure routing • Setup a default route 0.0.0.0 if no WAN interface is used

©Comdasys 2011 All rights reserved

53

Basic Setup Network - WAN

• Configure WAN IP address here if WAN interface is used • The “Gateway” must be configured here as default internet gateway • Make sure that you have not configured 0.0.0.0 in the routing configuration when configuring the gateway here
©Comdasys 2011 All rights reserved

54

Basic Setup Network - Virtual Interfaces

• Configure a virtual interface for having a second LAN address • Required for some PBX trunks (Avaya IPO, Cisco CM) which do not allow to have a trunk interface & subscriber registrations from one IP address • use virtual IP for registrations and interface IP for trunk configuration

©Comdasys 2011 All rights reserved

55

Telephony Setup – Step 1 PBX Integration

©Comdasys 2011 All rights reserved

56

Telephony Setup Overview – Setup Guideline – Step 1
• SIP user accounts are already configured on your PBX • One account was tested before with another SIP phone, e.g. you can receive incoming / make outgoing calls and the CallerID is set and displayed correctly on both ends • Configure Telephony Settings on server, configure one user • Setup & verify WIFI on mobile (e.g. use integrated web browser) • Install client, setup client and verify basic WLAN call • Test consultation to verify that your PBX allows two simultaneous calls per user

©Comdasys 2011 All rights reserved

57

Telephony Setup Registration / User Account / Cellular Number
Two independent accounts are configured for each user: 1. the registration towards the PBX (defined on PBX and configured on controller) 2. the user account between controller and MC Client (defined on Controller and configured in Client)
©Comdasys 2011 All rights reserved

PBX number/extension: 4000 PBX Username: 4000 PBX Password: (none)

SIM Card with +491791234567 Register 4000 (always) MC Client Username: 14000 Pw: foo

MC Controller Configuration PBX Number: 4000, PW: (none) SIP number: 14000, PW: foo Cell Nr: +491791234567 Register 14000 (if WIFI or Packet data network available)

58

Telephony Setup Global Settings

• Go with the standard options as indicated here – for details check tooltips or Admin Manual • Don’t enable Inband DTMF detection unless there is a reason for it

©Comdasys 2011 All rights reserved

59

Telephony Setup Global Settings (cont.)

• Activate APN if you want to use Apple Push Notification on iPhone (requires that a DNS server is configured and that internet access from the controller is allowed) • Change “Number of GSM-digits to match” if you country uses less then 10 digit numbers in the cellular network • Disable Identity Headers if your PBX does not understand certain headers

©Comdasys 2011 All rights reserved

60

Telephony Setup Global Settings (2)

• Configure “External IP for NAT” only if you are using the NAT scenario with port forwarding • Setting is only used by the SBC (port 5062)

©Comdasys 2011 All rights reserved

61

Telephony Setup Port Settings

• It is not recommended to change the default port unless you need this for a special use case • NAT Port forward scenario: Define a SBC RTP Start/End Port if you plan only forward a range of ports • leave everything else blank to go with the defaults

©Comdasys 2011 All rights reserved

62

Telephony Setup Numbering Profiles

• The Numbering Profiles convert numbers from the mobile world e.g. +49… to a format which your PBX will understand an adds the necessary prefixes to dial a number • Setup a numbering profile (required) which matches to your PBX location and dialing rules • leave unused fields empty (e.g. Outgoing Prefix or Area Code

©Comdasys 2011 All rights reserved

63

Telephony Setup Example dial patterns
User Enters +4989548433350 +493123456789 089548433350 03123456789 +39123456789 Controller Dials 0548433350 003123456789 0548433350 003123456789 00039123456789

©Comdasys 2011 All rights reserved

64

Telephony Setup Numbering Profiles (2)

• Same example for UK / other countries • Area code not configured • Area prefix set to 0

©Comdasys 2011 All rights reserved

65

Telephony Setup Numbering Profiles (3)

• Same example for Italy • Area Code and Area Prefix left empty if country does not use Area prefix

©Comdasys 2011 All rights reserved

66

Telephony Setup Numbering Profiles (4)
• Same example for North America

©Comdasys 2011 All rights reserved

67

Telephony Setup Endpoints

• Configure a Endpoint – the IP address of you PBX • The endpoint will be used to configure a PBX (next slide) • You might have multiple Endpoints and use them for multiple PBX / or trunks in different configurations • Setup Outbound Proxy if you want to enforce that all SIP requests are sent to that IP or if your sip domain is a name that cannot resolved by DNS

©Comdasys 2011 All rights reserved

68

Telephony Setup PBX

• Setup your PBX by selecting the endpoint you created before • Assign SIP Trunk here • Country setting is used for playing the right ringing and busy tone only • Setup the DTMF mode which the controller will use in order to speak with the PBX • Leave local port empty

©Comdasys 2011 All rights reserved

69

Telephony Setup PBX

Select the call forwarding type: • Standard: use client based forwarding using 302 response • CSTA: Set server based call forwarding on PBX using CSTA standard (only on few PBX) • Trunk: if your PBX does not support CFW at all it will be emulated by the MC controller. A trunk is required for this setup

©Comdasys 2011 All rights reserved

70

Telephony Setup (PBX) Registrations

• Configure your registrations towards the PBX here. • PBX Username is the name used for the Authorization-Username • PBX number is the number used for registration, to make and receive calls • Most setup use the same number for PBX Username and PBX Number

©Comdasys 2011 All rights reserved

71

Telephony Setup (MC) User Accounts

• The SIP Number must be different from Registration (internal limitation) • You can use any number/name you want • A password must be assigned • Don’t forget to activate the user

©Comdasys 2011 All rights reserved

72

Telephony Setup User Account Settings

• Static roaming is allowed by default,
you can disable it if you don’t want to have incoming calls in cellular mode • Enable “Call Waiting” if you want to receive more than one call at the same time on the mobile • Activate MWI to see the mailbox status of your PBX • Only enable Call Reverse if you want to use that scenario • Enable security to enforce SRTP • Boost WLAN volume (-2 to 2)

©Comdasys 2011 All rights reserved

73

Telephony Setup Check registration status

• Registration status must be REGED • check username / passwort / PBX configuration if the status is FAILED

©Comdasys 2011 All rights reserved

74

Telephony Setup – Step 2 Cellular Integration

©Comdasys 2011 All rights reserved

75

Telephony Setup – Cellular Integration Overview – Setup Guideline – Step 2
• Setup cellular integration: Setup GSM Nr + Special FMC Nr. • Verify outgoing cellular call (call through) • Verify incoming cellular call (static roaming) • Check if number representation is OK

©Comdasys 2011 All rights reserved

76

Telephony Setup – Cellular Integration Setup GSM numbers

• Recommended way: configure the cellular number in international format with leading + • The “Use Numbering Profile” option will convert the number into the right format before calling the mobile • Cellular number is verified for Call through, Call-back, the last 10 digit must match
©Comdasys 2011 All rights reserved

77

Telephony Setup – Cellular Integration Setup GSM numbers

• Other way: Disable the “Use Numbering Profiles” and configure the mobile number with outgoing prefix

©Comdasys 2011 All rights reserved

78

Telephony Setup – Cellular Integration Assign GSM numbers
• Assign GSM Number in the User Accounts Configuration • Each user can have multiple GSM numbers but only one activated • Use GUI or SIM-Switch to change numbers

©Comdasys 2011 All rights reserved

79

Telephony Setup – Cellular Integration Special FMC numbers
• One special FMC number is used by all users to access a specific service • Each special FMC number is used for a different service (CallThrough, Callback, SIM-Switch, IMS-Handover …) • Numbers must be reachable from PSTN (external DID) • Configure the number in your client in full E.164 format e.g. +49895484333920 • Configure the number on the controller as it is send by your PBX e.g. 5484333920 or 920

©Comdasys 2011 All rights reserved

80

Telephony Setup – Cellular Integration Special FMC numbers
• By default active registration is disabled – number must be routed by PBX using a routing rule or trunk configuration • If Active Registration is enabled Controller will register the number using Number, Reg. Name and Password

©Comdasys 2011 All rights reserved

81

Telephony Setup – Cellular Integration Special FMC numbers – two different setups

• Active Registration = Disable (recommended setup) • Configuration of call-route / trunk on PBX necessary • Call through supports DTMF dialing + direct dialing • Active Registration (easy setup) • number acts like a normal subscriber • MC Controller sends a “SIP REGISTER” to PBX • Some PBX limit the number of calls for one registration account • Call through supports DTMF dialing only

©Comdasys 2011 All rights reserved

82

Telephony Setup – Cellular Integration Special FMC numbers – Call-through
• There are two ways how a client can dial a number: • DTMF dialing (default) • DTMF tones are used for dialing the number (or data channel) • Direct dialing (fast setup for extension calls) • Called number is appended to the Call-through number • Can work only if Call through Active Registration = Disable and PBX can route number ranges e.g. +49895484333920xxxxx • Not available for all PSTN providers / countries

©Comdasys 2011 All rights reserved

83

Telephony Setup – Cellular Integration Call-through: direct dialing
• Example: Call-trough number is configured as +49895484333920 • PBX routes all calls starting with +49895484333920 to the controller e.g. +49895484333920xxxxx 1. user dials 350 2. call-through number is called by client as +49895484333920350 3. controller strips of its own number and dials 350 4. controller answers the call only after 350 has answered

©Comdasys 2011 All rights reserved

84

Telephony Setup – Cellular Integration Call-through: direct dialing
• Enable direct dialing by setting the “max. GSM number length” parameter on client • The length of a called GSM number is restricted to 19-21 digits (depends on network provider) • use 19 as “max GSM number length” to be save • recommended to have a short CT number => client allowed to dial longer extensions

©Comdasys 2011 All rights reserved

85

Telephony Setup – Cellular Integration Call-through - test call
• Simply call the Call through number from one of your mobiles (without client) • You will hear some short DTMF sounds if “Client Early media” is enabled • Dial extension via keypad • Call will be established after 1,5 seconds not dialing another digit • If the Call-Through is rejected then it is very likely that your GSM number was configured wrong - do a packet trace and check if the incoming cellular call indicates the correct cellular number in the FromHeader
©Comdasys 2011 All rights reserved

86

Telephony Setup – Step 3 SIP Trunk for cellular mode

©Comdasys 2011 All rights reserved

87

Telephony Setup – SIP Trunk for cellular mode Basics
• By default all calls are send out through the users extension • The SIP trunk helps to separate calls that are established to the mobile side in cellular mode • Required for scenarios where PBX does support only two simultaneous calls per subscriber • Using the SIP-Trunk will change the number representation for incoming calls in cellular mode

©Comdasys 2011 All rights reserved

88

Telephony Setup Static Roaming without trunk - 354 calls 350 (MC)
• Incoming calls to the handset in cellular mode are established as outgoing call using the subscriber account • Two channels of the subscriber in use (incoming / outgoing) • Doing a feature (e.g. consultation would require third voice channel on PBX
©Comdasys 2011 All rights reserved

354

2. Outgoing Call From: 350 To: 000491791234567

1. Incoming Call From: 354 To: 350

Displays: 350

MC Client with PBX extension 350 SIM Card with +491791234567

89

Telephony Setup Static Roaming with trunk – 354 calls 350 (MC)
• Incoming calls to the handset in cellular mode are established as outgoing call using the SIP-Trunk • Only one subscriber channel in use (incoming) • SIP trunk can point to the PBX or to other SIP GW
©Comdasys 2011 All rights reserved

354

2. Outgoing Call From: 354 To: 000491791234567 using sip-trunk

1. Incoming Call From: 354 To: 350

Displays: 354

MC Client with PBX extension 350 SIM Card with +491791234567

90

Telephony Setup SIP Trunk configuration

• Setup trunk, use basic configuration as indicated here • Select an existing endpoint or use any other endpoint • Use Active Registration to register the trunk if required • Go to PBX Settings and select the new created trunk there
©Comdasys 2011 All rights reserved

91

Telephony Setup SIP Trunk configuration

• Some PBX (Cisco CM, Avaya IPO) do not allow subscribers and trunking from one peer / ip address (refuse registration) • for this special case, setup a second (virtual) LAN address LAN1:1 and use this local interface with the second address for the PBX registrations • The trunk should always use the first (physical) interface IP, use this IP in your PBX configuration

©Comdasys 2011 All rights reserved

92

Telephony Setup SIP UA & SIP Trunk for PSTN interconnect Trunk example
PSTN GW 10.10.1.240 SIP Trunk for Call-through & Static Roaming (cellular calls)

PBX 10.10.1.250:5060

Deskphone: 5002

SIP UA registration 4699 4758 …

LAN1: 10.10.25.124 (physical address for trunk)

LAN1:1: 10.10.25.125 (virtual address for SIP UA)

PBX config: Trunk setup for SIP-trunk (udp) to sip:10.10.25.124:5060
©Comdasys 2011 All rights reserved

WAN: 82.11.22.33 (for connecting clients from the internet)

MC Client Extension: 14699

93

Telephony Setup SIP UA & SIP Trunk for PSTN interconnect Trunk example
PSTN GW 10.10.1.240

PBX 10.10.1.250:5060

Deskphone: 5002

SIP Trunk for Call-through & Static Roaming (Cellular calls)

SIP UA registration 4699 4758 …

LAN1 10.10.25.124 (address for SIP UA)

PSTN GW config: Trunk setup for SIP-trunk (udp) to sip:10.10.25.124 :5060
©Comdasys 2011 All rights reserved

WAN: 82.11.22.33 (for connecting clients from the internet)

MC Client Extension: 14699

94

Telephony Setup – review

©Comdasys 2011 All rights reserved

95

Telephony Setup Assignment of configuration groups

Endpoint PBX Numbering Profile PBX

Endpoint SIP Trunk

Registration Registration

Registration …

User
©Comdasys 2011 All rights reserved

User
96

Telephony Setup – legacy SIP PBX setup

©Comdasys 2011 All rights reserved

97

Telephony Setup legacy SIP PBX
SIP Trunk for Call-through & Static Roaming (cellular calls) & User extensions

PBX 10.10.1.250:5060

Deskphone: 5002

LAN1: 10.10.25.124:5070 (physical address for trunk)

PBX config: Trunk setup for SIP-trunk (udp) to sip:10.10.25.124:5070
©Comdasys 2011 All rights reserved

WAN: 82.11.22.33 (for connecting clients from the internet)

MC Client Extension: 14699

98

Telephony Setup legacy SIP PBX

• Use the Mode “Trunking” to Connect PBX which don’t have support for SIP user accounts / SIP phones • Set local port to 5070 and configure your PBX to send all calls to the LANA address SIP port :5070 • Use UDP only for the trunk connection • Setting up a trunk for cellular use and select this for correct numbering in cellular mode

©Comdasys 2011 All rights reserved

99

Telephony Setup legacy SIP PBX - summary
• Trunking mode offers easy integration for PBX which don’t support SIP phones • If PBX supports SIP phones, it is recommended to the “SIP Registration mode” • Features might be limited on some PBX trunks (no MWI, call-transfer, hunting-groups etc.) • Handover, Consultation and Conference are fully handled by the Controller and require only basic call support from PBX • Set call forwarding type “Trunk” if standard is not supported on your trunk

©Comdasys 2011 All rights reserved

100

Licensing

©Comdasys 2011 All rights reserved

101

Licensing Overview
• Controller licenses • Used for Enterprise Installations (VMWare) or 5000 series • Other Hardware (1800,2800,3800) do not need a server license • Client licenses • Installed on Controller – activated after 30 days trail

• License portal http://licenses.comdasys.com • Used to create Client and Server license keys • One account for each customer / order
©Comdasys 2011 All rights reserved

102

Licensing License Keys
• Example Shows controller with 10 installed controller licenses and zero client licenses

• Copy MAC address from controller • Use license portal to generate the license keys

©Comdasys 2011 All rights reserved

103

Licensing License Portal – Create client license (1)

• Go to Client Licenses -> New Client License • Paste controller MAC address • Select number of (new) users • Create license

©Comdasys 2011 All rights reserved

104

Licensing License Portal – Create client license (2)

• Look for “MAC based” client licenses • Copy Key and paste it into the Controller

©Comdasys 2011 All rights reserved

105

Licensing License Portal – Create client license (3)

• Paste license key into the controller • Save

©Comdasys 2011 All rights reserved

106

MC Client - Licensing Platform differences
• Server based (MAC) client licenses (iPhone, Nokia 3.0, Blackberry 3.0, Android 2.0): • License contingent (e.g. 30 users) is generated via licenses portal for one specific controller • Client obtains license automatically from controller after 30 days • Old: Client (IMEI based) licenses (Nokia,Blackberry,Android): • License key must be generated and entered for each phone individually • Useful if phone is used for different controllers (test-phone)

©Comdasys 2011 All rights reserved

107

MC Client Old: Client based Licensing
• By default Nokia, Blackberry and Android have a grace period of 30 days • Until then they must be activated using a license based on the phone IMEI • Licenses are obtained from the Comdasys license portal

©Comdasys 2011 All rights reserved

108

Device Portal

©Comdasys 2011 All rights reserved

109

Device Portal Basics

• Access Comdasys device portal: http://devices.comdasys.com • Get latest information about supported handsets or learn about known limitations of phone models • Check scenario ratings if device matches to your use case

©Comdasys 2011 All rights reserved

110

Device Portal

©Comdasys 2011 All rights reserved

111

MC Client - Overview

©Comdasys 2011 All rights reserved

112

MC Client Installation Possibilities
• Recommended way: Apple Appstore / Android Market / Ovi Store / Blackberry Appworld • Search for “imc client” / “mc client” • Manual Install Install Client directly via phone browser from: http://ftp.comdasys.com/pub/updates/MCClient • Installation via Desktop Software (Nokia PC-Suite / Nokia Ovi-Suite / Blackberry Desktop Manager)
©Comdasys 2011 All rights reserved

113

MC Client Manual Installation via Web browser

• Copy link and from client and send it to mobile via email or SMS

©Comdasys 2011 All rights reserved

114

MC Client Direct installation via web-browser

1. Copy link from Webserver and send it to mobile via email or SMS 2. Open link on Mobile to launch installation
©Comdasys 2011 All rights reserved

115

MC Client Configuration
• Manual Configuration • Enter Settings for registrar, username, password • Configure at least the call through number • Useful for quick testing and first user setup • OTA / Redirect Configuration • Configure deployment group with common settings, add users to this group, push redirect information to the redirect server • Start client and enter mobile number to download configuration

©Comdasys 2011 All rights reserved

116

MC Client Redirect (1)
PUSH Config URL, Mobile +491791234567 https://82.11.22.33:448/... Controller Public IP 82.11.22.33 MC Controller

Redirect Server provisioning.comdasys.com
Mobile +4917788998811 Config-URL https://82.11.22.33:448/cc.cgi?u=14008&....

+491791234567 Comdasyshttps://82.11.22.33:448/cc.cgi?u=14000&.... Redirect server does … … redirect services for configuration download

• Push Configuration URL for each mobile user using controller deployment (see screenshot)
MC Client

©Comdasys 2011 All rights reserved

117

MC Client Redirect (2)
Controller Public IP 82.11.22.33 Redirect Server provisioning.comdasys.com
Mobile +4917788998811 +491791234567
…

MC Controller

Config-URL https://82.11.22.33:448/cc.cgi?u=14008&.... https://82.11.22.33:448/cc.cgi?u=14000&....
…

• Redirect database contains mobile number and configuration URL of the PBX user after pushed by the Admin • User downloads configuration after first client startup by entering the mobile phone number into the client
118

MC Client

©Comdasys 2011 All rights reserved

MC Client Redirect (3)
1 Controller Public IP 82.11.22.33 MC Controller

2

• Client contacts Redirect Server and sends it mobile number, entered by Mobile Config-URL +4917788998811 https://82.11.22.33:448/cc.cgi?u=14008&.... the user (1) +491791234567 https://82.11.22.33:448/cc.cgi?u=14000&.... • Redirect server returns configuration … … URL of controller and removes redirect entry from database GET Config URL for Mobile 491791234567 • Client downloads configuration from Controller directly (2)
MC Client GET Config: https://82.11.22.33:448/cc.cgi?u=14000&.......

Redirect Server provisioning.comdasys.com

©Comdasys 2011 All rights reserved

119

MC Client Redirect notes
• After downloading the configuration via redirect server the redirect information is deleted on the redirect server – this ensures that configuration goes to only one phone • Subsequent configuration downloads from the client will always go directly to the controller (configuration URL stored in Client) • push the deployment information again via controller to repeat initial configuration (e.g. after factory reset of the client or the phone)

©Comdasys 2011 All rights reserved

120

MC Client Redirect - perquisites
• Controller needs an internet connection and a route to the internet • Controller needs a configured DNS server (e.g. 8.8.8.8) for resolving the provisioning server • Check DIAGNOSTICS->Deployment Status on controller after first redirect push • Client needs either Packet Data connection or WIFI with Internet access for contacting the redirect server • Client needs either Packet Data connection or WIFI with Internet for downloading the configuration via the Public IP from Controller • Configuration download via WIFI possible via LAN IP if no Public IP is available on controller
©Comdasys 2011 All rights reserved

121

MC Client Registration State
All MC Clients show a registration status • Green: • Blue/Cyan: • Yellow: • Red: • Gray: Successful registered for VOIP - calls routed via WIFI or 3G Successful registered “InfoMode” - calls routed via cellular connected to network / registration in progress registration failed / connection refused offline - no WIFI / packet data connection active / available

©Comdasys 2011 All rights reserved

122

MC Client – Nokia

©Comdasys 2011 All rights reserved

123

MC Client – Nokia Platform differences
• S60 3rd Edition (Initial release) • Old models E65,E61i ... use the MR Client • S60 3rd Edition (Feature pack 1/2) • Current models E71, E66, E51, E52 ... use 3rd Edition Client • S60 5th Edition (Touch Screen) • N97, 5800 XpressMusic, X6-00, C6-00 ... Use 5th Edition Client • Symbian^3 ... Use 5th Edition Client • C6-01 • Find out the right platform - check: http://www.forum.nokia.com/devices -> Device Matrix

©Comdasys 2011 All rights reserved

124

MC Client – Nokia Installation
• Installation via Ovi-Store, search for “mc client” • Manual OTA installation: Send link via SMS or Email -> Open link to download • Enter ftp.comdasys.com into mobile Webbrowser

©Comdasys 2011 All rights reserved

125

MC Client – Nokia Configuration via Redirect
• Enter mobile phone number to get configuration via redirect • Confirm security warnings – accept certificate • Initial configuration download will use the first available WIFI AP or the first packet data AP • Check packet data AP order if you experience problems • Go to Settings -> Factory Reset to repeat redirect download

©Comdasys 2011 All rights reserved

126

MC Client – Nokia AP Configuration 3rd ed.

• Enter AP Configuration by clicking on the AP bar • Move Up/Move Down to change WIFI priority • Blacklist WIFI hotspots you don’t want to use with the client • Change Packet Data AP to VoIP for voice over 3G • Make sure that the first packet data AP is the correct one (here “o2 Surf”) and that not a WAP AP which cannot be used by the client

©Comdasys 2011 All rights reserved

127

MC Client – Nokia Packet Data settings

• Off = no data channel usage • Minimal = GPRS allowed for: Callback, DnD on/off, configuration download and corporate contacts • Home Network = register only in your provider network • Always on = register “on demand“ even in roaming networks

©Comdasys 2011 All rights reserved

128

MC Client – Nokia Manual Configuration

• Systen settings are hidden to the end user • Goto Settings-> Admin Settings • Enter code #398 to open Admin settings

©Comdasys 2011 All rights reserved

129

MC Client – Nokia System VoIP Settings

• Go to Options -> Settings -> Options -> Download configuration • Check packet data AP order if you experience problems

©Comdasys 2011 All rights reserved

130

MC Client – Nokia FMC Settings
• Setup at least the Call-Through No. • Leave MTC No. empty

©Comdasys 2011 All rights reserved

131

MC Client – Nokia Application Settings
• Most application settings are quite special, consult manual in case you need them

©Comdasys 2011 All rights reserved

132

MC Client – Nokia Application Settings (2)
• Enable / Disable LCR here • Set Dial Mode to “Always MC Client” if calls should be routed always through the client • Enable Maintain 3G Connection if you want to use VoIP over 3G

©Comdasys 2011 All rights reserved

133

MC Client – Nokia Main-Screen & Out-call-Features

• Dial extension number / or access address book from client directly • Use Feature menu to execute features, change call forwarding or access voicemail

©Comdasys 2011 All rights reserved

134

MC Client – Nokia In-Call-Screen and Features

• In call go to the Features Menu • When having multiple calls use cursor to toggle between active call (green Phone icon = active call)

©Comdasys 2011 All rights reserved

135

MC Client – Blackberry Installation

©Comdasys 2011 All rights reserved

136

Blackberry Installation Basics
• Blackberry with VoIP over WLAN supported on newer models • Best VoIP performance with 5.0 firmware and newer • Recommended to upgrade to 5.0 firmware on older models (e.g. Bold 9000) • VoIP over 3G supported - bypassing the BES server

• Installation via Desktop Manager / OTA deployment or BES

©Comdasys 2011 All rights reserved

137

Blackberry Installation Appworld Install

• Use Blackberry AppWorld to install client • Updates will be provided automatically through Appworld • Alternative: use link from Comdasys FTP server

©Comdasys 2011 All rights reserved

138

Blackberry Installation Manual Install

• Find out the firmware version of your BB to select the right client: Use Blackberry and navigate to Options-> Device -> About

©Comdasys 2011 All rights reserved

139

Blackberry Installation Device Permissions
• Set all application permissions to Allow and save them • Be carefully since the Client can´t work if the permissions are denied by the Blackberry OS

©Comdasys 2011 All rights reserved

140

Blackberry Installation Installation & Reboot

• After Installation a reboot is required (remove battery) • Before the reboot the client will be uninitialized and want work

©Comdasys 2011 All rights reserved

141

Blackberry Installation Permissions
• When stating the client you might get asked for Application permissions. Allow them and check the “Do not ask again” • If you have issues answered this option wrong check the Application permission: Option -> Security options -> Application Permission -> MCClient 4.6.0 -> Edit Permission

©Comdasys 2011 All rights reserved

142

Blackberry Installation APN configuration

• For download configuration and for the packet data connection a proper packet data configuration is required • Even if the download and installation works you need this for the TCP services • Check that your APN is configured: Options -> Advanced Options -> TCP Version 6 : Options -> Device -> Advanced System Settings -> TCP IP
143

©Comdasys 2011 All rights reserved

Blackberry Installation Security Settings

• If you still cannot start the download try again and check the Handheld security configuration: Options -> Security Options -> TLS and change the “TLS Default” from Proxy to Handheld

©Comdasys 2011 All rights reserved

144

Blackberry Installation WIFI Configuration

• If you want to use access point roaming (Multiple AP connected together using the same SSID ) make sure that you allow the “inter-access point handover” (disabled by default)

©Comdasys 2011 All rights reserved

145

Blackberry Installation Download Configuration via Redirect Server

• After startup client asks for mobile phone number • Enter mobile phone number to download the configuration • Do a “Factory reset” if you want to do the redirect download again

©Comdasys 2011 All rights reserved

146

Blackberry Installation Download Configuration

• Old method of configuration download • Download configuration via OTA using username@domain & password

©Comdasys 2011 All rights reserved

147

MC Client – Blackberry Usage and Configuration

©Comdasys 2011 All rights reserved

148

Blackberry Main Screen / In Call-Screen

• Main screen: Dial a number right away or use menu to select call-type or execute features

• In Call: Features can be executed during a call by opening the menu using the Blackberry key

©Comdasys 2011 All rights reserved

149

Blackberry Basic settings – FMC Numbers
• Setup at least the Call-Through No. • Use E.164 format the special numbers

©Comdasys 2011 All rights reserved

150

Blackberry Basic settings – Dual Mode Settings
• Use Single Mode for cellular mode with data channel or Dual Mode for WIFI calling on supported handsets

©Comdasys 2011 All rights reserved

151

Blackberry Basic settings – VoIP Settings

• Setup registrar with port 5062 (SBC)

©Comdasys 2011 All rights reserved

152

Blackberry Basic settings – Network Settings
• Setup packet date channel usage • Local Network = use data channel only in home country

©Comdasys 2011 All rights reserved

153

Blackberry Basic settings – Call Preference
• Set to Always MC Client if all call should be routed through the client

©Comdasys 2011 All rights reserved

154

Blackberry Basic settings – Misc. Settings

• Enter Misc settings to enable Autostart, LCR or IM/Presence

©Comdasys 2011 All rights reserved

155

Blackberry Hidden settings

• To enter hidden settings press # 398 inside of the configuration dialog

©Comdasys 2011 All rights reserved

156

Blackberry Traces

• Enable logging and restart App • Send logfiles directly via email to your PC • Logging is automatically disabled after sending trace

©Comdasys 2011 All rights reserved

157

Blackberry Ringtone Settings

• By Default you must set the Ringtone for the WIFI mode. • Go to: Profile Settings -> Change Sounds and Alerts-> Sounds for the Selected Profile -> Other Applications -> MC Client Call • Use a short ringtone and set Count=1. Playback of ringtone stops only after Green or Red Button is pressed
©Comdasys 2011 All rights reserved

158

Blackberry Blackberry Enterprise Server (BES) Setup

• Optionally the Application Policies can be set by the BES • Installation of client also possible via BES • Configuration download via MC Controller

©Comdasys 2011 All rights reserved

159

Blackberry Firmware Upgrade
• In some cases it is necessary to upgrade the BB device to a recent firmware: • http://us.blackberry.com/support/downloads/download_sites.jsp • If you operator does not provide a recent firmware you can also use the FW from other vendors e.g. Rogers Canada: • Go to: c:\Programs\Common Files\Research In Motion\AppLoader • Delete vendor.xml • run loader.exe to do the firmware upgrade

©Comdasys 2011 All rights reserved

160

MC Client – iPhone

©Comdasys 2011 All rights reserved

161

iPhone Basics
• Support for iPhone 3G/3GS/4G and iPad (headset required) • Installation done via Appstore – search for “imc client” • updates via Appstore • OTA configuration download supported • Server based client licenses must be installed on MC Controller • Registration will be refused if no license installed on Controller

©Comdasys 2011 All rights reserved

162

iPhone Basics
• Enterprise calls are dialed via iMC Client App • multitasking support for iOS 4.1 - receiving calls when client is running in background • APN – Apple push notification – puts client into foreground for incoming cellular calls • APN must be enabled on MC Controller – internet connection and DNS server required on controller

©Comdasys 2011 All rights reserved

163

iPhone Basics
• • • • Automatic Handover cellular-> WIFI Handover WIFI -> cellular manually triggered VOIP over 3G supported Note: For cellular use a 3G connection must be preset to execute features in cellular mode

©Comdasys 2011 All rights reserved

164

iPhone Configuration download via Redirect

• After first startup client asks to enter the cellular number for configuration download • After configuration download application must be restarted

©Comdasys 2011 All rights reserved

165

iPhone Application restart

• With Multitasking the application needs to be restarted to activate the new settings 1. Go to home screen, click button once 2. Click button twice (double-click) to open the taskbar 3. Long press the application icon (hold down for two seconds) 4. –> small red symbols will appear: Click on the red symbol to close the application

©Comdasys 2011 All rights reserved

166

iPhone Manual Configuration

• Go to Settings and enter the iMC Client settings • Setup Server Address / Port, Account Name and Password, call through number • restart Application to activate changes

©Comdasys 2011 All rights reserved

167

iPhone Configuration download

• Go to the About icon and enter the Status menu • Hit Update Settings to download configuration • restart application in order to activate new settings

©Comdasys 2011 All rights reserved

168

iPhone Dialer and Features
• Numbers can be dial directly via the dial pad or via the Contacts address book • Out of call features can be executed using the features menu

©Comdasys 2011 All rights reserved

169

iPhone Calltype selection

• Dial a number and long press (hold down) the green dial button to select the call type

©Comdasys 2011 All rights reserved

170

iPhone Incall screen and Features

• Press … to access other Features & Handover to Cellular

©Comdasys 2011 All rights reserved

171

MC Client – Android

©Comdasys 2011 All rights reserved

172

Android Basics
• Installation via Android Market - search for “mc client” • Or: manual installation of .apk file via http://ftp.comdasys.com • Status icon (top left) shows running MC Client • Configuration download via cellular number

©Comdasys 2011 All rights reserved

173

Android Client Dialpad v.s. Native Dialer

• Number can be dialed via Client or Native dialer if Call Preference is set to “Always MC Client”

©Comdasys 2011 All rights reserved

174

Android Manual configuration
• Start the MC Client and enter Menu / Settings • Settings mostly identical to other client platforms • Leaving the Settings screen activates changes

©Comdasys 2011 All rights reserved

175

Android Access Settings and Call type pre-selection

• Press menu button and select “Settings” to access the configuration • Setup “Call type pre-selection” to choose a default call-type outside WIFI

©Comdasys 2011 All rights reserved

176

Android Settings

• IMS number must be configured for WLAN to Cellular handover

©Comdasys 2011 All rights reserved

177

Android Settings

©Comdasys 2011 All rights reserved

178

Android Misc Settings

• In “Energy Saving” mode some devices might turn of WIFI in standby

©Comdasys 2011 All rights reserved

179

Android Logging

• SD Card required • File stored in /sdcard/MC Client/ • Send logfile via Email or access SD-Card

©Comdasys 2011 All rights reserved

180

Android In-Call / Outcall Features

• 3G connection required for features in cellular mode

©Comdasys 2011 All rights reserved

181

Client Deployment OTA Setup

©Comdasys 2011 All rights reserved

182

Client Deployment - OTA Basics

• Deployment is configured using “User Groups” • Each group can have different settings • Users are assigned to a group • Deployment options: • Configuration Deployment (via redirect server) • Configuration Deployment (using username & IP) • Client Binary Deployment (discontinued by App-stores)

©Comdasys 2011 All rights reserved

183

Client Deployment - OTA Basics

• Add a group and select common numbers / profiles for the group

©Comdasys 2011 All rights reserved

184

Client Deployment - OTA Special FMC numbers
• The External DID for Call through etc. are configured in the Special FMC numbers dialog • Each Group can select one of those numbers

©Comdasys 2011 All rights reserved

185

Client Deployment – OTA OTA Feature-File Edit

• Add a new OTA profile for changing the client default settings • Edit OTA-Profile and add Client Settings to it

©Comdasys 2011 All rights reserved

186

Client Deployment – OTA OTA Example
Dual-Mode: DUAL_MODE Dual-Mode-Network: GPRS_DYNAMIC Call-Preference: ENTERPRISE_ONLY Auto-Start: true Codec: ilbc

©Comdasys 2011 All rights reserved

187

Client Deployment - OTA LCR /OTA Feature-File Edit
• OTA-File: Common syntax for settings, supported by all client platforms • Unknown settings are ignored if platform does not support a special setting • Basic settings generated by the deployment, others can be added by the administrator • Check Client manual for supported OTA Keys

©Comdasys 2011 All rights reserved

188

Client Deployment - OTA LCR /OTA Feature-File Edit (old editor)

For doing copy&paste use old editor: https://controller-ip/vpnbox-cgi/cgi/lcr_file.cgi

©Comdasys 2011 All rights reserved

189

Client Deployment - OTA • Assign user to a group User Settings
• Setup email address (for informational purpose only) • Set “Force Config Download” to yes if client should refresh configuration on next startup (Nokia 3.2, BB 3.2, iPhone 3.3.5, Android 3.1 and later)

©Comdasys 2011 All rights reserved

190

Client Deployment - OTA Configuration Deployment
•Select user for Deployment and hit Send to deploy via “Redirect-Server”

©Comdasys 2011 All rights reserved

191

Mobile Least-Cost-Routing (MLCR)

©Comdasys 2011 All rights reserved

192

Mobile Least-Cost-Routing (MLCR) Basics
The Comdasys Mobile Convergence Solution helps you save costs by optimizing the call routing in the Cellular Network “Mobile Least-Cost-Routing” (MLCR)

©Comdasys 2011 All rights reserved

193

Mobile Least-Cost-Routing (MLCR) Basics
• LCR table on device will automate the call type selection according to the following criteria: • Destination Number Prefix • Roaming state (0= Home network; 1 = foreign Network) • MCC (Mobile Country Code of connected network) • First matching entry is used (from top to bottom) • According to these criteria you can set a call type (Call through, HTTPS Callback, Cellular Callback, Direct Call)

©Comdasys 2011 All rights reserved

194

Mobile Least-Cost-Routing (MLCR) MCC
• • • • • • MCC = Mobile Country Code Germany: 262 Italy: 222 UK: 234, 235 USA: 310 - 316 for reference use: http://en.wikipedia.org/wiki/List_of_mobile_country_codes

©Comdasys 2011 All rights reserved

195

Mobile Least-Cost-Routing (MLCR) LCR-Call Types
• Call Through (routes through PBX, usually best when in home Country -> reduces international costs) • HTTPS Callback (when in roaming or with Travel SIM card -> incoming calls cheaper than outgoing. Cellular data connection required) • Cellular Callback (Callback in cellular, no data, slower) • Direct Cell Phone Call (! shows SIM Number! -> used if special tariffs apply)

©Comdasys 2011 All rights reserved

196

Mobile Least-Cost-Routing (MLCR) LCR Table Configuration
• LCR table consists of multiple policy lines in the following format: N,R,CT,CB,DC,HCB,CC, • N= Target Number Pattern • R= Roaming; 0=false, 1=true (in foreign network) • CT= do Callthrough • CB= do Callback • DC= do DirectCellular • HCB= do HttpsCallback • CC= Country Code (rule matches only in CC network) • -> Select your call type with 1, the others must set to 0
©Comdasys 2011 All rights reserved

197

Mobile Least-Cost-Routing (MLCR) lcr.dat Example
Example: • Calls to 0800 (service numbers) from Germany (MCC:262) direct via SIM card • HTTPS callback when calling from UK (MCC:234,235) with a UK SIM card • Callback in all other countries (if Roaming mode on) • Call throug for all other calls (if Roaming mode off = from Germany)

+49800,0,0,0,1,0,262 0049800,0,0,0,1,0,262 0800,0,0,0,1,0,262 *,0,0,0,0,1,234 *,0,0,0,0,1,235 *,1,0,1,0,0,* *,0,1,0,0,0,*

©Comdasys 2011 All rights reserved

198

Mobile Least-Cost-Routing (MLCR) Deployment via Controller

©Comdasys 2011 All rights reserved

199

Advanced Server Topics

©Comdasys 2011 All rights reserved

200

Advanced Server Topics FMC Internal Features
• FMC uses some internal feature codes which should not be used by the PBX / Enduser • **xx range: e.g.: **41 hold, **42 resume, **00 initiate handover • *34x range: *341 used by discontinued client from 3rd party vendor • If you plan to send feature codes like **86 to your PBX, define them as ***86 on the client and re-map them on the controller to **86 again • Take care when defining feature codes on your PBX containing a # since this is defined a terminate dialing sequence in the telephony world and cannot be called from all phones from the cellular network (e.g. the iPhone)

©Comdasys 2011 All rights reserved

201

Advanced Server Topics Numbering Profiles
• Numbering Plan of PBX needs to be adapted to the Mobile world • End-users want to dial normal numbers (without special prefixes for outgoing line) • Adaptation is done by the number converter (Telephony->Numbering Profiles) • You can have two Profiles • From profile: for calls from the PBX (incoming) • To profile: for calls to the PBX (outgoing) • Two separate profiles can be used if the PBX does not set right number format for incoming calls

©Comdasys 2011 All rights reserved

202

Advanced Server Topics Numbering Profiles

©Comdasys 2011 All rights reserved

203

Advanced Server Topics Number Conversions
• The two converter profile (call from Client -> PBX) can be overritten using the “number conversions” • Feature can be used to reformat numbers if this can not be done by the PBX • If a number conversions rule matches, the Number converter will not executed • Use Perl compatible Regular Expressions to match and replace numbers - check http://perldoc.perl.org/perlre.html

©Comdasys 2011 All rights reserved

204

Advanced Server Topics Number Conversions

• ONLY used for outgoing calls • Specify priority for the order – only one pattern will be matched and replaced • do any digit manipulation you want here • take care that special characters like + and * need to be escaped with \ in the source pattern • Always begin source pattern with ^ to match begin of number

©Comdasys 2011 All rights reserved

205

Advanced Server Topics Number Conversions - examples

• Map feature code ***86 from the client to **86 to the PBX • Strip off your office prefix when dialing a number which belongs to internal extensions • Don’t do number conversions for *26*x features • Don´t do number conversion for *xx*x features • Don’t do number conversion for any features starting with * or #
206

©Comdasys 2011 All rights reserved

Advanced Server Topics PBX Access Code Mapping
• Maps access codes from the client to a different access code on the server. Easier than Number Conversions – less powerful • Useful to adapt : • Different client features to one PBX • Different PBX features to one Client feature

©Comdasys 2011 All rights reserved

207

Advanced Server Topics PBX Access Code Mapping

• Enable “Use Number Converter” if you want that remaining digits after the feature code should be passed through the converter

©Comdasys 2011 All rights reserved

208

Maintenance Update, Backup, Restore

©Comdasys 2011 All rights reserved

209

Update Options

• Full-Update: • upload of .update file via WebGUI • File size around 30 MB • Changes the system version • Reboot necessary • Hotfix installation: • Typically less 1 MB • Does not change the version number • File /etc/config/hotfixes however tells which hotfixes have been installed
©Comdasys 2011 All rights reserved

210

Update / hotfix installation

Updates are available via the support portal or on the Comdasys FTP: http://ftp.comdasys.com/pub/updates/FMC/

©Comdasys 2011 All rights reserved

211

Update / hotfix installation via CLI

• Upload hotfix/update using scp or WinSCP to the /tmp directory of the box • IMPORTANT: use BINARY Transfer with WinSCP • Install it using the installUpdate command (above) • reboot

©Comdasys 2011 All rights reserved

212

Backup
Download configuration via WebGUI to have a local backup Restore it using the same page

©Comdasys 2011 All rights reserved

213

Configuration Rollback

• Use configuration rollback to jump back to a previous configuration • Rollback data will be deleted after doing an update

©Comdasys 2011 All rights reserved

214

Remote Backup
• Remote backup will push the configuration to a backup server via ftp or scp upload • Setup Interval for Time/Day: Daily 1-24 Hour Weekly 1-7 (Monday-Sunday)

©Comdasys 2011 All rights reserved

215

Remote Backup – SSH keys

• SSH keys are used for authentication • Public key (id_dsa.pub) needs to be installed on the backup server: ~/.ssh/authorized_keys • The Private key (/etc/root/.ssh/id_dsa) is used by the MC Server to login to the backup server (scp)

©Comdasys 2011 All rights reserved

216

Remote Backup – SSH key generation

• Create keypair on the MC Server using • ssh-keygen -t dsa (don’t assign a password to the private key) • You will get the files id_dsa.pub and id_dsa (Private key) • Copy the public key “id_dsa.pub” to your backup server • scp /etc/root/.ssh/id_dsa.pub user@backupsrv:~ • Install the key on the backup server • ssh user@backupsrv • mkdir ~/.ssh • cat ~/id_dsa.pub >> ~/.ssh/authorized_keys

©Comdasys 2011 All rights reserved

217

Factory Reset
• Restore Basic Configuration & reboot -> reset Basic Configuration (but keep licenses)

• Restore Factory Defaults & reboot -> Full Factory Reset • Reset ‘Dualmode‘ database -> clear the database (apply config required)

©Comdasys 2011 All rights reserved

218

Factory Reset / Password reset
• WARNING: after a factory reset, ALL your data on the appliance will be removed! • Usage: After connecting a serial console you need to power up or reboot your box. Then wait until you see the following prompt:
SYSLINUX 1.62 0x3e713b13 Copyright (C) 1994-2001 H. Peter Anvin boot:

• Enter „passwordreset“ or „factoryreset“. • The default password is always „sesam“. The user name on the CLI is „root“, on the WebGUI „admin“

©Comdasys 2011 All rights reserved

219

UC – Presence and IM

©Comdasys 2011 All rights reserved

220

IM / Presence Instant Messages

• See presence status of other People before calling them • Send & receive IM messages from Client • Change presence state on mobile • Presence state goes automatically to busy when on a call

©Comdasys 2011 All rights reserved

221

IM / Presence Usage Example: Google Talk

• See presence status of the mobile client • Send IM message

©Comdasys 2011 All rights reserved

222

UC – Presence and IM Basics
• Presence and IM support using SIP Simple or XMPP • • • • Simple: XMPP: Presence & IM handled independent from PBX XMPP server (e.g. Openfire) does the Presence & IM handling PC / other devices can connect to XMPP sharing one identity

©Comdasys 2011 All rights reserved

223

UC – Presence and IM Setup of XMPP Endpoint
• Setup presence server • Enable TLS for “modern” XMMP servers (required)

©Comdasys 2011 All rights reserved

224

UC – Presence and IM Setup of XMPP Users
• Assign FMC user to an presence user • Always keep in mind the usernames are case sensitive

©Comdasys 2011 All rights reserved

225

UC – Presence and IM Basics

• Phone subscribes to all users in the address book with an email entry using the same domain name (not on iPhone) • Optionally it subscribes all users having an IM field configured in the contact • Client does not save any presence status or buddy lists

©Comdasys 2011 All rights reserved

226

XMPP with Google Server Configuration Example
• Connect to talk.google.com • Make sure to have DNS and a proper routing configured • Use only the user part of the Email address as username

©Comdasys 2011 All rights reserved

227

Corporate Directory LDAP & MS Exchange

©Comdasys 2011 All rights reserved

228

Corporate Directory Basics

• Search for users inside your directory and dial them directly

©Comdasys 2011 All rights reserved

229

Corporate Directory Basics

• Client connects through the https interface to make a directory lookup • Directory lookup done from Server via LDAP • Exchange Server 2003 & 2007 can be integrated using the corperate phonebook feature

©Comdasys 2011 All rights reserved

230

Corporate Directory Controller Config

• Specify IP and port of your LDAP server • Specify search base •Disable ADS if lookup speed is slow • Set incoming encoding for umlauts

©Comdasys 2011 All rights reserved

231

Support Portal

©Comdasys 2011 All rights reserved

232

Support Portal http://portal.comdasys.com

• Get an account for the support portal and login using your username and password • Each person should have an individual account • If you don’t have an account yet contact [email protected]
©Comdasys 2011 All rights reserved

233

Support Portal Basics

• You are assigned to the Comdasys and “your company” project (select them as indicated above) • The Comdasys project contains the Comdasys specific updates & information
©Comdasys 2011 All rights reserved

234

Support Portal File Section – your project

• Download branded clients or customer specific adaptations from there

©Comdasys 2011 All rights reserved

235

Support Portal Comdasys Project - Documents

• Server & Client updates can be obtained from the Comdasys documents folder

©Comdasys 2011 All rights reserved

236

Support Portal Activity
• Receive email notifications for changes (new version / hotfix etc.)

©Comdasys 2011 All rights reserved

237

Support Portal Issue Tracker
• Access the issue tracker to look for already reported issues • Add new support cases here

©Comdasys 2011 All rights reserved

238

Support Portal Issue Tracker
• New tickets will be assigned by Comdasys automatically (don’t assign them) • The “Assigned to” field indicates who is responsible to do the next action • After each update from your side set the “Assigned to” back to the last involved Comdasys personnel • Close issue after it is solved for you

©Comdasys 2011 All rights reserved

239

Demo Kit

• • • •

Request Demo Kit Install the Demo kit using Vmware (e.g. free Vmware Player) Demo Kit contains one license for one user / extension Client can be used for 30 days without license

• Contact sales for downloading the demo Kit

©Comdasys 2011 All rights reserved

240