Page 1 Aastra 430 Aastra 470 This document describes the system functions and fea- tures of communication servers of the Aastra 400 series. It is intended for planners, installers and system manag- ers of Aastra 400 communication systems. syd-0367_en / 1.3 – R3.0 – © 03.2013...
Page 2: Table Of Contents
About Aastra ........
Page 3 Aastra Mobile Client (AMC) ........
Page 4 4. 7. 1 PISN-Internal Calls ..........99 4.
Page 5 5. 10 General bell........... . 161 5.
Page 6 6. 5. 3. 3 Call to the public Network via an operator console....216 6. 5. 3. 4 Call to the public network via SIP network interfaces... . 216 6.
Page 7 7. 3 Routing in the private leased-line network ..... . 280 7. 4 User-to-user signalling (UUS) ........282 7.
Page 8 9. 2. 3 SIP-RFC supported by Aastra 400 ....... 356 9.
Page 9 9. 5. 5 Three-party conference from an enquiry call ....404 9. 5. 6 Conference ........... . 406 9.
Page 10 9. 6. 17 Callback if user busy / free ........467 9.
Page 11 9. 10. 3. 5 Functions with Aastra Alarm Server......564 9. 10. 3. 6 Interface descriptions .
Page 12: Product And Safety Information
User groups The phones, softphones and PC applications of the Aastra 400 communication so- lution are particularly user friendly in design and can be used by all end users with- out any specific product training.
Page 13 • Make sure that the versions of the user documents comply with the software level of the Aastra 400 products used and that you have the latest editions. • Always read the user documents first before you install, configure and put a Aastra 400 communication solution into operation.
Page 14 All parts and components of the Aastra 400 communication solution are manufac- tured in accordance with ISO 9001 quality guidelines. The relevant user information has been compiled with the utmost care. The functions of the Aastra 400 products have been tested and approved after comprehensive conformity tests. Nonethe- less errors cannot be entirely excluded.
Page 15: Safety Information
Hazard warnings are affixed whenever there is a risk that improper handling may put people at risk or cause damage to the Aastra 400 product. Please take note of these warnings and follow them at all times. Please also take note in particular of hazard warnings contained in the user information.
Page 16: Data Protection
Protection against listening in and recording The Aastra 400 communication solution comprises features which allow calls to be monitored and recorded without the call parties noticing. Inform your customers that these features can only be used in compliance with national data protection provisions.
Page 17: About This System Manual
DECT plan- ning, and the possibilities for networking several systems into a private network (PISN) or an Aastra Intelligent Net (AIN) are not part of this Manual. They are de- scribed in separate documents.
Page 18 See also Reference to other chapters within the document or to other documents. Aastra Intelligent Net Particularities that have to be observed in an AIN. Safety Considerations Special hazard alert messages with pictograms are used to signal areas of particular risk to people or equipment.
Page 19: About Aastra
North America, Europe and Africa as well as Internet Service Providers and distributors of renown. Aastra Technologies Limited, (TSX: “AAH”), is a leading company at the forefront of the enterprise communication market. Headquartered in Concord, Ontario, Can- ada, Aastra develops and delivers innovative communication products and appli- cations for businesses.
Page 20: System Interfaces
Central interface for connecting AMS, a CTI server, IP system phones, SIP terminals, for the network-side connection to an SIP service provider, or to implement an Aastra Intelligent Net. • Door Intercom Systems Special interface for connecting door intercom systems •...
Page 21: Network Interfaces
System interfaces 2. 1 Network Interfaces The system supports the following types of network interfaces: • Basic rate interface BRI-T for connection to – the public ISDN network – the private leased-line network • Basic access S for connection to external –...
Page 22: Basic Rate Interface Bri-T
System interfaces 2. 1. 1. 1 Basic rate interface BRI-T Basic access T is suitable for connection to both the public ISDN network and the private-leased-line network. 2. 1. 1. 2 BRI-S basic rate interface external The basic access S is an BRI-S interface configured as external (S-bus proto- external...
Page 23: Point-To-Point And Point-To-Multipoint Connections
System interfaces 2. 1. 1. 3 Point-to-Point and Point-to-Multipoint Connections Basic accesses can be configured as point-to-point or as point-to-multipoint (TEI Management setting in the configuration of the network interfaces). Point-to-Multipoint Connection without a communication server The basic access in point-to-multipoint configuration allows a selective dial-up of the terminals connected in parallel using MSN, the Multiple Subscriber Number.
Page 24 System interfaces Point-to-Multipoint Connection with communication server If a communication server is connected using point-to-multipoint, a direct dial number must be created for each MSN number, with all the digits of the MSN number. NT1: Network Terminal MSN: Multiple Subscriber Number U/T: ISDN reference point DSI:...
Page 25 System interfaces Point-to-Point Connection without Direct Dial Without direct dialling in, only one call number is available. The individual internal users can only be reached indirectly via the number. This variant is suitable above all for systems with primarily outgoing traffic. NT1: Network Terminal U/T:...
Page 26 System interfaces Point-to-Point Connection with Direct Dial With direct dial the individual communication server users can be reached directly via their direct dial number. NT1: Network Terminal DDI: Direct dialling U/T: ISDN reference point DSI: Digital terminal interface DSI BRI-S: ISDN terminal interface FXS: Analogue terminal interface Fig.
Page 27: Primary Rate Interface Pri
System interfaces 2. 1. 2 Primary rate interface PRI A primary rate access is a digital network interface for connection to the public net- work or the private leased-line network. It can be set for the protocols DSS1 (public ISDN network) and QSIG / PSS1 (private leased-line network). A primary rate access has thirty 64 kbit/s user information channels and one 64 kbit/s control and signalling channel (30B+D).
Page 28: Clock Synchronization
The up-circuit communication server has a connection to the public network. It can also be an Aastra 400 system or a third-party product, provided it supports the QSIG protocol. As a rule the down-circuit communication server is connected with the up-circuit communication server via its own fixed lines.
Page 29 System interfaces Example: Down-circuit connection with cordless system Fig. 9 Digital down-circuit connection with QSIG System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 30: Direct Dialling Out (Ddo)
"Call to DSS1 Terminal Equipment on the S Bus (DDO)" Chapter in the "System Functions and Features" System Manual Tip: The CPU2 applications card of an Aastra 470 communication server already contains a fax server and its use is subject to the acquisition of the relevant licences.
Page 31: Sip Access
System interfaces 2. 1. 3 SIP access The communication server can be connected to one or more SIP providers via the Ethernet interface on the basic system. The communication server supports 10 SIP access with up to 30 channels per SIP access. One SIP Access Channels licence is re- quired for each channel.
Page 32 System interfaces System configuration The tables below list the AMS configuration parameters required. Tab. 2 SIP provider configuration: General Parameter Parameter value Remarks Name <Name> Name of the SIP provider Broadband range <Name> Predefined broadband range used for this SIP provider. Use ‘+’...
Page 33 System interfaces Tab. 4 SIP provider configuration: Proxy Parameter Parameter value Remarks IP address <Address> IP address of the proxy server at the SIP provider All the commu- nication server’s external SIP messages are sent to this address (Primary proxy). If it is not available, the messages are sent to the alternative IP address (Secondary proxy)
Page 34: Analogue Network Interfaces
System interfaces Parameter Parameter value Remarks Password <Password> Password of the SIP account with the SIP provider. This parameter is to be specified only if the SIP provider requires authentication. Registration required <Yes / No> If this parameter is set on Yes, the SIP account will attempt to register with the provider.
Page 35 System interfaces Parameter Parameter value Remarks Dialling tone detec- Yes / If Yes, the communication server waits for the dial tone from tion the exchange before starting to dial. Dialling tone time [0...1200 seconds] Maximum waiting time for the exchange dial tone if exchange dial tone detection is activated.
Page 36: Analogue Down-Circuit Connection
System interfaces 2. 1. 4. 1 Analogue down-circuit connection With an analogue down-circuit connection the features of the up-circuit communi- cation server can also be utilized. This results in the following special applications for the user: • Depending on the system configuration the user makes phone calls in a com- plex environment.
Page 37 Fig. 12 Enquiry call behind communication server Situation: The existing call connection of an Aastra 400 user already seizes a trunk line to the up-circuit communication server. The procedure for setting up an in- quiry call depends on the type of terminal: •...
Page 38: Attenuation On Analogue Network Interfaces
System interfaces 2. 1. 4. 2 Attenuation on analogue network interfaces With analogue network connections you have a choice of four different attenua- tion settings: • Long • Long D for long lines • Short • Short D for short lines On lines with a loop resistance <...
Page 39: Terminal Interfaces
System interfaces 2. 2 Terminal interfaces The communication server supports digital and analogue user-network interfaces. 2. 2. 1 Digital user-network interfaces On each of these digital user-network interfaces several appropriate terminals can be hooked up and operated simultaneously. 2. 2. 1. 1 Terminal interface BRI-S The S user-network interface is a digital 4-wire interface used for connecting ISDN terminals, Terminal Adapters and ISDN PC cards.
Page 40 S-bus mode (S bus protocol =ETSI). Aastra Intelligent Net: In an AIN the call charge format of ISDN terminals depends on the coun- try and is based on the country configured with the region of the node concerned or user.
Page 41: Dsi Terminal Interfaces
The DSI digital terminal interface is a proprietary, system-specific 2-wire interface used for connecting following terminals: • DSI system phones • Aastra DECT Radio units Fig. 14 DSI terminal interfaces Two system phones can be connected in parallel to a terminal interface DSI. Ad- dress allocation is done by means of a switch on the phone.
Page 42: Ip Terminal Interface
2. 2. 1. 3 IP terminal interface The IP terminal interfaces are implemented via an Ethernet interface on the com- munication server. Besides IP system phones Aastra 400 also supports Aastra SIP terminals and standard SIP terminals by other manufacturers. Fig. 15...
Page 43: Analogue Terminal Interfaces
No call charges are transmitted to the connected terminals via analogue terminal interfaces. CLIP display is possible (see Technical Data in the Aastra 415/430 System Manual or the Aastra 470 System Manual). One analogue terminal interface per communication server can be configured for connecting a general bell.
Page 44: Special Interfaces
The Ethernet interface on the basic system is available for the following purposes: • data exchange with AMS • signalling and transmitting voice data (VoIP) in an Aastra Intelligent Net (AIN) • linking up the Open Interfaces Platform (OIP) • the connection of a CTI, alarm, ATAS or messaging server, etc.
Page 45: Interface For Door Intercom System
A loudspeaker system can also be operated via the interface for door intercom sys- tems. See also: "Special interfaces" Chapter in the Aastra 415/430 or Aastra 470. System Manual System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 46: Interface For General Bell
This eliminates the need for an external ringing voltage source. See also: "Special interfaces" Chapter in the Aastra 415/430 or Aastra 470. System Manual System functions and features as of R3.0...
Page 47: Numbering Plan
Numbering plan Numbering plan This Chapter features the different types of internal and external numbering plans available in the various systems. It explains the differences between in- ternal numbering plans for the private network and external numbering plans for the public network. It tells you what you need to know when creat- ing numbering plans for each particular network.
Page 48 Numbering plan Numbering Plan Identifier E.164 Numbering plan E.164 comprises the following types of number: Tab. 10 E.164 types of number Type Of Number Structure Example Subscriber [SN] 624 11 11 National [NDC] [SN] 32 624 11 11 International [CC] [NDC] [SN] 41 32 624 11 11...
Page 49 Numbering plan PNP Numbering Plan Identifier The PNP numbering plan comprises the following types of number: Tab. 11 PNP types of number Type Of Number Structure Example Level 0 [RIN] 1313 Level 1 [RP1] [RIN] 60 1313 Level 2 [RP2] [RP1] [RIN] 62 60 1313 The system supports private networks up to and with Level 1 [RIN] Regional Intern Number: all destination numbers within a Level 0 region...
Page 50: The System's Numbering Plan
Numbering plan 3. 2 The System's Numbering Plan The system's internal numbering plan is the numbering plan used for a stand-alone communication server or a PINX in a private network. The numbers entered in the numbering plan are used both to dial up call destinations in the communication server and to execute control functions..
Page 51: Categories In The Numbering Plan
Numbering plan 3. 2. 1 Categories in the Numbering Plan The allocation of categories to numbers and number ranges can be freely config- ured, provided a number of rules are observed. The default settings depend on the country. Rules for an Internal Numbering Plan Numbers are always interpreted starting from the left..
Page 52 Depends on the number of terminal interfaces installed. Depends on the type of communication server Only with Aastra 415/430 and if the corresponding number of ODAB card(s) is fitted System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 53: Exchange Access Categories
Numbering plan 3. 2. 2 Exchange Access Categories Tab. 13 Exchange access categories in the internal numbering plan Category Name Name Explanation Number Number range Explanation Exchange access, Busi- Call charges are added up <ext. call No.> Prefix, truncated ness on the Voice calls, business before dialling out or Data calls business cumu-...
Page 54: Category For Abbreviated Dialling
7500. Any user who wants to call Manhattan, New York, simply dials "NY" by name, then adds the local number. Aastra Intelligent Net: In an AIN with nodes in different countries the abbreviated dialling num- bers must always include the international prefix (e.g. 00) and the country code (e.g.
Page 55 Numbering plan Name The name is used: • To dial by entering the name rather than the call number (dialling by name). • To display the name on the user’s own system phone when the CLIP number of an incoming call matches the number stored under the abbreviated dialling (see "Replicating the Name Display in the Communication Server", page 81).
Page 56: Category For Emergency Number
Entering the destination numbers is subject to the same rules as for abbreviated di- alling. Aastra Intelligent Net: In an AIN the nodes can be located in different countries, which means it makes sense to enter in the numbering plan the emergency number nor- mally used in each country.
Page 57: Category For Internal Users
Digital phones of the series Dialog 4200 • DECT Aastra , 9d or GAP cordless phones: DECT phones must be logged on to the sys- tem using a logon procedure. This is done using the Log on cordless phone but- ton in the terminal configuration.
Page 58: Mobile Phones
Although the communication server does not have a GSM receiver, mobile phones can be connected to Aastra 400. The mobile phone is assigned to a user and can be reached internally using his user number. If the mobile phone user dials a call...
Page 59 Numbering plan Integration of mobile phones The integration of mobile phones requires one Mobile Phone Extension licence per mobile phone. There are two steps to mobile phone integration, which contains the following features: Integration step 1 • The mobile phone is assigned to a user and can be reached internally using his user number.
Page 60 See also: An overview of the function codes supported at integration levels 1 and 2 can be found in the "Mobile Phones on Aastra 400" User’s Guide. Automatic authentication of the integrated mobile phone If the CLIP authentication parameter is set on CM_4.2_Mobile phone settings...
Page 61 Numbering plan screened must be configured to in the corresponding trunk group (default set- ting = no). Manual authentication of the integrated mobile phone If the CLIP authentication parameter is set to CM_4.2_Mobile phone settings, the integrated mobile phone is authenticated manually using the following proce- dure: 1.
Page 62: Aastra Mobile Client (Amc)
1. Purchase a AMC Extension licence and enter the licence code in AMS. In addition to the licence code an Aastra Mobile Client access code is also printed out. You System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 63 DSP configuration. 8. On the licence server start the Aastra Mobile Client administration. 9. Enter the EID No. and the Aastra Mobile Client access code (see item 1). 10.Configure the parameter for the Aastra Mobile Client as shown in Tab. 18...
Page 64 Mobile phone integration configured as CDE destination (e. g. +41326553867). DTMF delay [ms] <Delay time> • Delay time after connection setup until the Aastra Mobile Client sends DTMF characters. Auto login <Check box> • Activate for automatic authentication with CLIP.
Page 65 Interval [days] See also: A separate User’s Guide is available for the Aastra Mobile Client. It con- tains a list of the mobile phone operating systems supported as well as a short description of the telephony functions provided that can be oper- ated using menu keys.
Page 66: Virtual Terminals
Numbering plan 3. 2. 5. 4 Virtual terminals Virtual terminals respond in the same way as analogue internal terminals except that they • do not physically occupy a port as there is no hardware involved, • do not require a B channel. Other properties •...
Page 67: Pisn Users
Numbering plan 3. 2. 6 PISN users Tab. 19 User category in the internal numbering plan Category Number / Number Range Name Explanation Number PISN users Users on another PINX in the PISN Not allocated Default settings for Switzerland This category comprises users who belong to the same PISN but are connected to a different PINX.
Page 68 Numbering plan Entering the Number of a PISN User in Full A complete PISN user number unequivocally identifies a user at another PINX or a virtual user. Each unequivocal number of a PISN user can be allocated a name in the user con- figuration.
Page 69 Numbering plan Example of Entering PISN Users Fig. 20 PISN with two regions Tab. 20 Entering PISN users in PINX 2 Number of Variant entries PINX 1 PINX 3 PINX 4 Entries Number in full 200,201...299 60200, 60201...60299 60300, 60301...60399 Numbers partly with wildcards 20X, 21X...29X 602XX 603XX...
Page 70: Separate Regional Prefix Category
Numbering plan 3. 2. 7 Separate Regional Prefix Category Tab. 21 Category for separate regional prefix in the internal numbering plan Category Number / Number Range Name Explanation Number Explanation Own region prefix Level 1 prefix for the region Not allocated Prefix, truncated on detec- allocation of a PINX in the tion...
Page 71: Shared Numbering Plan
Numbering plan 3. 2. 8 Shared Numbering Plan PISN users are structured in the internal numbering plans of the PINX. From the PINX’s viewpoint its own users are internal users and the users of the other PINXs are PISN users. If two or more PINXs are structured in such a way that they split the users’...
Page 72: Pisn With Different Regions
Numbering plan 3. 2. 9 PISN with different Regions A PISN can be divided into several regions. Each region is identified by its regional prefix. Users who call a user in a different region first dial the prefix of the destination re- gion, then the internal number of the user they want.
Page 73: Identification Elements
Identification elements Identification elements Correctly identifying and displaying a call is the essential requirement for ad- equately implementing the system's networking philosophy. This Chapter looks at how the origin of a call is identified using different ringing tone pat- terns and how the caller's number (CLIP) or name (CNIP) is displayed. It de- scribes how CLIP and CNIP displays are created under different system condi- tions, how they can be influenced, and how to suppress the CLIP display.
Page 74: Internal And External Ringing Patterns
Identification elements 4. 1 Internal and External Ringing Patterns The ringing pattern provides a means of identifying whether the call originates from within the PBX (internal call) or from the outside (external call). The rhythm of the ringing pattern differs in each case Fig.
Page 75 Ringing pattern = automatic can be used to force a situation where the single ringing tone is always used for all calls. Alternative for the Aastra 5300, Aastra 5300ip series of system phones and the Aastra 2380ip IP softphone...
Page 76: Displaying Numbers (Clip) And Names (Cnip)
Identification elements 4. 2 Displaying Numbers (CLIP) and Names (CNIP) During both the ringing phase and the call itself the caller’s call number or name (or both) are shown on the terminal’s display. • The indication of the caller’s phone number is referred to as CLIP (Calling Line Identification Presentation).
Page 77 – In the terminal configuration, the parameter Terminal supports CLIP must be set to Yes. – The terminal must support CLIP display. – Restriction for Aastra 415/430: Different CLIPs can only be sent to 2 analogue terminals simultaneously. CLIP Numbers Outside the Registered Number Range...
Page 78: Displaying The Clip
Identification elements 4. 2. 1 Displaying the CLIP CLIP functions process incoming and outgoing calls. Fig. 27 CLIP of an incoming and an outgoing call CLIP of an Incoming Call User A calls user B: User A sends his CLIP, which is received in the communication server by the trunk group, processed and displayed to user B.
Page 79: Clip With Incoming Calls
Identification elements 4. 3 CLIP with Incoming Calls The CLIP number of an incoming call is processed and presented in two stages: • Analysis and processing of the CLIP number • Presentation of the CLIP number on the destination user’s terminal 4.
Page 80: Presentation Of The Clip On The Terminal
Identification elements TON of the CLIP Prefix Conversion number National Long-distance code that Code is truncated, matches the separate PINX is set to subscriber. No matching long-distance CLIP number and remain unchanged code Subscriber CLIP number and remain unchanged See also the examples in "Examples of CLIP Displays in the PISN", page 4.
Page 81: Replicating The Name Display In The Communication Server
Identification elements 4. 3. 3 Replicating the Name Display in the Communication Server The communication server will try to assign a name to the CLIP number of an in- coming call from the public network and to display that name on the system phone (CNIP).
Page 82: Flow Charts For Name Identification (Cnip)
Identification elements 4. 3. 4 Flow charts for name identification (CNIP) [1] Possible prefixes: own prefix, country code, area code or own regional prefix. [2] Continues on Fig. Fig. 28 Analysis and processing of an incoming call in the communication server System functions and features as of R3.0 syd-0367/1.3 –...
Page 83 Identification elements From Fig. Fig. 29 Presentation of the CLIP / CNIP of an incoming call on the terminal System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 84: Clip With Outgoing Calls
Identification elements 4. 4 CLIP with Outgoing Calls With an outgoing call the CLIP number is transmitted along with the NPI and TON information. In principle there are two possible variants for creating a CLIP number: • The communication server creates the CLIP number automatically, based on the origin and routing of the call.
Page 85: Entering A Fixed Clip
Identification elements 4. 4. 2 Entering a fixed CLIP In practice a permanent CLIP number is used if the CLIP of the user concerned is al- ways to remain the same in the public network, regardless of the path used for routing an outgoing call.
Page 86: Clip Flowcharts For Outgoing Calls
Identification elements 4. 4. 4 CLIP flowcharts for Outgoing Calls Continues in Fig. Fig. 30 CLIP of an outgoing call to an external user in the public network Continues in Fig. Fig. 31 CLIP of an outgoing call to a PISN user System functions and features as of R3.0 syd-0367/1.3 –...
Page 87 Identification elements From Fig. 30 Fig. 31 Fig. 32 Creating an automatic CLIP for outgoing calls System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 88: Clip Display With A Virtual Network Pisn User
Identification elements 4. 4. 5 CLIP Display with a Virtual Network PISN User A public network user can be set up as a virtual PISN user in the communication server. Internal users will then perceive the user as another internal user: A call is signalled with the internal ringing pattern.
Page 89: Outgoing Call With Local Call Forwarding
Identification elements This redirecting information at user C is available for CFU, CFB, CFNR Call Deflec- tion (CD). (With CD forwarded from is displayed instead of deflected from.) 4. 5. 1. 1 Outgoing call with local call forwarding The configuration possibilities for the redirecting information depend on the desti- nation user: If the destination user is •...
Page 90: Incoming Call That Is Already Redirected
Identification elements 4. 5. 1. 3 Incoming call that is already redirected The redirecting information is also available to the called user in the case of an in- coming call redirected via a PISN user or a user in the public network. If the call is routed via a call distribution element it is useful in certain cases if the name/ number of the CDE is displayed instead of the redirecting information.
Page 91: Incoming Call With Cde Overflow
Identification elements 4. 5. 2. 2 Incoming call with CDE overflow If in the event of a CDE overflow the call is routed from one call distribution ele- ment to another due to the entries under CDE if busy CDE if no answer, the redi- recting information provided to the calling user depends on the new destination: If the destination is...
Page 92: Clip / Colp Settings
Identification elements 4. 6 CLIP / COLP Settings The following settings affect the CLIP and, by analogy, the COLP, too. Fig. 33 CLIP incoming Fig. 34 CLIP outgoing System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 93 Identification elements Tab. 24 CLIP related settings Configuration Element Parameter Affect on CLIP Incoming Outgoing ✓ User Automatic CLIP CLIR ✓ CLIR for redirecting COLR COLR for redirecting Numbering plan NPI ✓ Type of number TON ✓ Number ✓ PISN users Number ✓...
Page 94: User
Identification elements 4. 6. 1 User Call to the Public Network Call to the public network with exchange access prefix via a trunk group with Net- work type = public: Automatic CLIP = yes, the DDI number will be used as CLIP if the user is himself reachable by incoming calls via the path trunk group →...
Page 95: Pisn Users
Identification elements 4. 6. 2 PISN users Number setting The call number entered under Number is compared with the CLIP number of an in- coming call. If the two numbers match up, the PISN user number is displayed as the CLIP with private level...
Page 96 Identification elements Numbering Plan identifier, Type of Number, Number These settings are used if the CLIP number could not be created automatically. This is the case when there is no suitable DDI number available with a call to the public network.
Page 97: Clip/Clir Settings
"22"", see also "Numbering Plan Identifier E.164", page 48). Aastra Intelligent Net: In an AIN the nodes may be spread over different regions or even coun- tries. Some settings do not apply throughout the system but only to one region. A region is assigned to one or more AIN nodes. An region can also be assigned for each trunk group.
Page 98: Examples Of Clip Displays In The Pisn
Identification elements 4. 7 Examples of CLIP Displays in the PISN Various scenarios are used in a sample network to illustrate how CLIP displays are handled in a PISN.Fig. 35 shows the sample network. Fig. 35 Sample network: PISN with two regions and one virtual network user System functions and features as of R3.0 syd-0367/1.3 –...
Page 99: Pisn-Internal Calls
Identification elements 4. 7. 1 PISN-Internal Calls Ordinary PISN-Internal Call User C (340) on PINX 2 calls user A on PINX 1 by a direct route. Both users belong to the same region. Fig. 36 Example 1: User C calls user A (excerpt from Fig.
Page 100 Identification elements PISN - Internal Call with Overflow Routing User C (340) on PINX 2 calls user A on PINX 1 via PINX 3 as all the available commu- nication channels between PINX 2 and PINX 1 are busy. PINX 3 belongs to Region 60.
Page 101: Outgoing Calls To The Public Network
Identification elements 4. 7. 2 Outgoing Calls to the Public Network Call to the Public Network via a Gateway PINX User C (340) on PINX 2 calls user F on the public network via PINX 1. PINX 1 has a DDI number for user C (54). The following CLIP characteristics are set in the trunk group configuration of PINX 1: •...
Page 102 Identification elements Call to the Public Network via a Gateway PINX with Overflow Routing User C (340) on PINX 2 calls user F on the public network via PINX 3 as all the availa- ble communication channels between PINX 2 and PINX 1 are busy. PINX 3 does not have a DDI number for user C.
Page 103 Identification elements Call to the Public Network via a Gateway PINX with Overflow Routing Automatic CLIP User B (330) on PINX 2 calls user F on the public network via PINX 3 as all the availa- ble communication channels between PINX 2 and PINX 1 are busy. PINX 3 does not have a DDI number for user B.
Page 104: Incoming Calls From The Public Network
Identification elements 4. 7. 3 Incoming calls from the public network User G on the public network calls user C on PINX 2 via PINX 1. He dials 055 555 55 Fig. 41 Example 6: User G calls user C (excerpt from Fig.
Page 105 Identification elements Call from the Public Network with Overflow Routing User G on the public network calls user C on PINX 2 via PINX 1 and PINX 3 as all the available communication channels between PINX 2 and PINX 1 are busy. He dials 055 555 55 54.
Page 106 Identification elements Call made by a PISN user in the public network PISN user E (310) on the public network calls user C on PINX 2 via PINX 1. He dials 055 555 55 54. Fig. 43 Example 8: User E calls user C (excerpt from Fig.
Page 107: Clip Format For Transit Connections In Networks
Identification elements 4. 7. 4 CLIP format for transit connections in networks Different CLIP formats are sometimes used in a PISN with PINX in different coun- tries, with QSIG connection of third-party systems or applications, and with con- nections via an SIP network. The CLIP format and an exchange access prefix can be configured to ensure that the correct CLIP is displayed in networks whenever possible, even with interna- tional transit connections.
Page 108: Clip On Analogue Exchange Accesses
Identification elements 4. 8 CLIP on analogue exchange accesses The systems are capable of receiving the number of incoming calls on analogue ex- change accesses and forwarding it to terminals. This requires a number of settings to be made in AMS. The network provider must also support CLIP on analogue ex- change accesses in accordance with ETSI standard (ETS 300 778-1).
Page 109: Routing Elements
Routing elements Routing elements The purpose of a routing element is to distribute incoming and outgoing calls to their destinations. This Chapter features all the elements involved in call routing. The settings allocated to a routing element are carried out in the sys- tem configuration.
Page 110: Overview
Routing elements 5. 1 Overview From the system’s viewpoint a destination is an interface (e.g. network interface or terminal interface). In this context user groups or user configurations are also rout- ing elements, not destinations. Fig. 44 shows how all the routing elements relate to one another: Routing via the numbering plan to one of the elements.
Page 111 Routing elements Network interfaces Network interfaces provide the access to the communication server from the out- side. The settings for the network interfaces are used to specify network-specific characteristics (e.g. point-to-point or point-to-multipoint connection or the distri- bution of B channel groups at the primary rate access). As network interfaces are not routing elements per se, they are not discussed fur- ther in this chapter.
Page 112 Routing elements User groups In a user group incoming and internal calls are routed to a group of internal desti- nations in accordance with a pre-configured call distribution pattern (see page 140). User configuration All the user-specific settings are grouped together in the user configuration. This chapter deals exclusively with settings that are specific to routing and identifica- tion (see page...
Page 113: Trunk Groups
Routing elements 5. 2 Trunk groups Fig. 45 Trunk groups in relation to the other routing elements Network interfaces with the same characteristics are grouped together in a trunk group. For example, it is specified whether the network interfaces allocated to a trunk group are connected to a private network or the public network.
Page 114: Trunk Groups Of Network Interfaces
Routing elements 5. 2. 1 Trunk Groups of Network Interfaces General Rules and Settings A network interface can only be assigned to a single trunk group. A trunk group contains either analogue or digital network interfaces (the network interface entered first is decisive). The digital network interfaces of a trunk group lead either •...
Page 115 Routing elements Seizure Sequence for Outgoing Calls Within a bundle the system will first try and seize the network interface that was entered last (large numbers). If for whatever reason this interface is not available, it will then attempt to seize the second last interface, then the third last, etc. (see also Fig.
Page 116 Routing elements Configuration: Once a trunk group contains a B-channel group, the trunk group’s protocol can no longer be changed. For this reason it is important to proceed using the following configuration stages: 1. Enter the network interface of the basic or primary rate access in the first trunk group (e.g.
Page 117: Routing Functions Of The Trunk Group For Incoming Calls
Routing elements 5. 2. 2 Routing Functions of the Trunk Group for Incoming Calls The following incoming routing functions are assigned to the trunk group: • Restricting the number of calls incoming simultaneously per trunk group • Routing a call to one of the following elements: –...
Page 118 Routing elements Generating a Ring-back Tone With the settings outgoing call, ring-back tone incoming call, ring-back tone system is able to control, within certain limitations, the generation of the ring-back tone on digital trunk connections. These settings do not have to be altered in nor- mal operation.
Page 119 "Direct Dialling Plan (DDI plan)", page 124. Aastra Intelligent Net: In an AIN the nodes may be spread over different regions or even coun- tries. Some settings do not apply throughout the system but only to one region. A region is assigned to one or more AIN nodes. An region can also be assigned for each trunk group.
Page 120: Route
Routing elements 5. 3 Route Fig. 47 Routes in relation to the other routing elements The route function applies only to outgoing calls. A route determines the direction of outgoing calls through allocation to trunk groups. All outgoing calls are routed via a route to one or more trunk groups. They also include calls routed via the Least Cost Routing function and transit calls in a PISN.
Page 121: The Route's Routing Functions
Routing elements 5. 3. 1 The Route’s Routing Functions The route is allocated the following outgoing routing functions: • Routing an outgoing call to one or more trunk groups • Restricting the number of calls outgoing simultaneously • Polling an external digit barring •...
Page 122: Other Routing Functions For Outgoing Calls
• With Aastra 415/430 all routes are allocated numbers from 170 upwards in the numbering plan. • On the Aastra 470 system the first 24 routes are allocated numbers from 170 up- wards in the numbering plan. Aastra Intelligent Net: In an AIN the local network interfaces of nodes can be prioritised for each route (setting CM_3.1.6, parameter Use node network interfaces first).
Page 123 Routing elements Adding a Prefix to the Call Number Send access code is used to define a prefix which is added to a call number (which no longer has an exchange access prefix). The prefix can be used to transmit a call to the public network via a third-party PINX by specifying a route number as the exchange access prefix for the gateway PINX..
Page 124: Direct Dialling Plan (Ddi Plan)
Routing elements 5. 4 Direct Dialling Plan (DDI plan) Fig. 49 Direct dialling plans in relation to the other routing elements Direct dialling is used to reach internal users directly from the public network or from another PINX. The incoming call is linked with a call distribution element on the basis of the call number's direct dial portion.
Page 125 Routing elements Several Direct Dialling Plans per communication server / PINX Several direct dialling plans are available. This ensures that the same user can be reached from the outside via different network accesses and that the correct CLIP is also transmitted in outgoing traffic. Fig.
Page 126 Routing elements Linking a Direct Dial Number with a Call Distribution Element Direct dial numbers are created as blocks with 1 to several numbers. When the number range is created each direct dial number is automatically linked with a call distribution element.
Page 127 A CDE is defined as standard as the destination for a DDI. If a fax server is in operation on the applications card of a CPU2 (Aastra 470 only), routing destination = Fax server must be configured for the fax numbers (see also "Fax service", page...
Page 128: Call Distribution Element (Cde)
Routing elements 5. 5 Call Distribution Element (CDE) Fig. 52 Call distribution elements in relation to the other routing elements Call distribution elements are used to route an incoming call to an individual desti- nation or to a combination of destinations. Each call distribution element is assigned a switch group.
Page 129 Routing elements Restrictions: • Call forwarding unconditional and call forwarding on no reply cannot be applied to a call distribution element. • The features Call waiting / Intrusion and automatic callback cannot be activated on call distribution elements • A call distribution element cannot be stored under a team key. •...
Page 130: Call Destination
• ERC: External remote control (can only be selected once a password has been entered under CM_5.10, see page 537) • Special destinations: – PSTN overflow (see AIN System Manual "Aastra Intelligent Net") – Voice Mail (see page 417) –...
Page 131 Routing elements The destinations are defined for each of the three switch positions of the selected switch group (e.g. for Day, Night, Weekend). Other destinations can be defined for each switch position. Fig. 53 Destinations of the call distribution element System functions and features as of R3.0 syd-0367/1.3 –...
Page 132 Routing elements Alternative Destinations A call distribution element can be linked with two other call distribution elements for the routing to alternative destinations: • One of the call distribution elements is used for the routing to alternative desti- nations if a call at the original destination is not answered. •...
Page 133 Routing elements Note: If a call forwarding destination is defined under Default CF if no answer in the user configuration, the call will be redirected after the internal or external delay configured there (see "Default forwarding per user", page 190). Announcement service A previously activated welcome announcement by the announcement service will remain activated if the call is routed to the alternative destination.
Page 134 Fig. 56 Application example of the configuration of an alternative destination if busy Aastra Intelligent Net: If in an AIN a satellite user can no longer be reached due to a connection interruption or because of insufficient bandwidth between the Master...
Page 135: Routing Functions For Incoming Calls
Routing elements 5. 5. 2 Routing Functions for Incoming Calls Call distribution is allocated the following incoming routing functions: • Routing a call to a destination, depending on the position of the allocated switch group (see "Call destination", page 130). •...
Page 136: Other Functions And Settings Of The Cde
Routing elements 5. 5. 4 Other Functions and Settings of the CDE Name Name is used to assign a name to each call distribution element. The name is used for identification purposes. • With incoming calls it is displayed on the system phone. •...
Page 137: Switch Groups
Routing elements 5. 6 Switch Groups With the aid of the switch groups the routing configuration for the system can be conveniently adapted to the time and situation-related requirements of the cus- tomer. This means for example that calls during the day can be routed differently to calls at night, or differently at times with a high call volume to times with a low call volume (e.g.
Page 138 The switch groups can also be switched over via FXS interfaces configured as con- trol inputs or via the control inputs of an ODAB options card (Aastra 415/430). The switch group configuration determines which of the switch groups 1…20 are switched.
Page 139 • All the office workers’ direct dialling numbers are routed in the call distribution elements to UG 17 (Aastra 415/430) or UG 25 (Aastra 470) in which voice mail is located. As the user-specific allocation of the digit barring also depends on the switching position of the switch group, they need to be adapted accordingly.
Page 140: User Group
Routing elements 5. 7 User Group Fig. 58 User groups in relation to the other routing elements In a user group incoming and internal calls are routed to a group of internal desti- nations in accordance with a pre-configured call distribution pattern. System functions and features as of R3.0 syd-0367/1.3 –...
Page 141 Routing elements Incoming Calls User groups are selected by means of their call numbers or names (name selec- tion). The call numbers of user groups are a separate category of the numbering plan. CFU or CFNR cannot be made to a user group (except for user groups with special functions and user groups configured as "large").
Page 142: Ordinary User Groups
Routing elements 5. 7. 1 Ordinary user groups 5. 7. 1. 1 Elements of a User Group A user group consists of one or more of the following elements: • Member group: Group with up to 16 internal users (members). Each user can be allocated several terminals (see "One Number user concept", page 368).
Page 143 Routing elements Fig. 59 Elements in a user group Call Distribution to the Elements A call is distributed in parallel to the connected elements of a user group. Each ele- ment can be individually delayed. The delay time can be set globally to 3, 5 or 7 ringing cycles and applies throughout the system to all line groups.
Page 144: Call Distribution In The Member Group
Routing elements 5. 7. 1. 2 Call distribution in the member group There are three possibilities for call distribution to the members within member line group: • Global • Linear • Cyclic Global Call Distribution In a global call distribution all the available members in the group are called simul- taneously.
Page 145 Routing elements Cyclic call distribution Call distribution is the same as in the linear variant except that each new call is first signalled in each case to the next member in the row. Fig. 62 Cyclic call distribution Delayed Calls to Subgroups The members of the member group element can also be subdivided into a main group and a subgroup (UG subgroup as of member...
Page 146 Routing elements The duration of the delay time and forwarding time can be set globally to 3, 5 or 7 ringing cycles. Other delay times can also be specified on a user’s terminal, e.g. the delayed signal- ling on a line key of a key telephone or on a team key. Fig.
Page 147 Routing elements Note: A maximum of 50 terminals can be called simultaneously for each call. This limit is quickly reached if a user group with global call distribution contains many users with several terminals. If so, only the first 50 termi- nals will ring, starting with the user group members with the lowest posi- tion number.
Page 148 Routing elements Cyclic call distribution and CFNR of user group members *67 (Call Forwarding Busy) and *61 (Call Forwarding on No Reply) to any destina- tions can always be activated without causing the members to be excluded from the user group. Special case call forwarding on no reply if busy: Situation: A user in a user group has activated CFNR to an internal destination (case A), an ex-...
Page 149: Large User Groups
Cordless phones like other terminals are assigned to a user. The following restric- tions apply: • Two cordless phones are allowed per user. • In the UGs 1...16 (Aastra 415/430) or 1...24 (Aastra 470) the group call is used for those DECT cordless phones on which the parameter Busy if busy is set to with the allocated user.
Page 150: User Groups For Voice Mail And Other Applications
User group 17 (Aastra 415/430) and user group 25 (Aastra 470) have been designed to accommodate a voice mail server. User groups 18 to 21 (Aastra 415/430) or 26 to 29 (Aastra 470) are provided for ap- plications that require a call forwarding to a user group.
Page 151: User Groups 14, 15 And 16
Routing elements 5. 7. 3. 1 User Groups 14, 15 and 16 After initialization, the element operator console and the first four users are en- tered as members in a user group 16. After an initialization each trunk group is allocated call distribution element 1. It is allocated user group 16 as the destination for all three switch positions.
Page 152: User Groups 30 - 99
User groups 30 - 99 Note: With user groups 30 - 99 (available only in the Aastra 470 ) no DECT group calls are possible, i. e. all cordless phones in these user groups are called individually. For many UG members with cordless phones this can quickly lead to a DECT system overload, with the result that not all cordless phones are called.
Page 153: User Configuration
Routing elements 5. 8 User Configuration Fig. 64 User configuration in relation to the other routing elements All the user- and terminal-specific settings are grouped together in the user config- uration. This chapter deals with the following topics: • Routing and identification-specific settings •...
Page 154: Routing Functions For Incoming Calls
Routing elements 5. 8. 1 Routing Functions for Incoming Calls The incoming routing functions in the user configuration are as follows: • for terminals, the allocation of the internal user number to one or more physical destinations (terminal interface, terminal selection digit and terminal type) •...
Page 155 Routing elements Call Number of the PISN User for Outgoing Calls If a PISN user is in a virtual network, his external (DDI) number will be listed here without the exchange access prefix. If a PISN user is in a fixed network, a number is not usually entered here (see "Call to the private Leased-Line Network", page 220).
Page 156: Operator Console
If all the line keys are busy, other calls will be sorted into the call queue. On an Aastra 1560 / Office 1560 the calls are entered in the external call queue. To answer the call the operator selects it directly from the call queue displayed on the graphic interface.
Page 157 If all the line keys are busy, the calls will be placed into the internal call queue. On an Aastra 1560 / Office 1560, the calls are entered in the call queue for internal calls on the graphic interface. The operator select the call directly form the call queue.
Page 158: Routing Functions For Outgoing Calls
The CLIP consists of the personal internal user number. On the Aastra 1560 / Office 1560 the operator console number and a name can be added instead of the personal internal user number for calls from the internal call queue.
Page 159 Routing elements The configuration as a two-company system only affects the display on the opera- tor console. The following points need to be taken into account to ensure that the two-company operation is clearly separated: • Use a separate direct dialling plan for each company. •...
Page 160: Capolinea
Routing elements 5. 9. 4 Capolinea The purpose of the Capolinea feature is to ensure that each incoming call is an- swered. Therefore calls not answered by the destination users are routed to alterna- tive destinations (see "Response if busy", page 193).
Page 161: General Bell
Country parameter is configured to IT on the Master, Capolinea is available throughout the AIN. Other Subjects Related to the Operator Console: Terminals, Aastra 1560 / Office 1560 PC operator console, user-related features, numbering plan 5. 10 General bell Calls with the general bell as destination can be signalled visually or acoustically using an external supplementary equipment.
Page 162: Using Terminals As Key Telephones
The following system phones can be configured as key telephones: • Office 35 • Office 45/45pro • Aastra 5370/5370ip • Aastra 5380/5380ip A system phone automatically becomes a key telephone as soon as a KT line is placed on one of the phone's line keys.
Page 163: Kt Lines And Line Keys
Routing elements Note: The SIP phones of the Aastra 6700i series, the Aastra BluStar 8000i and a number of standard SIP phones can also be used as key telephones. The number of lines per terminal is configurable. A maximum of 2 simultane- ous call connections is possible.
Page 164 Routing elements KT Lines Each call distribution element is allocated under its reference number one or more lines for key telephones (KT lines) if (or destination combinations with that desti- nation) has been set as the destination (see "Call destination", page 130).
Page 165 Routing elements Terminating KT Lines and through KT Lines Any number of line keys from different key telephones can be allocated to the same KT line. If only one key telephone is allocated to one or several identical KT lines, we talk of a terminating KT line (TL). If several line keys of different key tele- phones are allocated to the KT line, we talk of a through KT line (THL).
Page 166: Incoming Calls Via A Kt Line
Routing elements 5. 11. 3 Incoming Calls via a KT Line All calls can be routed to a KT line if the destination is defined in the correspond- ing call distribution element: • Calls from the public ISDN network • Calls from the public analogue network •...
Page 167 Routing elements Transferring to a Key Telephone A call transferred to a key telephone is offered on the key telephone’s personal key or on a line key. If the call comes from the public network, it is signalled with the ex- ternal ringing pattern.
Page 168: Outgoing Calls Via A Kt Line
Routing elements 5. 11. 4 Outgoing Calls via a KT Line A KT line can be configured either as an outgoing line to the network or as a normal internal line. KT Line as an Outgoing Line to the Network Direct network access is enabled when a call is set up: The network dialling tone is obtained.
Page 169: Application Examples For Key Telephones
Routing elements 5. 11. 4. 1 Application Examples for Key Telephones Destination Combination KT+UG The combined destination KT line and user group 5 has been configured in call dis- tribution element 1 with number 200 in the numbering plan. Two line keys are connected to the KT line 1/1 It is therefore a through KT line The first line key belongs to the key telephone with user number 211;...
Page 170: Destination Kt
Routing elements 5. 11. 4. 2 Destination KT Travel agency Application The number for the travel agency’s Africa Desk is listed in the telephone directory under the number 222 22 20. Calls for travel to Africa are first route to the Africa Desk At the Africa Desk the calls are answered by employees 1 to 3.
Page 171 Routing elements Substitution Circuit The first call is answered by the manager personally; a second simultaneous call will ring on the deputy manager’s set; the third call will ring in the secretary; the fourth caller will obtain "busy". The calls can be visually signalled everywhere im- mediately.
Page 172: Queue With Announcement (Number In Queue)
Routing elements 5. 12 Queue with announcement (Number in Queue) Fig. 72 The queue with announcement in the context of the other routing elements The queue with announcement (Number in Queue) can be inserted as an option between the call distribution element and the destination (or combination of desti- nations).
Page 173 Routing elements Utilization of the queue with announcement is subject to the acquisition of a li- cence. Restrictions: Any call forwarding actions (CFU, CFNR, default call forwarding, call forwarding if unobtainable, etc.) configured at the call destination are not executed. Integrated mobile phones and PISN users are not called.
Page 174: Acd Server
Routing elements 5. 13 ACD Server Fig. 73 The ACD server in relation to the other routing elements With an ACD application on the third-party CTI interface, control of the call routing is shifted from the communication server to the external ACD server (ACD: Auto- matic Call Distribution).
Page 175 Routing elements Fig. 74 Communication server call routing controlled by the ACD server If the call is not answered by the destination user (agent) after a set time has elapsed (ACD ringing duration) or if the destination user is busy, the communication server returns the call to the queue and informs the ACD server accordingly.
Page 176 Routing elements Call Routing in the event of an ACD Server Failure Alternative destinations have to be defined so that calls can be routed to a destina- tion even in the event of an ACD server failure (see "Alternative Destinations", page 132).
Page 177: Call Routing
Call routing Call routing This Chapter describes the interplay between the routing elements for the various types of traffic: call routing for internal, incoming and outgoing traf- fic. Other topics include Least Cost Routing, exchange-to-exchange traffic, transit routing in the private leased-line network, overflow routing and break-out.
Page 178 Call routing Internal destinations Remarks • Analogue terminals • Aastra SIP terminals and standard SIP termi- nals • IP system phones • Cordless phones • Integrated mobile phones External mobile number stored • Virtual terminals Internal destinations to which another desti- nation has been permanently allocated: •...
Page 179: Dialling Internal Destinations Via External Call Numbers
Call routing 6. 2. 2 Dialling internal destinations via external call numbers Internal users can also reach internal destinations by dialling an external call number with the help of an allocation table in AMS. This is particularly helpful when dialling with the aid of a phone book directory. In this way an internal and an external call number do not have to be stored in the phone book directory.
Page 180 Call routing A call to the following phone numbers is routed to internal destination 3867: • 00326553867 • 00041326553867 Note: Instead of Exchange access business, the digits for Exchange access private, Cost cen- tre selection Route selection can also be used. Restrictions: •...
Page 181 Call routing • Sometimes call numbers are given the following signs for better readability: "-", "/", "(", ")" and "blank". These signs are filtered out by the communication server before dialling. • If a call number contains the country code as well as the national prefix, the na- tional prefix can also be automatically filtered out.
Page 182: Internal Digit Barring
Call routing 6. 2. 3 Internal Digit Barring There are several digit barring options available for internal traffic. The same rules apply as for external digit barring facilities (see "Digit barring", page 207). 6. 2. 4 Internal ringing duration The ringing time for an internal user can be configured from 30 to 18000 seconds in the AMS Configuration Manager using the Internal ringing duration.
Page 183 Call routing One and the same trunk group cannot contain both analogue and digital network interfaces Fig. 77 Routing and destinations of an incoming call Call routing depends in principle on whether a call originates • from the public network or •...
Page 184: Call From The Public Network
Call routing Fig. 78 Routing an incoming call 6. 3. 1. 1 Call from the Public Network A call with a suitable direct dial number is routed to the destination via the call dis- tribution element allocated in the direct dialling plan. If a suitable direct dial number is not found, the call is routed in the same way as a call from the public network without direct dialling (see "Routing without Direct Di-...
Page 185 Call routing Routing with Direct Dialling Fig. 79 Routing a call from the public network with direct dialling Tab. 41 Setting the routing parameters Parameter Parameter value Trunk group 1: • Network interfaces Network interfaces in this trunk group • Incoming connection Number of connections allowed simultaneously •...
Page 186 Call routing Routing without Direct Dialling A call without a suitable direct dial number is routed to the call destination via the call distribution element allocated in the trunk group. One and the same trunk group cannot contain both analogue and digital network interfaces. Fig.
Page 187: Call From The Private Leased-Line Network
Call routing 6. 3. 1. 2 Call from the Private Leased-Line Network In the private leased-line network, direct dialling plans are set up only if calls are to be routed to their destinations via call distribution elements in order to benefit from the advantages of the flexible routing properties of call distribution elements (see "Call Distribution Element (CDE)", page...
Page 188 Call routing Routing with Direct Dialling A call with a suitable number in the direct dialling plan is routed to the destination via the call distribution element allocated there. If the first few digits of the phone number match the number entered under regional prefix in the numbering plan, they will be truncated before the search for a suitable direct dial number is carried out.
Page 189 Call routing Parameter Parameter value Call distribution element 3: • Destinations Switch position 1: User 220 + KT • Incoming connections Number of connections allowed simultaneously Direct Routing A call without direct dialling is routed directly to a destination of the internal num- bering plan.
Page 190: Personal Call Routing
Call routing 6. 3. 1. 3 Personal call routing Several terminals can be allocated to an internal user. A call to this user is routed to all the terminals allocated to him or only to a number of them (see "One Number user concept", page 368).
Page 191 Call routing Tab. 46 Interaction of Default Call Forwarding with... Function / Configuration / Situation Response CFU or CFB active Only CFU is executed (*21 and *67 still have priority over the default call forwarding at the user. Call Deflection (CD) activated before Default Call Default Call Forwarding is not executed Forwarding CFNR activated after 0, 3, 5 or 7 rings...
Page 192 Call routing Default Call Forwarding with calls already forwarded: Situation: User A calls user B, who has redirected to user C. A default call forwarding to user D is configured at user C. Tab. 47 Default Call Forwarding response to calls already forwarded User B has …...
Page 193: Response If Busy
Call routing 6. 3. 3 Response if busy The following Chapter describes how the system responds when busy and how that response can be influenced using specific settings. 6. 3. 3. 1 Response if the call destination is busy If the call destination is busy, an incoming call will be handled according to the type of destination.
Page 194 Call routing Call waiting not allowed or not possible If no alternative destinations have been configured, the following rules apply: • In the case of an incoming call from the public ISDN network the caller obtains the busy tone. If the caller has subscribed to the service Automatic callback (CCBS) with the net- work provider, he can activate that service.
Page 195 Call routing Fig. 83 Call distribution if user is busy System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 196 Call routing Call destination: Busy User Group A user group is busy if all its members are busy, if call waiting is rejected, if call wait- ing is not enabled for any of the user group members and if neither the element operator console nor the element general bell is activated.
Page 197 Call routing Fig. 84 Call distribution if user group busy Call destination: Busy KT Line If an incoming call is routed to a busy KT line, the call will be rejected and the caller obtains the busy tone. Call destination: User with a Stored Message If a user has stored a message, an incoming call will be routed to the preconfigured Call Forwarding Unconditional destination.
Page 198: Forwarding A Call If Busy
Call routing 6. 3. 3. 2 Forwarding a call if busy To ensure that each incoming call is answered, the following configuration recom- mendations must be observed: Configuration for Users and Terminating KT Lines • Configure Call Forwarding on No Reply if busy and preconfigured Call Forward- ing on No Reply.
Page 199: Not Forwarding A Call If Busy
Call routing 6. 3. 3. 3 Not Forwarding a Call if busy If the caller is to obtain the busy tone when the user is busy, the following configu- ration recommendations must be observed: • Do not configure an alternative destination if busy (leave the CDE if busy setting blank).
Page 200: Response If Unobtainable
Call routing 6. 3. 4 Response if unobtainable Various redirection destinations can be configured for each user so that ideally no calls are left to idle for whatever technical reasons. The call is then redirected de- pending on why the terminal is unobtainable and the call’s origin (internal/exter- nal).
Page 201 Call routing Note: If PSTN overflow is enabled and configured in the AIN, an attempt will first be made to route the call via the PSTN. Category 3: Satellite in offline mode or terminal port inactive • The required user is on a satellite that is currently in offline mode. •...
Page 202: Emergency Routing
Call routing 6. 3. 5 Emergency Routing 6. 3. 5. 1 Routing if the Call Destination is busy If the call destination is busy, an incoming call will be handled according to the type of destination. Busy call destinations may be: •...
Page 203: Release Destination If Dialling Is Incomplete
Aastra Intelligent Net: In an AIN the availability of Capolinea depends on the Master settings. If the Country parameter is configured to IT on the Master, Capolinea is available throughout the AIN.
Page 204: Automatic Reject Of Collect Calls
Call routing 6. 4 Automatic reject of collect calls The public network in Brazil offers the possibility of collect calls. A collect call is a call in which the called party accepts the costs of the call. The called party normally has a few seconds to reject the collect call before he incurs costs.
Page 205 Call routing Handling of collect calls The handling of collect calls can be configured with various parameters per trunk group, per user group, and per user: Tab. 53 Handling collect calls: Trunk group configuration Parameter Meaning Handling of collect calls Trunk group configuration •...
Page 206: Outgoing Traffic
Call routing 6. 5 Outgoing traffic All outgoing calls are routed to a network via a route. The authorization to make outgoing calls can be specified for each user (page 218). Digit barring facilities can also be used to regulate dialling access on the basis of the numbers dialled (page 207).
Page 207: Digit Barring
Call routing 6. 5. 2 Digit barring Digit barring facilities are user-definable filters used for regulating exchange access authorization based on the numbers dialled. Several digit barring facilities are available in each case for internal and outgoing traffic (internal and external digit barring facilities).
Page 208 Call routing Bypassing the digit barring Digit barring facilities are bypassed in the following cases: • Deactivation of the external digit barring allocated to the user in the route con- figuration Example: The digit barring is deactivated in the route configuration for route 1 and acti- vated in the route configuration for route 2.
Page 209 Call routing Example: • Basic function enable all • Digit "6" is entered in the barring list. This digit barring restricts all phone num- bers that begin with 6. • The digit sequence "62" is entered in the barring list. This digit barring only re- stricts phone numbers that begin with 62.
Page 210 Call routing Examples of digit barring facilities A user or user group may only dial the following external destinations: • Destinations within their own network group • Destinations of network group 031 and 033 • Destinations in Germany (0049) The following restrictions also apply: •...
Page 211: Call To The Public Network
Remote control (*06) of */# function codes and setting of the system time and system date (*57, *58) barred. • Internal digit barring 8 (Aastra 415/430) and 16(Aastra 470): Remote control ex- ternal barred (ERC *75, *85). Aastra Intelligent Net: In an AIN the digit barring settings apply to the entire network.
Page 212 A name can be stored with each abbreviated dialling number, thereby also ena- bling name dialling. Aastra Intelligent Net: In an AIN with nodes in different countries the abbreviated dialling num- bers must always include the international prefix (e.g. "00") and the coun- try code (e.g.
Page 213 Call routing Dialling the emergency number Depending on the switch group and switch position, the emergency number dials one of the three stored phone numbers. The phone numbers must have an ex- change access prefix. The external digit barring is bypassed. The call is routed via the user’s route, provided the stored phone number does not already have a prefix for exchange access with route selection.
Page 214: Routing The Call
Call routing 6. 5. 3. 1 Routing the call One and the same trunk group cannot contain both analogue and digital network interfaces. Fig. 88 Routing a call to the public network Tab. 54 Setting the routing parameters Parameter Parameter value User configuration BN 220: •...
Page 215: Call To The Public Network Via A Key Telephone
Call routing 6. 5. 3. 2 Call to the public Network via a Key Telephone Dialling via a line key on a key telephone routes the call via the allocated KT route The KT route is entered in the call distribution element of the KT line. The call charges can be logged (among others) at the KT cost centre.
Page 216: Call To The Public Network Via An Operator Console
Call routing Parameter Parameter value • Network interfaces Network interfaces of this trunk group • Network type Public • Protocol DSS1 Not relevant for trunk groups with analogue network interfaces 6. 5. 3. 3 Call to the public Network via an operator console Dialling via a line key of Company A routes the call via Route 1.
Page 217 Call routing Fig. 90 Routing a call to a virtual network PISN user via the public network Tab. 56 Setting the routing parameters Parameter Parameter value User configuration PISN-BN 440: • Route 1 (route reference number) • Number 333 33 40 (phone number to be dialled, without exchange access prefix) Route 1 •...
Page 218: Exchange Access
External priority = emergency). Fig. 91 Network access rights for users with and without Priority exchange allocation Aastra Intelligent Net: In an AIN, priority exchange allocation can only be guaranteed on the local exchange interfaces, not across the entire network. Example...
Page 219 Call routing Fig. 92 Overview of a configuration for emergency applications Scope The priority setting is activated only in the case of direct dialling, not however in the case of call forwarding, CFNR etc In a private network the prioritization of an outgoing connection is only possible on the communication server connected to the public network (gateway PINX).
Page 220: Call To The Private Leased-Line Network
Call routing 6. 5. 4 Call to the private Leased-Line Network The call to a fixed network PISN user is routed via the private leased-line network. The PISN user must be created in the internal numbering plan. The caller dials the PISN user number.
Page 221: Call To A Dss1 Terminal Equipment On The S Bus (Ddo)
Call routing Parameter Parameter value • Numbering plan identifier NPI Trunk group 2 • Network interfaces Network interfaces of this trunk group • Network type Private • Protocol QSIG QSIG / PSS1 ISO 6. 5. 5 Call to a DSS1 Terminal equipment on the S Bus (DDO) The BRI-S interface can be used to address a terminal equipment that has its external...
Page 222: Least Cost Routing (Lcr)
Protocol DSS1 Terminals with a separate direct dialling plan down circuit from an Aastra 400 com- munication server can also be addressed from the public or private leased-line. From a routing technology viewpoint this corresponds to the situation "Routing a call from the public / private network to the PISN"...
Page 223 Call routing The network of the required network provider can be reached directly or indirectly from the communication server. Direct Network Access The communication server is directly connected with several networks operated by different network providers. Fig. 95 Direct access to network A or B using LCR Indirect Network Access The communication server is connected to a specific network (network A).
Page 224: Lcr Function
Call routing For indirect access the phone number dialled must contain the following informa- tion: • Call number of the destination user. • Network provider required (in the example network provider B). • The code information (in the example for network provider B) used by B to check whether the caller is a subscriber to his network.
Page 225 Call routing Fig. 97 Outgoing exchange traffic using LCR The call is analysed and routed in three stages: • Classification of the outgoing call on the basis of the LCR table and allocation to a particular routing table. • Using the routing table to select a primary and alternative network provider, de- pending on the time of day and the weekday.
Page 226 Call routing Fig. 98 Example of call routing using the LCR function System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 227: Allocating The Internal Routing Table (Lcr Table)
Call routing 6. 6. 3 Allocating the Internal Routing Table (LCR Table) The LCR table is used to categorize an outgoing call and allocate it to a routing ta- ble. A call is categorized by the evaluation of the phone number digits. The first digits of an external phone number can be evaluated in terms of the LCR function if they are entered in the LCR table (evaluatable digit sequence) and allo- cated to a routing table (2nd column).
Page 228 Call routing External and PISN-Internal Entries (E and I Prefix) To indicate whether an entry in the LCR table relates to an external destination in the public network or to a destination in the private leased-line network, the prefix (for external) or (for PISN-internal) must be added to the digit sequence.
Page 229 Call routing Fig. 99 Routing the emergency number 999 If "E999" is entered for the emergency number instead of "X999", an exceptional routing can be configured. The table below shows the routing for prefixes X and E. Tab. 62 Difference in routing with the X prefix and the E prefix Force network provider is ena- Force network provider is not ena- Dialling "999"...
Page 230: Selecting The Network Provider (Routing Tables)
Call routing 6. 6. 4 Selecting the Network Provider (Routing Tables) The routing tables are used to select a primary or an alternative network provider for a categorized call, depending on the time of day and the weekday. A total of 20 routing tables with up to 10 time zones each can be defined. Tab.
Page 231: Time Zones
Call routing 6. 6. 4. 1 Time zones The time zones are used to allocate network providers depending on the time of day. This means it is possible to take account of the fact that network provider 3 for example is more cost effective at night than network provider 2 If the time at which a connection is set up is outside the defined time zones the call is routed in accordance with the user configuration (without LCR function).
Page 232: Alternative Routing (Fallback Routing)
Call routing 6. 6. 4. 2 Alternative Routing (Fallback Routing) If the LCR function realizes that access to the network provider initially selected is not possible, a call is routed to the alternative network provider and an event mes- sage is generated (LCR via alternative network provider).
Page 233: Conversion And Routing (Network Provider Table)
Call routing 6. 6. 5 Conversion and Routing (Network Provider Table) The phone numbers are converted specifically for each network provider based on the network provider table; the call routing is then determined. 20 network provid- ers can be entered in the table. Tab.
Page 234 Call routing Conversion Rules The conversion rules specify how a dialled phone number is to be converted to en- able automatic access to a network provider. Tab. 68 Conversion rule parameters Parameter Meaning Add access code "0"–"9", "*", "#" Add specified characters Add dialled phone number <x–y>...
Page 235 Call routing Examples Relating to the conversion Rules Access code for network B via network A: 132 User dials: 0-0 1222 774518 User-ID: 26013 PIN: 7725 Fig. 100 Reference illustration for the following examples Tab. 70 Table with examples of conversion rules and phone numbers converted accordingly Rule Conversions Result string...
Page 236: Bypassing Lcr Manually (Forced Routing)
Call routing 6. 6. 6 Bypassing LCR manually (Forced Routing) A user may be authorized through the user configuration to determine the net- work provider himself by bypassing the LCR settings (Force route = Yes). Depending on whether the network provider he wants is connected directly or in- directly, the user will add to the phone number either a route prefix or the prefix of the network provider he wants.
Page 237: Lcr With Key Telephones
(see also "Alternative Routing (Fallback Routing)", page 232). Aastra Intelligent Net: In an AIN the master’s LCR configuration always applies to all the nodes. The LCR configuration of a satellite is effective in the offline mode only (i. e. when the connection to the master is interrupted).
Page 238: Call Logging And Data Protection
Call routing 6. 6. 9 Call logging and Data Protection In connection with the LCR function, the OCL output format PC5 (recommended) or PC4 must be used (see "Output formats", page 312). When the data protection function is activated, the following data will not be out- put or output only in part, in OCL output format PC5 and PC4: •...
Page 239 Call routing 1. Stage: • The system reaches network provider B via network provider A • Network provider B seizes and the connection provider B – communication server is set up 2. Stage: The system transmits the phone number in DTMF mode in accordance with the configured conversion rule.
Page 240: Higher-Level Lcr Settings
Call routing 6. 6. 11 Higher-Level LCR Settings The table below summarizes once again the higher-level LCR settings. Tab. 75 LCR settings Parameter Parameter Remarks value Least Cost Routing (Account Manager): • LCR On / Off Activate / deactivate LCR function throughout the system (see page 224)
Page 241: Exchange-To-Exchange Connection
Call routing 6. 7 Exchange-to-Exchange Connection Exchange-to-exchange traffic covers all interactions involving at least 2 users in the public network and at least 1 internal user. 6. 7. 1 Exchange-to-Exchange Connections In an exchange-to-exchange connection two seized exchange lines to the public network are connected with each other locally in the communication server.
Page 242: Setting Up Exchange-To-Exchange Connections
Call routing User-specific configuration The settings described in the last section can also be configured individually for each user. The user-specific configuration takes priority over the setting for the sys- tem as a whole. If a user’s settings are not to deviate from the settings made for the system as a whole, the parameter has to be configured to According to exchange settings...
Page 243: Clearing Down Exchange-To-Exchange Connections
Call routing 6. 7. 1. 2 Clearing down Exchange-to-Exchange Connections Digital-Digital (D-D): The public network sends the communication server a release signal once the ex- ternal call partners of an exchange-to-exchange connection have finished the call. The connection can then be cleared down by the communication server. Without a release signal, the communication server cannot clear down an ex- change-to-exchange connection.
Page 244 With this setting the detection can be adapted to the existing level. Aastra Intelligent Net: Detection of the congestion tone is automatically adapted to the country configured under the region. In an AIN the nodes may be spread over dif- ferent regions or even countries.
Page 245 Call routing System configuration Tab. 77 Exchange-to-exchange connections: System configuration Parameter Parameter value Remarks Exchange settings: • Exchange-to-Exchange Not enabled Digital-digital only Throughout the system Connection Digital-analogue also Analogue-ana- logue also • Disconnect timeout <1...120 minutes> valid only for call type Analogue-Ana- logue •...
Page 246: Possible Exchange-To-Exchange Connections
Call routing 6. 7. 1. 3 Possible Exchange-to-Exchange Connections The following system features can be used to set up exchange-to-exchange con- nections: • Call Forwarding Unconditional • Call Forwarding on No Reply • Call Deflection • Switching calls • Conference circuit The following tables and examples illustrate which features are available in which situations.
Page 247 Call routing Connecting two outgoing calls This situation occurs for example • when setting up a conference when both conference parties are called. • when the attendant sets up a connection for a member of staff, then calls him back and transfers the call. Tab.
Page 248 Call routing Two incoming calls The B channels of two incoming calls can be connected with each other via a con- ference circuit or by a normal call handover by going on-hook (transfer). Tab. 80 Features supported Switching calls User A User C Conference circuit Fig.
Page 249: Transferring Call Forwarding Unconditional To The Exchange
Call routing 6. 7. 2 Transferring Call Forwarding Unconditional to the Exchange Internal users can divert their terminal to external destinations. When an external user calls the destination diverted externally, the exchange-to-exchange connec- tion created occupies two B channels. The system can be configured so that such call forwarding are transferred from the communication server to the public network, thus freeing the two B channels.
Page 250 Call routing Call Deflection Call Deflection (CD) is a supplementary service for ISDN users and is available only on a point-to-multipoint connection. Call deflection can be used to reroute a call during the ringing phase. The feature is also provided at the user interface (see "De- flecting a call during the ringing phase (CD)", page 381).
Page 251 Call routing With all call forwarding functions the call only continues ringing at user C once it has been forwarded to the exchange. Prerequisites Call forwarding to the exchange is subject to the following requirements: • ISDN network interfaces BRI-T/PRI (QSIG and analogue are not supported). •...
Page 252: Three-Party Connections In The Exchange
Call routing 6. 7. 3 Three-Party Connections in the Exchange A locally implemented three-party connection with two external users takes up two B channels. In point-to-multipoint operation the system can be configured so that the node of such a three-party connection is transferred from the communication server to the public network, thereby freeing up at least one B channel and other system re- sources.
Page 253 Call routing Description of the Procedure Calls on hold in the exchange (Fig. 108): • User is through to user B. • User B puts user A on hold: The call is put on hold locally in the communication server. •...
Page 254 Call routing Prerequisites The following requirements have to be met for three-party connections in the ex- change to be activated: • Basic accesses in point-to-multipoint operation (DSS1 only; QSIG and analogue not supported). • For Italy only: Basic accesses in point-to-point operation (DSS1 only; QSIG and analogue not supported).
Page 255 Call routing System configuration Tab. 83 Transferring three-party connections to the exchange: Settings Parameter Parameter value User configuration: • Exchange access authorization Network interface: • TEI management P-MP Trunk group configuration: • Transfer hold to the exchange • Three-party conference in the exchange •...
Page 256: Transit Routing In The Private Leased-Line Network
PINX in the private leased-line network, it assumes a transit function. It therefore acts as the transit PINX for the call. In this chapter you will find out how Aastra 400 resolves the gateway and transit function , and the settings required.
Page 257: From The Public Network To The Private Leased-Line Network
Call routing 6. 8. 1 From the Public Network to the Private Leased-Line Network Routing with Direct Dialling It is advisable to create direct dial numbers at the gateway PINX for all PISN users. An incoming call from the public network will then be routed on into the private leased-line network in accordance with the information relating to the dialled PISN user.
Page 258 Call routing Tab. 84 Routing parameter settings Parameter Parameter value Trunk group 1: • Network interfaces Network interfaces in this trunk group • Incoming connection Number of connections allowed simultaneously • Network type Public • Protocol DSS1 • Direct dialling plan 1 (number of a direct dialling plan) •...
Page 259 Call routing Routing without Direct Dialling An incoming call from the public network is routed on to the private leased-line network in accordance with the information relating to the PISN user allocated via the call distribution element. This is useful in only a few instances since all the calls are routed via the same call distribution element.
Page 260 Call routing Tab. 85 Routing parameter settings Parameter Parameter value Trunk group 1: • Network interfaces Network interfaces in this trunk group • Incoming connection Number of connections allowed simultaneously • Network type Public • Protocol DSS1 • Direct dialling plan 1 (relevant only if a suitable DD number is found) •...
Page 261: From The Private Leased-Line Network Into The Public Network
Call routing 6. 8. 2 From the private leased-line network into the public network A PINX will route an incoming call from the private leased-line network on towards the public network if the incoming call has a phone number • with NPI E.164 •...
Page 262 Call routing Tab. 86 Settings for PINX 2 routing parameters Parameter Parameter value Route 1: • Trunk groups 1 (reference number of one or more trunk group(s)) • Numbering plan identifier NPI E.164 • Type of number TON Unknown • Send access code –...
Page 263 Call routing The exchange access prefix is set under Send access code in the route configuration of the source PINX. One and the same trunk group cannot contain both analogue and digital network interfaces. Transit routing for private leased-line network → public network with exchange access prefix Fig.
Page 264: From The Private Leased-Line Network Into The Private Leased
Call routing 6. 8. 3 From the private leased-line network into the private leased-line network A call from the private leased-line network will be routed on at the transit PINX in accordance with the information of the PISN destination user. If the transit PINX is located in the same region as the destination user, the phone number’s regional prefix will be truncated.
Page 265: Testing Overflow Routing In The Pisn
Call routing Parameter Parameter value • Direct dialling plan 1 (relevant only if a suitable DD number is found) • Call Distribution Element Not relevant to this case User configuration PISN-BN 330: • Route 2 (route reference number) • Number Phone number to be dialled without exchange access prefix Route 2: •...
Page 266: Overflow Routing Within The Private Leased-Line Network
Call routing 6. 9. 1 Overflow routing within the private leased-line net- work Fig. 116 Overflow routing in the private leased-line network via dedicated lines Overflow routing in the private network can be resolved with the appropriate route configuration: Configuration example In PINX 1 let route 6 be provided for outgoing calls to PINX 3.
Page 267: Overflow Routing Via The Public Network
Call routing Fig. 117 Overflow routing in the private leased-line network using a sensible trunk group allocation in the route configuration 6. 9. 2 Overflow routing via the public network Fig. 118 Overflow via the public network -- the LCR function is used for this purpose Overflow routing via the public network is resolved using Least Cost Routing.
Page 268 Call routing Configuration example Fig. 119 Configuration example of overflow routing via the public network In PINX 1’s numbering plan, the PISN users of PINX 2 are entered according to the principle 60xxx. The numbers of the internal users match with their direct dial numbers (user B has internal number 300 and direct dial number 300).
Page 269 Call routing • Under normal conditions, calls whose phone numbers begin with "60" will be routed in accordance with the user configuration. If the normal path is not avail- able, the calls will be routed via the alternative network operator. •...
Page 270: Break-Out
Call routing 6. 10 Break-Out An outgoing, external call is to be routed into the public ISDN only at the PINX that is closest to the call destination. If the source PINX and gateway PINX are a long way apart and connected with each other via dedicated lines, break-out can help to achieve considerable call charge savings.
Page 271 Call routing Configuration example The PINXs of a company with branch offices in Zurich and Geneva respectively are connected with each other via a dedicated line. Outgoing calls made from Geneva to the local rate zone in Zurich are always to be routed into the public network at Zurich.
Page 272 Call routing Planning the routes and trunk groups To keep a network configuration as transparent as possible, it is a good idea always to use the same trunk group and the same route for the same function on all the PINXs.
Page 273 Call routing Tab. 91 Settings for break-out routing at the source PINX (PINX 1 in Geneva) Parameter Parameter value User configuration: • Automatic CLIP (permanently CLIP number entry is used) • E.164 • National • CLIP number 022 827 9x xx (x stands for the user’s DD number) LCR table: •...
Page 274 Call routing Settings at the gateway PINX (PINX 2) Specifying the transit route The transit route is specified using the Transit route setting. If an incoming call has a phone number with numbering plan identifier = E.164, it will be forwarded via the defined route.
Page 275: Data Service
This section also deals with user-to-user signalling and the fax service on a CPU2 applications card (Aastra 470 only). 7. 1 Overview Outgoing data-service connections are set up and routed in a similar way to call connections.
Page 276: Data-Service Connections And Destination Tables
Data service 7. 2 Data-service connections and destination tables Data-service connections are routed via the call distribution element to a data- service destination table. In the data-service destination table each data-service type is allocated internal or PISN-internal destinations. There are several data-serv- ice destination tables;...
Page 277 Data service Routing to a destination in the data-service destination table Fig. 122 Incoming data-service routing from the public network with direct dialling to a destination in the data-service destination table Tab. 94 Routing parameter settings Parameter Parameter value Trunk group 1: •...
Page 278 Data service Routing to a data-service individual destination If in the data-service destination table Individual destination is entered as the desti- nation for a data service type, the call is routed to the destination entered under Data service individual destination in the call distribution element.
Page 279 Data service The call is also routed to this destination if no data-service destination table is allo- cated in the call distribution element: Fig. 124 Incoming data-service routing from the public network with direct dialling to a data-service individual destination but without entry in a data-service destination table System functions and features as of R3.0 syd-0367/1.3 –...
Page 280: Routing In The Private Leased-Line Network
Data service 7. 3 Routing in the private leased-line network Data services are also available in the private leased-line network. To route a call at a gateway or transit PINX on into the private leased-line network, a PISN user is en- tered as the data service destination.
Page 281 Data service Parameter Parameter value • Data-service destination table 2 (reference number of the data-service destination table) Data-service destination table 2: • Data service type Fax 4 PISN user 330 User configuration PISN-BN 330: • Route 2 (route reference number) •...
Page 282: User-To-User Signalling (Uus)
UUS is not supported in the private leased-line network and is only available at the PINX which is connected to the public network. Aastra Intelligent Net: UUS is not supported in an AIN. The service is available only at the nodes that are connected to the public network.
Page 283: Fax Service
• e-mail confirmation to sender once fax message has been successfully sent. Scope The fax service only runs on the CPU2 applications card of an Aastra 470. It can be used both on a single system and in networked systems. Supports fax messages of the type Group 3 fax.
Page 284 Data service Setting up the fax service on the communication server To set up the fax service on the communication server via a digital network inter- face (ISDN/CAS or SIP), proceed as follows: 1. Configure the fax server settings (see Tab.
Page 285 • Start the fax client setup, with the following parameter request, whereby you must replace fax.local with the new domain name: Aastra-Fax-Client- Setup32.exe /v“REG_ADDREXTFAXPREFIX=\”[SMTP:\” REG_ADDREXTFAXPOSTFIX=\”@fax.local]\”” • Check the registry input. This should be as follows, with the new domain name in place HKEY_LOCAL_MACHINE\SOFT- of fax.local:...
Page 286 Data service Parameter Explanation Trunk group settings (CM_3.1.5) Base number For digital network interfaces: The base number is the call number for the direct dial range for the fax destinations with- out the direct dial portion. Enter the base number in canonical format. Example: •...
Page 287: Call Logging (Cl)
Call logging (CL) Call logging (CL) Call data and call charges can be logged and evaluated in great detail with the aid of the system. This Chapter explains the concept of individual charge counting (ICC) and the setting options for logging call data for outgoing (OCL) and incoming (ICL) calls.
Page 288 Call logging (CL) Individual charge counting or ICC At the end of a call individual charge counting (ICC) assigns call charges to individ- ually allocated cumulative counters. The data is stored in the communication server, and it can be viewed via the system configuration and output in a variety of ways via the Ethernet interface See also: "Individual charge counting or ICC", page 290...
Page 289 Call logging (CL) Call logging in the PISN In a PISN, call data is logged for each PINX. PISN-wide evaluation is carried out us- ing PC-based applications for the acquisition and evaluation of call data. Fig. 128 Call logging in the PISN System functions and features as of R3.0 syd-0367/1.3 –...
Page 290: Individual Charge Counting Or Icc
Call logging (CL) 8. 2 Individual charge counting or ICC Individual charge counting (ICC) automatically assigns call charges to cumulative counters at the end of a call; these call charges can be viewed in the System Config- uration, output at the corresponding interface as individual or complete reports, or deleted.
Page 291 Call logging (CL) Counter readings Each counter indicates the following values: • Total amount of the call connections • Charges for the last call connection • Number of connections • Logging period for the call data Call charge allocation • Network interface counters add up all the call charges incurred via their network interface.
Page 292 The amount per metering pulse and the local currency depend on the parameter settings in the OCL/ICC menu. Aastra Intelligent Net: In an AIN call logging takes place centrally on the Master. Call charges are displayed on the system phones in the same format and in the same cur- rency throughout the AIN.
Page 293: Surcharge Calculator
Call logging (CL) drain counter All call charges that cannot be unambiguously allocated will be added up by the system in a drain counter (cost centre 100). Example: Call charges for a call that was active when emergency operation was released (Business/Private allocation not possible).
Page 294: Icc Reports
Call logging (CL) 8. 2. 3 ICC reports ICC reports list all call charges over a user-definable period of time. The reports are output on the printer or PC set up for ICC. There are two different kinds of ICC reports: •...
Page 295 Call logging (CL) Fig. 135 Individual report for a network interface Fig. 136 Individual report for all calls made by Room 34 Individual reports or individual receipts can also specify the following status infor- mation: Tab. 98 Additional information between Numbers and Connections Symbol Meaning If a cumulative counter has been printed out but not cleared (interim report), the cumulative coun- ter is automatically marked with an "*".
Page 296 Call logging (CL) Complete reports All cumulative counters are printed out continuously, with a new page for each par- tial area. The entire header is printed out and a serial number added. If an A4 page is insufficient to hold all the related data of an area, a new page is started, with only the headers repeated to explain the columns.
Page 297 Call logging (CL) Fig. 139 Complete report for business data connections Fig. 140 Complete report for all network interfaces System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 298: Call Logging For Outgoing Calls (Ocl)
Call logging (CL) 8. 3 Call logging for outgoing calls (OCL) OCL is used to log the outgoing connection data of individual calls and output the data via the system’s corresponding interface at the end of the call. OCL can be acti- vated and deactivated throughout the system and for each user.
Page 299: General Ocl Settings
The ICC, however, logs all the call charges and allocates them to the cumulative counters. Aastra Intelligent Net: In an AIN the charge values as of which a printout is made can be adapted specifically for each node using the AMS Configuration Manager. Please...
Page 300 Call logging (CL) Digit barring if output is blocked If for whatever reason the printer cannot print or the PC cannot receive data (see "Printer faults", page 311), the next calls are stored internally in the communication server. After that, the selected digit barring (e.g. 1) becomes active. Then only the numbers enabled by the digit barring can be dialled.
Page 301: Surcharge Calculator
Call logging (CL) 8. 3. 2 Surcharge calculator The surcharge calculator is used to assess surcharges on top of the official call charges. Four independent surcharge calculators can be configured and allocated to the cu- mulative counters of the users or rooms. Call charges are indicated to each user (only on system phones with a display) while the call is in progress.
Page 302 Call logging (CL) Fig. 143 Cost curve for the application example See also: System configuration: – OCL/ICC/ICL – OCL; user configuration – Charge pulse; User configuration – OCL; only on connection – Report; OCL/ICC/ICL – Surcharge calculator; OCL/ICC/ICL parameters System functions and features as of R3.0 syd-0367/1.3 –...
Page 303: Data Protection
Call logging (CL) 8. 3. 3 Data protection The system offers the option to activate data protection, i. e. to blank out on the printout the last 4 digits of the number dialled (Fig. 144). Data protection can be ac- tivated separately for business and private calls.
Page 304 Call logging (CL) Variable allocation Individual calls can be assigned to a cost centre either before the call by dialling the exchange access prefix code for cost centre selection or during the call using a */# function code. With line keys, variable cost centre allocation is possible only using a */# function code.
Page 305: Charge Management
Call logging (CL) 8. 3. 5 Charge management If an external call is forwarded internally, the charges incurred can be passed on to the next user. This feature can be activated and deactivated throughout the system and applies only locally in the PINX. User A is making an outside call. After a while he hands the call over to user B.
Page 306: Virtual Charges
Call logging (CL) 8. 3. 6 Virtual charges You have the possibility of setting up virtual charge counting for exchange line cir- cuits that do not provide call charge information (e. g. SIP). To do so, enter the charge pulse interval in seconds in the route configuration (CM_3.1.6) using the pa- rameter Pulse interval for virtual charges.
Page 307 Call logging (CL) Fig. 147 Incoming call logging ICL can be switched on or off for each call distribution element. Sort characters are used to differentiate between data and call connections and be- tween answered, transferred and unanswered calls. Fig. 148 ICL can be switched on or off in each call distribution element System functions and features as of R3.0 syd-0367/1.3 –...
Page 308 Call logging (CL) Application Example • Customer service: 032 655 33 33 • ON, for customer service calls only (see Fig. 148). Analysis is used to determine the quality of the call handling. One possible result of the analysis is that customer service is constantly busy between 10 a.m. and 11 a.m., and that an extra employee might be required during that period.
Page 309: Call Data Output
Call logging (CL) 8. 5 Call data output The ICL, OCL and ICC data is output on printers or other output devices via the Eth- ernet interface. It is possible to configure which data is output on which of the available interfaces.
Page 310: Output Types
Call logging (CL) 8. 5. 1 Output types The output type depends on who triggered the output. The output types are as fol- lows: Output type ICC output • Output at user’s request, e.g. using a command on the operator console •...
Page 311: Printer Faults
Call logging (CL) Setting the page length In principle, the page length can be set individually for all output types. If, however, only one output device is connected, the page length set for Service printer output type will apply. 8. 6 Printer faults If it is not possible to print on the CL printer for at least one minute (e.g.
Page 312: Output Formats
Call logging (CL) 8. 7 Output formats An output format defines which call data is to be output in which format. The fol- lowing output formats are available: Formats PC1 to PC5 Used for output on a PC. The PC5 format is the most comprehensive PC format and is recommended for all systems upgraded with a new PC application for the acqui- sition and evaluation of call data.
Page 313: Structure Of The Pc5 Output Format
Call logging (CL) 8. 7. 1 Structure of the PC5 output format The PC5 format is used to output incoming and outgoing call data (ICL and OCL) on • stand-alone communication servers • PINX in private networks. It is the most comprehensive PC format and is generally recommended when up- grading with a new PC application for the acquisition and evaluation of call data.
Page 314 Call logging (CL) Data field name In PC5 format the data field name is not output. Data format A data field consists of a certain number of characters and a specific data format. Tab. 105 shows the symbols used for describing the data fields in Tab.
Page 315: Data Fields Of The Pc Format
Call logging (CL) 8. 7. 2 Data fields of the PC format Tab. 107 shows the complete data record of a PC5 output. The data fields are listed in their task sequence. Tab. 107 PC5 format Lengt Data field Name Data format Formatting Offset...
Page 316: Explanation Of The Data Fields
Call logging (CL) 8. 7. 2. 1 Explanation of the data fields User number Outgoing: • Entry for the caller’s user number. • Entry for source PINX and stand-alone communication server; otherwise the data field remains empty. Incoming: • Contains an entry for destination PINX and stand-alone communication server; otherwise the data field remains empty.
Page 317 Call logging (CL) Sort character The three-digit sort character xyz is used for identifying a data record. It is used to make the following distinctions: Tab. 108 Meaning of the digits used in the sort character Digit Meaning Destination/source network and connection direction Type of network access/exchange-to-exchange connections Call handling Tab.
Page 318 Call logging (CL) Value – Outgoing connections on phone booth exten- sions – Outgoing connections on room extensions Rejected connection with destination • ERC (external remote control) • ACD (ACD queue) Tab. 112 Examples of sort characters Sort character Meaning Outgoing connection to the public network, business network access, self dialling Outgoing connection to the PISN, network access with cost centre selection, transferred Outgoing connection to the PISN, network access with cost centre selection, self dialling...
Page 319 Call logging (CL) Date and time of start of connection • Entry for the time of the start of connection on the logging communication server or in the PISN. • In the case of forwarded calls the time logged is the time as of which the trans- ferred call begins.
Page 320 Call logging (CL) Caller identification 1 and caller identification 2 These fields have a different meaning depending on the direction (incoming or outgoing calls). • Caller identification 1, incoming: The number which the calling user wants to present to the called user is entered here.
Page 321 Call logging (CL) Fig. 151 Caller identification outgoing Destination number 1 and destination number 2 These fields have a different meaning depending on the direction (incoming or outgoing calls). • Destination number 1, incoming: – For incoming calls: no entry. –...
Page 322 Call logging (CL) Fig. 152 Destination number incoming • Destination number 1, outgoing: Entry for the call number dialled by the PINX or by the communication server. Depending on the LCR configuration this call number may differ from the call number dialled by the user.
Page 323 Call logging (CL) Fig. 153 Destination number outgoing Time To Answer (TTA response time) In the case of calls transferred internally the call time is logged with the transferred user. The amount of time from the start of the ringing phase to the answering of a direct call is entered here (in seconds).
Page 324: Server
Call logging (CL) 8. 7. 3 Examples of the PC5 output on a stand-alone commu- nication server 8. 7. 3. 1 Outgoing calls to the public network A business call is set up with the public network using self dialling. The digit se- quence 010 is therefore entered as the sort character.
Page 325 Call logging (CL) Fig. 155 Call to a free user and phone conversation • User A (032 624 21 11) calls user B (032 624 22 01). • User B’s terminal rings. • User B answers the call. • User A talks to user B. •...
Page 326 Call logging (CL) Unanswered calls 0 is entered in the Duration field in the case of unanswered calls. The Time Date fields indicate the time at which the call was received. The sort character is 322. The time entered in the field indicates how much time elapsed before the caller hung up.
Page 327 Call logging (CL) Calls to a busy User If a busy user is called while protected against call waiting, 0 is entered in the Dura- tion field. The Time Date fields indicate when the call was received. The sort character is 322. Time To Answer is 0. Fig.
Page 328 Call logging (CL) Transferred call, charge management deactivated The transferred phase of the connection is logged on a separate ICL. The call ini- tially answered is given sort character 321. The sort character for the second ICL line is 320. Fig.
Page 329 Call logging (CL) Tab. 118 ICL output for a transferred call without prior notice DATE TIME DURATION CHARGES METPUL EXCH 020798 10:26 00H01M00 00101 020798 10:27 00H12M03 00101 DEST1 DEST2 SEQ.NO. SERIAL NO. 0326242111 0326242111 0115 0326242111 0326242111 0116 With prior notice: •...
Page 330 Call logging (CL) Tab. 119 ICL output for a transferred call with prior notice DATE TIME DURATION CHARGES METPUL EXCH 020798 10:26 00H01M00 00101 020798 10:27 00H12M03 00101 DEST1 DEST2 SEQ.NO. SERIAL NO. 0326242111 0326242111 0117 0326242111 0326242111 0118 Transferred call, charge management deactivated The entire call is logged in a single line.
Page 331: Examples Of Pc5 Output In A Pisn
Call logging (CL) 8. 7. 4 Examples of PC5 output in a PISN Fig. 163 PISN with two regions and shared numbering plan for Region 50 Tab. 121 Configuration of the PISN above Separate prefix Numbering plan for Internal (local) users PISN users code PINX 1...
Page 332 Call logging (CL) Direct outgoing connection A connection is set up directly to the public network using self dialling (cost type: business). Fig. 164 User B dials user A (0 022 222 22 22) Tab. 122 OCL output on PINX 1 DATE TIME DURATION...
Page 333 Call logging (CL) Tab. 123 OCL output on PINX 2 (source PINX) DATE TIME DURATION CHARGES METPUL EXCH 50300 180598 14:50 00H03m05 0.00 00000 00103 DEST1 DEST2 SEQ.NO. SERIAL NO. 50300 0222222222 0222222222 5677 PISN number of user C. Outgoing call to the PISN. Self dialling network access, business. CHARGES 0 is entered here as the charges are incurred at PINX 1 and are not forwarded to PINX 2.
Page 334 Call logging (CL) Direct incoming call Fig. 166 User A calls user B (055 555 55 50) Tab. 125 ICL output by PINX (destination PINX) DATE TIME DURATION CHARGES METPUL EXCH 50250 180598 14:56 00H01m12 1.50 00015 00101 DEST1 DEST2 SEQ.NO.
Page 335 Call logging (CL) Tab. 126 ICL output (line 1) and OCL output (line 2) at PINX 1 (gateway-PINX) DATE TIME DURATION CHARGES METPUL EXCH 180598 14:56 00H01m12 00103 180598 14:56 00H01m12 0.00 00000 00119 DEST1 DEST2 SEQ.NO. SERIAL NO. 0222220000 0222222222 0012 1237...
Page 336: Protocol Format
Call logging (CL) 8. 7. 5 Protocol format This format is used for direct output on the printer. It is used if data acquisition is not carried out on the data carrier of a corresponding system. The structure with page header and subsequent data lines is designed to make the protocol printout easier to read.
Page 337 Call logging (CL) Content, text Structure Length Print offset 'Underline ''—..— Line 2 end New line The page header • can be suppressed with the setting ..._OCL page length = 99. • Output every time at the beginning of each page. •...
Page 338 Call logging (CL) With Data protection the last 4 digits of the number are replaced by "." (full stop) characters. In Switzerland and other countries this applies to private calls (data protection for business calls never ac- tive); in Germany, business calls (data protection for private calls never active). Example of Protocol format (combined with header line): Fig.
Page 339: Individual Receipt Format
Call logging (CL) 8. 7. 6 Individual receipt format This format is used for output on the receipt printer for the purpose of confirmation and cash collection of the call made immediately beforehand. As this structure is unlikely to be covered by an electronic system, no detailed de- scription of the format will be given here.
Page 340: Output Formats Pc1 To Pc4
Call logging (CL) 8. 7. 7 Output formats PC1 to PC4 Output formats PC1 to PC4 are older formats which, although they are still sup- ported, are no longer being expanded. Output format PC 5 is therefore recom- mended for new applications. At the end of each call the call data logged is printed out on one of the system’s Ethernet interfaces in the CL output...
Page 341 Call logging (CL) Sort character Special characters used in the data string In principle, all outputs are in the form of text based on the ASCII standard. Special, non-printing ASCII characters are used for structuring the data records: Tab. 131 Special characters Meaning Hexadecimal value Usage...
Page 342 Call logging (CL) Tab. 133 The second digit means Value Meaning Direct connection. Appears whenever "7" or "8" does not apply unambiguously. Answered directly (incoming traffic) Unanswered (incoming traffic) Exchange-to-exchange connection, established by CFU / CFNR / CD to the network Exchange-to-exchange connection, transferred by internal user Outgoing data service connections Outgoing connections on phone booth extensions...
Page 343: Pc1 Format
Call logging (CL) 8. 7. 7. 1 PC1 format This format covers requirements for direct transfer to a PC (PC1). Format structure Tab. 135 PC1 format Data field, meaning Structure Format Length Offset Start of data record User (cost centre) number ttttt Sort character Date...
Page 344: Pc2 Format
Call logging (CL) Example of PC1 format The charge data is printed out every time the handset goes on-hook. This also ap- plies in cases where an external connection is forwarded. Fig. 171 CL output with PC1 8. 7. 7. 2 PC2 format This format is an extension of the PC1 format.
Page 345 Call logging (CL) Data field, meaning Structure Format Length Offset Primary channel group / trunk card number / net- cbbpp work interface number Direct dialling numbers ddddddddddd Number of metering pulses iiiii Call number dialled zzzzzzzzzzzzzzzzzzzz Serial number llll Carriage Return Line Feed The primary channel group is output in position "c", the trunk card number in position "bb"...
Page 346: Pc3 Format
Call logging (CL) 8. 7. 7. 3 PC3 format The PC3 format has been expanded to include the fields TTA (Time to answer) and Seq. (Sequence). However, these fields are relevant only to incoming traffic. 8. 7. 7. 4 PC4 format If the feature "Least Cost Routing"...
Page 347 Call logging (CL) Example of PC4 format Fig. 173 CL output with PC4 Depending on the number dialled by the user and the configuration in the LCR ta- bles the number actually dialled by the communication server may be different or identical.
Page 348: Features
Features Features Aastra 400 provides a multitude of features that can be activated or operated by the user. This Chapter contains a systematic description of all these fea- tures. 9. 1 Overview The features described in this chapter are as follows: •...
Page 349: Description Categories And Terminology
Features 9. 1. 1 Description categories and terminology Each feature consists of a detailed description with the following headings: • Scenario • Detailed Description • Prefix and suffix dialling Function Codes • System configuration • Reference to Other Features An illustration represents the feature scenario in a simple, clearly structured form. The following symbols are used: Tab.
Page 350: Information About The System Phones
Information about the system phones Unless otherwise specified, information on the system phonesOffice 45 also in- cludes Office 45pro, Aastra 5360 also includes Aastra 5360ip, Aastra 5361 also in- cludes Aastra 5361ip, Aastra 5370 also includes Aastra 5370ip, Aastra 5380 also in- cludes Aastra 5380ip, Office 135 also includes Office 135pro, Aastra 1560 also in- cludes Aastra 1560ip and Office 1560 also includes Office 1560IP.
Page 351: Terminology
Features 9. 1. 3 Terminology The following terms are used: Tab. 140 Terms are used Term Usage Internal user An internal user has an internal user number. An internal user is assigned one or more terminals. External user An external user is located in the public network (outside the private network). PISN users A PISN user is connected to another node (PINX) of the private network (PISN: Private Integrated Services Network).
Page 352: Network Services, Authorizations And Operation
A certain number of functions such as the three-party conference with two exter- nal users can be carried out both externally in the public network and internally in the communication server. On Aastra SIP phones and a number of standard SIP phones, three-party conferences are possible locally on the phone itself.
Page 353 Features Fig. 174 Conference circuit feature and three-party conference supplementary service The figure below shows a three-party conference connected in the communication server with one internal user and two exchange users: Fig. 175 Three-party conference feature with 1 internal and 2 external users The three-party conference feature is carried out locally in the communication server.
Page 354: Isdn Supplementary Services Supported
Features 9. 2. 1. 2 ISDN supplementary services supported In the following overview ISDN supplementary services are categorized as follows: • Identification services • Connection services • Rerouting services • Call charge services • Other services As a rule network interfaces are wired as a point-to-point connection (P-P). How- ever, the point-to-multipoint (P-MP) connection type is also possible.
Page 355 Features Rerouting services Tab. 143 Rerouting services Name of the service Remark P-MP ✓ ✓ Call Forwarding Unconditional CFU in the exchange, supported via */# function code ✓ ✓ Call Forwarding Busy CFB in the exchange, supported via */# function code ✓...
Page 356: Notifications Supported By The System
A whole range of RFCs are supported for connecting Aastra 400 communication servers to SIP providers on the one hand and SIP terminals to Aastra 400 communi- System functions and features as of R3.0...
Page 357: Features In The Private Network
Features cation servers on the other. They can be found in a table in the "SIP and SIP termi- nals" System Manual. 9. 2. 4 Features in the private network This Chapter describes the user-related features in a PISN. Standardized operation and signalling The way in which a feature is actuated on the terminal and its signalling are identi- cal whatever the network used (local, PISN or public network).
Page 358: Virtual Networking In The Isdn Network
Features 9. 2. 4. 2 Virtual Networking in the ISDN Network In a virtual networking or in a virtual PINX in the public network the following con- ditions have to be met: • The feature is supported end-to-end by the public ISDN network. •...
Page 359: Features In The Up-Circuit Communication Server
In private QSIG networks a number of features can be operated on third-party PINXs via QSIG (applies only to Aastra 400 or Aastra IntelliGate systems). In such cases it is irrelevant whether the QSIG networking is effected via a basic rate access or a primary rate access and which QSIG variant is selected as the protocol.
Page 360: User-Related Features
Features 9. 2. 6. 2 User-related features Operation of the user-related features is subject to the definition of the PISN users in one’s own numbering plan. The features can be divided into two groups: Features That Set up a Call Connection The following user-related features are supported by the communication server and can be activated via the keypad, the function key or the Foxkey: Tab.
Page 361: User-Related Authorizations
Features 9. 2. 7 User-related authorizations A class-of-service authorization in the user configuration is required in order to run user-related features. In addition specific features and call destinations can be disabled using the internal digit barring (see "Digit barring", page 207).
Page 362: Operating The Features On The Terminal
With system phones, features can be operated in the following ways: • Menu-supported with Foxkey for all system phones with a display and for the Aastra 1560 / Office 1560 PC operator console • Using the Foxkey alone, for system phones without a display •...
Page 363: Configurable Keys
2 by double clicking. Note: Double-clicking is not possible on the Foxkey, on the Hotkey (Office 135, Office 160) and on the number keys of an Aastra M535. Tip: The call number of a call distribution element can also be stored under a number key, provided it is listed in the internal numbering plan.
Page 364 • Signalling an existing connection to the team member (differentiating between internal and external call on Office 45, Aastra 5380 and Aastra 1560 / Office 1560). • And, depending on the terminal, other telephony functions (e.g. setting up an...
Page 365: Languages Supported
✓ Hungarian – – – ✓ Welsh – – – ✓ ✓ Russian – – Other languages may be added SIP phones of the Aastra 6700i series only System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 366 Greek. A country-specific language as well as de, fr, and en are provided. The default language is specified for each country after initialization. Aastra 1560 / Office 1560 operator console Operating languages on the operator console: • All the languages listed are available •...
Page 367 Features Default values • The default currency value is defined by country based on international abbrevi- ations. It can be configured in all specified languages at a later time with AMS. • The title for an OCL / ICL printout is defined per country based default value on international abbreviations.
Page 368: One Number User Concept
Note: The function can be executed from any terminal. However the purely visual signalling is supported only by the system phones of the Aastra 5300 and Aastra 5300ip series and by the Aastra 2380ip soft- phone. • The Busy if busy parameter is used to configure whether or not a user should be busy for other callers.
Page 369 • Only one each of the following terminals can be allocated to a user: – Operator console – Aastra 2380ip IP softphone – Softphone Aastra BluStar for PC – Aastra BluStar 8000i SIP phone Functions in prefix dialling Tab. 151 Functions...
Page 370: Call Forwarding Unconditional Functions
Features 9. 4 Call Forwarding Unconditional functions 9. 4. 1 Call Forwarding Unconditional (CFU) Calls intended for B are diverted to destination C. Fig. 179 Call Forwarding Unconditional Call Forwarding Unconditional responds differently depending on the System Con- figuration and the function code used. The various CFU types are as follows: •...
Page 371 5 seconds in which to answer the call. Possible destinations: • Users: internal, external , PISN • Coded ringing • UG: 17 to 21 (Aastra 415/430) or 25 to 29 (Aastra 470) and user groups configured as "large". • Standard text (leave message) Requirement: C is not protected against Call Forwarding Unconditional (*02).
Page 372 Features Functions in prefix dialling Tab. 154 Call Forwarding Unconditional: Functions Function codes Activate CFU / CFB to any user No. *21 destination No. / *67 des- tination No. Activate CFU / CFB to user last configured *21# / *67# Clear CFU / CFB #21 / #67 Activate preconfigured CFU...
Page 373: Call Forwarding Unconditional To Exchange
Features 9. 4. 1. 1 Call Forwarding Unconditional to exchange Settings for exchange-to-exchange traffic (see also "Exchange access authoriza- tions", page 361) • Exchange-to-exchange connection enabled: – External and internal calls are diverted to an external destination; a first-ring CFU is not carried out. Requirement: User with direct dial is defined. –...
Page 374: Wait For Connection" Setting
Features 9. 4. 1. 2 "Wait for connection" setting Specifies whether a Call Forwarding Unconditional of an external call to the ex- change is always switched through or only if the called party answers a call (and a connection is therefore set up): •...
Page 375: Examples Of Call Forwarding Unconditional
Features 9. 4. 1. 3 Examples of Call Forwarding Unconditional The following examples illustrate three different cases of call distribution: • Digital network interface without DDI or DDI number to user. • Digital network interface with DDI number to user + UG busy. •...
Page 376 Features • B makes a CFU to C. • A calls B, communication server sets up direct connection with C, C rings. • The user group will become active irrespective of the configuration of the Wait for connection parameter. • If user B is busy, A obtains the busy tone. Digital network interface with DDI number to user + KT and user + KT busy Fig.
Page 377: Follow Me
Features 9. 4. 2 Follow me User B wants to divert calls originally made to his own terminal to a terminal C, where he is currently located. He therefore configures a Call Forwarding Uncondi- tional directly on destination terminal C. Fig.
Page 378: Call Forwarding On No Reply (Cfnr)
• Users: internal, external , PISN • Coded ringing • UG: 17 to 21 (Aastra 415/430) or 25 to 29 (Aastra 470) and user groups configured as "large". Requirement: C is not protected against calls (Do not disturb, *26) or Call Forwarding Unconditional (*02).
Page 379 Features Note: The internal number of a call distribution element can only be used as the destination for a CFNR in a special case, namely if at least one CDE desti- nation is configured on ACD. If not, Not available is displayed whenever the function is activated.
Page 380 Features Functions in prefix dialling Tab. 160 Call Forwarding on No Reply: Functions Functions Function codes Activate CFNR to user *61 destination No. Clear CFNR to user: Activate CFNR to user last configured *61# Clear CFNR to user last configured Activate preconfigured CFNR Clear preconfigured CFNR Activate CFNR to general bell (coded ringing)
Page 381: Deflecting A Call During The Ringing Phase (Cd)
Features 9. 4. 4 Deflecting a call during the ringing phase (CD) Calls intended for B are deflected to destination C during the ringing phase. (CD: Call Deflection). In such cases the call is not forwarded automatically but manually by user B. Unlike CFNR the call is signalled only at destination C after it has been forwarded.
Page 382 Features • Calls on the line of a key telephone or an operator console cannot be forwarded (exception: the Personal key on an operator console). • If the call is not answered at the destination, a recall is not made. •...
Page 383: Reject Call
Features 9. 4. 5 Reject call Calls for B are rejected during the ringing phase. This immediately clears down the call set-up and therefore the ringing at B. User A obtains the busy tone. Fig. 186 Rejecting a call during the ringing phase Detailed Description Tab.
Page 384: Twin Mode / Twin Comfort
Features Functions during the ringing phase Tab. 166 Rejecting a call: Function Function System phones (without Office 10) Rejecting a call during the ringing phase System configuration Tab. 167 Rejecting a call: System configuration Parameter Parameter value Remarks No settings Reference to Other Features Features: •...
Page 385 Features • Answered call list • Last number redial list: • Message list Note: AMS is used to determine whether Twin Mode or Twin Comfort is avail- able on the cordless phone. If the Twin Comfort function is activated, no other function can be allocated to the charging contact; instead it has to be deactivated again via AMS.
Page 386: Do Not Disturb
Features 9. 4. 7 Do not disturb To ensure that user B is no longer disturbed, all incoming calls are automatically di- verted to an alternative destination C, which has to be specified using the system configuration. Fig. 188 Do not disturb Detailed Description Tab.
Page 387 Features System configuration Tab. 172 Do not disturb: System configuration Parameter Parameter value Remarks Do not disturb <CFU destination> Reference to Other Features Features: • "Call Forwarding Unconditional (CFU)", page 370 System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 388: Substitution
Features 9. 4. 8 Substitution In the attendant’s absence, calls to operator console B can be forwarded to a pre- configured destination C. Fig. 189 Proxy activated Detailed Description Tab. 173 Substitution Inter- Operating sequence / signalling on the termi- Scope face •...
Page 389 Features Function in prefix dialling Tab. 174 Substitution: Function Function Office 45 as operator console Switch proxy on and off System configuration Tab. 175 Substitution: System configuration Parameter Parameter value Remarks Substitution <User No.> Reference to Other Features Features: • "Call Forwarding Unconditional (CFU)", page 370 System functions and features as of R3.0...
Page 390: Dect Follow Me
Features 9. 4. 9 DECT Follow Me The system is such that a DECT call cannot be handed over from one system to an- other (Handover). However, with the new DECT Follow Me feature the reachability of DECT users in a PISN has been improved. This allows a DECT user to be reached without delay in 4 PINXs (DECT Follow me must not be confused with the feature "Follow me", page 377).
Page 391 Application Notes: Application Notes are available for both configuration options (see https://pbxweb.aastra.com Aastra Intelligent Net: In an AIN the availability of the cordless phones across all the nodes is guaranteed even without the "DECT Follow me" feature (network-wide roaming). The phones are automatically registered whenever there is a switch from the coverage range of one node to that of another, and can then be called directly on the new node.
Page 392: Organising Absences On The Workstation
The activated status is indicated on the display. Displaying A’s presence status: Possible system phones: • For internal calls (prior to the call) • Aastra 5300, Aastra 5300ip, Aastra 600d, • In the call lists Aastra 6700i, Aastra 2380ip • During dialling by name •...
Page 393 Features Note In connection with CFUs the CFU last carried out is always active. Example: A presence profile with a CFU to voice mail is currently acti- vated. CFU to a user is then carried out. An incoming call is now routed to this user even if the presence profile is still active.
Page 394 Features System configuration Tab. 178 Presence Profiles User configuration Parameter Parameter value Remarks Description <Text> An additional text can be typed in here to be dis- played to the caller in addition to the presence sta- tus. Example: "I'm in the laboratory." Call forwarding type <Keep settings as is For-...
Page 395: Connections Involving Several Users
Features 9. 5 Connections involving several users 9. 5. 1 Music on hold In the following chapters a user is put on hold in each case in connection with the features Hold, Brokering, Three-Party Conference and Call Transfer. Depending on the configuration selected for the parameter Music on hold the user on hold will ob-...
Page 396 It can be replaced by another file if required. There is also the possibility of recording a text via the phone or to feed in audio data via an audio device connected to the audio input (Aastra 415/430) or an FXS interface in the External audio source (Aastra 470 mode).
Page 397 Features Recording with a phone or audio equipment Recording with the phone: After the function code is entered, a start tone is audible and can be recorded over the handset. Note: Loss of quality is to be expected when recording using DECT, IP or SIP phones.
Page 398 Features Notes: – Wave files with incorrect format cannot be played. – Wave files that are longer than the time available as defined in AMS under CM_7.2_File management cannot be loaded and will generate a corresponding error message. Tips: – To prevent an existing file from being overwritten, the moh.wav file can first be renamed in the communication server’s file system using AMS under CM_7.2_File management.
Page 399: Hold (Enquiry Call)
Features 9. 5. 2 Hold (enquiry call) An A – B connection is put on hold if one of the callers, e.g. user B wants to set up an enquiry call connection with C. Fig. 192 Putting a call on hold Detailed Description Tab.
Page 400: Enquiry Call With Return To Initial Call
Features System configuration Tab. 184 Hold (enquiry call): System configuration Parameter Parameter value Remarks Hold in the exchange • In the group configuration. • Local feature does not require a setting Music on hold None External audio source see also "Music on hold", page 395 Internal audio source Hold tone...
Page 401 Features Detailed Description Tab. 185 Enquiry call with return to initial call Operating sequence / signalling on the termi- Interface Scope Music on hold is played to user A, who is on hold Possible interfaces: internal, external, PISN Possible interfaces: internal, external, PISN With hold in the public exchange, the signalling depends on the network provider.
Page 402: Brokering (Switching Back And Forth Between Two Calls)
Features 9. 5. 4 Brokering (switching back and forth between two calls) A user can switch back and forth as often as required between his call party and the user on hold. Fig. 194 Brokering Detailed Description Tab. 188 Brokering (switching back and forth between two calls) Operating sequence / signalling on the termi- Interface Scope...
Page 403 Features System configuration Tab. 190 Brokering: System configuration Parameter Parameter value Remarks Hold in the exchange • In the group configuration. • Local feature does not require a setting Music on hold None External audio source see also "Music on hold", page 395 Internal audio source Hold tone Welcome announcement...
Page 404: Three-Party Conference From An Enquiry Call
Features 9. 5. 5 Three-party conference from an enquiry call In an enquiry call (with A on hold), B can set up a three-party conference with C. Fig. 195 Three-party conference Detailed Description Tab. 191 Three-party conference (conference from enquiry call) Operating sequence / signalling on the termi- Interface Scope...
Page 405 Features Functions System phones Analogue terminal Three-party conference in • With digit suffix dialling: 5 R 5 (R = control key) the exchange: Return to enquiry call Three-party conference in • R 2 (R = control key) the exchange: Return to •...
Page 406: Conference
Features 9. 5. 6 Conference User A can set up a conference call with several users. This can be done in three dif- ferent ways: • Variable conference: Here the conference participants are all listed in the same dialling string and are all called up at the same time. •...
Page 407 Features Notes: – If the conference tone is deactivated in the system configuration, a conference participant who is intruded upon will not hear an attention tone. Observe the national data protection regulations. With a three- party conference in the public exchange, the signalling depends on the network provider.
Page 408 Note: On SIP phones of the Aastra 6700i series, the Aastra BluStar 8000i and a number of standard SIP phones, three-party conferences are possible locally on the phone. For this, the number of line keys in the terminal con- figuration must be at least 2 and the parameter Conference circuit = In phone.
Page 409: Call Transfer (Switching)
Features 9. 5. 7 Call transfer (switching) Users A and B are in a call. User B hands over the call with or without prior notice to user C. See also: For more information on the switching functions and the operator con- soles, see "Operator console", page 156.
Page 410: Call Transfer Without Prior Notice
Features Suffix dialling function Tab. 199 Call transfer with prior notice: Function Function All terminals Call transfer hang up System configuration Tab. 200 Call transfer with prior notice: System configuration Parameter Parameter value Remarks Hold in the exchange • In the group configuration. •...
Page 411 Features Detailed Description Tab. 201 Call transfer without prior notice Operating sequence / signalling on the termi- Interface Scope If A is on hold, he obtains the ring-back tone or Possible interfaces: Music on hold. internal, external , PISN • When B calls user C, he obtains the ring-back tone (B must hear this tone before he can hand over the call) •...
Page 412: Call Transfer If Busy
Features 9. 5. 7. 3 Call transfer if busy A user B can hand over a call with user A to the busy user C after making an enquiry call to C by activating a recall and then hanging up. As soon as the busy user C is free again, C's phone automatically begins to ring.
Page 413 Features If the call is not answered by C within the configured recall time (C still busy or does not answer), B again obtains ringing (see "Recall", page 414). If user B intrudes on C’s call and then goes on-hook, the call with A is also trans- ferred.
Page 414: Recall
Features 9. 5. 8 Recall Recall reminds a user that a call has been transferred but not answered. Recall is triggered if the internal user does not respond within the recall time in the case of transfer without prior notice. Fig.
Page 415 Features If the transferred user has • activated or CFB, the recall time used is the one defined at the CFU destina- tion. • activated CFNR Default CF if no answer, the switched user’s own recall time is used. • forwarded the call during the ringing phase (Call Deflection), the switched user’s own recall time is used.
Page 416: Call Acceptance
Features 9. 5. 9 Call acceptance An internal user C can accept a connection with user A after being contacted in an enquiry call by user B, who was connected with A. Fig. 201 Call acceptance Detailed Description Tab. 208 Call acceptance Operating sequence / signalling on the termi- Interface Scope...
Page 417: Added Features
Overview Basic voice mail system A basic voice mail system is included in the basic configuration of every Aastra 400 system. Essentially it provides the functions of an answering machine. Each mail- box owner has up to three personal greetings which he can record himself using a phone.
Page 418: Voice Memory Capacity And Voice Channels
For the voice channels the appropriate DSP resources need to be allocated on the DSP chips. Without configuration the Aastra 415/430 communication server only provides the two basic voice-mail voice channels. The Aastra 470 communication server has 8 Enterprise voice mail channels in its basic configuration. An Enterprise Voice Mail licence and 6 Audio Record &...
Page 419: Operation Of The Voice Mail Functions
Features verted to G.729 format using the Aastra WAV Converter. Licences of the type G.729 Codec are also required for the voice compression of audio data. – Voice messages can only be sent as attachments if they are always in G.711 format.
Page 420: Recording Greetings With The Pc And Uploading Them Onto The Communication System
More detailed user information on how to activate a mailbox, signal new voice messages, and listen to, delete and deflect voice messages are described in the User's Guide "Voice mail system on Aastra 400". Note: New voice messages can also be signalled via e-mail using an e-mail sys- tem connected to OIP.
Page 421 Features Note: Aastra 415/430 only: If the Voice mail mode is on Expanded (only G.729), the Wave files have to be converted to the G.729 format prior to the upload with the Aastra WAV Converter. The wave files with the greetings must now be uploaded onto the communication server’s file system:...
Page 422: Audio Guide
Features 9. 6. 1. 5 Audio guide The Audio Guide provides the date, time and call number of voice messages re- ceived and explains the procedure and administration for navigating the voice mail menu when retrieving your own voice messages. Three Audio Guide languages can be loaded onto the system simultaneously and individually allocated to each mailbox.
Page 423 Features Tab. 212 Using macros in the destinations Macro Meaning The "N" macro allows the caller to carry out suffix dialling. This can be a complete call number or part of the end digits of a call number. With macro "K" the system waits for the user PIN to be entered in the form of *PIN# (this is the PIN of the user whose greeting is being played back).
Page 424 Features • Deflect to mailbox (with greeting) The call is transferred to the user mailbox number entered in the field Destina- tion. The mailbox’s active greeting is played back directly. Examples of destinations: – 444: The activated greeting for the mailbox of user 444 is played back. –...
Page 425 Features – If recording is not enabled with the mailbox’s active greeting, a message can still be left. – If the user does not have a mailbox or if an invalid call number is entered, no action is carried out. •...
Page 426: Scope
Features • Case 4: D’s greeting is played back. B leaves a message and hangs up. --> A is connected with D’s mailbox. The greeting is no longer played back, but A can also leave a message. Note: If user B hangs up during or after C’s greeting, A is connected with C’s mailbox. The remaining behaviour is analogous to cases 3 and 4.
Page 427 Features Forwarding in line groups • If a user who is a member of user group uses CFU to forward to voice mail, the behaviour is the same as if he had used CFU to external or to a PISN user (see "Call Forwarding Unconditional (CFU) for user group members", page 147).
Page 428: Access Concept
Features 9. 6. 1. 8 Access concept The mailbox owner can carry out his own voice message management and config- uration of personal greetings. However a special authorization is required for re- cording and deleting global greetings. For this a user must be assigned an authori- zation profile with the administration right Audio services.
Page 429 Features Tab. 214 General mailbox settings Parameter Value range Remarks Mailbox name Mailbox name Mailbox name Number of rings before answer <0..9> CFU delay until the voice mail system answers the call. With Call Forwarding on No Reply (CFNR) the configured delay must also be added.
Page 430 Features Tab. 216 E-mail notification Parameter Value range Remarks Notification of a new voice mes- Newly recorded voice messages generate an e-mail sage to the user’s email address and any additional email destinations that may have been entered. The parameter is configurable only if the user has a valid e-mail address configured.
Page 431 Features Parameter Value range Remarks Recording after greeting enabled Allows the caller to leave a personal voice message after the global greeting. Duration <0..300> sec. Status display greeting x Profile ID auto attendant <Profile name> Each greeting can have a predefined transfer pro- file assigned to it.
Page 432: Functions In Prefix Dialling
Features 9. 6. 1. 10 Functions in prefix dialling Functions for personal greetings On system phones with a display, personal greetings are recorded, monitored and activated using the Foxkey. The same functions are also available using */# function codes. The user operates the settings on his own terminal: Tab.
Page 433: Suffix Dialling Functions
Features "[ ]" the digits inside the brackets are optional "nn" stands for the node number. If no node number is indicated, the node used is that of the terminal with which the functions are carried out. With IP system phones this is always the Master; with cordless phones it is the node at which the phone is currently located.
Page 434 Features Fig. 202 Quick User's Guide Tips: – You can skip the Audio Guide information using the #-key. – The voice mail menu is also available when retrieving messages from the voice mailbox with your own phone (using function code *#94 or by calling the number of the voice mail system).
Page 435: Dialling By Name
Features 9. 6. 2 Dialling by name Instead of entering user B’s phone number, user A can dial user B’s name. The com- munication server supports "dialling by name" and "dialling with quickdial". Please refer to the Operating Instructions of the system phones for more details. Fig.
Page 436: End-Of-Selection Signal
Features 9. 6. 3 End-of-selection signal The input of an external number can be completed with the character #. The com- munication server (or network system) interprets this as the end of selection and immediately switches through. Detailed Description Dialling with end-of-selection signal is important in several cases: •...
Page 437 Features Fig. 205 Dialling with end-of-selection signal with the LCR function activated Function in prefix dialling Completing dialling with end-of-selection signal: External user No. #. System configuration Tab. 224 End-of-selection signal: System configuration Parameter Parameter value Remarks No settings System functions and features as of R3.0 syd-0367/1.3 –...
Page 438: Call Waiting
Features 9. 6. 4 Call waiting Call waiting is used to notify an internal, busy user B that another user C is waiting to talk. User B can choose to take C’s call (and put the original call on hold, end the original call or set up a three-party conference) or reject it.
Page 439 Features Functions Tab. 226 Call waiting: Suffix dialling functions Functions System phones Analogue terminal Activate call waiting • R6 or R*43 • *43 (R = control key) Answer without hold → End call and • answer other call • Use digit suffix dialling: 1 Answer with hold →...
Page 440: Intrusion
Features 9. 6. 5 Intrusion If the called internal user B is busy, the internal user C has the possibility of intrud- ing into the current call. User C hears the current call and has the possibility of talk- ing to user B into whose call C has intruded. User A is not normally aware of this. User B can choose to take C’s call (and put the original call on hold, end the original call, set up a three-party conference) or reject it.
Page 441 Features Tip: If intrusion is disabled, it is possible to send a text message to an intruded user if he has a system phone with display, and to do so even during a call. Functions Tab. 230 Intrusion: Suffix dialling functions Functions System phones Analogue terminal...
Page 442: Silent Intrusion
• C has the authorization for silent intru- sion. • A Silent Intrusion licence is in place. Supported only for system phones of the Aastra 5300, Aastra 5300ip, Aastra 600d series and the Aastra 2380ip system softphone System functions and features as of R3.0...
Page 443 Features If B is making an exchange all, Silent intrusion will only work if this feature is also en- abled for exchange calls, throughout the system. Notes: – In connection with the Silent intrusion feature, relevant national data protection regulations must be observed. –...
Page 444 Features Functions Tab. 235 Silent intrusion: Suffix dialling function Function System phones Analogue terminal Activate silent intrusion Use digit suffix dialling: 4 R4 (R = control key) Tab. 236 Silent intrusion: Function in prefix dialling Function System phones Analogue terminal Activate silent intrusion With function key in prefix dialling (config- –...
Page 445: Announcement To One Or More Users
Creating announcement groups: • It is possible to define up to 8 (Aastra 415/430) or 16 (Aastra 470) announcement groups. • Each group can consist of up to 16 users.
Page 446 – If the announcement is on an analogue phone, it calls with a special call pattern (200 ms ring – 200 ms pause – 200 ms ring – 200 ms pause etc.). Some analogue Aastra phones (e. g. Aastra 1930) or from other manufacturers, specially designed for retirement homes and hospitals are able to recognize this ringing pattern and switch automatically to hands-free mode.
Page 447: Intercom
Requirement: • The system phone supports the auto- matic announcement facility (Office 35, Office 45, Aastra 5370, Aastra 5380) • Automatic handsfree is activated on the system phone. System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 448 Function code System phones Set up announcement or duplex *7998 User No. • mode (calling party) • Office 35, Office 45, Aastra 5370, Aastra 5380: double-click team key Setting on the destination phone Automatic handsfree Announcement Note: The automatic hands-free talking setting on a system phone can be either disabled, enabled (all internal incoming calls incl.
Page 449: Charge Recall
Features 9. 6. 9 Charge recall By activating a charge recall, user B can transfer an exchange line to an internal user A. At the end of the exchange call, user B is called back with an indication of the call charges. Fig.
Page 450: Picking Up A Call
Features Detailed Description User B: Charge recall can only be activated from digital system phones with a dis- play. User A: At the end of the call, the user’s exchange access is automatically barred again. Under Charge recall in the AMS Account Manager a time can be configured for both standard and phone booth connections by which a charge recall is delayed when the handset goes on-hook.
Page 451 Call pick-up *86 <User No.> or *86 <UG No.> for any • user called in the UG at that particular • Office 35, Office 45, Aastra 5370, moment. Aastra 5380: click the Team key System configuration Tab. 248 Picking up a call: System configuration...
Page 452: Hotline
Features 9. 6. 11 Hotline User A can be allocated one of 20 different hotline destinations. Whenever the handset of a terminal assigned to user A is picked up, the configured hotline desti- nation number D will automatically be dialled once the set delay has expired. One hotline destination and a delay time can also be configured for each terminal.
Page 453 Features • Door phone (entrance gates) • Phone booth connection • Fax Additional applications: • Temporary hotline for hotel room and phone booth phones • Baby alarm on hotel room phone • Hotline to network in conference rooms • Hotline to reception in unoccupied hotel rooms •...
Page 454: Sending And Reading Text Messages
Message groups for text messages: • It is possible to define up to 8 (Aastra 415/430) or 16 (Aastra 470) groups. • Each group can consist of up to 16 users. • These message groups are also used for the Announcement feature (see "An-...
Page 455 Features In principle callback requests and notifications by the voice mail system are dis- played with a higher priority on the system phone, i.e. before any text messages. A maximum of 16 text messages are stored for any given destination user. Tip: A busy user who is also protected against intrusion and call waiting can still be reached using text messages.
Page 456: Message Function
Features 9. 6. 13 Message function A MESSAGE can be sent from any terminal to all system phones. Depending on the terminal the receipt of a MESSAGE is signalled by a callback request. Fig. 215 Activate MESSAGE Detailed Description Tab. 254 Activate MESSAGE Operating sequence / signalling on the ter- Interface Scope...
Page 457 Features Functions in prefix dialling Tab. 255 Activating MESSAGE: Functions Functions Function codes Activate MESSAGE *38 User No. Answer MESSAGE (trigger callback) *#38 Clear MESSAGE on the destination phone #38# Clear MESSAGE on the executing phone #38 User No. System configuration Tab.
Page 458: Leave Message
Features 9. 6. 14 Leave message If user B is absent or unobtainable for longer period of time, he can leave a mes- sage in the system for internal users. If user A now calls user B from a system phone with display, the system will send to A’s display the text left by B.
Page 459 Features Functions in prefix dialling Tab. 258 Leaving a message: Functions Functions Function codes Activate leave message *24 Text. No. [Param] # Clear leave message System configuration Tab. 259 Leaving a message: System configuration Parameter Parameter value Remarks Preconfigured CFU <User No.>...
Page 460: Standard Texts
If the Call Centre is connected, text message No. 8 must not be reconfigured. Aastra Intelligent Net: In an AIN with nodes in different language regions it makes sense to spec- ify a common language (e.g.
Page 461 Features System configuration Tab. 261 Standard texts: System configuration Parameter / action Parameter value Remarks Text message <Message text> for message 1...16 Texts can be edited Reset to initialization <Language> Individual standard texts cannot be standard texts reset. Reference to Other Features Features: •...
Page 462: Park
"Configurable keys", page 363). The Aastra 1560 / Office 1560 operator console also allows locally parked calls from other users to be retrieved. The parked call is signalled on all the assigned system phones of user B and can be retrieved from any of these phones.
Page 463: Central Call Parking
Features Functions Tab. 263 Local parking: Suffix dialling function Function System phones Park call locally Tab. 264 Local parking: Function in prefix dialling Function System phones Retrieve call System configuration Tab. 265 Local parking: System configuration Parameter Parameter value Remarks No settings Reference to Other Features Features:...
Page 464 Features Detailed Description Tab. 266 Central call parking Operating sequence / signalling on the ter- Interface Scope minal Once the function has been executed, the user Restriction: obtains the acknowledgement tone. Only 1 call can be parked centrally throughout the system at any given time. The parked user will obtain the signalling for Possible interfaces: Music on...
Page 465: Call Parking Function Of The Key Telephone
Features 9. 6. 16. 3 Call parking function of the key telephone A call signalled on a line key can be parked on the line key: • The call is parked automatically if another call arrives on another line key and is answered.
Page 466: Call Parking Function On The Operator Console
The active call is not to be transferred just yet and the attendant answers the incoming call. The original call is automatically parked on the corresponding line key (Office 45) or in the call queue (Aastra 1560 / Office 1560). Fig. 220...
Page 467: Callback If User Busy / Free
Features 9. 6. 17 Callback if user busy / free This feature is used to obtain an automatic callback if a user is busy or if a call to a user who is signalled as free goes unanswered. 9. 6. 17. 1 Callback if user busy User A has the possibility of activating a callback to busy user B (callback request).
Page 468: Callback To Free User
Features • B is external: 30 min • B is in the PISN: can vary in an heterogeneous PISN (system: 45 minutes) Callback to a busy external user B: If user B is a communication server user, he must have his own direct dial number and his communication server must also support the feature.
Page 469 Features Fig. 222 Callback to free user Detailed Description Tab. 274 Callback to free user Interface Operating sequence / signalling on the terminal Scope Once the function has been executed, A obtains Restriction: the acknowledgement tone. User A can only initiate one callback at a time.
Page 470: Wait Until Free
Features 9. 6. 17. 3 Wait until free The Wait-until-free feature is a Callback-if-busy feature without the user who initi- ates the call having to hang up. He stays on the phone and waits until the busy user becomes free. The callback is triggered as soon as the called user has been free for 5 seconds.
Page 471 Features System configuration Tab. 279 Wait until free: System configuration Parameter Parameter value Remarks No settings Reference to Other Features Features: • "Callback if user busy / free", page 467 • "Message function", page 456 System functions and features as of R3.0 syd-0367/1.3 –...
Page 472: Team Functions
Scope System phones that support the Team key: Office 35, Office 45, Aastra 5361, Aastra 5370, Aastra 5380, Aastra 1560 / Office 1560, Aastra 2380ip System configuration Tab.
Page 473: Locking And Unlocking Terminals
Features Reference to Other Features Features: • "Configurable keys", page 363 9. 6. 19 Locking and unlocking terminals Terminals are locked to prevent misuse or to force the allocation of call charges on a user-pays basis. Terminals on the system can be locked and unlocked in different ways: •...
Page 474: Locking / Unlocking Terminals (Telephone Lock)
Features 9. 6. 19. 1 Locking / unlocking terminals (telephone lock) The phone lock inhibits or restricts the following operating possibilities: • Dialling possibilities for internal and external calls, by activating internal and ex- ternal digit barring. • Operation of terminal settings. The dialling restriction can be lifted by entering a PIN: •...
Page 475: Unlocking The Terminal For Each Call
Features System configuration Tab. 282 Phone lock: System configuration in AMS Parameter Parameter value Remarks Change PIN Setting per user in the user authorization Internal digit barring set- Enable *33 and #33 Allow phone lock locking variant tings for the unlocked state Internal Digit Barring, phone Internal digit barring 1 to 8 Definition of internal dialling possibilities in...
Page 476 Features • Using the private phone book of the terminal’s user • Dialling by name Typical application: Unlocking non-personal terminals in publicly accessible premises (meeting rooms, entrance lobbies, coffee-break areas). Tip: Configure a key with the unlock function. Unlocking your own terminal An authorized user unlocks his own terminal.
Page 477: Making Calls With Your Own Settings On A Third-Party Phone
Features System configuration Tab. 285 Unlocking the terminal for each call: System configuration Parameter Parameter value Remarks User configuration of the terminal to be locked: • Phone lock Activates the lock • Internal Digit Barring, Internal digit barring 1 to 8 Definition of internal dialling possibilities in phone lock the locked state...
Page 478 Features Detailed Description After function code #36, the user dials his own internal user number and his per- sonal PIN. This activates his digit barring settings and the call charges are charged to his charge counter: The called party sees the caller's user number and not the number of the terminal being used by the caller.
Page 479: Private Calls With Pin
Features 9. 6. 21 Private calls with PIN This feature is used to charge private phone calls automatically to private charge counters, using the appropriate System Configuration. Users must always enter their valid PIN beforehand. They can do so both on one of their own terminals and on a third-party terminal on the same communication server or within a PISN.
Page 480: Appointment Reminder Call
Features System Configuration requirements: • For this feature to be used, the default PIN must be changed first (see "Locking / unlocking terminals (telephone lock)", page 474 for the syntax). • A private exchange access must not be defined or the private exchange access prefix must be barred for all users using internal digit barring.
Page 481 Parameter value Remarks No settings Aastra Intelligent Net: In an AIN with different time zones the execution of an appointment reminder call is always determined by the time zone of the user for whom the appointment reminder call was activated. This has to be taken into account in particular when activating an appointment reminder call for a different user using remote control.
Page 482: Acceptance Of A Call Or Data Connection
Features 9. 6. 23 Acceptance of a call or data connection: 9. 6. 23. 1 Preliminaries User D can enable user C to take over an existing call or data connection A-B. Fig. 225 Preparing to take over an active connection Detailed Description Tab.
Page 483: Accepting The Connection
Features Functions in prefix dialling Tab. 291 Preparing to take over an active connection: Functions Functions Function codes Preparations for taking over a call or a data connection from *87 B*C# (call) or with *84 B*C# (data con- user B to user C nection) Clearing the preparations for taking over a call or a data con- #87 C (call) or with #84C (data connection)
Page 484: Take (Taking A Call)
Features Function in prefix dialling Tab. 294 Taking over an active connection: Function Function Function code Take over call / data connection *88# Reference to Other Features Features: • "Take (taking a call)", page 484 • "Fast take (pick up a call or a call connection)", page 486 9.
Page 485 Features System configuration Tab. 296 Take: Key configuration Function type Note In AMS or on the cordless phone the following Requirement: command is used to prepare a configurable Prepare call acceptance authorization must be enabled key to allow user C to take over user B’s call: with user C.
Page 486: Fast Take (Pick Up A Call Or A Call Connection)
Features 9. 6. 25 Fast take (pick up a call or a call connection) The Fast take function combines and expands the two features Take a call and Pick up a call: Fast Take allows an internally authorised user C •...
Page 487 Features System configuration Tab. 299 Taking over an active connection: System configuration Parameter Parameter value Remarks Fast Take User configuration (user C) Fast Take Protection User configuration (user B Application example • DECT headsets logged on to the communication server as GAP cordless termi- nals usually have only one key (for seizing a call and hanging up).
Page 488: Room Monitoring (Baby Surveillance)
Room monitoring (Baby surveillance) This feature is designed specifically for monitoring infants. Acordless system phone (Office 135, Aastra 600d) is switched to a special monitoring mode and coupled with an internal or an external destination number. If noise levels in the area surrounding monitoring phone A exceed a specific value, a call is automatically triggered to the configured destination B.
Page 489: Functions
The microphone used for room monitoring is switched on with a 10 second time lag (Office 135). On cordless phones of the Aastra 600d series the delay is config- urable (10, 20 or 30 s). The time lag allows the user to position the cordless phone and then leave the room.
Page 490 Features Triggering the call If a noise exceeds the configured level for more than 2 seconds, a call is immedi- ately triggered to the destination user. • If the destination user is busy, the room monitoring microphone is re-activated after a 15 s delay. •...
Page 491: Passive Room Monitoring
Features ing call. Once the call has been cleared down, the monitoring phone switches back to monitoring mode without delay. If the destination user calls the monitoring phone, the phone temporarily switches to passive room monitoring (see next chapter). Tips: –...
Page 492: Conversation Recording
• Aastra 600d recording is possible. • When call recording is in progress, a symbol • Aastra 1560 / Office 1560 appears in the display of system phones (except on • Terminals of the series the Aastra 6700i).
Page 493 Features Call recording can be started and stopped in the following situations: • In a call connection • In a conference call • During an incoming/outgoing call • During dialling with call preparation • During dialling with the line seized (overlap dialling) The recording begins only once the call connection has been established.
Page 494 Once the wave files are sent by e-mail, they are erased from the communication server. Aastra Intelligent Net: In an AIN the voice channel for call recording must be made available at the following locations: –...
Page 495 Features Parameter Parameter value Remarks Send call recording to user's e-mail <Yes / No> If other e-mail addresses have been address entered for the call recording, this value can be configured to (CM_4.1). E-mail addresses call recording <E-mail address_1, e- E-mail addresses are entered separated mail address_2...>...
Page 496: Special Features
Features 9. 7 Special features Here describes features that are available only in combination with a special appli- cation or supplementary equipment, e.g. announcement service or door bell. 9. 7. 1 Coded ringing on general bell The installation of a general bell feature provides a paging system, albeit with a lim- ited scope.
Page 497 Features Functions Tab. 306 Coded ringing on the general bell: Functions in prefix dialling Functions Function codes Activate coded ringing *81 User No. Activate CFU to coded ringing Clear CFU to coded ringing Answer coded ringing Tab. 307 Coded ringing on the general bell: Suffix dialling function Function Function code System phones...
Page 498: Answer General Bell
Features 9. 7. 1. 1 Answer general bell A call can be signalled on the general bell (ringing signal) and be answered by any user B who hears it. Fig. 231 Answer ringing signal on general bell Detailed Description General bell is activated via user group (UG) or via proxy. If other calls are routed to the general bell, they are placed in a queue (max.
Page 499: General Bell On Analogue Terminal Interface Fxs
Once the connection is made, no calls can be made or received via the port. Aastra Intelligent Net: In an AIN a general bell can be configured per node. System configuration Tab.
Page 500: Announcement Service
Features 9. 7. 2 Announcement service The announcement service is for incoming external calls, but if required it can also be used for internal calls via a call distribution element. If a call from A is not an- swered within a preset delay time by internal user B (who is either free or for whom call waiting is enabled), the caller will hear a welcome announcement (provided the call has not been rerouted to the alternative destination (Capolinea) before-...
Page 501 Features Welcome announcements It is possible to define up to 20 (Aastra 415/430) or 50 (Aastra 470) welcome an- nouncements. A welcome announcement comprises one or more (up to 20) se- quences. In each sequence the parameters of the following table are to be config- ured in AMS under CM_5.4_Welcome...
Page 502 Features calls routed via a call distribution element are to be answered by the announce- ment service. Allocation in the call distribution elements The allocation of a call to a predefined welcome announcement of the announce- ment service is made in the call distribution elements under CM_3.1.4_CDE destina- tions, depending on a switch group’s switch position.
Page 503 External audio source (Aastra 470 mode). The recordings made in this way are stored as audio files in the file system of the communication server. It is also possible to record an- nouncements with a PC, store it as a wave file, and then upload it on to the commu- nication server.
Page 504 Features Tab. 315 Announcement service: Recording functions Functions Function codes Recording a welcome announcement with a phone *911 xx [*nn] # Recording a welcome announcement with audio *921 xx [*nn] # equipment Check recording *#911 xx [*nn] # or *#921 xx [*nn] # Delete recording #911 xx [*nn] # or #921 xx [*nn] # "xx": File number <10...29>...
Page 505 Features Recording with the PC: Announcements can also be recorded with a PC through a connected microphone (e. g. with the Windows Audio Recorder). The recordings have to be stored as wave files in a particular format under a predefined name. •...
Page 506 Master. – The number of welcome announcements and voice channels in an AIN is determined by the Master: If an Aastra 470 is used as the Master, each node also has 50 welcome announcements and 6 simultaneous voice channels at its disposal, regardless of the type of communication server used there.
Page 507: Queue With Announcement (Number In Queue)
Features 9. 7. 3 Queue with announcement (Number in Queue) A's call lands at a busy call destination B. The caller will first obtain the greeting of the announcement service, if so configured. He will then obtain a greeting an- nouncement, e.
Page 508 Features The greeting is assigned an auto attendant's profile. As an option the profile can al- ready comprise DTMF actions to offer the caller alternatives for handling the call. With monitoring actions the Auto attendant announcement action is configured at the parameter End of greeting.
Page 509 Features nouncement = Yes. Clicking the Done button automatically executes the follow- ing configurations: – A virtual user Q1 (user without assigned terminal) with the selected call number is created (CM_4.1). – A mailbox Q1 is created and assigned to the virtual user (CM_5.1.2). –...
Page 510 Features Description of the configuration parameters Tab. 318 Queue (CM_3.1.12): System configuration Parameter Parameter value Remarks Max. number of entries <1...200> Size of the queue Destination <Destination or combination of destinations> Auto attendant <Yes) / No> If the caller is in position 0 in the queue, the announcement during selected destination will ring.
Page 511: Clear Configurations
Features 9. 7. 4 Clear configurations With this function each user has the possibility of clearing all the personal func- tions he has activated with the exception of night service, logging in/out in user groups, status of CLIR permanent, and appointment orders. Detailed Description Tab.
Page 512: Lcr Function
Features 9. 7. 5 LCR Function If the LCR function is activated, dialled call numbers are analysed and converted. This means that the communication server may actually dial a different call number than the one entered by the user (see "LCR function", page 224).
Page 513 "ordinary" users. Aastra Intelligent Net: In an AIN the nodes can be located in different countries, which means it makes sense to enter in the numbering plan the emergency number nor- mally used in each country.
Page 514: Suppression Of The Call Number Display
Features Terminal-related response: The following applies provided no emergency number destination is con- figured on the corresponding terminal: – Desk phones and virtual terminals use the emergency destination assigned to the node. – Cordless phones use the emergency destination of the node at which the phone is currently located.
Page 515 Features • In combination with an abbreviated dialling that contains other */# function codes • In combination with dialling using a line key Functions Tab. 325 CLIR per user: Functions Functions Function codes Activate CLIR for one call *31 external destination Deactivate CLIR for one call #31 external destination Activate CLIR permanently...
Page 516: Recording Malicious Calls (Mcid)
Features 9. 7. 8 Recording malicious calls (MCID) By activating the Malicious Call Identification service, MCID for short, a user B can have the threatening or nuisance calls from an external user A recorded by the net- work provider so that the caller can be identified. The recording can be activated either during the call or after the call during the busy tone signalling (once the caller has rung off ).
Page 517 Features Tab. 327 Recording of malicious calls Operating sequence / signalling on the ter- Interface Scope minal Activate during the call / after the call during Internal user the busy tone signalling Connection restrictions: Network provider confirms activation (the type •...
Page 518: User Group: Logging In And Logging Out
Features 9. 7. 9 User group: Logging in and logging out Members of user groups can log themselves out and back in again. The logout and login procedure can apply simultaneously for all the user groups or specifically for one user group only. Detailed Description Tab.
Page 519: Home Alone
Features System configuration Tab. 333 User group: System configuration Parameter Parameter value Remarks User groups (UG) Members <user No.> for <UG No.> Call routing User group <Call numbers> for <UG No.> Numbering plan Reference to Other Features Features: • "Coded ringing on general bell", page 496 •...
Page 520 Features Functions in prefix dialling Tab. 335 User group: Functions Functions Function codes Activate Home Alone *49 UG No. Clear Home Alone #49 UG No. System configuration Tab. 336 Home alone System configuration Parameter Parameter value Remarks Home alone CM_3.1.2 Busy if busy CM_4.5 Application Example...
Page 521 Features Fig. 235 Home alone UG 1 (Private) contains users A, B, C and D. User D is also in UG 2, along with user E (carpentry workshop). Home Alone is activated in both UGs. 1. An incoming outside call to the business number is answered by Mrs. Smith at the office (user D).
Page 522: Switching Switch Groups
Features 9. 7. 11 Switching switch groups Switch groups defined in the system configuration can be selected by user A using switch contacts or a function code from the terminal. The switchover can also be carried out automatically using time-controlled functions in the System Configura- tion (see "Time-controlled functions", page 540)
Page 523 Features External switches: The switch groups can also be activated via control inputs, e.g. via a preconfigured time-switch clock. External switches have a higher priority, i.e. they must be open (status 0) so that switching via function key, function code or AMS can be carried out. Function in prefix dialling Tab.
Page 524: Switch Control Outputs
Various equipment or installations can be controlled using control outputs on FXS interfaces or the ODAB options card (Aastra 415/430). The telephone can be used to operate sun blinds, for example, or to switch the lighting on or off throughout the building.
Page 525: Door Function
Aastra Intelligent Net: In an AIN control outputs can be used as a mix of FXS interfaces and ODAB options cards (Aastra 415/430 only). An authorized user can switch all the control outputs, regardless of where they are located. The call numbers of all control outputs of an AIN are defined in the numbering plan.
Page 526: Door Bell
Features 9. 7. 13. 1 Door bell Depending on the system configuration, pressing the door bell triggers a call to any internal destination B. Detailed Description Tab. 343 Door bell Operating sequence / signalling on the ter- Interface Scope minal •...
Page 527: Open Door
Features Aastra Intelligent Net: In an AIN the configured destinations must not be on the same node as the connected door intercom. Reference to Other Features Features: • "Open door", page 527 • "Dial door intercom", page 528 9. 7. 13. 2 Open door This function actuates the door opener of any door.
Page 528: Dial Door Intercom
Tip: Store the function code on a function key (I*74 call number) Aastra Intelligent Net: In an AIN an authorized user can actuate all the door openers of the con- nected door intercom system, regardless of the node to which they are connected.
Page 529 Reference to Other Features Features: • "Door bell", page 526 • "Open door", page 527 Only with Aastra 415/430 and if the corresponding number of ODAB card(s) is fitted System functions and features as of R3.0 syd-0367/1.3 – R3.0 – 03.2013...
Page 530: System Time And System Date
Features 9. 7. 14 System time and system date The system time and system date are used as information in many areas, for in- stance for the display on system phones, for call logging, for event messages, etc. The system time and system date are also required for the appointment reminder call and the time-controlled triggering of */# function codes.
Page 531 Features Aastra Intelligent Net: In an AIN there are additional configuration parameters for time synchro- nization between the nodes. The Master is always in area 1. This area is always assigned the Master time. Time differences with other nodes can now be configured based on the Master time.
Page 532: Free Seating
Features 9. 7. 15 Free seating Free seating is intended for workstations that are used by several staff members. With free seating each member of staff is able to log in to a non-personalised phone with his call number and PIN and personalise that phone for a specific amount of time.
Page 533 Features Tab. 355 Free seating pool User configuration Parameter Parameter value Scope / remarks Automatic logout <No Logout after Daily No: The user has to log out of the free seating at> phone Log out after: The user is automatically logged off once the set time has expired.
Page 534: Remote Control Features
Features 9. 8 Remote control features A large number of features can be remote controlled either from within or outside the system: • Remote controlling features from within the system: User A activates / deactivates a feature on user B (Tab.
Page 535 *#94 user PIN # Listen to voice messages without audio guide *#916 user PIN # only Office 135/135pro, Office 160pro/Safeguard/ATEX and phones of the Aastra 600d series Tab. 357 User-independent features remote-controlled from within and from outside the system Feature...
Page 536: Remote Controlling Features From Within The System
Features 9. 8. 1 Remote controlling features from within the system A user A can use function code *06 to carry out features from his terminal on behalf of another authorized user B. Example: An internal user activates call forwarding on no reply: Fig.
Page 537: Remote Controlling Features From Outside The System
Features 9. 8. 2 Remote controlling features from outside the system An external user A can use a DDI number specially set up for remote control and a password valid throughout the system to remote-control a group of features via the public ISDN network (External Remote Control or ERC).
Page 538 Features Function in prefix dialling Tab. 361 External remote control: Function Function Dial string with function code Execute feature with function code <DDI No.> < Password> #*06 <user No.> <*/# function code> using external remote control Example: An external user activates call forwarding on no reply: Fig.
Page 539 Selects the internal digit barring for Default values: switch position 1 to 3 of switch • Digit barring settings: group 1 8/8/8 (Aastra 415/430) 16/16/16 (Aastra 470) • Digit barring 8/16: *85, *75, #75 barred Protection against User-specific (enable remote control of the user’s...
Page 540: Time-Controlled Functions
9. 8. 3 Time-controlled functions Up to 50 (Aastra 470 up to 500) time-controlled functions (*/# function codes) can be defined in the System Configuration to be executed once at a particular time on a particular date. It is also possible to define recurring functions to be executed at a particular time on a particular weekday or every weekday.
Page 541 Features Switch Group Assignment Each function can be assigned one of the switch groups 1 - 20. This allows you, for example during holiday periods, to activate or deactivate whole groups of func- tions. All functions with allocation of the corresponding switch group are active on switch postion 1 and inactive on switch positions 2 + 3.
Page 542: Hospitality/Hotel
• User-friendly solution configurable using the AMS Configuration Manager or WebAdmin. • Functions operated using the Aastra 5380/5380ip reception phone or the web- based Aastra Hospitality Manager application. • Connection to a Property Management System (PMS) via the communication server's Ethernet interface.
Page 543 – Supported only on Aastra 470. The MWI switch on the underside of the phone must be set to + or –. Additional information in the Aastra 470 System Manual in the Chapter entitled "Installing, powering and connecting terminals". if compatible Redial list only System functions and features as of R3.0...
Page 544: Configuration And Operating Concept
– No licence required. – See also Aastra 5380/5380ip User's Guide. • Medium-sized establishments (10 to 100 rooms): – Functions operated by the receptionist using the web-based Aastra Hospital- ity Manager application integrated in the communication server (no installa- tion required).
Page 545 WebAdmin as Hospitality Administrator. This function contains all views that are re- quired to set up Aastra Hospitality Manager and the Reception menu in Aastra 5380/5380ip and to define the default values. You can also use a menu item to launch the Aastra Hospitality Manager.
Page 546: Network Printer And Aastra 400 Print Spooler
You can download the Aastra 400 Print Spooler from the Aastra Software Down- load Server or source it from your distribution partner. As an alternative to the Aastra 400 Print Spooler, you can also connect a serial printer directly to the communication server via an IP adapter and a switch for small businesses without IT infrastructure.
Page 547 Features The function codes can be executed on the room phone or any other internal phone. Tab. 368 Maintenance notices: Functions Functions Function codes Enter maintenance notice *53 <Maintenance code> # Delete all maintenance notices for the room #53 # Enter maintenance notice on another internal phone *53 <Maintenance code>...
Page 548 Features Tab. 370 Charge direct: Functions Functions Function codes Charge amount to guest room *54 <Item No.> * <Amount> # Charge amount to the guest's room on another internal *54 <Item No.> * <Amount> * <Room No.> # phone Item number: Max. 5 digits, amount: indicate in cents Notification service Alongside system phones, most analogue phones have a message LED.
Page 549: System Configuration
Room cleaning • Room cleaning service <Yes / No> Yes: The display of the cleaning status in the Aastra Hospitality Manager is activated. The status can be set by authorised personnel. • Room cleaning status <Default / Enhanced>...
Page 550 Features Parameter Parameter value Remarks • If busy, the wake-up call <1...100> If the guest is busy on the phone at the time of the remains active for wake-up call, the wake-up call cannot be put through. However it does remain active for a cer- tain amount of time and is put through as soon as the line is free.
Page 551 <IP address> Enter here the IP network address of the PC where the Aastra 400 Print Spooler is installed. • Port <Port> Enter here the port configured on the Aastra 400 Print Spooler. • Print format <Text / HTML> Select here the print format for the network printer.
Page 552 • Floor <Number> Floor where the guest room is located. This entry defines the vertical arrangement of the guest rooms in the view display of Aastra Hospitality Manager. • Room Name <No. - [Name]> Name of the guest room •...
Page 553: Setting Up Phone Booths
It is also possible to pick up calls and to trans- fer calls (for instance pick up calls). This relieves the workload on the reception staff. The Office 45 can be used as an operator console; the Aastra 1560 / Office 1560 as a PC operator console.
Page 554 Features Phone booth operation, variant 1 A hotline destination is defined for user 45. When the receiver goes off-hook, "11" is dialled automatically and the operator console starts ringing. Fig. 242 Signalling on the operator console with variant 1 of phone booth operation Operating sequence on the operator console •...
Page 555 Features Phone booth operation, variant 2 Guest user 45 contacts Reception because he wants to make a phone call. Fig. 244 Signalling on the operator console with variant 2 of phone booth operation The guest in the phone box picks up the receiver within 2 minutes and obtains a dial tone.
Page 556: Message And Alarm Systems
Features • Suffix dial 29 or wait 2 seconds • Press the End key As a call is signalled, the user in the phone box picks up the receiver, obtains a dial tone and dials. When the call in the phone box is completed the charge recall signal rings on the operator console and the call charge information is displayed in the same way as in variant 1 or 2 (possibly with a delay depending on the configuration).
Page 557: Internal Messaging System For System Phones
MEs. Examples of ESMEs include the IMS (Integrated Message Server) and Mailgate (both Ascom Wireless Solutions products). Aastra 400 ensures the connections between the IMS and the 9d phones. 9d phones do not register with under the GAP standard but as system phones. The IMS communicates with the communication server via the LAN interface.
Page 558: External Messaging And Alarm Systems
Features 9. 10. 3 External messaging and alarm systems External messages in Short Message format (SM) are signalled to the PBX by an SM server (e.g. IMS: Integrated Message Server) via the Ethernet interface using the SMPP protocol logged in the communication server. The ATAS protocol is used for the external alarms of an alarm server.
Page 559 Features the communication server via LAN. The communication settings between the SMSC and the ESME can be configured in AMS: Tab. 376 ESME settings Parameter Remarks address, Port IP address and port of the ESME for outgoing messages Type The ESME type is specified here (SM application, SM gateway or SM Service Centre).
Page 560: Alarm Handling
Features 9. 10. 3. 2 Alarm handling External alarms from an alarm server are not handled by the SMSC but sent directly to the corresponding destination phone. No more alarms can be sent to the corre- sponding phone if the storage location is full. The alarm server is responsible for ensuring that alarms are delivered.
Page 561 Features Function Redkey On each system phone one or more function keys can be configured as Redkeys. Depending on the application an alarm can then be triggered, a heating system switched on, a process controlled, etc., with the aid of the ATAS protocol on an ATAS server.
Page 562: Alarm Trigger With Atas/Ataspro
This setting can be configured with AMS for each DECT cordless phone. Hotkey mode On the Office 160Safeguard/ATEX and Aastra 630d the Redkey function is available on the SOS key on the upper side of the phone. With the parameter 1 Hotkey only the Redkey function is triggered with the automatic alarm triggers (Man-down, no movement or escape alarm) as well as the SOS button and the hotkey.
Page 563 See also: The operation and configuration possibilities for alarming the Office 160Safeguard/ATEX and the Aastra 630d such as alarm delay, detection time and alarm signalling are described in detail in the relevant user’s guides. System functions and features as of R3.0...
Page 564: Functions With Aastra Alarm Server
Features 9. 10. 3. 5 Functions with Aastra Alarm Server If an Aastra Alarm Server is integrated into your communications system, the fol- lowing additional features will be available on your phone. Direct response Note: This function is used mainly by nursing staff in the health sector.
Page 565 A / A2 The patient phone automatically answers the Phones supported: call in hands-free mode. • All analogue phones by Aastra or other manufacturers that support the auto- matic hands-free mode (via special ring or FSK) (e. g. Aastra 6730a, Aastra 1930).
Page 566 B or a user group comprising several call num- bers of nursing staff. The Aastra Alarm Server detects the call from the patient to the hotline destination via CSTA interface and responds in accordance with its con- figuration.
Page 567: Interface Descriptions
• The patient can also be an external user. In this case his call is routed to the hot- line destination via a DDI number. • On the Aastra Alarm Server all the patients must be configured as endpoints and assigned to a room. The nursing staff must be configured as endpoints and as a hotline.
Page 568: Features Overview
Feature not supported on this terminal See also The SIP terminals of the Aastra 6700i product series and other SIP termi- nals of Aastra Telecom Schweiz AG and outside manufacturers are included in the features overview of the "SIP in Aastra 400 and Aastra IntelliGate"...
Page 569 Tab. 381 Features overview (in alphabetical order) Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones...
Page 570 [*nn] # xx = file number <10...29> yy = welcome announcement <01...20> for Aastra 415/430 or <01...50> for Aastra 470 nn = node No. (optional) A n n o u n c e m e n t s e r v i c e...
Page 571 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Answer general bell A n s w e r g e n e r a l b e l l •...
Page 572 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series ✓ ✓...
Page 573 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series • Protect against C a l l F o r w a r d i n g o n N o R e p l y ( C F N R ) •...
Page 574 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Call transfer C a l l t r a n s f e r ✓...
Page 575 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series • Activate in suffix dial- *** *81 oder –...
Page 576 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Discreet ringing D i s c r e e t r i n g i n g ✓...
Page 577 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series • With charge recall –...
Page 578 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series • Enter maintenance...
Page 579 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series • Answer with ***3 –...
Page 580 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Music on hold M u s i c o n h o l d •...
Page 581 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Phone lock P h o n e l o c k ✓...
Page 582 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Remote maintenance /...
Page 583 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Suppress the call...
Page 584 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series • Send standard text with *35 Gr.
Page 585 Aastra 1560 Office series Office 135 Integrated Aastra Analogue Other SIP Office 1560 25,35,45 Office 160 ISDN termi- Features mobile 6700i SIP Office 10 terminals terminals Aastra Aastra 5300 Aastra 600d nals phones series (DTMF) 2380ip series series Voice mail (Basic or...
Page 586 W a i t u n t i l f r e e Mobile phone integration level 2 is required for features introduced with ***. except Office 25 and Aastra 5360/5360ip for internal calls only call number assigned to this control output in the numbering plan...
Page 587: Limited Warranty (Australia Only)
(1) year period from the date of original purchase ("Warranty Period"). If there is a defect or malfunction, Aastra shall, at its option, and as the exclusive remedy under this limited warranty, either repair or replace the product at no charge, if returned within the warranty period.
Page 588 Aastra will not accept liability for any damages and/or long dis- tance charges, which result from unauthorized and/or unlawful use. To the extent permitted by law, Aastra shall not be liable for any incidental dam- ages, including, but not limited to, loss, damage or expense directly or indirectly arising from your use of or inability to use this product, either separately or in com- bination with other equipment.
Page 589 Limited Warranty (Australia only) 1.1 To the extent permitted by law and subject to clause 1.2 below, the liability of Aastra to you for any non- compliance with a statutory guarantee or loss or damage arising out of or in connection with the supply...
Page 590: Index
Call waiting ....... 438 Aastra Alarm Server ..... . . 564 Calls on a third-party phone .
Page 591 Do not disturb ......386 Incoming traffic ......182 Door function .
Page 592 Shared Numbering Plan ....71 Signalling from one user to another user . . . 282 OCL ........298 Silent intrusion .

This manual is also suitable for:

470 415 430

Aastra 400 Series System Manual

Product and Safety Information

System Interfaces

Numbering Plan

Identification Elements

Routing Elements

Call Routing

Data Service

Call Logging (CL)

Features

Quick Links

Related Manuals for Aastra 400 Series

Summary of Contents for Aastra 400 Series