Course10:Basic - PBX - Advanced Object Properties and Behaviour

From innovaphone-wiki

Jump to: navigation, search

This book explains more advanced properties and behaviour of the PBX user object as well as their related function keys. Most of them apply to many of the PBX object types.


Call Forwardings

The innovaphone PBX supports a number of fish-help.png call forwarding types. Call forwarding destinations screenshot.png can be configured using its extension (No, the Number field in the destinations object properties) or its (short) name (Name, the Name field in the destinations object properties). This is done in the PBX's PBX / Objects list.

Btw: call diversion and call forwarding are often used as synonyms.

Calls to Objects with no Endpoint registered to

An innovaphone PBX has all the call forwarding types known from legacy PBX systems. A special case though is a call to an object where there is no endpoint registered at all for. This situation triggers the CFNR.

Rejecting Calls

Users can reject alerting calls on the phone (depending on the phone e.g. by pressing the disconnect key). This will trigger a CFB.

Forwarding Loops

It is quite easy to unintentionally configure call forwarding loops . These are detected by the PBX and the CFx causing the loop is ignored.

For example, in a screenshot.png simple scenario where there are extension 10, 20, 30 and 40 and there are CFUs like


When 30 calls 20, the call will ring at 10, although there is a CFU on 10. This is because executing this CFU to 30 would close the loop. And is thus ignored.

Conditional Forwardings

fish-help.png Call Forwarding can be made depending on some properties of the call to be forwarded.


screenshot.png When an Only or Only Not rule is configured for a call forwarding, the call is only forwarded if the start of its source number matches the rule's No entry (or the calling name, which is the calling objects Name property value, entirely matches the rule's Name entry).

The calling number provided with the call as well as all the diverting numbers are matched against the rule's No.

Internal / External Calls

Although external calls could be matched as Only From 0, calling numbers are not always safe. External calls can be matched better using the Ext. / Int. switch.

Dynamic Conditions

Call forwards can be made screenshot.png dependant on dynamic conditions (e.g. the time of day). This is done by selecting a condition object (a.k.a. as fish-help.png boolean object) for the Bool property of the call forward setting.

The call forward is triggered only if the condition described in the boolean object is met (or is not met, if the Not check mark is ticked too).

Implicit Forwarding

Various screenshot.png implicit Call Forwarding are set in the fish-help.png Trunk object configuration. Those apply to incoming calls through the trunk to a destination where the call forwarding condition is met.

This is a convenient way to configure the handling of standard call forwarding situations such as CFB (Busy) and CFNR (No Answer) globally. In addition, special situations like calls to incomplete (Incomplete) or wrong (Invalid) extensions can be handled.

Most of those implicit forwards are of course optional, the PBX works fine without setting those. However, one of them, Loopback, you will want to consider for sure! If you don't set this, external callers will be able to call in to your PBX and straight call out to the trunk again. This way, you will bear the cost!

Note that implicit forwarding settings apply to calls through (that is, from) the trunk object to local extensions whereas call forwarding set on the trunk apply to calls to the trunk!

Disabling Forwarding

Any call forwarding can be disabled explicitly by configuring a minus (-) as call forwarding destination. This does make sense for CFNR and CFB only.

This will also disable implicit forwardings imposed by the trunk object.

(Overall Description) This feature is essential on fax lines when you set Busy (CFB) or No Answer (CFNR) globally on the trunk line. If for example, such calls are forwarded to the switchboard, an incoming fax to a busy fax device will be forwarded to the switchboard too. This will probably not make the receptionist happy! You should then disable call forwards of both types for the fax line.

Object Specific Handling of Call Forwarding

Call Forwarding might be handled specially by objects of a certain object type.

For example, a fish-help.png CFB set on a trunk will not trigger when the trunk already has an active call as a CFB on an user object would. Instead, it is triggered when the object called through the trunk (usually an external number) is busy. You should refer to the Call Diversions section for the respective objects for details.

Setting Call Forwarding on the Phone

Call Forwarding information is stored in the PBX and can be set from the PBX's configuration user interface thus.

However, for end users, it is much more convenient to set them directly from the phone. As H.323/H.450 defines a standard to communicate call forwarding settings between an endpoint and the PBX, H.323 based devices can be used for this. innovaphone phones allow end-users to do this through the Menu / User Setup / Call Diversion menu. fish-help.png Default forward destinations can be set in the Favorite Diversions properties of the phone's Phone / User-1 / Preferences tab.

However, only basic call forwarding settings can be set this way. Conditional forwarding properties can not. As they can't be set, they are not shown on the phone either. This is why such call forwarding settings are referred to as administrational call forwards sometimes. When set in the PBX, they are not shown on the phone and cannot be changed or deleted from the phone. In V10 users can set non-conditional call forwards types from within fish-help.png myPBX.

In SIP, there is no such protocol available and some SIP endpoints will instead perform limited call forwarding procedures autonomously. Setting the PBX's call forwarding settings is not possible thus.

Call Forward related Function Key

innovaphone phones feature a fish-help.png function key type fish-help.png Call-Forwarding. This function key provides a very convenient way of switching between a pre-defined set of call forwards (such as e.g. in-office, on-the road etc.).

Up to 4 independent screenshot.png forward settings can be defined. Users can then toggle through those settings by pressing the function key.

The current status of the call forward setting is retrieved from the PBX and matched to the defined sets. If none matches, the idle state is assumed.

This feature is not available when the phone is registered via SIP.

The CFNR Timeout

The fish-help.png timeout for the CFNR function is set in the Response Timeout property in the PBX / Config / General tab of the PBX. If not set, the timeout is set to 15 seconds. It can be overridden for each individual object in the Response Timeout field of the object's fish-help.png properties.

Limiting Call Forwarding

Call forwarding can be limited by setting the Diversion Filter in the object's fish-help.png PBX/Objects properties (you will learn how to set up filter in one of the next chapters). The filter is evaluated on call forward time, not on call forwarding setup time.

This allows for example to disable costly call forwards to external recipients (such as mobile phones).

Call Transfers

In contrast to call forwarding, call transfers are initiated by the end user on a call by call basis. A transfer can be initiated in alerting and connected state, both blind transfer and consultation transfer is available, as well as call deflection.

A blind transfer is initiated using the redial key on the phone. The call is redirected to the new destination right away and thus disappears from the transferring phone.

For a consultation transfer (which is available in connected state only), the call is put on hold, a new call is placed to the intended destination. The 2 calls are then transferred by either putting the receive on hook (transfer by on-hook can be disabled by setting the No Call Transfer on Hook-On property in the Phone / Preferences tab of the phone) or via the R / 4 fish-help.png R-key sequence or by using a fish-help.png Transfer function key (function keys can be defined in the Phone / User-1 / Function-Keys tab.

When a consultation transfer is initiated while the consultation is still in alerting state, it is sometimes referred to as semi-blind transfer.

The Redirect Function Key

The fish-help.png Redirect function key essentially performs a blind transfer of an alerting call, much like pressing the redial key would do. This is also known as call deflection or call redirection.

By default, when there is an active (connected) call when the function key is pressed, the redirection is performed on the first waiting call. This is convenient to get rid of call waiting on a call-by-call basis (as opposed to setting a CFB).

If the Redirect Active Call property is set in the function key configuration, the active call is redirected instead.

The Recall Timer

When a blind transfer or call redirection is attempted but there is no response to it, the call can be transferred back to the original transferrer. This feature needs to be enabled by setting the fish-help.png Recall Timeout property in the PBX / Config / General tab of the PBX.

Controlling external Transfers

By default, transfers of external calls to external destinations are not allowed.

This is because such transfers would create calls which impose costs on the owner of the external trunk line. At the same time, as they disappear from the transferrers phone, they cannot be controlled any further.

To allow external call transfers, you need to enable the fish-help.png Enable External Transfer check-mark on the PBX's PBX / Config / General configuration tab.


Filter provide a generic and flexible means to define fish-help.png call filters. They are configured in the PBX's PBX / Config / Filter configuration tab.

A filter defines a set of number prefixes which are matched against the called party number of a call. They can be made dependant on the current status of a boolean object at match time. If one of the numbers matches the head of the called number, the filter is applied to the call.

This can be used for restricting call destinations for PBX (user) objects and to limit call forwards set for an object. For example, you would define a filter that screenshot.png disallows calls to the local trunk line on non-business hours and screenshot.png apply it as Filter setting to individual PBX (user) objects to make sure users need to place external calls through the switchboard then.

Another use of filters is for the prevention of call forwards. You would screenshot.png apply the same filter as Diversion Filter to make sure external call forwards are disallowed outside of business hours.

Filters are generally checked at execution time, not at configuration time.

Disallowing incoming external Calls

Filters are applied to the called party number, so they control whom a given user object can call. To control who may call a certain user, appropriate filter would need to be set for all potential callers.

A common case of restricting incoming calls is to disallow direct calls to an extension from external. This can be achieved by simply setting the fish-help.png Reject ext. Calls check mark on the user. Note that in this case neither CFNR nor CFB are triggered, but CFU is honoured. Also the rejected call will trigger the fish-help.png Invalid destination property defined in the Trunk Line object.

Manipulating the Number sent

When an endpoint registers to an user object and then places a call, the call will normally convey the user objects Number property as CGPN.

Changing the CGPN

It is possible to change the CGPN by setting the fish-help.png Send Number property of the calling object.

In a help desk scenario, you may want to set the Send Number property to the help desk number for all agents to make sure individual extensions are not sent to called customers.

Suppressing the CGPN

As an alternative, a call can be initiated with the calling line id explicitly suppressed. This must be done by the calling endpoint (i.e. the phone). There are several options to do this.
Setting the User Default

In the Menu / User Setup menu of the phones, the Number Presentation entry will set the user's default for the calling line id suppression. This is also available in the Phone / User-1 / Preferences tab's Hide own Number property.
Using a Function Key

An equivalent setting can be done by configuring a fish-help.png Hide Own Number function key in the phone's Phone / User-1 / Function-Keys tab. When the key is in the Active state, calls will have their CGPN suppressed.
Call by Call

When using prepared dialling, pressing the menu key before the call is actually initiated will show a context menu on the phone that allows to turn the calling line id on and off for this call.

Limit the Number of concurrent calls

The Busy On ... Calls property allows to reject calls to the object when there are already as much calls in this direction active for this object (counting all calls from all endpoints registered with this object) as configured for this property. Setting it to 1 for example will make sure no additional call is sent to an endpoint registered with this PBX (user) object, as long as there is already one. However, such an endpoint can still place multiple concurrent outgoing calls.

This is useful to cope with devices that do not handle call waiting situations gracefully.

Please note that when is Busy On ... Calls set to 1, there will be no call waiting situation on the user's device, as the extraneous calls are never sent to the device. As a result, such calls will also not be listed in the devices call list! It is thus generally not recommended to use this setting for users with innovaphone telephones. They should rather be handled using the phone's call waiting configuration (see next chapter).


If the object is of type fish-help.png Gateway or fish-help.png Trunk Line, then calls both from and to this object will be counted extraneous and rejected. This effectively limits the total number of calls at any point in time for the endpoints registered.

Call Waiting

When a call is signalled to an endpoint and there is already an active call, then this is referred to as call waiting. The handling of such a situation depends on the endpoint used.

The fish-help.png Call Waiting property in the phone's Phone / User-1 / Preferences settings defines how an innovaphone phone handles this situation. When set to disabled, a user busy will be signalled to the caller. When set to one of the enabled modes, alerting is signalled to the caller and the call is presented to the phones user. The default tone option will alert the user every so often with a call waiting tone. The beep once option will alert the user with a call waiting tone only once, whereas the silent option will play no call waiting tone at all.

The fish-help.png Call Waiting function key allows the user to turn call waiting on and off conveniently. Call waiting is turned off in idle state.

Twin Phones

Sometimes, multiple phones are registered to a single user object, for example when an user has both a fixed line and a mobile (DECT, Wifi) phone sharing the same number. In this scenario, additional incoming calls should be signalled to the active phone only, as otherwise the phone the user is currently not using would ring. Setting Busy On ... Calls doesn't help really as it would inhibit the call waiting to the currently active phone.

To handle this scenario, set fish-help.png Twin Phones in the user's object properties. If so, additional calls are signalled to the currently busy phones only, leaving it to this phone to handle the call waiting situation.

Transfer between Twin Phones

However, when a twin phone calls itself, the call is not sent to the calling phone but to all others registered to the object. This allows a user to transfer a call from one of his twin phones to another (e.g. from the fixed line phone to the DECT leave the desk while keeping the call).

Do not Disturb

An innovaphone phone can be brought into do not disturb mode (DnD) by either pressing the micro off key on the phone in idle mode or using the fish-help.png Do not Disturb function key.

In DnD mode, the phone will not ring on incoming calls. There are various modes available, either in the Action area of the Do not Disturb function key configuration or in the fish-help.png Do Not Disturb area of the phone's Phone / User-1 / Preferences settings.

The modes include the option to send an absent message to callers while the phone is in DnD mode. This message can also be defined via the phone's Menu / User Setup / Do not disturb / Out of Office Msg. menu.

Hiding an Object from the PBX Directory

When an object is created in the PBX, its properties are available from the PBX via LDAP. Phones will take advantage of this and include the new object in their so-called PBX Directory.

Directories are used whenever an outgoing call is initiated with a name dialled instead of a number. Even more, the directories are searched for a matching number when an incoming call without name identification is received.

Sometimes however, the object information should rather be hidden to other users so that they cannot locate the object via the directory. In this case, set the Hide from LDAP object property.

Applying basic Properties to a Number of Objects

When many objects share similar properties, a fish-help.png configuration template object can be screenshot.png created and screenshot.png applied to other PBX objects. These objects will then share the settings present in the template, unless they are not explicitly overridden in the receiving object.

Templates can be screenshot.png nested.

Managing Phone Configurations

Traditionally, phone configurations used to be stored on the respective phones directly. While this is easy and convenient, it turns out to be a problem when many phones need to be managed. Often, similar settings shall be applied to several phones, which is difficult and error prone to do. Also, when a phone is replaced, its configuration needs to be restored from a recent backup.

This is why the user-specific part of the phone configuration can be stored in the PBX. To screenshot.png enable this feature, tick the fish-help.png Store Phone Config check-mark in the user object's User configuration tab. You will then find a link config in the Phone column of the PBX's PBX / Objects tab. The phone configuration is screenshot.png now shown both in the PBX's configuration UI (by clicking on the config link) and the phone's configuration UI.

Normally, any existing configuration on a phone is retrieved and saved in the PBX's phone configuration. However, it is possible to discard any phone configuration. See the fish-help.png Store Phone Config and Discard Config on Phone properties for more details.

Using Templates for Phone Configurations

Phone configurations can also be stored in fish-help.png configuration templates. If a configuration template screenshot.png includes a phone configuration and this template is assigned to a PBX (User) object, the user will inherit the phone configuration from the template.

If the user itself has a phone configuration stored in the PBX, the template's and the user's configuration are merged and then applied to the actual phone.

Finally, a configuration template can screenshot.png inherit up to 4 other configuration templates. This can be used to build a template tree.


fish-help.png Groups can be created by screenshot.png assigning group names to PBX objects.

A group defines a set of PBX objects that in some way belong together. A single object may belong to many groups.

Group membership can be active or passive. When a group member is active, then it somehow knows about the other members in a group. Whereas a passive member has no knowledge of the other group members.

Consider 5 objects which are member of the same group. 2 of them are active.

screenshot.png Group Membership Types

User 1 and User 4 know about the other objects as they are active members of the group. All others don't.

Objects can be active member in one group and passive member in another. Objects can also be active members of more than one group. Group membership alone does not do anything, neither passive nor active membership. However, groups are used to configure various other features.

Groups are limited to 2000 members. Don´t use existing "Name" for group name.

Group Pickup

Active members of a group can pick alerting calls for other members in this group.

There are several ways to do this.

Pickup using the DTMF Object

If there is an fish-help.png DTMF Features object present in the PBX, any endpoint can initiate a group pickup by dialling the *0# feature code. If there is an alerting call in one of the groups the caller is an active member of, this will be connected to the previously alerting call right away.

It is also possible to pickup a specific call if more than one are currently alerting. This is done by dialling the *0*<user># feature code, where <user> is the extension of the object the call is alerting on.

For innovaphone IP phone users, it is usually better to use the fish-help.png Pickup or fish-help.png Partner function key. The DTMF feature is useful for H.323 devices that do not support call pickup, for SIP devices and for non-IP devices, such as DECT phones.

Pickup using the Pickup Function Key

innovaphone phones can do pickups via the fish-help.png Pickup function key (configured in either the Phone / User-1 / Function-Keys tab of the phone or in the config dialogue of the PBX's PBX / Objects object configuration). This function key will be idle as long as there is no pick-able call and go to the active state when there is one.

When in active state, the alerting call will be signalled to the user (there are several options available like turning on an LED, issuing an audible alert or hiding the involved party numbers). When the function key is used in active state, the PBX will send the call to be picked to the picking phone too. The user can then examine the detailed call info presented with the new call and decide whether to really pick the call or not. This is in contrast to how the DTMF object works, as this will connect the picked call right away.

For this to work, the picking phone must be aware of all pick-able calls of course. This is done by setting the fish-help.png Group Indications property in the picking users PBX object configuration. This property is set to the name of a group the picking user object is an active member of. The PBX will send status information for all objects that are known to the picking user object due to the group membership.

screenshot.png Group Indications

Group memberships can become quite complex. It is a common configuration mistake to configure a Pickup function key but no appropriate group indications.

The Partner Function Key

The fish-help.png Phone/User/Function-Keys/Partner Partner function key allows to pick calls quite similar to the Pickup function key. However, it does not perform a group pick up. Instead, each partner function key is explicitly bound to one other PBX object (the partner object). The partner object must be configured in the Partner Identification properties of the phones function key definition.

Just like with the Pickup function key, the user that has the Partner key defined on his phone normally needs to have a proper fish-help.png Group Indications in his own PBX user object defined.

When a call alerts at the partner object, the function key will signal it and pressing the key will have this call alert on the users phone just like with the Pickup key.

However, the Partner function key can do much more.

Monitoring the Partner's Busy State

When the fish-help.png Partner key is configured correctly, it will not only show alerting calls that may be picked up. It will also show active calls along with the connected parties number (depending on key configuration, the Show connected party in busy state property must be set in the Partner function key properties).

Monitoring the Partner's Presence State

The Partner key can also display the fish-help.png presence information of your partner. For this to work, you need to switch on the fish-help.png Subscribe for Presence check-mark in the function key definition.

Busy vs. Presence State

A user's presence state is different from his busy state. The busy state includes phone usage information only, that is, if the user has call, if it is alerting or connected, which numbers are involved. The presence state instead only has a condensed notion of the user's phone activity (the so-called on-the-phone state element). However, in addition to that, further information such as an activity (lunch, meeting, vacation...), a user defined note or the general ability to receive instant messages may be included in the presence state. In fact, presence states can be utterly complex, but most software currently available will only make use of the elements mentioned.

In the PBX, the users fish-help.png presence state can be edited in the Presence column of the PBX / Objects list. The end user can also edit it directly using the phone's User Setup / Presence menu.

Obtaining States

There is however another huge difference between busy and presence state. The busy state is sent proactively to interested parties. This is controlled by the group configuration discussed before.

The presence state however is requested by interested parties. So when a Partner function key has the Subscribe for Presence check-mark set, it will send a request to that effect to the target user's PBX. There is no need to touch the PBX configuration for this to work. The only thing to make sure is that the requesting user has the fish-help.png right to see the target user's presence state. This is configured in the Access column of the PBX's PBX / Objects list.

Also, as the requesting party sends a request to the target users PBX, obtaining the presence status works cross-PBX (although in this course you will not deal with multi-PBX configurations). Group indications are sent only between users registered with the same PBX!

The presence state will also be sent back to a user calling the object. The calling user will see the status in his phone's status line while the call is alerting.

A second way of defining Access Rights is by using groups. Access rights are implicitly assigned to active users of a PBX user group. Active group members can see the presence and call information of other users in the group. Group Indications are not needed in this case, since the group-information is displayed on a phone by using the Subscribe for Presence mechanism explained before.
Access rights assigned to users/groups/domains by means of a Config-Template or by the user himself, overwrite access settings inherited by groups.
The recommended way of granting users access to your presence is by using Access Rights.

Using Dialog Info as an Alternative to Group Indications

Requesting the Dialog Info from the partner object is an alternative method to obtain the remote users busy state. As with presence info, this information is not sent proactively from the partner object to the requesting user like group indications are. Instead, the user (in fact, the phone) interested in the partner object's busy state send a dialog info subscribe request to the partner object's PBX. It will then receive the information as responses to the request. Again, as for requesting the presence state, this does not require group indications to be configured. Instead, the partner object must fish-help.png allow the requesting user to obtain dialog info. This is configured in the Access column of the PBX's PBX / Objects list.

Dialog Info is used to obtain the partner object's busy state when the Subscribe for Dialog Info check-mark is ticked in the the fish-help.png Partner function key definition. If so, no group indications are required or used any more for this function.

From V9 on, this is the recommended method to implement the partner key. However, for compatibility reasons, the method based on group indications is still valid.

Again, similar to the previous chapter, you can use groups to define Access Rights.

Calling the Partner and Intrusion

When there is no alerting call for the partner object, pressing the Partner function key will initiate a call to the partner.

The function key can be configured such that when the partner is already engaged in a conversation, the call is initiated as an intrusion call (fish-help.png Perform Intrusion if Partner is busy). An intrusion call connects immediately and creates an implicit 3 way conference between the active call before the intrusion and the intrusion call. The intruder is then part of the intruded call.

By default, both parties of the original call will hear an intrusion tone. This can be disabled though using the fish-help.png No Local Intrusion Tone property in the Phone / Preferences configuration tab of the respective phones.

The Partner function key can be configured such that the call is silently intruded to. Instead of creating a 3 way conference, this intrusion type will create a uni-directional channel from the intruded phone to the intruder. The intruder will not be heard by the original call parties and no intrusion tone is sent. This type of intrusion is configured by selecting Silent Monitoring as the value for the Type property in the Partner fish-help.png function key configuration properties.

Call intrusion needs to be enabled using the fish-help.png  Enable Call Intrusion property on the calling phone's Phone / User-1 / Preferences configuration tab.

The Dial Function Key

The fish-help.png Dial function key defines a quick dial key to a fixed destination number. The function key is available both in the phone's idle state and when an active call is present.

By default, when a call is present, the previously active call is put on hold and a new call to the destination is created. However, when the Send in Active Call property is set in the function key configuration, no new call will be created in this case. The digits from its Number property are sent within the current call instead. If the call was already connected, the digits are sent as DTMF. If not, the digits are sent like single digits sent in overlapped dialling mode.

When no call is present, and the Prepare property is set in the function key configuration, the phone will go into the prepared dialling mode just like as if you had dialled the digits of the destination number on the phone's keypad. You then have the chance to edit the number before you go off hook and initiate the call.

Announcement Calls

When the fish-help.png Announcement property is set in the function key configuration, the call will be sent as an announcement call. Such a call will be connected right away. There is no need for the recipient to go off hook for this. Instead, the phone goes into hands-free mode.

For this to work, announcement calls must be enabled in the Allow Outgoing property of the fish-help.png Announcement Calls area of the calling phone in the phone's Phone / User-1 / Preferences configuration tab. Also, the destination phone may choose to reject any incoming announcement call for a given registration by setting the Reject Incoming property.

By default, the announcement call is connected and the destination phone's microphone is turned off. This way, silent surveillance of a room is inhibited. If surveillance is desired, the destination phone needs to set the Micro On property.

A phone can be configured to accept any call as an announcement call, even those that have not been initiated as such. This can be done by setting the Treat Incoming as Announcement property for this phone.

Any announcement call takes precedence over currently active calls (except if the currently active call is an announcement call too). That is, any currently active call on the destination phone when an announcement call comes in is put on hold and the connected announcement will become the active call.

Call Parking

Calls can be parked. When a call is parked, it is disassociated from the object it has been active on when parked and is placed in to a special area on the park destination object, occupying a numerical park position (starting from 0). The call will disappear from the requesting phone and the remote end will hear music on hold.

Parked calls differ from held calls in that they disappear from the callers phone completely as long as they are parked. Also, other users can un-park the parked call which then looks much like a call pick-up. This allows calls to be moved between users without a call being made between source and destination (in fact, the source doesn't even need to be able to call the destination).

When no park position is specified during park or un-park, the park area is treated like a queue.

Park using the DTMF Object

If there is an fish-help.png DTMF Features object present in the PBX, any endpoint can initiate a park to its own PBX object by dialling the *16<position> feature code, where <position> is a one-digit park position from 0 to 9. Likewise, feature code #16<position> will un-park the parked call. The un-parked call will be connected to the caller right away.

If the call is to be parked to another PBX object, feature code *17<position><target> and #17<position><target> will do.

Like with all DTMF object features, this will work with just any phone.

The Park Function Key

The fish-help.png Park function key allows a user to park the current call to a specific extension. Such calls can then be un-parked later on using the same function key. The extension the call is being parked to is set in the Number property of the Park Destination area in the Park function key's configuration.

Any un-parked call will appear as an alerting call (just like when picking a call) on the callers phone. However, if you decide not to un-park the call by pressing the disconnect key, the parked call will be disconnected and the previously parked party will see a user busy indication.

The Park function key will work only if the user receives group indications from the object the calls are parked to (that is, the object defined by the properties in the Park Destination area of the function keys configuration).

Line Key Feature in the Trunk Object

Any incoming or outgoing call through a fish-help.png Trunk Line object will automatically get a parking position assigned, even though the call isn't parked yet. The Trunk Line object will send group indications for all calls. Each call will retain this parking position as long as it flows through the Trunk Line object.

This allows other users to configure separate fish-help.png Park function keys for each available B-channel in the Trunk Line object. These would specify the Trunk Line object in the Park Destination area of the function key configuration. The Position property would be set to ascending numerical values starting with 0.

With these keys - a.k.a. as line keys - a line can be acquired, monitored, a call can be parked on the line and un-parked up from the line. This effectively simulates an old style line-key telephone system.

In such cases, you should enable the Trunk Line flag, a new option which synthesizes the behaviour previously obtained using Park Active Call before Unpark and Automatic Connect after Unpark from Version 7.
Personal tools