Reference8:Administration/PBX/Objects/Edit Forks: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
With this page call forking can be configured for a user. This means a call for this user is not only sent to endpoints registered to the user object, but also to the forking destination (No/Name). If a mobility object is configured for the forking, the phone identified by the forking destination can use the mobility functions. A delay can be configured for the call to the mobile endpoint. This delay is not supported for normal call forking without mobility functions. | With this page call forking can be configured for a user. This means a call for this user is not only sent to endpoints registered to the user object, but also to the forking destination (No/Name). If a mobility object is configured for the forking, the phone identified by the forking destination can use the mobility functions. A delay can be configured for the call to the mobile endpoint. This delay is not supported for normal call forking without mobility functions. | ||
Operator calls from a waiting queue are not sent to forking destinations. | |||
== Properties of Mobility== | == Properties of Mobility== | ||
| Line 10: | Line 11: | ||
|- | |- | ||
|valign=top nowrap=true|'''Device''' | |valign=top nowrap=true|'''Device''' | ||
|Optional, the Device name of the User can be configured here. This name is used by SOAP (TAPI) to address this device for example when initiating a call. | |||
| | | | ||
|- | |- | ||
| Line 16: | Line 18: | ||
| | | | ||
|- | |- | ||
|valign=top nowrap=true|'''Disable'' | |valign=top nowrap=true|'''Disable''' | ||
|Disabling the Mobility features for the mobile device, this can be en/disabled via [[Reference8:Administration/PBX/Objects/DTMF_Features#Enable.2Fdisable_mobility |DTMF featurecodes]] | |Disabling the Mobility features for the mobile device, this can also be en/disabled via [[Reference8:Administration/PBX/Objects/DTMF_Features#Enable.2Fdisable_mobility |DTMF featurecodes]] | ||
| | | | ||
|- | |- | ||
|valign=top nowrap=true|'''Call-Waiting''' | |valign=top nowrap=true|'''Call-Waiting''' | ||
|Enable or disable call- | |Enable or disable call-waiting for the mobile endpoint, if a mobile endpoint is in a call a call waiting tone will be played from the PBX to the mobile endpoint via the RTP stream. | ||
|- | |- | ||
|valign=top nowrap=true|'''GSM-License''' | |valign=top nowrap=true|'''GSM-License''' | ||
Latest revision as of 14:06, 8 January 2013
With this page call forking can be configured for a user. This means a call for this user is not only sent to endpoints registered to the user object, but also to the forking destination (No/Name). If a mobility object is configured for the forking, the phone identified by the forking destination can use the mobility functions. A delay can be configured for the call to the mobile endpoint. This delay is not supported for normal call forking without mobility functions.
Operator calls from a waiting queue are not sent to forking destinations.
Properties of Mobility
For the function of the Mobility features a Mobility license must be installed.
| Object | The Mobility Object (Long Name) must be set, if the mobile endpoint (GSM Phone) needs to use the mobility features . | |
| Device | Optional, the Device name of the User can be configured here. This name is used by SOAP (TAPI) to address this device for example when initiating a call. | |
| Delay | A Delay in seconds can be configured to call the mobile endpoint | |
| Disable | Disabling the Mobility features for the mobile device, this can also be en/disabled via DTMF featurecodes | |
| Call-Waiting | Enable or disable call-waiting for the mobile endpoint, if a mobile endpoint is in a call a call waiting tone will be played from the PBX to the mobile endpoint via the RTP stream. | |
| GSM-License | When using the innovaphone GSM client a GSM license is needed and need to be activated |