Stimmen - 2, Durchschnittliche Bewertung: 3.5
(
)
)
|
Anleitung Zusammenfassung
An unconfigured phone (phone right out of the box) added to a network, attempts to auto-discover a configuration server on the network without any end-user intervention. When it receives DHCP option 66 (TFTP server), it automatically gets configured by the TFTP server. An already configured phone (either previously configured by auto-discovery or manually configured) added to a network, uses its predefined configuration to boot up. Notes: 1. Configuration parameters received via DHCP do not constitute configuration information, with the exception of a TFTP server. Therefore, you can plug a phone into a DHCP environment, still use the auto-discovery process, and still allow the use of the TFTP server parameter to set the configuration server. 2. DHCP option 66 (TFTP server details) overrides the mDNS phase of the auto-discovery. Therefore, the DHCP option takes priority and the remaining process of auto-discovery continues. 3. As the phone performs auto-discovery, all servers in the network (including the TFTP server), display in the phone window. However, only the server configured for TFTP automatically configures the phone. 41-001024-00, Rev 09, Release 1.4.1 IP Phone Release Notes 1.4.1 New Features in 1.4.1 IP Phone Features for Sylantro Servers Last Call Return (lcr) Support A new feature has been added to the IP phones that allow a user or administrator to configure a "last call return" function on a softkey or programmable key. This feature is for Sylantro servers only. You can configure the “lcr” softkey feature via the configuration files and the Aastra Web UI. How it works If you configure "lcr" on a softkey or programmable key, and a call comes into your phone, after you are finished with the call and hang up, you can press the key configured for “lcr” and the phone dials the last call you received. When you configure an “lcr” softkey, the label “LCR” displays next to that softkey on the IP phone. When the Sylantro server detects an “lcr” request, it translates this request and routes the call to the last caller. For the 480i/480i CT, applicable parameters to configure for “lcr” are: • softkeyN type (“Type” in Web UI) • softkeyN line (“Line” in Web UI) • softkeyN states (“Idle, Connected, Incoming, Outgoing” in Web UI) For the 9112i/9133i, applicable parameters to configure for “lcr” are: • prgkeyN type (“Type” in Web UI) • prgkeyN line (“Line” in Web UI) Note: For more information about “lcr” see the SIP IP Phone Administrator Guide, Release 1.4.1. 41-001024-00, Rev 09, Release 1.4.1 SIP IP Phone Models 480i, 480i CT, 9112i, 9133i Release Notes New Features in 1.4.1 Support for additional “Alert Info” keywords for distinctive ringing New configurable, distinctive ringing support has been added to release 1.4.1 for Sylantro servers. The following “info” parameters allow you to configure specific priority alert tones for each parameter that may appear as keywords in the “Alert-Info” header of a Sylantro server: • alert-acd (auto call distribution) • alert-community-1 • alert-community-2 • alert-community-3 • alert-community-4 You can configure these priority alert parameters via the configuration files or the Aastra Web UI. Configuring via the Configuration Files In addition to the priority alert parameters that already exist (from previous releases), you can also now configure the following parameters for priority alerting. Parameter – alert auto call distribution auto call distribution (in Web UI) Aastra Web UI Basic Settings->Preferences-> Priority Alerting Settings Configuration Files aastra.cfg,
Telefonanlagen - AASTRA 480I (555.77 kb)
Telefonanlagen - AASTRA 480I CT (555.77 kb)
Telefonanlagen - AASTRA 9112 I (555.77 kb)