BusinessPhone Communication Platform 7.0
Facilities

## Mobile Extension

General
Network provider
Operation
Technical Realization
Abbreviations
Call from a mobile phone
Automatic system number translation
Call to a Mobile Extension
DTMF sending (end to end) by a Mobile Extension
Inquiry / refer back by a Mobile Extension
Call back & CTI
Suffix dialling by a Mobile Extension
Basic programming
Programming - Automatic system number translation
Security check in case of not provided A‑number
Security check with a CTI automated attendant
Limitations & Capacity
Equipment
Ericsson P900/P910 used as mobile extension
P900/P910 features
How it works
References

## General

A mobile subscriber, be it 2G, 2.5G or 3G or any standard GSM, GPRS, D-AMPS, UMTS, can be used like an extension in BusinessPhone.

The traffic to, as well as from, the mobile user passes through the BP. While passing the BP, the system will be able to link services to the calls. Users of the Mobile Extension are defined in the BP as mobile extensions. This means that the mobile user will have access to the corporate network. The mobile user will also be able to use services like an analogue extension such as inquiry, short number dialing, camp-on, intrusion, call back, etc.

### Network provider

In order to save costs it is recommended to negotiate a flat rate or decreased rate contract with the GSM network provider (e.g. with a GSM gateway or a direct link to the GSM network provider), that all calls from the telephone done to the access point and from BusinessPhone to GSM phone are at a cheap rate.

## Operation

See Facility Description - General (15534‑ASB 150 02 Uen)

### Technical Realization

Mobile Extension is realized without additional Hardware. Security is provided by ASB 150 02.

### Abbreviations

Abbreviation / Term | Definition
ASB 150 02 | The PABX: BusinessPhone 50/128i/250
BP | Business Phone, the ASB 150 02 PABX
CPN | Called Party Number
dir. no. | directory number
ME | Mobile extension

### Call from a mobile phone

If the Mobile Extension wants to make a call, the Mobile Extension has to dial first (can be done automatically by a calling card) the access point, which is represented by a Mobile Access Number. Up to 16 Mobile Access Numbers can be created in order to support different tenant groups and reroute positions. The Mobile Access Number is needed to provide security.

The Mobile Access checks the received A-number of the caller. The Mobile Access manages a list of programmable A-numbers indicating the permission of using the Mobile Extension feature. Each A-number of the list has an assignment to a corresponding internal directory number of a Mobile Extension. Depending on the membership of the list the call is rerouted to the assigned Mobile Extension (if the A-number is registered - authorization ok) or to an answering position (if the A-number is not registered - authorization failed).

In case of a not provided A-number the Mobile Access Number ensures an alternative voice guided authorization which can be a CTI group. The Mobile Extension user has to run through authorization by typing in the customer identity manually.

If the authorization is successful the internal dial tone notifies the readiness to receive further dial information - the mobile extension user may type in the number of the desired destination. The digits received from the PSTN from now on are in the DTMF-format.

In case that there is not any DTMF register available the originator process is released and the mobile extension receives an appropriate tone.

### Automatic system number translation

The mobile phone Sony Ericsson P900 could do automatic number translation directly in the phone - but if used as mobile extension, this function should be switched off - the number translation should be done in the PBX.

Mobile Extension users can be categorized for usage of the origin public numbers for their calls. Provided that a number is stored properly in the mobile phonebook (or manually dialled), i.e. in the international number format, e.g. +43 664 123 4567, then the system itself detects and modifies the received number for an efficient routed call setup to the external or internal destination.
This is also solving the problem of storing 2 numbers in the phonebook for the same entry, i.e. calls direct to a public destination or routed over BP to the same destination.

The ’calling card functionality’ of a mobile phone optimizes the utilization of public phonebook numbers.

#### Call to external destination

All public call numbers must be stored/dialled in the mobile phonebook in the format of ’public international’, e.g. +43 7683 5839.

Note: A wanted external destination cannot be reached when a short public number is used, i.e. a number with less or equal number of digits as defined for internal directory numbers in acc. to system category ’internal number length of inband CPN’, command 6804.

#### Call to internal destination

All internal call numbers can be stored/dialled in the mobile phonebook in the format of ’public international’, e.g. +43 1 81100 9999, or just as an internal directory number, e.g. 9999*.

*) Here it’s highly recommended to used the ’#’ as ’forward-end-of-selection’ sign for internal directory numbers. I.e. by programming the confirmation (verification) code of calling card to ’#’ which is send after the internal directory number.

This speeds up the call setups to internal destinations. Otherwise are these calls delayed due to pre-analysis of number plan type, defined as ’internal number length of inband CPN’ with command 6804. The delay time will be according the time supervision for digit receiving at incoming calls, command 1412.

#### Prerequisites and number translation

A received number from Mobile Extension, defined as ’inband Called Party Number’, is identified by the system as either ’own internal call destination’ or ’other external call destination’. This requires identification of own system which is done by programming of own complete public number, e.g.:
Own country code: 43 command 2236
Own area code: 1 command 2237
Own subscriber code = public number: 81100 command 2220

This gives own system public number id.: 43181100

An external call destination may be prefixed, depending of the destination, e.g.:
International prefix: 00 command 1936
National prefix: 0 command 1937

The external calls needs route access dir. no. definition, e.g.: Tenant route: 00 command 6803

Example 1, ME calls an internal destination with its own public number:

The user dials manually or using phonebook: (00) 43 1 81100 9999

- (00)431811009999 :received digits
43181100 xxxx :own system id. (digit mask)

Probably leading prefix’s (00) are remove, thereafter are received digits compared to digit mask. Matching digits are removed, remaining digits are used for the new call setup, here:

- 9999 : any internal dir. no.

Example 2, ME calls an local external destination:

The user dials manually or using phonebook: (00) 43 1 81200 9999

- (00)431812009999 :received digits
43181100 xxxx :own system id. (digit mask)

Probably leading prefix’s (00) are remove, thereafter are received digits compared to digit mask. Matching digits are removed, remaining digits are used for the new call setup, i.e. local call.
External (route) access code is included to the number for the new call setup, here:

- 00 812009999: route access dir. no. + send digits

Example 3, ME calls an international external destination:

The user dials manually or using phonebook: (00) 46 123456789

- (00)46123456789 :received digits
43181100 xxxx :own system id. (digit mask)

Probably leading prefix’s (00) are remove, thereafter are received digits compared to digit mask. No matching digits, no number modification, i.e. international call.
External (route) access code and internat. prefix digits are included to the number for the new call setup, here:

- 00 0046123456789: route access dir. no. + send digits

### Call to a Mobile Extension

A Mobile Extension user is called by dialling the internal directory number of the Mobile Extension assigned to ít‘s public telephone number. There is no authorization check for calling a Mobile Extension. No external access restrictions of the caller are relevant in this case - the call is treated like an internal call.

If a Mobile Extension individual is called, the information about its assigned external number is requested with the help of the Mobile Access. Also in this case an assignment list is used to convert the number, but now it is used reverse. Now the internal directory number is the starting point for conversion. The Mobile Access also adds a possible tenant route number if necessary.

If the call set up fails the call originator process is released with appropriate tone.

In case that the mobile extension is called and no DTMF register is available the call setup works as usual but the mobile extension can not make an inquiry. Additionally the following warning is generated: 0x0B Register Seize Request Cancelled

#### The mobile extension

- After a cold start no Mobile Extensions exist in a system.
- The mobile extension can act either as:

- stand alone extension or
- the slave of a Master-Slave unit

- The opposite party of a Mobile Extension always displays the internal directory number of the Mobile Extension, its public number is not shown to the opposite party.
- In order to support the correct connected information for the public mobile phone the opposite number is transmitted to the trunk the public phone is connected to.
- Mobile Extensions calls need additional register resources used to convert DTMF-signals, sent by a Mobile Extension terminal as dial information, to digits. These registers are always connected when a Mobile Extension is involved in a call and are not available for the regular traffic.

### DTMF sending (end to end) by a Mobile Extension

After the call setup of a Mobile Extension terminal has been completed (i.e. the public mobile phone is connected to the internal directory number of the Mobile Extension), the Mobile Extension receives the internal dial tone and is able to dial the number of the ’real’ destination.

In this case the digits are sent in DTMF-format on the speech channel the Mobile Extension terminal is connected to.

By pressing the star-key the Mobile Extension user initiates DTMF-sending. This is the indication to ASB 150 02 to look upon the following DTMF-signals as pure DTMF sending without processing the digits. Thus access to opposite parties which demand a DTMF control like call answering machines is possible.

Once DTMF-sending was requested, it cannot be turned back within the actual call.

### Inquiry / refer back by a Mobile Extension

After a Mobile Extension user is in speech connection with its opposite party he is able to request an inquiry by dialling ’1’ and the digits necessary to dial the number of a new destination.

Referring back immediately by pressing ’1’ for a second time before dialling further digits is not possible. This restriction is conditional on the problem to distinguish between immediate refer back (’11’) and 1st digit of the new destination (’11...’). A only way out is to release the call and to wait for the recall.

If a ME user makes an inquiry to a new destination and the ME user gets a call progress tone (ringback, busy, blocked etc.), then the ME user can return to the parked party by typing ’1’.

If an inquiry call to a new destination is already in speech state, then the ME user has the following possibilities:

- ’11’ to terminate the actual call
- ’12’ to switch between calls
- ’13’ to establish a conference

### Call back & CTI

- If a Mobile Extension orders an internal or a CN callback, the duration of callback ringing time is set fixed to 30 seconds - even if command 9006 (Maximal ringing time at the initiating extension for Call Back calls) is set to another value.
- Time within the user is requested to lift the handset in case of a call set up done by the CTI application is set fixed to 30 seconds.

### Suffix dialling by a Mobile Extension

Facility access using suffix dialling by a Mobile Extension is identical to that of an analogue phone user.

## Basic programming

5434 |  | Create Mobile Access

5534 |  | Delete Mobile Access

5634 |  | Alter Mobile Access

8735 |  | Mobile Access reroute position on no A-number

8736 |  | Mobile Access reroute position on no authorization

2270 |  | Assign A-number of Mobile Extensions

1038 |  | Forward CLI/COL

- If set to 2 (Forward for transit/gateway calls and external diverted calls) the display of the ME shows the A-number, assuming that the public operator allows and supports this function.

0151 |  | Tenant group

6803 |  | Tenant-Route

## Programming - Automatic system number translation

0195 |  | CPN modification at call from ME?

1412 |  | Time supervision between digits at automatic incoming traffic

1936 |  | Prefix calling number for E.164 number plan with international type of number

1937 |  | Prefix calling number for E.164 number plan with national type of number

2220 |  | Public number

2236 |  | Own country code

2237 |  | Own area code

6804 |  | Internal number length of inband CPN

## Security check in case of not provided A‑number

In case of a not provided A-number the reroute position of the Mobile Access can be

- a CTI group = CTI automated attendant.

### Security check with a CTI automated attendant

The exit position of the CTI automated attendant is a Fictive number.

#### BackStage 4.0 or higher

BackStage is set-up on a dedicated PC to monitor the Fictive Number.The CTI AA directory number must be set in the Busy lamp field. Example of a routing table (one row per Mobile extension):

Customer Id = e.g. GSM number + Pin code | Routing target = dir. no. of ME
0664123456781111 | 400
0664123455662222 | 401
0664123477883333 | 402

#### BusinessLink

For details please refer to document Computer Telephony Integration (CTI) (900/155 34-ASB 150 02 Uen); if V.24 is used:

Command | Comments | Value
6009 |  |
| Baud rate | 19200

#### CTI automated attendant:

For details please refer to document Computer Telephony Integration Groups (153/155 34-ASB 150 02 Uen)

4426 |  | CTI-AA prompts 1-24

- reference 01: ’AUTHORITY CHECK’
- reference 02: ’PLEASE ENTER YOUR GSM PHONE NUMBER AND YOUR PINCODE’
- reference 03: ’WRONG ENTRY. PLEASE TRY AGAIN’

#### BusinessPhone commands for CTI automated attendant

Command | Comments | Value
5428 |  |
| Create CTI Group | 1200

Note

8733: Exit position directory number (1150 - fictive number - controlled by BackStage)

## Limitations & Capacity

A Mobile Extension individual is not allowed to be specified as a CTI operator, a CTI ACD-agent, a MSU master, a member of a PBX-group in parallel ringing mode or as a guest extension.

If a Mobile Extension is a member of PBX-group (in serial ringing mode) and the ME gets a call, the following command is without any function:

3507 |  | Reroute on no answer

If a Mobile Extension is a conference leader, then the maximum number of conference participants (including the leader) is 3.

As per call setup and per involved Mobile Extension a permanently connected DTMF-receiver will be required, the register pool of the system has to be increased appropriate to the programmed Mobile Extension individuals in the system.

There is no possibility to indicate, if the registers are used for regular extensions or for Mobile Extensions. So it depends on the adequate configuration of the system if there is a lack of register resources or not.

The maximum number of Mobile Extensions in the system is limited by the sum of all regular and Mobile Extensions. However, the maximum number of Mobile Extensions in a system is limited to 100. The number of allowed Mobile Extensions in a system depends on the ASB 150 02 licensing. The following steps exist: 2, 5, 10, 15, 20,..., 95, 100.

If a call should be transferred before answer to a Mobile Extension, the originator has to wait for the ring back tone, otherwise a RECALL is performed.

Basically the mobile extension acts like an analogue DTMF telephone. For details please refer to: Facility Description - General (15534‑ASB 150 02 Uen)

Diversion on no reply should not be activated to the GSM´s mailbox - otherwise the BusinessPhone´s diversion / mailbox is bypassed.

## Equipment

- The basic feature is supported by ASB 150 02 R14 or higher system releases whereas utilization of public phonebook numbers for ME user is supported by ASB 150 02 R15 or higher system releases.
- appropriate number of DTMF register boards (a mobile extension needs for the whole conversation time a DTMF register). The number of DTMF register boards depends on the traffic and the number of Mobile Extensions; in case of 200 mErlang simultaneous calls:

  max. number of Mobile Extensions | DTMF register blocks *)
  15 | 1
  35 | 2
  55 | 3
  75 | 4
  100 | 5

- MFU, VMU-HD_8 has 1 x DTMF register block
- BTU-D, REG has 2 x DTMF register blocks

- *) 1 DTMF register block has 4 DTMF registers

- In order to have access to the feature, the proper licensing concept has to be used, see Facility Description – General (155 34-ASB 150 02 Uen), chapter ASB 150 02 Licensing
- BMS 3.1 or higher

## Ericsson P900/P910 used as mobile extension

It is of prime importance that users can access all the features and functionality of their enterprise communication system, no matter which phone they are using. That is why the P900/P910 was developed to work together with the ASB 501 04 and the ASB 150 02 Communication System. With its pen and large screen, the P900/P910 makes it easy for users to benefit from all the functionality of their PBXs.

### P900/P910 features

The Sony Ericsson P900/P910 is a triple-band mobile phone, an MP3 audio and MPEG4 video player, an advanced handheld device and a mobile video and digital camera.

The P900/P910 contains a functional block called Corporate Telephony. This extends all the functionality of BusinessPhone to users on the move. The function of routing calls via the PBX to a final destination is taken care of inside the telephone. This process is completely transparent to the user.

The user activates PBX features through a graphical user interface by pressing feature buttons. Each button displays an easy-to-understand text description of the function and sends away a string of DTMF tones. It can even send data that the user is prompted to provide, like the return time after a meeting. Feature buttons and text descriptions are easily configurable.

#### Call handling features:

The most frequently used call handling features can be displayed during ongoing calls. Additional call features are displayed on a list under the 'More' button.

#### Other telephony features:

Other telephony features are displayed under the 'corporate' status bar button. To open the command window

- click on the PCCF (PBAX Calling Card Feature) icon

- select ’Command’ button

The commands will result in a call being made to the ASB 150 02 and the DTMF string being automatically sent to the PBX. The call is cleared immediately after tone sending, if this is specified.

### How it works

For call handling please refer to chapter:

- Call from a mobile phone
- Automatic system number translation
- Call to a Mobile Extension

#### Step by step instruction

1. The feature buttons can be defined, which tones they generate and what text they display. Additionally it can be defined how the P900/P910 should handle calls to and from the corporate switch. This is all done in an XML-structured configuration file, with the extension ~pbx.
2. The ~pbx file is transmitted via web browsing, e‑mail, PC sync, Infrared transmission IR, Blue Tooth or inserted on a Memory Stick.
3. Go to Phone -> Edit -> Preferences -> Calling cards and enters the P900/P910 device lock code and select Import.
4. Point to the configuration file and click the ’Import’ button.
5. Select 'Always use calling card' or 'Prompt before call'.
6. Select the imported calling card as the active card.
7. The P900/P910 adds a PCCF (PBAX Calling Card Feature) icon to the display. This icon is a shortcut to the currently selected calling card name and mode of operation.

### References

A typical PBX-file is available on the Service and Support Plaza (Info Channel -> Service Support Plaza -> Knowledge Base -> BusinessPhone -> Download Area -> External Devices ). Along with the typical PBX file there is also a PBX-file editor available on the Info Channel which allows easy modification of the PBX-file.

Sony Ericsson published a White Paper for this solution. This document is highly recommended for partners launching this service as it provides in-depth information about the solution and the way of working.

For more information please go to www.sonyericsson.com -> Professional Solutions -> Areas of use -> Corporate Telephony

Revision: G © Ericsson Enterprise 2005