SIP IP Phone Models 480i, 480i CT, 9112i, 9133i Release Notes
New Features in 1.4.1
Feature | Description | Page |
|
|
|
Last Number Redial | A user can now press the REDIAL key to dial the last number | page 15 |
| dialed. They can also press the REDIAL button once, scroll |
|
| the list of numbers, then press the REDIAL button again to |
|
| dial the number that displays on the screen. |
|
|
|
|
XML Objects and | The following are new XML objects on the IP phone: |
|
Enhancements | • XML: AastraIPPhoneStatus object - The IP phones now | page 16 |
| ||
| display a status message on a single designated line on |
|
| the phone’s idle screen when XML information is pushed |
|
| from the servers. |
|
| The 480i/480i CT phones display messages on the |
|
| second line (where “No Service” would display). The |
|
| 9112i/9133i phones display messages on the first line |
|
| (overriding the DisplayName). Long messages that are |
|
| wider then the phone screen get truncated. |
|
| • XML: AastraIPPhoneExecute Object - This object | page 23 |
| provides the ability to execute commands on the phone |
|
| using XML. Specific commands you can use with this |
|
| object are Reset and NoOp. |
|
| The following are XML enhancements on the IP phone: |
|
| • XML: Action URI - This feature provides administrators | page 25 |
| the ability to specify a URI for the phone to GET when |
|
| certain events occur. |
|
| • XML: Softkey URI - This feature allows the user to specify | page 30 |
| variables in the XML softkey URIs that are bound when |
|
| the key is pressed. |
|
| • XML: HTTP Refresh Header - All current XML screen | page 33 |
| objects now have the ability to be refreshed by adding a |
|
| Refresh and URL setting to the HTTP headers. |
|
Backup Proxy/Registrar | The IP phones now support the use of a backup SIP proxy/ | page 34 |
Support | registrar. You can configure this feature on a global or |
|
| basis via the configuration files or the Aastra Web UI. |
|
|
|
|
Release 1.4.1 introduces a process that allows the phones to | page 39 | |
mDNS |
| |
| be automatically configured by a TFTP server. |
|
|
|
|
5 |