Reference13r1:PBX/Objects/Edit Forks

From innovaphone-wiki

Jump to: navigation, search
There are other versions of this article: Reference8 | Reference9 | Reference10 | Reference13r1 (this version)

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. 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 require a UC license to be sent to forking destinations.

No/Name
Forking destination
Bool/Not
The forking can be turned on and off by a Boolean object. With the Not checkmark the state is inverted.

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.
Mobility license is required
Device
The Device name of the User should be configured here (e.g. "Smartphone"). This name is used by SOAP (TAPI) to address this device for example when initiating a call, by myPBX to enable/disable Mobility for the User (on the Call Forward settings Screen of myPBX) and for Mobility Client OptiCaller for HTTP CallBack/CallThrough.
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. See R-Key Functions for waiting calls handling options.
Mobility features are required
GSM-License
When using the innovaphone GSM client a GSM license is needed and need to be activated. NB: obsolete
Min-Alert
The minimum time in seconds a call must ring on the mobile phone until it can be accepted. If the call is accepted before this time, the call is rejected by the PBX. This way it can be achieved that the announcement from a mobile provider for phones not available does not accept a call and calls can be accepted on a fixed phone on the same number in case the mobile phone is switched off. The alert time is measured from the alert to the connect signalling. If there is no alert message (e.g. because there is a connect right away), the alert time is counted as null. Note: If the carrier doesn't send any Alert/180 Ringing, you may need to enable Carrier w/o Alerting .
Mobility features are required
Max-Alert
Maximum time the mobile phone rings. After this time the PBX terminates the call to the mobile phone. This way it can be avoided that the mobile voicemail accepts the mobility call.
Mobility features are required
Personal tools