Aastra OpenCom 100 series, Mounting And Commissioning User Manual

Page: 182 / 256

Telephony
180
change. This function mode is optimised for using busy keys on the system network
(see PBX Networking starting on page 157). Please note the following points:
• Busy key information can be transferred via all connection types of a PBX system
networking: Q.SIG-ISDN, Q.SIG-IP and SIP-Tie-Line. The
Protocol extension option
has to be activated in the bundle configuration for Q.SIG-ISDN.
• Busy keys only function between OpenCom 100 / Aastra 800 communications
systems with the release 10 system software.
• If there are multiple lines available in a bundle for PBX system networking, one of
the lines is selected for busy-key signalling. If this line fails, it can take a few
minutes until the dynamic subscriber list is updated.
Note
The “call number busy” busy-key function is the only one supported for PBX system
networking. The “device busy” busy-key function requires device ID transmission.
This is not supported by PBX system networking.
PIN Code Telephony
The users in a company normally use the existing terminals primarily for company-
related communication. Now the users would like to also be able to make private calls
in some cases. Private calls require:
• seizure of special external lines,
• changed and valid authorisations,
• recording separate charges and
• that destination call numbers not be saved for redialling.
This function can be realised using the “PIN Code Telephony” feature. To initiate a
special call, the user on any terminal uses a special menu function or code procedure.
After the user enters his/her own internal call number and associated user PIN, the
desired attributes for the next call are activated.
When the call is finished, the previously active telephone configuration is restored.
This external call number dialled is not recorded in a redial list.