Mobile Call Control

Mobile call control is only supported on IP500 systems and only on digital trunks. It allows a user receiving a call on their twinned device to access IP Office dial tone and then perform dialing action including making calls and activating short codes.

After answering a twinned call, the Mobile Call Control user can dial ** (within 1 second of each other) to place that call on hold and instead get dial tone from the IP Office. Any dialing is now interpreted as if the user is logged into an analog extension on the IP Office using their user settings. That also include user BLF status indication.

•

Mobility Features licenses are required in the IP Office configuration for all the users that will be configured for any of the IP Office mobility features including Mobile Call Control and one-X Mobile Client usage. The same single license also allows the user to use mobile twinning, mobile call control and one-X Mobile if required. Check that the configuration contains valid Mobility Features licenses.

•	If a Mobile Call Control user remote hot desks to another IP Office system within an SCN, they take their licensed status with them rather than consuming or requiring a license on the remote system.

•	Trunk Restrictions This feature is only supported on the IP500 and only on the following trunk types:

•	IP500 Universal PRI (Not on T1 robbed-bit and E1R2 channels set to Loop Start emulation).

•	Routing via trunks that do not support clearing supervision (disconnect detection) should not be used.

•	DTMF detection is applied to twinned calls to a user configured for this feature. This will have the following effects:

•	DTMF dialing is muted though short chirps may be heard at the start of any DTMF dialing.

•	DTMF dialed by the user will not be passed through to other connected equipment such as IVR or Voicemail.

•

WARNING
This feature allows external callers to use features on your phone system and to make calls from the phone system for which you may be charged. The only security available to the system is to check whether the incoming caller ID matches a configured users' Twinned Mobile Number setting. The IP Office cannot prevent use of these features by caller's who present a false caller ID that matching that of a user configured for access to this feature.

In addition to using ** to access mobile call control, the user has access to the following additional controls:

•	Clearing a Call: 52 It may be necessary to clear a connected call, for example after attempting a transfer and hearing voicemail or ringing instead. To do this dial * for dial tone and then *52 (this is a default system short code and can be changed if required).

•	Return to Dial Tone: ## Return to dial tone after getting busy, number unobtainable or short code confirmation tones from the IP Office.

1.	License Mobile Features Enter the licenses for Mobile Twinning and confirm that they are valid by merging and retrieving the configuration.

2.	Configure the user for Mobile Twinning and Mobile Call Control On the User \| Mobility tab do the following:

•	The match must be at least 6 digits. If either the CLI or the Mobile Twinned Number is less than 6 digits no match will occur.

•	Matching is done for up to 10 digits. Further digits are ignored. If either the CLI or Mobile Twinned Number is less than 10 digits, matching stops at that shorter length.

•	If multiple matches occur the first user in the configuration is used. IP Office Manager will warn against configuration where such a conflict may exist.

3.	On systems with some unsupported trunk types, further changes such as Outgoing Group ID, system shorts codes and ARS may be necessary to ensure that calls to the mobile twinned numbers are only routed via the

The IP Office can be configured to allow Mobile Call Control users to use this function when making an incoming call to the IP Office. This requires the user to make the incoming call from the same CLI as their Mobile Twinning Number (even if they do not actually use Mobile Twinning).

•	If the caller ID does not match a Twinned Mobile Number of a user with Can do Mobile Call Control enabled.

1.	License Mobile Features Enter the licenses for Mobile Twinning and confirm that they are valid by merging and retrieving the configuration.

2.	Configure the user for incoming Mobile Call Control On the User \| Mobility tab do the following:

•	Set the Twinned Mobile Number to match the CLI of the device from which the user will be making calls.

3.	Add a FNE Short Code In the system short codes section of the configuration add a short code similar to the following. Key points are the use of the FNE Service feature and the Telephone Number value 31.

4.	Add an Incoming Call Route for the user Create an incoming call route that matches the user's CLI and with the FNE short code created above as its destination.

5.	On systems with some unsupported trunk types, further changes such as Incoming Group ID changes may be necessary to ensure that only calls received on trunks that support Mobile Call Control are routed to this short code.

A new FNE code (FNE32) is supported for the IP Office 4.2 Q3 2009 maintenance release and higher. For a Mobile Call Control or one-X Mobile client user, FNE32 immediately redials on switch the DDI digits received with the call rather than returning dial tone and waiting for DTMF digits as with FNE31. This is called Mobile Direct Access (MDA).

MDA requires the user's external telephony provider to provide a direct trunk with DDI to the IP Office (ie. an ISDN or SIP trunk). By assigning a specific incoming line group ID to the trunk, an incoming call route can be created for the same line group ID with blanks incoming number and incoming CLI fields. The destination is a short code set to FNE32.

User validation is performed using the CLI in the same way as for normal Mobile Call Control. In addition the call will be rejected no DDI digits are provided. Once connected the user can use the other Mobile Call Control features such as **.