Revision as of 17:07, 26 January 2011
The Mobility Object provides mobile extension services for users. These services are call waiting, hold retrieve, transfer and delayed call to a mobile extension. For a user, at least one forking to a mobile number must be configured (using the Fork column in the PBX Objects tab) and within the forking configuration a Mobility object must be selected.
Configuration
Tone Interface
|
An PBX object to which a dial tone provider is registered. This can be used to off-load the media streaming for dial tones from the PBX. If left empty the local HTTP interface is used for dial tones
|
R-Key
|
DTMF sequence which is interpreted as R-Key (hook-flash). Default is '**'.
|
R-Key Functions
With the R-Key sequence the services of handling multiple calls can be invoked. In the following table R-<digit> means the DTMF sequence for the R-Key followed by the DTMF for <digit>. For example if an R-Key sequence of '**' is configured R-0 means a DTMF sequence of '**0'.
R
|
Put active call on hold and get new dial tone. If there are other held or waiting calls, there will be a delay of 3s until this is executed.
|
R-0
|
Reject a waiting call
|
R-1
|
Disconnect the active call and retrieve a held call.
|
R-2
|
Put the active call on hold and retrieve the held call.
|
R-3
|
No functionality, reserved for 3pty conference.
|
R-4
|
Transfer held call to the active call. Just hanging up the call on the mobile device, when an active and a held call is present, does the same thing.
|
R-#
|
Put active call on hold and get new dial tone in case there are already held or waiting calls. Same as 'R' and wait for timeout.
|