Howto:Quescom Mobility Services Pack - SIP Testreport

From innovaphone-wiki

Jump to: navigation, search

innovaphone Compatibility Test Report

Contents

Summary

Mobility Services Pack

QuesCom Mobility Service Pack is a software solution based on the QuesCom Gateways to deliver a One Number reachability whether the user is in the office or on the road. Users receive all calls and faxes on a single number (DDI). Not only does the user receive his office calls on his mobile, but all his calls appear to originate from his desk phone. The user's physical location and mobile phone number remains private. The caller always dials the same extension , the called user can pick up the call with any associated phone.

Furthermore not only the "one number" reachability is here the benefit , also the mobile phones turns into a PBX extension.

The GSM Gateway is optional and not a must when using the Mobility Services Pack.

  • Features:
    • Fax over IP (T.38)/Fax to email
    • DTMF
    • Multiple Ring
    • Vcc - Voice Call Continuity (described below)
    • Multi- party Conferencing
    • Mobile Client for Nokia E & N Series (MobiQ®)
    • Mobile Client for Microsoft Version 5 and Version 6 (MobiQ®)
    • Gsm Gateway
  • Supported Codecs by the QuesCom
    • G711
    • G729
    • G723
    • G726
    • T.38 UDP

Certification Status

Image:Recprod.PNG The tests for this product have been completed and it has been approved as a recommended product (Certification document).

Testing of this product has been finalized September 30, 2008.

Testing Environment

Scenario

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_1.png

Description

Three IP phones (1, 2 and 3). Ext.2 was configured as a one number user. Only calls to one number users will be routed to the Q200. This was achieved by creating multiple registration in the innovaphone PBX for the corresponding user.

The QuesCom needs two numbers to address the Mobility access Features, in our Test-scenario:

Mobility access number is 8

The VCC (Voice Call Continuity) number is 9 (reachable via mobility access number)

Mobility Access Features

Calls received are redirected in accordance with rules and filters defined by the user.

User Web interface for handling redirections and profiles.

Mobile Extension

Access to PBX-like functions from any registered mobile phone: call hold, call resume, conference call, switching between calls, transfer, selection of redirection profiles.

Mobile Least Cost Routing

VCC

Voice Call Continuity (VCC) is a feature that permits a user to continue a call on an associated phone by simply dialing the VCC service access number. The ongoing call is continued without any interruption. In the test scenario, the GSM phone calls Ext.4 via the QuesCom Gateway, then Ext.2 dials 9, the call is continued on Ext.2 and released on the GSM.

tested call flows

Inbound to normal user

1. An outside caller dials Ext1.

2. This is a normal user, so the call is sent directly to the phone

Inbound to One number user

1.An outside caller dials Ext2.

2. This is a one Number user, so the innovaphone Pbx handles the ringing of the Ip phone, and the second registration calls the Q200.

3. The Q200 then puts out calls to the defined Multi ring numbers (in this case Ext.3 and a GSM).

4. The RTP stream will be established to the first of the 3 phones to answer the call; the other calls will be terminated.

Mobility

1. Ext.2 user is on the road with his GSM. He places a call to his colleague at Ext.1 with simply pressing only the extension number. The MobiQ client software will automatically dial the Trunk number and the Mobility access number (in this case 8).

2. innovaphone pbx routes the 8 to the Q200.

3. Once connected, MobiQ client dials 1, and the call is routed to the innovaphone pbx.

4. innovaphone pbx rings Ext.1.

VCC

1.An external PSTN user calls the One number user Ext.2. The call is answered on the GSM phone (see call flow inbound to One number user)

2. The user wishes to continue the call on his fixed phone. He dials the VCC access number (in this case 9).

3. The call is continued seamlessly on his fixed phone and hung up on the GSM.

Fax

Inbound to user fax number

1.An external fax dials Ext.6. 2. This is the fax number for the user of Ext.2, so the IP800 routes the call to the Q200. The Q200 has Ext.6 associated to the fax service, so the Q200 receives the fax. 3. The fax is sent as an e-mail with a TIFF attached to the defined SMTP server. 4. The user can then consult the fax with any e-mail client software and a standard image viewer.

Outbound fax

1. The Ext.2 user sends a fax from his computer using the VPD (Virtual Printer Driver) software. 2. The Q200 send the fax via the IP800 over T38. 3. The IP800 sends the fax over ISDN to the destination.

Test Results

For more information on the test procedure, please read the following wiki article: SIP Interop Test Description.

Basic Call

calls between mobile phone via QuesCom and innovaphone phones (both directions).

Tested feature Result
call using g711a Yes
call using g711u Yes
call using g723 Yes
call using g729 Yes
Overlapped sending Yes
early media channel Yes
Fax using T.38 Yes
CGPN can be supressed Yes
Reverse Media Negotiaton Yes
Long time call possible(>30 min) Yes
Voice Quality OK? Yes

Direct Dial In

Tested feature Result
Inbound(QuesCom -> innovaphone) Yes
Outbound(innovaphone -> QuesCom) Yes

DTMF

Dtmf tested from mobile phone via QuesCom to innovaphone pbx and vice versa.

Tested feature Result
DTMF tones sent correctly Yes
DTMF tones received correctly Yes

Hold/Retrieve

Tested between mobile phone via QuesCom and innovaphone phones. Tested in both directions.

Tested feature Result
Call can be put on hold Yes
Held end hears music on hold / announcement from PBX Yes
Held end hears music on hold Yes

Transfer with consultation

innovaphone phone transfers mobile call (via QuesCom ) and vice versa. Call returns works only when innovaphone phones transfers call (pbx feature).

Tested feature Result
Call can be transferred Yes
Held end hears music on hold Yes
Call returns to transferring device if the third

Endpoint is not available

Yes

Transfer with consultation (alerting only)

innovaphone phone transfers mobile call (via QuesCom ) and vice versa. Call returns works only when innovaphone phones transfers call (pbx feature).

Tested feature Result
Call can be transferred Yes
Held end hears music on hold or dialing tone Yes
Call returns to transferring device if the third

Endpoint is not available

Yes

Blind Transfer

Tested between mobile phone via QuesCom and innovaphone phones.

Tested feature Result
Call can be transferred Yes
Held end hears dialing tone Yes

Broadcast Group & Waiting Queue

Calls from mobile phone (via QuesCom) to innovaphone pbx.

Tested feature Result
Mobile phone can make a call to a Broadcast Group Yes
Mobile phone can make a call to a Waiting Queue Yes
Announcement if nobody picks up the call Yes

Configuration

Graphical overview of the configuration.

image:Howto-Quescom_Mobility_Services_Pack_Shemaquescom.png

Firmware version

All innovaphone devices use V7 08-70107 as firmware.

QuesCom version : IAD05.00B402P000/ent

SIP Trunk to QuesCom

Configuring the Sip trunk to the QuesCom gateway - this is an Gateway without registration, only the Ip address of the QuesCom is needed to configure.

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_TestreportQuescom_2.png

Parallel Ringing

For configuring the parallel ringing (means mobile phone and fixed phone should ring parallel ) a gateway with register as gateway mode needs to be configured.

In the Alias List (see picture below) the name and number of the pbx extension needs to be configured, for configuring more users simply add them in the Alias list .


image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_3.png

In the Pbx there you have 2 registrations one one User object , one the local Ip Phone and one registration for the Gateway (described above)

Note this parallel ringing feature does not scale large - because every user must be configured in the alias list - it is limited , based also on the length of the names 
please read therefore  Maximum number of aliases on a GW interface

VCC pbx configuration

Enable Twin Phones on the user Object (for the One Number/parallel ringing User).

If the Twin Phones is active and having a call e.g on the fixed Phone- a second call is signalled - this second call will only be signalled on the phone the User is connected with.- the second registered phone will not ring and therefore will not have a missed call shown in the call list.

Also a Vcc (Voice Call Continuity) feature is possible- so forwarding the established call from the fixed phone to the second registered phone (in our case the mobile phone) - simply forward the call to the own extension.

image: Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_4.png


The QuesCom Vcc feature is reachable via 89 - so that the user only dials one digit (9) from the fixed Ip phone to get the call from the mobile phone - configure a map object

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_12.png


There must be a gateway configured that points back from the QuesCom into the pbx (e.g calls from the Gsm phone to a pbx extension ).

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_7.png

Also this Gateway addresses Numbers that are not known in the Pbx (the Mobility Access and VCC Number 8 and 89) , therefore configure a gateway Object in the pbx.

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_10.png


And set in the Pbx/general this Gateway Object as Root node external calls

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_9.png



Route Settings

For routing calls to the QuesCom there mus be a route configured that points from the "parallel ringing Gateway" (the Gateway what registers to the Users in the pbx) to the QuesCom

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_5.png


Calls coming from the Provider must always go first into the QuesCom (for the Vcc and Mobility feature )

Therefore a route is defined what routes all calls beginning with 8 direct into the QuesCom .

As described in the Scenario above the Mobility Service is addressed with extension 8 (so the Mobi client from QuesCom dials automatically the 8 followed by the destination number)

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_6.png


Calls coming from the QuesCom (e.g mobile phone) and should be routed into the Isdn


image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_8.png


Also for calls from the QuesCom into the pbx - configure a emty map below .


For calls coming from the Pbx to QuesCom (Vcc - pressing the Vcc Number on the associated fixed Ip Phone to get the call from the cell phone)

image:Howto-Quescom_Mobility_Services_Pack_-_SIP_Testreport_Quescom_11.png


Features & Comparison

innovaphone has a basic mobile Extension solution. Based on this it shows here a comparison between the innovaphone Mobile Extension solution the QuesCom Mobility Services Pack with and without the Mobile client MobiQ and a very trivial soultion like setting a cfnr (call forward no answer) on the own pbx extension to the mobile phone .


Feature innovaphone basic mobile Extension QuescCom Mobility Services Pack with MobiQ client QuescCom Mobility Services Pack without MobiQ client Trivial solution setting a cfnr on the pbx extension to your own mobile phone
basic One number reachable (voice) yes yes yes yes
basic One number reachable (voice and fax with one number ) no yes with the next software version of Quescom yes with the next software version of QuesCom no
dialing from the mobile phone a pbx extension it shows the right cgpn. no yes no no
show right cgpn on mobile (when getting a call from external ) for showing external number clip no screening must be activated on provider side - see also Known Problems below for showing external number clip no screening must be activated on provider side - see also Known Problems below for showing external number clip no screening must be activated on provider side - see also Known Problems below for showing external number clip no screening must be activated on provider side - see also Known Problems below
show right cgpn on mobile (when getting a call from an internal pbx extension) for internal numbers shows up full Trunk number + extension for internal numbers shows up full Trunk number + extension for internal numbers shows up full Trunk number + extension for internal numbers shows up full Trunk number + extension
Busy information

correct busy state for other extensions or via tapi from the pbx

yes - due to multiple registration on one user object yes - due to multiple registration on one user object yes - due to multiple registration on one user object no
call list

all phones (e.g fixed and mobile) have one caller list with same data/details -

no no no no
Presence

all endpoints should have the presence state of the other users (for example via cti or partner functionkeys )

no ,mobile phone don't have presence informations of other users no, mobile phone don't have presence informations of other users no, mobile phone don't have presence informations of other users no
VCC Voice Call Continuity (from mobile to fixed phone) no yes (dial only the VCC Number at your fixed phone and have the call immediately on your mobile phone ) yes (dial only the VCC Number at your fixed phone and have the call immediately on your mobile phone ) no
VCC Voice Call Continuity (from fixed phone to mobile) yes but here the handling is different, you need to forward the call to the own extension from the fixed phone - then it rings on the mobile phone yes but here the handling is different, you need to forward the call to the own extension from the fixed phone - then it rings on the mobile phone yes but here the handling is different, you need to forward the call to then own extension from the fixed phone - then it rings on the mobile phone no - only forward the call to the mobile number
activating different call forward profiles on the Mobile Phone no yes yes but needs to dial the dtmf features no
Fax server integration (fax to email) no yes yes no
Standard-features on the mobile phone

hold/retrieve - 3rdparty conference, call forward /transfer

no yes yes dialing with dtmf codes no
Voicemail MWI on mobile phone same MWI as on the fixed phone no no no no
Central Phone book - all devices using same phone book no, alternative the third party product VoiceDirector can be used as central phone book. no, alternative the third party product VoiceDirector can be used as central phone book. no, alternative the third party product VoiceDirector can be used as central phone book. no
automatic 2 -stage dialing - means dialing into the pbx and then to the original dialed destination) no (needs to dial into a waiting queue and then dialing the destination number ) yes (only dialing the destination number, the isdn trunk of the pbx is dialed automatically) yes (needs to dial the isdn Trunk of the pbx and add the destination number with a p (pause) between) no


Known Problems

As with all mobile solutions, cell phone users will change their local phone book entries, if they have no MobiQ client (as they must not dial out directly any more but go through 2-stage dialing.But also users with the MobiQ clients needs to add some phone book entries, pbx users needs to be twice (full number and only the extension) For the mobility number/phonebook resolution you must have both the extension and full number saved in the contact.

When calling out to a cell phone, it is desirable to send the calling line id of the original caller to the cell. The innovaphone PBX will do this in fact, however, under normal circumstances this calling line id is rejected by the carrier and replaced by the trunk lines base number.

This is because the number sent is not associated to the trunk line (that is, to the carrier it looks like spoofing invalid calling party numbers). The only solution here is to enable "clip no screening" on the trunk line (there is a separate wiki Howto:How does "CLIP no screening" work? article about this topic).

But Clip No screening has also its disadvantage.(for international calls). Some carrier interconnects may remove the user provided number when passing a call. For example, we have seen this for calls from German Telecom to Italy. In this case, since the defaulted network provided number is left only, the destination user will not see the callers extension, since the defaulted number always carries the "main" extension.

QuesComs Mobile Client Software MobiQ supports E and N Series of Nokia Phones - there is also Support for Microsoft Mobile Version 5 and Version 6 - this client was not tested by innovaphone, only tested with the Nokia E65.

Related Articles

Quescom configuration document

Personal tools