Low Level

Design for
Mobile PBX

May, 2010

1
Version Changes Date
0.1 Initial draft May 10, 2010
0.2 Changes according to STC comments May 16, 2010
0.3 Final changes – technical part June 5, 2010
0.4 Prefix updated August 10, 2010
0.5 Changes according to STC comments August 11, 2010
Contents

1 Introduction ............................................................................................ 5

2 Mobile PBX Solution Architecture ............................................... 7

2.1 Solution .................................................................................................... 7
2.2 Supported Features .................................................................................9
2.3 Service Customization (Business/Private Role)..................................... 10
2.4 Scenarios........................................................................................... 11
2.4.1 Mobile Originated Call (private role) ...................................................... 11
2.4.2 Mobile Originated Call (business role) ................................................... 12
2.4.3 hiQ4200 Originated Call (business role) ................................................ 13
2.4.4 Mobile Terminating Call .........................................................................14
2.5 End to End Call Flows............................................................................ 15
2.5.1 Call Flows .............................................................................................. 15
2.5.2 Special Cases ........................................................................................ 18
2.6 Technical Requirements ........................................................................19

3 Mobile PBX Implementation................................................................ 20

3.1 Software/License Updates ..................................................................... 20
3.2 Integrations ............................................................................................ 22
3.3 Installations ............................................................................................ 22

4 Appendix - Glossary ............................................................................ 23

[Type text]

Table of Figures
Figure 1: Solution
Overview........................................................................................................................ 5
Figure 2: Solution Architecture - The parts marked in RED are new additions in this project. The
boxes in ORANGE have software/license updates in the project
..................................................................... 7
Figure 3: Mobile PBX Connectivity
............................................................................................................ 8
Figure 4: Mobile originated Call (private role)
........................................................................................ 11
Figure 5: Mobile originated Call (business role)
.................................................................................... 12
Figure 6: hiQ4200 originated Call (business role)
................................................................................. 13

4 (24)
1 Introduction
Mobile PBX is a solution that delivers PBX functionality such as
Attendant service, Call Hunting, Outgoing Call Blocking as a service
available over the GSM Network. Fixed and Mobile network can offer
to their enterprise customers hosted communication services, covering
simultaneously mobile and fixed users.

Figure 1: Solution
Overview

The users can be combined in the same private numbering plan and have
a common set of business group features like enterprise common contact
list, presence status of other users, or definition of line, toll or call
restrictions. Depending on the sort of terminal, subscriber features are
assigned to each individual user, like speed‐dialing, calling number
display, creation of black‐list / white‐list for screening, support of
conference calls. The hiQ 4300 based ComManager can be used to
view the calls, configure calls (e.g. define rules for inbound calls, define
presence status), control calls (e.g. accept and end Voice / Video calls,
initiate Voice/Video calls, Transfer, On Hold, retrieve ).
The scope of this project is to provide IP Centrex features (originating,
terminating and mid‐ call features) as well as web services (presence,
address book, call control, call journal, feature settings) to the mobile
network users.

Migrations scenarios (e.g. fixed mobile substitution with the re‐use of the
SIP based landline phone number) shall be supported. Following items are
included in the scope of this project:
• hiQ4200/4300 system expansion with 4k PBX/IP‐PBX & 6k Mobile
Centrex users
• Movious
expansion
• Integration with Mobile network (optional physical
connectivity)
• Multi Vendor Integration (application level
integration)
• Service Customization (business/private role
functionality)
• Integration & Verification with Billing
system
• Integration & Verification with Provisioning
system
• Integration & Verification with
OSS
• iSuite NMS/EMS Application
expansion

6 (24)
2 Mobile PBX Solution Architecture

2.1 Solution
Mobile PBX solution is built on top of the existing IP Centrex which uses
the Application Servers hiQ4200 and hiQ4300. This feature allows a
Business Group to span across Mobile 2G and 3G Endpoints (GSM, UMTS).
The hiQ4200 provides IP Centrex services for dynamically registered SIP
subscribers, as well as for Mobile subscribers who are provisioned statically
as virtual SIP subscribers on the hiQ.

Figure 2: Solution Architecture ‐ The parts marked in RED are new additions in this
project. The boxes in
ORANGE have software/license updates in
the project

The hiQ 4200 (VoIP server) and hiQ 4300 (Business Management server)
are connected to the mobile network via the NGN network. And opposite,
mobile devices are connected via the MSC / NGN to the voice application
server. SIP phones (and PBX’s) are connected via the Session Border
Controller to the voice applications server.
 When a Mobile subscriber initiates or receives a call, the mobile network
transfers the call to NGN via PSTN (SN), which then forwards it to the
hiQ4200 via SIP‐I GW. The hiQ4200 executes A‐party and/or B‐party
services and routes the call to either the NGN or a SIP Client depending on
the destination of the called party.

Web‐based rich communication services are accessed via any standard

internet browser or via a dedicated JAVA application installed on the mobile
phone.

Figure 3: Mobile PBX

Connectivity

The service triggering is done based on the prefix to the B‐party number. The
MSC will forward the call with prefix to the NGN network. The NGN soft switch
will forward call to IPCX (SIP‐I GW) based on prefix to the B‐Party number. The
voice application server will execute the originating and (if possible) the
terminating services. The MSC and NGN soft switch need to support the P‐
asserted‐identity (calling party number) and the privacy (CLIR) headers.

When using international trunks between the visited MSC and the NGN the
assigned routing prefix and the dialed number must not exceed the
maximum called party number length supported via the international trunk.
Charging of incoming calls in case Mobile user is roaming would have high
processing impact on Billing system. Due to this, roaming for Mobile
subscribers will not be allowed.

The Mobile PBX user will be a postpaid subscriber which will be able to use his
8 (24)
Mobile services
even if his personal limit has been reached.

9 (24)
2.2 Supported Features

The Mobile PBX supports the following

features:

Basic VoIP:
• Support Presence Service with Presence Screening List (redisplay via
refresh button)
• Calling Number Delivery
• Call Forwarding Variable Unconditional (CFV)
• Call Forwarding Busy Line (CFBL)
• Call Forwarding Fixed
• Call Forwarding Don't Answer (CFDA)/No Reply
• Courtesy Call for Call Forwarding
• Remote Activation Call Forwarding (RACF)
• Anonymous Call Rejection (ACR)
• Simultaneous Ringing
• Direct Outward Dialing (DOD)
• Direct Inward Dialing (DID)
• Business Group Main Number
• Fully Restricted Originating/Terminating Line
• Semi Restricted Originating/Terminating Line
• Traffic Measurements for Business Groups
• Billing for Business Groups
• Private Dialing and Numbering Plans
• Extension Dialing
• Serial Ringing
• Toll & Call Restrictions

ComManager Mobile
• Missed Call Logs
• Hosted Contact List with Presence Status
• Visual MWI Indication
• Dial From Contact List / Missed Call Logs
• Set own Presence Status
• Set Own Forwarding Status
• Web based mid call features

via GSM‐Network GSM‐Device

• Three Way Calling
• Call Hold
• Connected Party ID Display (intra‐switch)
 • Calling Party ID Display (intra‐switch)
• Call Waiting
• Call Waiting Caller Notification

List maintained by Web GUI via PC

• Selective Call Forwarding (via screening list only)
• Enhanced/ Selective Call Forwarding
• Selective Call Rejection (SCR)
• Selective Call Acceptance (SCA)
• ComMobile Rules settings ( Rules, Contacts etc.)

Voicemail, Unified messaging

• Full set of features

2.3 Service Customization (Business/Private Role)

requires this project to utilize only the existing network capabilities. Also it
is required to customize the service to support private and business roles
for mobile users.

User’s default role is “private”. In this case hiQ4200 originating services

are not triggered. The user is presented with the MSISDN to the called
party. The “business role” option is available on per call basis. The
hiQ4200 originating services are triggered in this case and the user is
presented with the business number to the called party.

For the terminating calls, hiQ4200 terminating services are not triggered if
the call is made to user’s MSISDN and the call is delivered as per the
existing routing/LNP. The hiQ4200 terminating services are triggered if
the call is made to user’s business number and the call is forwarded to
MSISDN.

10 (24)
 2.4 Scenarios

2.4.1 Mobile Originated Call (private role)

Dial
manually or
from the
phone contact
list

Regular CS
call

Dial
manually or
from
the hiQ4300
contact
using the
ComManager
Mobile
Figure 4: Mobile originated Call (private role)

1. The user dials the number of the called party as usual using the mobile
phone or the CS
version of ComManager Mobile.
2. As the hiQ4200 is not involved in the call, no Ctx services are
executed. With this short dialing (VPN service) is not possible.
3. The caller is presented with the MSISDN.
 2.4.2 Mobile Originated Call (business role)

Dial
manually
or from the
phone contact list
(with pre‐assigned
11* to
the
contact)

Dial manually or
from the hiQ4300
contact using the
ComManager
Mobile and the
“business Regular CS call
call” option which (11* shall result in
will routing
assign the 11* the call to hiQ4200)
prefix

Figure 5: Mobile originated Call (business role)

1. The user dials the number of the called party as usual using the mobile phone
or the CS
version of ComManager Mobile and assigns a prefix (e.g. 11*).
ComManager Mobile could assign the prefix also automatically to every call or
e.g. to
the office phone number or to a dedicated category of the hiQ4300 contact.
2. Because of the prefix the mobile network shall involve hiQ4200 in the call.
Short dialing
(VPN service) and Ctx originating services (CLIR, OCB, USCID, media status) are
possible.
3. When using the USCID service the caller is presented with the business
number.

Note: Prefix 11* is shown here onlyas an example. In final solution prefix *3 will be
used.
 2.4.3 hiQ4200 Originated Call (business role)

Dial manually or
from the hiQ4300
contact using the
ComManager
Mobile

MakeCall
to 014435000

Translate dialstring
Execute services (USCID)

Figure 6: hiQ4200 originated Call

(business role)

1. The user is using the click‐to‐dial (C2D) version of the ComManager

Mobile.
2. C2D ComManager Mobile will trigger the call setup via the mobile
internet to the hiQ4300 / hiQ4200. The hiQ4200 will setup both
call legs sequentially and connect them upon answer.
3. When using the USCID service the caller is presented with the business
number.
2.4.4 Mobile Terminating Call

Called Party = MSISDN

• Without the T_CSI the hiQ4200 will not be involved in the
terminating call leg. No terminating services are executed in the
hiQ4200.
• The call is delivered to the mobile phone via the existing routing /
LNP means in the operator’s network.

Called Party = Business Number

• The call to the business number shall be automatically routed via the
existing routing
/ LNP means to the hiQ4200.
• hiQ4200 will execute the terminating services associated with the
business number.
This services will be an operator provisioned CFSIE‐All to the user’s
MSISDN. With this the hiQ4200 will execute the terminating
services associated with the MSISDN, too.
• The call is delivered to the mobile phone via the existing routing /
LNP means in the operators network. CF notification / COLP must
not be used or COLR must be activated in the MSISDN profile to
protect the MSISDN from being shown / announced to the caller.

14 (24)
2.5 End to End Call Flows

2.5.1 Call Flows

Mobile PBX user calling another Mobile PBX user ‐ Dial from phone or call
setup from ComMng M:

Mobile PBX user calling another Mobile PBX user ‐ Call setup from
ComManager:
Mobile PBX user calling CS user ‐ Dial from phone or call setup from
ComManag M:

CS user calling Mobile PBX user:

16 (24)
Mobile PBX user calling IP Centrex user ‐ Dial from phone or call setup from
ComManag M:

IP Centrex user calling Mobile PBX user:

2.5.2 Special Cases

Ctx user in business role calling MSISDN of another Ctx

user
• If a Ctx user is using the business role and calling the MSISDN of
another Ctx user, the called party will be validated in the hiQ4200
and the terminating services associated with the MSISDN profile will
be executed.
• The execution of the terminating services associated with the
MSISDN profile can be suppressed by explicitly routing the called
MSISDN to the SIP‐I GW destination. This will create the same user
experience as in case of a call originated by a non‐Ctx user.

Ctx user in private role is calling another Ctx user

• If a Ctx user is using the private role and calling another Ctx user,
the hiQ4200 will validate the callers number (the MSISDN) and
execute the originating services (e.g. replace the MSISDN by the
business number). This means that calling another Ctx user in a
private role is not possible per default.
• If the use case must be supported in the operators network, the
SIP‐I GW must re‐ format the calling party number (P‐Asserted‐
Identity) when not receiving the *3 prefix. If the hiQ4200 receives
the P‐A‐I in e.g. national format the originating services associated
with the MSISDN will not be executed. An option is SIP‐I GW
sending the USCID suppression prefix for all calls which do not
have the *3 routing prefix assigned to the called party number.

18 (24)
2.6 Technical Requirements

Following are the mandatory requirements for this project:

1. The V‐MSC to route a prefixed call to the NGN network. NGN SS to

route a prefixed call to SIP‐I GW (IPCX).
2. The MSC, NGN SS to support the P‐Asserted‐Identity (calling party
number) and the privacy (CLIR) headers.
3. The MSC, NGN SS to support the diversion or history info headers to
detect CF loops.
4. The MSC, NGN SS to support INVITE, reINVITE and UPDATE with or
without SDP.
5. The mobile network to support GPRS or UMTS for HTTPS (SSL
certificate) based internet connections for the web service delivery to
the mobile phones.
6. The mobile phones to be JAVA capable.
7. The mobile phones to connect via UMTS or to support dual transfer
mode (GPRS + CS)
for web services used during an active CS call.
8. Zero size SDP INVITE message (SDP‐less INVITE) need to be
supported by all SIP entities in call trajectory. hiQ and SIP‐I GW
already support it. NGN, MNO side (Huawei SS, Huawei & E/// MSS)
also need to be confirmed.
9. Number ranges have to be reserved as business numbers for all dual
profile Mobile PBX
users and assigned to IP Centrex.

In addition to the above, below are the optional requirements:

1. The NGN SS to change the P‐Asserted‐Identity number format to a
national one when processing the terminating routing number prefix.
2. The MSC, NGN SS to support SIP / ISUP mediation for enhanced
services such as
CCBS/NR.
3. The mobile network to support service codes, e.g. *21*destination or
2*21*destination
(if the called party number must not start with “*”).
4. If integration to Al‐Jawal network via NGN network is not supported,
IP Centrex can be integrated with MNO directly. Then physical
connectivity to the MNO and integration effort will be needed.
3 Mobile PBX Implementation

3.1 Software/License Updates

The following software/licenses expansions will be made during this

project:

Model Description Item Description Total Qty

hiQ4200/4300 system expansion with 4k PBX/IP- hiQ4300 Mobile Client SW for PDA and Mobile Phone
1
PBX & 6k Mobile Centrex users (R13) V2 (SW update via MS)
hiQ4200/4300 system expansion with 4k PBX/IP-
ATTENDANT 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Service provider Admin 10,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Advanced voice 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Office suite integration 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Group Admin 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Business voice 10,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Presence service 6,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: COM MANAGER - Portal functionality 6,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Team function 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Family and community voice 10,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Base system software 10,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: COM manager - Enhanced functionality 6,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Video telephony support 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Classic voice 10,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: User self Admin 6,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: GROUPWARE Server synchronisation 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Instant messaging support 1,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: CALEA and Lawful Interception 10,000
PBX & 6k Mobile Centrex users (R13)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: COM MANAGER - Basic functionality 6,000
PBX & 6k Mobile Centrex users (R13)

20 (24)
hiQ4200/4300 system expansion with 4k PBX/IP-
hiQ SW: Specific features for SIP users 1,000
PBX & 6k Mobile Centrex users (R13)

Movious (expansion) Announcement/VR channel SW and Licensing 10

Movious (expansion) N-way conference channel SW and Licensing 7

Movious (expansion)
FAX channel SW 1
Mereon UM Mailbox - UM subscriber software
Movious (expansion) 2,000
licensing

Movious (expansion) Conference Bridge Audio, WEB SW and Licensing 5

Movious (expansion) AUTO ATTENDANT SW AND LICENSING 2

iSuite NMS/EMS Application expansion (R13) iSuite Basic License per subscriber for hiQ 10,000

iSuite NMS/EMS Application expansion (R13) iSuite IPMC per subscriber for hiQ R13 10,000

NETMANAGER BASE SYSTEM RTU FEE PER 1000

NetManager expansion 3
PORTS. PACKAGE V6.2

NetManager expansion NETM BASE SYSTEM (per POP ports) 1,898

NetManager expansion NetM Georedundancy (per 1000 Ports) 3

NetManager expansion NETM PP: NetM Georedundancy (per POP ports) 1,898

ALARM INTERFACE RTU FEE PER 1000 PORTS.

NetManager expansion 3
PACKAGE V6.2

NetManager expansion NETM PP: ALARM INTERFACE (per POP ports) 1,898
TTY INTERFACE RTU FEE PER 1000 PORTS.
NetManager expansion 3
PACKAGE V6.2

NetManager expansion NETM PP: TTY Interface (per POP ports) 1,898

NETM TECHNOLOGY PACKAGE FOR STMI (per

NetManager expansion 2
1000 trunks)

NetManager expansion SUBSCRIBER MAINTENANCE COMMAND 3

PERFORMANCE DATA COLLECTION RTU FEE PER

NetManager expansion 2
1000 TRUNKS. PACKAGE V6.2

NetManager expansion NETM PERF.DATA COLLECTION (per POP) 1,898

NetManager expansion NETM TECHNOLOGY PACKAGE FOR hiE9200 V4 3,796

NetManager TP for IP UNITY, RTU fee per NE
NetManager expansion 1
package V3.1
NetManager TP for ACME, RTU fee per NE package
NetManager expansion 1
V5.0

NetManager expansion Integration services for NetManager expansion 1

3.2 Integrations

Following integrations will be performed during this project:

Model Description Item Description Total Qty

Integration with Mobile network Integration with Mobile network 1

Multi Vendor Integration (MVI) Mulit Vendor integration 1

Service Customization Service Customization 10

Integration & Verification with Billing system Integration & Verification with Billing system 1

Integration & Verification with Provisioing

Integration & Verification with provisioing system 1
system

Integration & Verification with OSS Integration & Verification with OSS 1

3.3 Installations

Following installations will be performed during the project:

Model Description Item Description Total Qty

hiQ4200/4300 system expansion with 4k PBX/IP-

hiQ4200/4300 SW expansion installation 1
PBX & 6k Mobile Centrex users (R13)

Redundant power supply for existing IP routers Installation of additional power supply for IP-router 2

22 (24)
4 Appendix - Glossary
ACD Automatic Call
Distribution ACP Access Control
Protocol
ADMOSS Advanced Multifunctional Operator Service System
ADSL Asymmetric Digital Subscriber Line
ATM Asynchronous Transfer Mode
BG Business Group
BHCA Busy Hour Call Attempts
BICC Bearer Independent Call Control
BOOTP Bootstrap Protocol
B‐RAS Broadband Remote Access
Server CAGR Compound Annual Growth
Rate CAPEX CApital EXPenditure
CAS Channel Associated Signaling
CBR Constant Bit Rate
CLIP Calling Line Identification Presentation
CM Cable Modem
CO Central Office
CoPl Commercial Platform
CORBA Common Object Request Broker Architecture
CPE Customer Premises Equipment
CPG Customer Premises Gateway
CSTA Computer Supported Telecommunications Applications
CTI Computer Telephony
Integration DHCP Dynamic Host Configuration
Protocol DLU Digital Line Unit
DN Directory Number
DOCSIS Data Over Cable Service Interface Specifications
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
DSS1 Digital Subscriber Signaling No. 1
DTMF Dual Tone Multi Frequency
ETH Ethernet
FCAPS Fault, Configuration, Accounting, Performance Monitoring and
Security
FITL Fiber In The Loop
FSK Frequency Shift
Keying GUI Graphical User
Interface GW Gateway
HFC Hybrid Fiber Coax
HTTPS Hypertext Transport Protocol with Secure Socket Layer
IAD Integrated Access Device
IN Intelligent Network
INAP Intelligent Network Application Part
IP Internet Protocol
IPSEC IP Security Protocol
ISDN Integrated Services Digital Network
ISP Internet Service Provider
ISUP ISDN User Part
IUA ISDN User Adaptation layer
protocol IVR Interactive Voice Response
Systems LAC Local area code
LAN Local Area Network
LDAP Lightweight Directory Access Protocol
LEA LAW Enforcement Agencies
LEX Local Exchange
MG Media Gateway
MGCP Media Gateway Control Protocol
MIB Management Information Base
MML Man Machine Language
MSB Multifunctional
Switchboard MSF Multiservice Switching
Forum MSO Multiple Service
Operators MTA Media Terminal Adapter
MTP Message Transfer Part
(#7) NAS Network Access
Server
NAT Network Address Translator
NGN Next Generation
Network NNI Network Network
Interface NPV Net Present Value
OAM&P Operation Administration, Maintenance and Provisioning
OPEX OPerational
EXPenditure OSP Operator Service
Provider OSS Operation Support
System PBX Private Branch
Exchange POP Post Office Protocol
POTS Plain old Telephone Service
PRI Primary Rate Interface
PSTN Public Switched Telephone Network
PVC Permanent Virtual Channel
QoS Quality of Service
RAS Registration, Admission and Status
RDLU Remote DLU
RRS Registration and Roting Server
RSDLU Remote Shelter DLU
RTP Real Time Transport Protocol
SCTP Stream Control Transfer Protocol
(RFC 2960) SDSL Symmetric Digital Subscriber Line
SHDSL Symmetric DSL
SIP SIMPLE SIP for Instant Messaging and Presence Leveraging Extensions
SME Small Medium Enterprise
SMS Short Message Services
SNMP Simple Network Management Protocol
SOAP/XML Simple Object Access Protocol/Extensible Markup Language
SOHO Small Offices and Home Offices
SQL Structured Query Language
SS7 Signaling System No.7
SSH/CLI Secure Shell Command Line Interface
SSL Secure Sockets Layer
ToS Type of Service
TCP Transmission Control
Protocol TGCP Trunk Gateway Control
Protocol TTS Text To Speech
TTY Tele Type Interface
UCD Uniform Call
Distribution UM Unified Messaging
VoCable Voice over Cable
VoDSL Voice over Digital Subscriber Line
VoIP Voice over IP
VPN Virtual Private Network
WML Wireless Markup
Language XML Extensible Markup
Language

24 (24)