Scope This document provides a best practice guide on setting up, operating, servicing, and troubleshooting OpenStage phone in an Asterisk environment. Open Communications Principles and Best Practices 19/03/2012, page 2...
Contents Scope Contents Preparation Supplying Power for the Phones Connecting OpenStage Phones to the IP Network 802.1x LLDP-MED Configuration Options DHCP Options Plug & Play – One Step Provisioning and Configuration Single Phone Configuration (Local Menu, WBM) Using OpenStage@Asterisk Busy Lamp Function (BLF) XML Applications Send URL / Remote Server Control Call Completion (CCBS/CCNR)
Preparation This chapter contains all information that is necessary to connect an OpenStage phone to an Asterisk based communication system. This includes the power supply options (PoE or external supply) for each OpenStage model and its possible sidecar combinations. To enable a secure environment, 802.1x support for OpenStage is specified.
Page 5
Energy saving mode To reduce the energy consumption to a minimum, OpenStage phones offer an energy saving mode. The display backlight (phone and Key Module, if attached) is switched off after a configurable timeout. With OpenStage 40, the main display and key module backlight will be switched off after 90 seconds of inactivity (firmware version V2R0 onwards).
By this means, full Plug & Play is possible (see the following section). For further information, including an example configuration for dhcp, please refer to the OpenStage Asterisk Admin Guide [3]. Plug & Play – One Step Provisioning and Configuration...
parameters must be set or updated. When all these parameters have been sent to the phone, it is ready for operation. For further information, please refer to the WPI Developer’s Guide [8]. If a Firewall or NAT get in the Way In case the phones and the provisioning service reside in different networks or subnets that are separated by a firewall and/or NAT, it may be impossible for the provisioning service to contact the phones.
Possible uses for OpenStage XML Applications might be • Integration with groupware (e.g. Microsoft Exchange Server) or Unified Messaging systems (e.g. Siemens Enterprise Communications OpenScape) • phonebooks with access to address databases •...
An implementation according to the IETF BLISS draft is planned, but currently not available. The OpenStage call completion implementation is purely stimulus based and can be found http://wiki.siemens-enterprise.com/images/6/65/White_Paper_CC_10090.pdf CTI for OpenStage - UACSTA There are several use cases where remote control of a VoIP phone is required. Among these are server based features like ‘Call Forwarding’...
OpenStage does not generate CSTA Events. With these services a SIP server can easily control basic OpenStage functions. For futher information please have a look at: http://wiki.siemens- enterprise.com/images/e/e7/white_paper_uaCSTA_Public_version_2010803.pdf Changing the Caller Information – PAI Header SIP is a great protocol for call processing. However, in some use cases, additional and up-to- date information about a caller might prove to be very useful.
Multi Address Appearance (MAA) A telephone is normally associated with a directory number, or, generally, with a SIP AoR. This number is used for placing calls to the associated telephone and for displaying the telephone's (user's) identity when placing calls to another party. The number is also used when more than one call appearance is supported due to additional features like call waiting.
Example: OpenStage operates in MAA mode. Further information can be found at: http://wiki.siemens-enterprise.com/images/a/a3/White_Paper_MAA.pdf Automatic Call Answering Using Alert-Info Header Besides using uaCSTA, the phone can be set to automatically answer a call by adding an alert info header to the call. Thus, the SIP server is enabled to control whether a call is to be answered immediately and without user interaction.
Logging and Tracing OpenStage phones are perfect. But if something should go wrong anyhow, the customer service needs tools to focus on the problem. Service effort is needed, but should be minimized. Therefore, OpenStage phones provide plenty of tools and options to find the cause of a problem quickly, even if it is not located at the phone.
Local and Remote Tracing The phone is able to write internal trace files, and to send the trace data to a remote syslog server. The tracing can be configured in a differentiated way by setting discrete trace levels for each service. Please note that it is not recommended to enable all traces to the deepest level.
Page 16
Example Screen: OpenStage 80 represented in the HUSIM Phone Tester Open Communications Principles and Best Practices 19/03/2012, page 16...