To start this part of the exercise, be sure to load the more_pbx_details start configurations to the devices.

This will add a few users to your PBX on the IP411LEFT and register your phones. Be sure to wait for all your phones to  be registered before you proceed.

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. using the  reject symbol or by pressing the disconnect key). This will trigger a CFB.

---

 Call Forwarding can be made depending on some properties of the call to be forwarded.

CGPN

 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

Call forwards can be made  dependant on dynamic conditions (e.g. the time of day). This is done by selecting a condition object (a.k.a. as  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).

---

You will find a  sample boolean object called if-Working hours in your start configuration on the PBX / Objects. This object is configured so that it is "true" during working hours.

Various  implicit Call Forwarding are set in the  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), wrong (Invalid) extensions or calls which were rejected by the user after alert (Rejected) can be handled. If you use the Name field to specify the target here, it must correspond to the Name property of the target object.

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! This setting handles external calls to an extension which is the access code for your trunk (most often 0). This is most often used to call the switchboard (e.g. +49 7031 73009 - 0). 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!

---

In your configuration, you will see a Trunk Line PBX object called Trunk. Please configure this trunk so that incoming calls from extern through this trunk

• which are not answered
• as well as those which call out to an external number again

will be delivered to the user Edward Hyde.

---

All these target settings are available both in the Trunks PbxManager plugin and the advanced UI (in the Trunk tab of the PBX Trunk object editor).

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

This will also disable implicit forwardings imposed by the Trunk line object.

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 would be forwarded to the switchboard too. This will probably not make the receptionist happy! You should therefore disable call forwards of both types for the fax line.

---

In you configuration, you will find a PBX object called Facsimile which is intended to be used as a fax device. Please make sure that calls to this extension are not forwarded when the fax is busy or does not answer.

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

For example, a  CFB set on a trunk (remember: call forwards set on a trunk will be evaluated when you call to the trunk, that is, for outgoing calls) 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 (see  PBX/Objects for a list of all object descriptions).

Call Forwarding information is stored in the PBX (well, actually active call forwardings are stored there. User specific defaults for forwards currently turned off are stored in the User's App service database) and can be set by administrators from the PBX's configuration user interface thus.

However, for end users, it is much more convenient to set them either from the Profile App in myapps (we have seen this before) or 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 Call Settings page in the telephony app:

 Setting call forwards on the phone



To configure a diversion, press long on the respective button. This opens the edit field. Once configured, you activate/deactivate this diversion with a short press.

However, only basic call forwarding settings can be set both this way and in the Profile App. 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 to the end-user and cannot be changed or deleted by the user.

innovaphone phones feature a  function key type  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.).

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

To add a Call Forwarding function key, you would open Phone / User-1 / Function-Keys on the admin UI. In the Add Key section you enter a key number (functions keys are number column-wise in the phone UI), select Call Forwarding from the Type drop-down and click on Add.

 Setting up a call forward function key

You can define up to 4 independent  forward settings of call forward destinations (CFU (Always), CFB (Busy) and CFNR (No Response)). The user can toggle through the defined combinations using the function key. The current state is shown to the user by labelling the function key with the respective Text value.

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.

---

To practice, define a Call Forwarding function key #8 on the IP111 with 2 separate call forward settings to toggle through as follows:

Text	Type	Target Number
Out of Office	CFU	11
Busy	CFNR	13

The general 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 PBX object (e.g.  PBX/Objects/User) in the  Response Timeout field of the object's properties.

Call forwarding can be limited by  setting the Diversion Filter in the object's properties (see  PBX/Objects/User and  PBX/Objects/Config Template for a list of 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).

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.

Blind Transfer

A blind transfer can be initiated by one of the menu buttons which appear during an alerting or connected call:

 phone-blind-transfer



The first step can also be done by hitting the ''redial'' key on the phone.

The call is redirected to the new destination right away and thus disappears from the transferring phone.

Consultation Transfer

For a consultation transfer (which is available for a connected call 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 receiver 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  R-key sequence or by using a  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 call is still in alerting state (called party has not yet picked up), it is sometimes referred to as semi-blind transfer or semi-attended transfer.

The  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.

When a blind transfer or semi-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  Recall Timeout property in the PBX / Config / General tab of the PBX.

---

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

For example, you would define a filter that  disallows calls to the local trunk line on non-business hours and  apply it as Filter setting to individual PBX 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  apply the same filter as Diversion Filter to make sure external call forwards are disallowed outside of business hours.

---

The filter we have configured in the previous chapter has a significant drawback: it inhibits all calls to extern. What if a user need to call the fire brigade off working hours? We clearly must enhance the filter to allow for some exceptional numbers.

This can be done by specifying more than one condition. All conditions of a single filter are checked until one is found that matches and specifies nok or ok in the Next column. If no condition matches, the call is allowed.

To fix the problem, we can create a list of conditions where the most significant appears first and so forth.

---

We can fix our fire brigade problem by specifying a condition that allows calls to emergency numbers like the fire brigade (112 in Germany) before the more generic rule that inhibits 0.
Please enhance our filter accordingly!

Filters can be chained so that similar patterns do not need to be specified multiple times.

The idea is to specify another filter in the Next column instead of allowing (ok) or disallowing (nok) the call. If such a condition matches, the matching part of the number is removed (for the purpose of further checking) and the chained filter is applied on the remaining number.

See  restricted external calls via different trunk numbers and different number formats in the wiki for an elaborate example.

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  Reject ext. Calls check mark on the User object (or a template that the user inherits from).

Note that in this case neither CFNR nor CFB are triggered, but CFU is honoured. Also the rejected call will trigger the  Invalid destination property defined  in the Trunk Line object.

Filters on Trunk Objects

As with other objects, it is possible to  set a Filter for a Trunk object too. Although the tool tip suggests that this affects outgoing calls, it actually is applied on incoming calls. This is because from the PBX's perspective, an incoming call is an outgoing call from the trunk to another PBX object. So the filter works like for any other PBX object in fact.

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  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 (CLIR). This must be done by the calling endpoint (i.e. the phone). There are several options to do this.

Setting the User Default

Users can set their CLIR preference in the telephony app on hard-phones:

 Setting CLIR



The available options are Always (CLIR on), Never (CLIR off) and Once (CLIR on for next call).

Using a Function Key

An equivalent setting can be done by configuring a  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.

No CLIR on Internal calls

Sometimes you want to suppress the CGPN only for external calls. Internally however, the CGPN should be shown. This can be done by using CLIR (with one of the methods described above) and  set the  No CLIR on Internal calls property in PBX / Config / General.

NB: it is possible to change CLIR on outgoing external calls from "unknown" to a fixed extension. This allows you to configure CLIR for certain users (with or without No CLIR on Internal calls property in the PBX) so that these users will signal a fixed extension (e.g. -0) externally. We will not do exercise it in this course, if you are interested, see Number In in  Gateway/CGPN-Maps.

---

To practice, change the Hide own number setting on John Doe's phone to Always (when John is calling, "unknown" should be displayed as calling party at the receiving end).

Then configure the PBX so that John is shown as CGPN again when he calls internally.

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.

Gateways and Trunks

For objects of type  Gateway or  Trunk Line, the property is called Max Calls. In contrast to the Busy On ... Calls property, calls both from and to the object will be counted as extraneous and rejected. This effectively limits the total number of calls to and from the object (as opposed to only the calls to the object).

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  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  Call Waiting function key allows the user to turn call waiting on and off conveniently. Call waiting is turned off in idle state.

Sometimes, multiple phones are registered to a single user object, for example when a 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 the  Twin Phones property 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

When a twin phone calls its own extension, 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 phone to leave the desk while keeping the call).

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  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  Do Not Disturb area of the phone's Phone / User-1 / Preferences settings.

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 may be searched for a matching number when an incoming call without name identification is received (depending on the Disable Phonenumber Look-up setting).

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 in the PBX object you want to hide from the directory.

---

You have a PBX object in your configuration that is called Facsimile. The Facsimile has Number 9, so you will see it in the search result list when you simply press the 9 key on the phone (or you long-press 3 three times to get an f).

You may consider it useless to call the fax from a phone, so let us exclude it from the phone's directory search result !

When many objects share similar properties, a  Config Template object can be  created and  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.


If the Config Template should be valid on all of your PBXs (if you have more than one), leave PBX and Node empty (this is actually how the Install created the Config User and Config Admin templates - as it is a very rare situation that you don't want to make a template available in all PBXs).

---

To practice, please create a Config Template PBX object called Config Standard on your PBX / Objects that has the properties of the Config User template and adds some more. Be sure to hide it from directory search results. Set a Response Timeout of 5 seconds (you will note that this is an option which is not available in the Templates PbxManager plugin). Assign this template to user Jane Doe. Finally, set a CFNR with target No 11 for Jane Doe.

From Richard Roe's phone, call 12 and wait 6 seconds. See what happens!

The call should be forwarded to Edward Hyde after exactly 5 seconds. Notice the display on Edward Hyde's phone, it indicates that Richard Roe originally called Jane Doe:

 diverted call

Phone configurations can be stored on the respective phones directly. This can be done in the phone's registration specific settings, for example Phone / User-1 / Preferences.

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  enable this feature, tick the  Store Phone Config check-mark in the user object's User configuration tab (as the Install has done when creating the Config User template).

You will find a link in the Phone column of the PBX's PBX / Objects tab (it is called either + if there is no config yet or config). The UI opened when you click on this column looks exactly like the UI the phone provides to set phone-local configuration. However, it will set the phone configuration as part of the PBX's User object. This configuration is then used by all (innovaphone) phones which register with this User object!

If you configure phone-related settings both in the PBX and on the phone directly, the settings on the phone will override the settings received from the PBX. If the Store Phone Config check-mark is ticked in the respective PBX User object, changes done on the phone will be replicated back to the User object in the PBX.

When you need to set these options for many users (which is very likely!), you can set them in a Config Template object rather and assign it to the users. We'll look at this in the next chapter.

Cleaning up existing Phone Configurations

When you set the Store Phone Config check-mark, normally, any existing configuration on a phone is retrieved and saved in the PBX's phone configuration. This ensures that existing configurations on the phone are not lost. The phone configuration is cleared then (so that all configuration is now stored on the PBX).

However, it is possible to discard any configuration present on the phone. See the  Store Phone Config and Discard Config on Phone properties for more details.

Phone configurations can also be stored in  configuration templates. If a configuration template  includes a phone configuration and this template is  assigned to a PBX object, the object will inherit the phone configuration from the template too.

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

---

So please

•  check if the Store Phone Config and Discard Config on Phone check-mark in the Config User template (so that phone configurations are stored on the PBX and existing configurations on the phones are discarded) is set. This should have been done by the Install
  
• Recreate the function key (same parameters) as part of the Config User template this time
• delete the function key definition from John Doe's User object
  
• All user objects (Edward Hyde, Henry Jekyll, Jane Doe, John Doe and Richard Roe) will receive the function key through the Config User template.
  

Have a look at Edward Hyde's home screen on the IP232 (you may need to switch to the home screen by touching the home symbol):

 Function key on IP232

You see the the No CF function key on the screen's lower right, as we have assigned it to Key (that is, position) 8. Touch on the function key and see  how the call forwarding state is indicated.

Now if you also had an  old IP240, you'd see

 Function key on IP240

What a group is

A group defines a set of PBX objects that in some way belong together. This is used a lot in the PBX, for example to define call pickup groups. The administrator would assign group membership to all team members and then allow pickup for this group.

Group membership alone does not do anything, neither passive nor active membership. However, groups are used to configure various other features.

A single object may belong to many groups.

Inner Group Relationships

Not all group members are the same, as group membership can be active or passive.

When a group member is active, it can somehow be viewed as a group leader. In our call pickup example, active members of the group can pick calls from passive members - but not the other way round.

There can be more than one active member in a group. In fact, all members of a group can be active. In our pickup example that would mean that all group members can pick calls from all other group members.

Objects can be an active member in one group and a passive member in another. Objects can also be active members of more than one group.

Limitations

Groups are limited to 2000 members. Groups are known to a single PBX only. If another PBX has a group even with the same name, it is a different group.

Group names can be chosen freely. However, for better manageability, we recommend to use group names that clearly indicate that the name is for a group (such as group-pickup-team1 for example).

While it is possible to use the Name of existing PBX objects as a group name, it is not recommended!

Defining groups is costly. The PBX needs to track record of all group memberships and thus consumes internal memory (RAM). So do not assign users to groups unless it is really necessary!

Active group membership is even more costly, as it requires the PBX to check group members in many situations and thus consumes CPU cycles! So do not assign users active group membership unless it is really necessary!

The  Partner function key allows to pick alerting calls from other users. Normally, 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  function key definition.

Subscriptions

The Partner key uses a mechanism known as subscription to obtain the partner's call information. In addition to that, it can optionally also subscribe for Presence information. This is controlled by ticking (or un-ticking) the Subscribe for Dialog Info and Subscribe for Presence check-marks.

Still, the subscribing user must be entitled to the information. Otherwise, the subscription will not receive any information.

Groups

When the subscribing user is an active member in the same group as the subscribed-to user, subscription rights are granted.

Visibility

Users can define visibility rights which are  listed in the Visibility column in the PBX's object list.

The following are available for visibility right entries:

• the  the Group check-mark is ticked and Name is a group name:
  Each active member of the group is granted visibility
• otherwise the Name in the entry is an @ followed by a domain name (e.g. @dvl-ckl2.net) an:
  Users from that domain are granted visibility. The domain of a PBX user is the value of the System Name property in PBX / Config - if the Use as Domain check-mark is ticked
• otherwise the Name in the entry is a single @:
  This is a catch-all and is effective if no other entry matches
• the Name in the entry is the Name of another user (name or name@domain):
  this particular user is granted visibility

Operation

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. Depending on the various check-marks in the definition, the behavior of the function key can be modified.

The Hide calling Party in alerting State, Hide calling Party in ringback State and Show connected Party in busy State control the display of calling/called party information.

The Do not pick up an alerting Call disables the call pickup function.

However, the Partner function key can do much more as we will see in the next chapters.

---

Partner function keys seem to be a useful thing to have and we should provide them for all of our users. A straight forward approach is to configure it in a template.

There is only one problem: when we do this in a template, then every user that inherits the template has a Partner function key, which is good. But they all will share the same configuration and thus will have the same partner! This does not sound that useful.

•  Add a Partner function key to template Config User at position 4
• set Text for the Idle State to Partner #1
• tick the Subscribe for Dialog Info, Subscribe for Presence and Show connected Party in busy State check-marks

At this point, the Partner #1 key appears on all the phones. However, they are still not functional as we have not defined any Partner Identification.

• open John Doe's phone configuration from the PBX's object list
• you see the  Partner #1 key definition, which is inherited from the template
• open the definition and type Richard as Text in the Idle State and richard.roe as Name in the Partner Identification
  
• from Edward Hyde's phone, call Richard Roe (13), do not take the call

You expected to see Edward's call to Richard so you can pick it? Not so!

• take the call. Now you see  the On the phone note on John's partner key

At this point, you will see the call  indicated on John Doe's phone and you can pick it.

• on Jane Doe's IP112 press and hold the function key next to the Partner #1 label
• the function key editor opens
• press the  key on the right side of the Text: field
• enter johnny into the Text: field
• enter 14 (John Doe's Number) into the Number: field (you need to scroll down a bit)
  
• save your settings
  
• the function key label now has changed to johnny

Jane could have done that herself

• from Edward Hyde's phone, call John Doe (14)

As we have seen, when the Partner key is configured correctly, it will not only show alerting calls that may be picked up. It will also show active (that is, connected) 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).

The Partner key can also display the  presence information of your partner. For this to work, you need to switch on the  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 a 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 (available, away, busy, do not disturb), 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.

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. 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.

The partner function key is configured for intrusion, by  setting the Perform Intrusion if Partner is busy check-mark.

Intrusion must also be enabled on the intruding phone by  setting the Enable Call Intrusion option in the phones Phone / User-1 / Preferences settings. Of course, as with all such options, this can also be set in the PBX user object's phone configuration or in an inherited template.

By default, both parties of the original call will hear an intrusion tone. This can be disabled though  using the 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  function key configuration properties.

---

Let us configure call intrusion for Jane Doe to John Doe.

• enable call intrusion for Jane Doe's phone (tick Enable Call Intrusion)
• configure call intrusion on Jane Doe's Partner function key in conference mode (tick Perform Intrusion if Partner is busy and select Type Conference)
• From John Doe's IP111, call Edward Hyde (11), take the call
  
• The call is indicated at Jane Doe's function key
• Press the Partner function key on Jane Doe's IP112

Jane breaks into John's call and the intrusion is  indicated on Jane's display. Both John and Edward hear the local intrusion tone.

Note that when Jane talks, both John and Edward will hear her. When you change the Type setting in Jane's function key definition to Silent Monitoring and intrude the next call, Jane will not be heard by neither John nor Edward.

The  Dial function key defines a quick dial key to a fixed destination number. By default, when a call is present, the previously active call is put on hold and a new call to the destination is created (this is like the Partner function key behaves in this situation).

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 dialing mode just like as if you had dialed 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.

---

We decide to provide a Dial function key for all users which calls to the fire brigade! As you already guessed, we will put this into the template we already have:

• Add  a Dial function key to the Config User template on position (Key) #3
• Set the Text to Fire Alarm
• Set the Number to 0112 (0 will be our trunk line access code, 112 is the fire brigade (at least in Germany))
  

All users now can quickly issue an alarm, even from within a call.

When the  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   Outgoing: Allow property of the Announcement Calls.

The destination phone may choose to reject any incoming announcement call for a given registration by  setting the Reject property in the Announcement Calls / Incoming section. Also, by setting the Reject if Busy property announcement calls are only rejected when the phone already is busy with another call.

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.

Unless the Reject if Busy property is set, 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.

---

Edward Hyde is Jane Doe's secretary. This is why she needs to be able to perform announcement calls to him. As he often works a little off his phone, he wants to be able to talk to Jane Doe right away in such calls, without going off-hook. However, Jane should not disturb Edward when he already is engaged in a call.

•  Add a Dial function key for Jane Doe on position (Key) #2
• Also  allow outgoing announcement calls for her
  
•  Turn on the Reject if Busy and Micro on properties for Edward Hyde