AASTRA BluStar 8000i BAS Administrator Guides

Aastra BluStarTM 8000i Desktop Media Phone

BAS-Mode Administrator Guide

Release 4.0

41-001391-00 Rev 03 – 04.2012

Content

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-i

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-i

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-i

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-i

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preface-ii

Safety Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preface-ii

Obtaining Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preface-ii

Chapter 1:
System Overview

BluStar System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

System Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

BluStar Application Server Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

BluStar 8000i Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Chapter 2:
BluStar Application Server and Software Installation

Software Installation and Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Operating System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

BluStar Application Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

Initial System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Rebuilding a Failed High Availability Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Chapter 3:

System Administration Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Console User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Remotely Accessing the Console Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Logging In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Commonly Used Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Administration Web User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Logging In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Web User Interface Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

ii 41-001391-00 Rev 03 – 04.2012

Content

Form Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

Form Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 4:

My BluStar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

My Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Contact Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Contacts Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

Contacts Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

My Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

My Call Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

PC Software Downloads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

Proxy Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

Chapter 5:
Users

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Viewing, Editing, Adding, and Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Creating a User Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Deleting a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Managing Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Editing User Group Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Global Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Global Contact Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Global Contacts Access Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Global Contacts Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Global Address Book Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

SIP Authentication Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Authentication Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Registered Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

User Call Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

41-001391-00 Rev 03 – 04.2012 iii

Content

Chapter 6:
BluStar Devices

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

BluStar Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

BluStar 8000i Terminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

BluStar Device Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

Creating a Device Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Renaming a Device Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Deleting a Device Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Viewing Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Editing Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Changing Member Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Editing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

BluStar Device Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

Telephony Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Telephony Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Telephony Device Line Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

User Line Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

Download Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Adding Software to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

View Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19

Chapter 7:
Services

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

SIP Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

Routing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

Presence Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

Install Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

View Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

Regular Expression Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6

Bandwidth Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9

iv 41-001391-00 Rev 03 – 04.2012

Content

User Session Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

USL Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

USL Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Off-Server Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19

Outbound BAS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19

Inbound BAS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

Chapter 8:
Platform

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

Color coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

Navigating Log Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

Advanced Log Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

BluStar Log Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

BluStar Server Main Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

BluStar Services Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

System Monitor and High Availability Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

SIP Messages Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

BluStar Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

General Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

Web Server Access Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

Web Server Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

Cron Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

Boot Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6

System Monitor Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

Monitored Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-8

Setting Email or SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

MIBs Required to Process SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

IP Version 4 Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

IP Version 6 Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

41-001391-00 Rev 03 – 04.2012 v

Content

System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Platform Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

SIP Calls per Second Averages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

High Availability Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Service Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

BluStar Audit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

BluStar Audit Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

Platform Audit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

Platform Audit Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

Change Database Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

Failover Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

Version Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21

Network Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21

Security Banners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Security Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

Certificate Signing Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

Install Signed Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24

Certificate Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24

Chapter 9:
Tools

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

DB Connection Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

Location Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

SIP Proxy Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

Bandwidth Manager Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

Clearing Stale Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

Bandwidth Manager Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

Presence Agent Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

Clustering Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

vi 41-001391-00 Rev 03 – 04.2012

Chapter 10:

Content

Database

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Access and Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Data Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Manual Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Periodic Automated Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Database Daemon (DBD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Database Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Database In Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Controlling the PostgreSQL Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Controlling the DBD Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Chapter 11:
Fail-Over

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Network Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Using a Serial Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Chapter 12:
Security Management

Root Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Database Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Default Administrator Password for All BluStar Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Administration Web Interface Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Password Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

SSH Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

SSL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

Install Webserver Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

41-001391-00 Rev 03 – 04.2012 vii

Content

User Authentication Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

SMB Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Login Banners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Required Periodic Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

SBC Solution Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

Chapter 13:
SIP Services

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Abstract (from RFC3261): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Excerpt from the introduction and overview: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

SIP Concepts and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

The SIP Request-Response Transaction Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

SIP Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6

Location Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7

Call Handling Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7

Troubleshooting Location Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7

Service Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8

Required Periodic Maintenance Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8

Appendix A:
Server Subsystems and Protocols

BluStar Application Server 2.0 Port Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

viii 41-001391-00 Rev 03 – 04.2012

Welcome

The Aastra BluStar™ 8000i Desktop Media Phone is designed to enhance the way you communicate and collaborate. Offer­ing true HD video conferencing, the BluStar 8000i uses the latest in video and communications technology to enable a
natural high-quality video experience. With its advanced business collaboration features and applications, the BluStar
8000i is a productivity enhancing desktop media phone that is intelligent, intuitive, and easy to use.

About this Guide

This guide explains how to use your new BluStar 8000i in BluStar Application Server (BAS) mode, and provides informa­tion on the administration functions of the BAS SIP Platform.

Note:

This guide will be updated periodically with new and/or updated information. For details on what features have been
added or updated, please refer to the Aastra BluStar

Audience

This guide is for network administrators, system administrators, developers and partners who need to understand how to
operate and maintain the BluStar 8000i using the BluStar Application Server. It also provides some user-specific informa­tion. This guide contains information that is at a technical level, more suitable for system or network administrators. A
basic knowledge of networking and Session Initiation Protocol (SIP) concepts is assumed.

™

8000i Desktop Media Phone BAS-Mode Release Notes.

Documentation

The BluStar 8000i documentation consists of the following:

• Aastra BluStar

eral features and functions, and an overview of the terminal. The English, French, and Simplified Chinese version is
included in the box with the BluStar 8000i terminal. The quick start guide is also available in other languages and can
be downloaded from http://www.aastra.com/document-library.htm.

• Aastra BluStar

for an end user. The user guide can be downloaded from http://www.aastra.com/document-library.htm.

• Aastra BluStar

options available to configure and deploy the product in SIP Call Server mode.

• Aastra BluStar

to configure and deploy the product in BAS mode.

• Aastra BluStar

issues resolved for the BluStar 8000i in SIP Call Server mode.

• Aastra BluStar

resolved for the BluStar 8000i in BAS mode.

™

8000i Desktop Media Phone Quick Start Guide - Contains installation and set-up instructions, gen-

™

8000i Desktop Media Phone User Guide - Describes the most commonly used features and functions

™

8000i Desktop Media Phone SIP Call Server Administrator Guide - Provides all of the configuration

™

8000i Desktop Media Phone BAS-Mode Administrator Guide - Provides all of the information on how

™

8000i Desktop Media Phone SIP Call Server Release Notes - Provides new features and documents

™

8000i Desktop Media Phone BAS-Mode Release Notes - Provides new features and documents issues

41-001391-00 Rev 03 – 04.2012 Preface-i

Welcome

Typographical Conventions

• Commands or text that should be entered verbatim are shown in a monospace font, for example:

netstat -rn

• Parts of commands or entered values that should be replaced with varying details are shown in italics, for example:

less filename

• Icons or links that should be “clicked on”, are shown as underlined text, for example Home.

• The phrase “go to Tools / Options” suggests clicking first on the icon or link labelled “Tools”, then clicking on the icon

or link labelled “Options”.

• Buttons to click on or otherwise select, or keys to press, are shown between square brackets, for example “click on

Cancel” or “press Esc”.

Safety Summary

Please read the following safety -information before attempting to install or use the BluStar 8000i .

Alert!

For use with included AC/DC adaptor model no. 3A-603DB12 / Pour utiliser avec modéle 3A-603DB12.

Alert!

This product is designed for indoor use only and for ambient temperatures at or below 40° C (104° F).

Warnin g!

This equipment complies with Part 68 of the FCC rules and the requirements adopted by the ACTA. On the bottom of this equip­ment is a label that contains, among other information, a product identifier in the format US:AAAEQ##TXXXX.

If requested, this number must be provided to the telephone company.

Warnin g!

Hazardous voltage enclosed. Voltage or current hazard sufficient to cause shock. Disconnect power before servicing.

Danger!

There are no operator serviceable parts inside the chassis. Attempting to tamper with the parts inside the chassis may result in
serious injury to the user or damage to the equipment.

Danger!

This product is designed to work with a single-phase power system having a grounded neutral conductor. To reduce risk of elec­trical shock, do not plug into any other type of power system.

Danger!

The power cord for the terminal functions as the power disconnect device. Ensure that the power cord is readily accessible in case
of emergency and for servicing. Disconnect power before servicing.

Danger!

Use only the power cord provided. The terminal must use the grounded three-conductor power cord. Do not use two-conductor
extension cords.

Obtaining Assistance

If you have read this administrator guide and still have problems, please contact Aastra Telecom Support via one of these
methods:

North America

• Toll Free 1-800-574-1611

• Direct [phone]

• Online at http://www.aastratelecom.com/support, click on Contact Technical Support

Outside North America

Please contact your regional Aastra Technical Support.

Preface-ii 41-001391-00 Rev 03 – 04.2012

Chapter 1 System Overview

This guide is aimed at the administrator of a BluStar system and BluStar Application Server (BAS). This guide covers the
usage and administration of the BluStar 8000i in BAS mode that includes the servers, services, and systems supporting
these terminals, and that enable the terminals to communicate with each other.

BluStar System Components

The following image illustrates the typical interconnection options for the systems discussed in this document.

BluStar

BluStar

BluStar

Network

SIP Phone

BluStar Application Server

(Failover Pair)

SIP Registrar/Location Service

SIP Presence Service

SIP Proxy Service

(In/Out)

Directory & Settings

DB/Service

End User

Web UI

Fail Over Call Log

Admin CLI &

Admin Web UI

41-001391-00 Rev 03 – 04.2012 1-1

BluStar System Components

The remainder of this document focuses on the management of the following components:

BluStar Components

Note:

Please refer to the documentation included with each of the devices listed below for additional information regarding
their installation, configuration, and/or use.

• BluStar Application Server (BAS) and BluStar Application Server software (SIP Services, Web User Interface, and Data-

base).

• BluStar 8000i Terminal

Other Components

• SIP Phone(s)

Note:

Please refer to the documentation included with each of the devices listed above for information regarding their instal­lation, configuration, and/or use.

1-2 41-001391-00 Rev 03 – 04.2012

System Applications

System Applications

The BluStar system provides BluStar 8000i terminal users with the ability to:

• Make video and audio calls to another BluStar 8000i terminal or user, or receive calls from them, within the same local

network or intranet.

• Make video and audio calls to a BluStar 8000i terminal or user located in other domains (e.g. other organizations, or

independently administered branches of the same organization), or receive calls from them.

• Make intra-domain or inter-domain audio-only (voice-only) calls to non-BluStar 8000i SIP phones, or receive calls from

them.

BluStar Application Server Functions

The BluStar Application Server and its associated BluStar Application Server software host Session Initiation Protocol Serv­ices (SIP Services) as well as an SQL Database for storage of configuration settings, user accounts, and each user’s contacts
(address book). The BluStar Application Server is managed (administered) using a web interface as well as a console inter­face.

SIP Services provide signalling functions that facilitate creating and terminating calls between different terminals. They
provide mechanisms and communication channels that enable locating users, negotiating audio and video properties,
and setting up data streams to carry audio and video content. These mechanisms are used within one domain or between
servers in different domains..

BluStar 8000i Functions

The BluStar 8000i terminals have the ability to replace a conventional telephone by combining the features of a modern
telephone terminal with real-time, face-to-face video displayed on a high-resolution, flat-panel color touch screen.

41-001391-00 Rev 03 – 04.2012 1-3

Chapter 2 BluStar Application Server and Software Installation

The BluStar Application Server (BAS) is usually configured as a fail-over pair. The servers can be mounted in a 19 inch
rack. The platform hardware is 1U high. Please refer to the documentation supplied with your unit for detailed informa­tion on specific hardware features; and for the following instructions:

• Unpacking and physical installation.

• Planning the installation, e.g., ventilation, power, network.

Software Installation and Network Configuration

The BluStar Application Server is normally supplied with a pre-installed operating system, ready for initial configuration
and installation of the BluStar Application Server software.

An installation CD allows installing and re-installing the operating system. This may be required when an operating sys­tem has not been pre-installed, to revert to a specific version of the BluStar Application software, and in some cases
when upgrading BluStar Application Server software.

Operating System Installation

Notes:

• The procedure documented in this section need only be followed if the BluStar Application Server operating system

was not pre-installed. If the operating system was pre-installed, proceed with the instructions in BluStar Application

Server Configuration on page 2-2. Contact your support representative to ascertain whether your operating system

was pre-installed.

• Before proceeding, any data located on the BluStar Application Server that needs to be retained, whether in the
server database or in disk files, should be backed up and transferred to a different server.

Refer to Manual Backup and Restore on page 10-2, to perform a database backup.

Note:

The following procedure erases all data on the server hard disk(s). The install command formats the hard disk drive
disk(s) without any further prompting.

To install the Operating System:

Use the following procedure, or follow updated instructions (e.g., Release Notes) that accompany the installation CD.

Note:

If the hardware platform type is incorrect, the Application Server software will not install.

1. Ensure that a PS/2 keyboard and a VGA monitor have been connected to the server.

2. The server will have been pre-configured to boot from the CD drive. If you have adjusted this parameter in the server

BIOS, re-enable booting from CD.

2-1 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

3. Insert the installation CD and reboot the server by switching the server power off, waiting five seconds, and switching

the server power on again.

4. At the boot: prompt, enter:

install

5. During the installation process, the disk is formatted and partitioned, and the Linux operating systems and packages

are installed.

Note:

Installing additional software on the server may pose security risks. It is recommended that no additional software pack­ages be installed for security reasons.

6. At the conclusion of the installation process, an empty screen with a blue background may appear for a few minutes.

This is normal operation– please be patient.

7. The CD drive opens and the installation software next prompts the user to remove the installation CD from the drive.

Pressing Enter at the “- Complete -” … “Press Enter to reboot” dialog will close the CD drive and reboot the server.

Note:

Ensure that the installation CD has been removed from the drive before the server reboots in order to avoid repeating
the installation process.

8. When the server boots, the OS Loader software prompts the user to choose a Linux Kernel version to boot from. There

should be more than one choice here. The default selected option should be “BluStar Application Server”. Choose this
option for all normal use. Alternative options may include older versions of the “BluStar Application Server” kernel and
lastly “Disaster Recovery Linux” which may be used in emergency cases possible to recover data and/or use unsuppor ted
hardware.

9. Once the boot process has completed, the user is prompted to login. Log in as the user ‘root’ using the default password

‘blustar’.

BluStar Application Server Configuration

To configure the BluStar Application Server:

Use the following procedure, or follow the updated instructions (e.g., Release Notes) that accompany the installation CD.

Note:

The BluStar Application Server configuration procedure should be completed in the order given in the following pro­cedure. Do not skip steps!

41-001391-00 Rev 03 – 04.2012 2-2

Software Installation and Network Configuration

To run the BluStar Application Server Configuration tool:

1. Enter the following command at a command prompt:

./vconfig

2. A welcoming screen displays giving brief instructions for using the configuration tool. After reading the instructions,

press Enter to begin. The BluStar Application Server Configuration screen displays as shown:

The following operations may be initiated from this screen:

Network Configuration

Allows you to specify the network parameters for the network interfaces.

Network Connectivity Test

Tests for connectivity to the devices specified during Network Configuration.

Time Server

Allows you to set the BluStar

SSL Certificate Generation

Generates SSL certificates.

Software Installation

Installs the BluStar

Current Software

Allows you to view a list of currently installed software packages.

Upgrade Software

Allows you to upgrade the software from a CD. This option displays only after initial installation of the software.

SSH Key Distribution

Exchanges SSH keys between the BluStar

Reboot

Allows you to reboot the BluStar

Exit

Exits the BluStar Application Server Configuration program and returns you to a command prompt.

3. Continue with Network Configuration on page 2-3.

™

8000i Desktop Media Phone software.

™

8000i Desktop Media Phone’s timezone, time, and date parameters.

™

8000i Desktop Media Phones in a High Availability pair.

™

8000i Desktop Media Phone.

Network Configuration

Definition of basic networking parameters, e.g., IP address, hostname, DNS server(s), default gateway, and domain
names, is required before proceeding with any other server configuration operations.

2-3 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

Notes:

• Network Configuration must be completed before attempting to perform any other operation listed on the Server

Configuration menu.

• Do not attempt to configure the networking parameters by directly editing any system files. You must use the Net­work Configuration operation provided via the menu to configure the networking parameters for this platform.

• After configuring the BluStar Application Server Software, do not alter the BAS IP address or hostname using./vcon­fig. These settings should be changed using the BluStar Application Server Web UI. Please refer to System Settings on

page 8-14 for details.

On the BluStar Application Server Configuration menu, use the up and down arrow keys as necessary to select Network
Configuration, then press Enter. The Select Configuration Option menu displays.

Three different types of network configuration are supported by the BluStar 8000i :

• Single Node (Standalone)

Choose this option if you want to configure the BluStar 8000i as a stand-alone Application Server. Proceed to the Sin-

gle Node (Standalone) configuration procedure on page 2-5.

• Master Node (High-Availability)

Choose this option if you wish to configure the BluStar 8000i as the Master Node for a High-Availability pair. Continue
with the Master Node (High Availability) configuration procedure on page 2-6.

• Slave Node (High Availability)

Choose this option if you wish to configure the BluStar 8000i as the Slave Node of a High-Availability pair. Continue
with the Slave Node (High Availability) configuration procedure on page 2-7.

Note:

A Master Node must already have been configured prior to choosing the Slave Node option.

41-001391-00 Rev 03 – 04.2012 2-4

Software Installation and Network Configuration

Single Node (Standalone)

1. Select Single Node (Standalone) and press Enter to continue.

The BluStar Application Server Network Configuration menu displays:

2. Using the up and down arrow keys to select items on the menu, and the Enter key to edit the desired setting, enter

the following information:

Primary Interface Type

Specify the interface type. E100 is only option available.

Primary IP Address

Enter the server primary IP address.

Primary Netmask

Enter the server primary netmask.

Secondary Interface Type

Enter the server secondary interface type (if applicable).

Secondary IP Address

Enter the server secondary IP address (if applicable).

Secondary Netmask

Enter the server secondary netmask (if applicable).

Hostname

Enter a name for the server in fully qualified form (e.g., servername.mycompany.com) (Leave blank or None if not
applicable).

Primary Name Server

Enter the IP address of the Primary Name Server (if applicable).

Secondary Name Server

Enter the IP address of the Secondary Name Server (if applicable).

Default Gateway

Enter the IP Address of the default gateway (if applicable).

Time Server

The server contains a built-in NTP server. BluStar 8000i terminals synchronize time with the server. This option allows
you to configure the server to synchronize its time with an external time server by specifying either the IP Address
or fully qualified hostname of an external network time server.

3. When finished entering your server’s network configuration information, select Apply Configuration and press Enter

to restart the network services and enable the network device. When the BluStar Application Server V (ver) network
configuration successful! message displays, press Enter to return to the BluStar Application Server Configuration
menu.

Note:

After applying the configuration, do not change the network configuration by directly editing configuration files.

4. Continue with Network Configuration on page 2-3

.

2-5 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

Master Node (High Availability)

Note:

If you choose this option, you must subsequently configure a second BluStar 8000i as the Slave Node for this Master
Node.

If you wish to configure the BluStar 8000i as the Master Node for a High-Availability configuration, the settings are speci­fied on a menu similar to the one used for Single Node network configuration.

1. Select Master Node (High Availability) and press Enter to continue.

The first ten menu items are identical to those found on the Single Node configuration menu - and are configured in
the same way. Also, there are several additional settings that are required. These are the items beginning with “HA” as
shown in the following screen:

2. Using the up and down arrow keys to select items on the menu, and the Enter key to edit the following settings:

Primary Interface Type

Specify the interface type. E100 is only option available.

Primary IP Address

Enter the server primary IP address.

Primary Netmask

Enter the server primary netmask.

Secondary Interface Type

Enter the server secondary interface type (if applicable).

Secondary IP Address

Enter the server secondary IP address (if applicable).

Secondary Netmask

Enter the server secondary netmask (if applicable).

Hostname

Enter a name for the server in fully qualified form (e.g., servername.mycompany.com) (Leave blank or None if not
applicable).

Primary Name Server

Enter the IP address of the Primary Name Server (if applicable).

Secondary Name Server

Enter the IP address of the Secondary Name Server (if applicable).

Default Gateway

Enter the IP Address of the default gateway.

Notes:

• A default gateway address must always be provided. It is required to enable SIP services to synchronize their state via
multicast.

• When the server is placed on an isolated subnet, an unused IP address should be selected to act as a “dummy” gate­way.

41-001391-00 Rev 03 – 04.2012 2-6

Software Installation and Network Configuration

HA Shared IP

Enter the shared IP address for the HA server.

HA Shared Hostname

Enter a shared hostname in fully qualified form (e.g., servername.mycompany.com) (Leave blank or None if not
applicable).

HA Multicast Group IP

Enter the HA Multicast Group IP address. This address should be unique for the HA pair on this subnet.

3. When finished entering your server’s network configuration information, select Apply Configuration and press Enter

to restart the network services and enable the network device. When the BluStar Application Server V(ver) network
configuration successful! message displays, press Enter to return to the BluStar Application Server Configuration menu.

Note:

After applying the configuration, do not change the network configuration by directly editing configuration files.

4. Continue with Network Connectivity Test on page 2-8.

Slave Node (High Availability)

Note:

Slave Node configuration should be done only after configuring the Master Node of the HA pair. Slave Node configu­ration will fail if attempted before its Master Node has been configured.

When setting up the slave server for the first time, several questions are asked about the slave server and corresponding
master server’s configuration. The information entered enables the slave and master servers to communicate and
exchange configuration information.

To begin setup of the slave server

1. On the Select Configuration Options menu, select Slave Node (High Availability) and press Enter to continue.

The Slave Server quick setup screen displays, reminding you that the Master Node configuration must be completed
before proceeding.

2. Press Enter to continue. The following screen displays:

:

2-7 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

3. Using the up and down arrow keys to select items on the menu, and the Enter key to edit the following settings:

Local Primary Interface Type

Specify the interface type. E100 is only option available.

Local Primary IP Address

Enter the slave server primary IP address.

Local Primary Netmask

Enter the slave server primary netmask.

Local Hostname

Enter a name for the slave server in fully qualified form (e.g., servername.mycompany.com) (Leave blank or None
if not applicable).

Remote Primary IP Address

Enter the IP address of the Master Server.

4. When finished entering the information, select Continue from the menu and press Enter.

5. A dialog box displays asking you if you wish to continue with the values entered. Select Yes and press Enter.

6. On the resulting screen, enter the Slave server’s root password and press Enter.

7. On the resulting screen, enter the Master server’s root password and press Enter.

8. A series of messages appears indicating progress as the slave server is synchronized with the master server. Once the

configurations are synchronized, a configuration menu similar to the Master Node configuration menu displays. The
settings shown should be the same as those configured on the master server. No additional changes should be neces­sary.

Note:

After applying the configuration, do not change the network configuration by directly editing configuration files.

9. Continue with Network Connectivity Test on page 2-8.

Network Connectivity Test

The administrator should test the connectivity of the network as set up in the network configuration. The test performs a
“ping” to the default gateway and primary and secondary name servers (if configured). Review the output results for any
problems.

1. To test network connectivity, select the Network Connectivity Test, and press Enter.

This test pings the Default Gateway, the Primary Nameserver, and the Secondary Nameserver.

2. After the test has completed, press Enter when prompted to return to the BluStar Application Server Configuration

menu.

3. Continue with Time Setup on page 2-9.

41-001391-00 Rev 03 – 04.2012 2-8

Software Installation and Network Configuration

Time Setup

1. On the BluStar Application Server Configuration menu, use the up and down arrow keys to select Time Setup, then

press Enter. The following screen displays:

2. Press the spacebar to toggle the hardware clock setting.
Note:

Setting the hardware clock to GMT is recommended.

3. Press the Tab key to move to the list of time zones; then use the up and down arrow keys to select the desired time zone.

4. Press the Tab key to move to the Ok button; and press Enter or the spacebar to accept the time zone settings.

The following screen displays:

2-9 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

5. Read the information on this screen, then press Enter to continue. The following screen appears:

6. Use the Tab key to move the cursor to the field that you wish to change; then use the h, j, k, and l keys to change values.

When finished, tab to OK, then press Enter. The following screen displays:

7. Use the Tab key to move the cursor to the field that you wish to change; then use the up and down arrow keys to change

values. When finished, tab to OK, then press Enter. The display indicates that the date has been set. Press Enter to
return to the main configuration menu.

8. Continue with SSL Certificate Generation on page 2-11.
Note:

The Date and Time configuration is only applied to the server where the operation is performed. It must be repeated
on the High Availability peer in a fail-over configuration.

41-001391-00 Rev 03 – 04.2012 2-10

Software Installation and Network Configuration

SSL Certificate Generation

Apache and BluStar Manager set up their own self signed certificates by default. BluStar 8000i terminals, however,
require Certification Authority signed certificates. These can be generated as follows.

To generate SSL certificates for your installation, do the following:

1. On the BluStar Application Server Configuration menu, use the up and down arrow keys to select SSL Certificate Gen-

eration, then press Enter. The following screen displays:

2. Select and edit the certificate values as appropriate for your site.
Note:

For the Common Name field, the Application Server IP address (for a single-node configuration), or the shared IP
address (for an HA pair) will have automatically been entered based on the IP address supplied when configuring the
networking parameters. This field can not be edited.

3. When finished editing certificate values, select Generate Certificates, and press Enter. The script generates the certifi-

cate. This may take several seconds. When finished, the following is displayed:

2-11 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

4. Press Enter to continue. The following screen displays indicating that the Apache and Database Daemon have been

restarted:

5. Press Enter to return to the BluStar Application Server Configuration menu.

Note:

If you abort the SSL certificate setup before creating new certificates, the screen below displays. In this case, the pre­viously installed certificates (if any), or the default certificates provided with the system’s web server software will be
used for SSL.

6. Continue with Installing the BluStar Application Server Software on page 2-13.

41-001391-00 Rev 03 – 04.2012 2-12

Software Installation and Network Configuration

Installing the BluStar Application Server Software

Once initial configuration is completed (refer to Initial System Configuration on page 2-16), the Application Server is
ready for installation of the BluStar Application Server software.

1. On the BluStar Application Server Configuration menu, use the up and down arrow keys to select S oftware Installation,

then press Enter.

2. You are asked to confirm that you want to continue with the software installation. Select Ye s , then press Enter to

continue.

3. The End-User Software License text displays similar to the following:

4. Please read the text, using the spacebar, arrow keys, etc., as needed to view the information. When finished, press Enter.

2-13 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

5. A dialog box displays asking you if you accept the terms and conditions of the license agreement. Type yes and press

Enter if you agree. (If you answer no, the installation process aborts).

6. The Third Party Software Copyright and Licensing Information screen displays similar to the following:

Please read the text, using the spacebar, arrow keys, etc., as needed to view the information. When finished, press Enter.
The following screen displays:

7. Enter a new root password and press Enter. A second screen displays asking you to re-enter the new password. Do so,

then press Enter.

41-001391-00 Rev 03 – 04.2012 2-14

Software Installation and Network Configuration

8. The screen displays output indicating progress of the software installation. Near the end of the process which may take

several minutes, the system prompts you as follows:

BluStar Application Server software installation Complete!
This server must be REBOOTED to start functioning. Do you want to reboot now? ([y]/n)?

9. Press Enter to accept the default y response, and reboot the server.

Note:

Contact the Technical Assistance Center (TAC) if you need assistance, e.g., if errors are encountered.

10. Proceed to System Monitor Settings on page 2-15.

Notes:

• After installing the BluStar Application Server Software, do not alter the Application Server IP address or hostname
using ./vconfig. These settings should be changed using the BluStar Application Server Web UI.

• Please refer to Fai l-O ver on page 11-1

Installed software

This option can be used to determine the version number of the installed software. A list of the installed rpm’s is also
given.

Upgrade from CD

This option for upgrading of the server software only becomes available after initial installation of the software.

The release notes that accompany each software release describe the procedure to be used to upgrade to that release.

for more details on fail-over installations.

Note:

Upgrading software may in some cases destroy some configuration data. Contact the Technical Assistance Center
before attempting to upgrade a system that may contain critical configuration data such as user contacts or other con­figuration information.

Reboot

The server should be rebooted after completion of the single node or high availability installation process. If this was not
done previously, the administrator has the option to reboot the server now. If [n] is chosen, the server will have to be
rebooted later.

System Monitor Settings

Use the following procedure to enable monitoring of various BluStar Application Server system services; and to enable
email notification with disk space monitoring.

1. Using a web browser, go to http://server_ip_address and log in to the BluStar Application Server Web UI.

(The default root user password for the web-platform-admin role is blustar.)

2. Visit the Platform :: System Monitor Settings page, and click the Edit button.

3. On the resulting screen, shown in the image below, it is recommended that users enable Monitor Services for all

services; and that they Enable Notifications via email and also enable Disk Space Alerts. You must supply the SMTP
server hostname or IP address, and at least one email address to which the notifications will be sent. The recommended
disk space monitor setting is to send an alert when the devices become 70% full. You may also specify the number of
log lines to be included in the email. You may also set a threshold value for the CPU temperature that triggers a warning
email if the value is exceeded.

4. Click the Save button to save the settings.

5. Logout of the BluStar Application Server Web UI.
Note:

Disabling Monitored Services will cause the server to become unavailable. Service monitoring and disk space alerting
should only be disabled in exceptional circumstances, i.e., if there are specific reasons preventing their implementa­tion.

2-15 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

Most system management tasks can be performed remotely, i.e., across the network, using a web browser. Administration

Web User Interface on page 3-3, describes how to use the web user interface, referred to as the Web UI in this guide.

Initial System Configuration

When all the required software has been installed on the BluStar Application Server, the initial configuration of the system
needs to be specified. The exact procedure will differ according to the network and system topology selected for each spe­cific site.

41-001391-00 Rev 03 – 04.2012 2-16

Software Installation and Network Configuration

Rebuilding a Failed High Availability Server

If either the master or slave server fails, rebuilding the server may be necessary. This process synchronizes the failed
server with the properly functioning one. The two scenarios are outlined below.

Note:

A PS/2 keyboard and VGA monitor (both user-supplied) must be connected to the server to complete either of the fol­lowing procedures. For details on these connections, refer to the ViPr

Master server fails and slave server takes over

To get the master server back online:

1. Insert the Application Server CD into the disk drive of the failed master server.

2. Switch the master server off.

3. Disconnect the master server from the network.

4. Switch the master server on, and confirm that it is booting from the CD. If it is not, make sure that the Application Server

CD is properly inserted.

5. At the command prompt, type install.
Note:

All data will be erased from the master server, and restored when synchronized with the slave server.

6. Wait for installation to complete and reboot the server.

™

Application Server Quickstart Guide.

7. Reconnect the server to the same network that the slave is on.
Note:

The server will now be running and connected to the network, but SIP Software must be installed.

8. At the login prompt, login as root with password blustar.

9. To begin software installation, type ./vconfig.

10. Select Rebuild Server (High-Availability) from the Network Configuration menu.

11. Select Master Server and continue the installation.
Note:

The master server’s password should still be blustar.

12. The certificates are now synchronized. At the prompt, press enter.

Replicating files will be displayed above the prompt.

13. A network configuration dialog will appear on the screen. Scroll down and select Apply Configuration.

14. The ser ver software now installs. After pressing Enter at the prompt, the database will be resynchronized with the slaves.
Note:

The database synchronization may take some time. A progress bar will give an indication on the screen.

15. Select Ye s at the prompt to reboot.

16. Once the reboot completes, login to the server and verify that the master server is active in one of the following ways:
a) Enter vipr_ha_is_active at a command prompt. This command returns yes if the master server is the active device.

b) Using a web browser, visit the Platform :: System Status page via the server Web UI.

2-17 41-001391-00 Rev 03 – 04.2012

Software Installation and Network Configuration

Slave server fails and master server takes over

To get the slave server back online:

1. Insert the Application Server CD into the disk drive of the failed slave server.

2. Switch the slave server off.

3. Disconnect the slave server from the network.

4. Switch the slave server on, and confirm that it is booting from the CD. If it is not, make sure that the Application Server

CD is properly inserted.

5. At the command prompt, type install.

Note:

All data will be erased from the slave server, and restored when synchronized with the master server.

6. Wait for installation to complete and reboot the server.

7. Reconnect the server to the same network that the master is on.

Note:

The server will now be running and connected to the network, but SIP Software must be installed.

8. At the login prompt, login as root with password blustar.

9. To begin software installation, type ./vconfig0

10. Select Rebuild Server (High-Availability) from the Network Configuration menu.

11. Select Slave Server and continue the installation.

Note:

The slave server’s password should still be blustar.

12. The certificates are now synchronized. At the prompt, press enter.

Replicating files will be displayed above the prompt.

13. A network configuration dialog will appear on the screen. Scroll down and select Apply Configuration.

14. The server software now installs. After pressing Enter at the prompt, the database will be resynchronized with the

master’s.

Note:

The database synchronization may take some time. A progress bar will give an indication on the screen.

15. Select Yes at the prompt to reboot.

16. Once the reboot completes, login to the server and verify that the master server is active in one of the following ways:

a) Enter vipr_ha_is_active at a command prompt. This command returns NO if the master server is the active device.
b) Using a web browser, visit the Platform :: System Status page via the server Web UI.

41-001391-00 Rev 03 – 04.2012 2-18

Chapter 3 System Administration Mechanisms

Console User Interface

Remotely Accessing the Console Interface

To remotely access the console interface, Secure Shell (SSH) client software is required. This is preinstalled on most new
BSD variants or Linux. It may be obtained for most versions of Unix, Linux or BSD at http://www.openssh.org.

To open an SSH session, type at your workstation’s command prompt:

ssh viprserverip -l root

where viprserverip is the hostname or IP address of the BluStar Application Server.

SSH for Windows is available at http://www.chiark.greenend.org.uk/~sgtatham/putty/.

The console interface may also be accessed by connecting a VGA monitor and PS/2 keyboard to the server.

Logging In

When the server is powered up, status messages (often reporting on the initialization of devices or services) will appear.
After the server boot process has completed, a login prompt will be displayed. If this is the first log in, and if no other
users have been created during the installation process, the root username and the password entered during the soft­ware installation process should be entered.

Commonly Used Commands

Information on Linux commands can normally be found by referring to the manual pages, which can be viewed using
the man command.

Example: To view the manual page of the netstat command, including descriptions of all parameters, type

man netstat

netstat

The /bin/netstat command is used to display information regarding network connectivity to and from the plat­form.

Example: To view the routing table, type

netstat -rn

ifconfig

The /sbin/ifconfig command is used to view the status of a network interface.

Note:

Use the vipr_config

command (and not the ifconfig command) to reconfigure network interface parameters.

3-1 41-001391-00 Rev 03 – 04.2012

Console User Interface

service

The /sbin/service command is used to stop, start or restart, or to obtain the status of, any registered service installed
on the platform.

Example: To restart the Apache webserver daemon, type:

service httpd restart

top

/usr/bin/top displays a list of the top processes currently running on the machine. The processes can be ordered by

various values such as CPU usage, memory usage, etc. General information regarding the health of the system is also
displayed.

less

/usr/bin/less is used to view files on the console. Press [h] to obtain help or [q] to exit.

Example: To view the hosts file, type:

less /etc/hosts

shutdown

/sbin/shutdown is used to halt (i.e. shut down) or reboot the platform.
Example: To reboot the platform immediately, type:
shutdown -r now

vipr_config

vipr_config displays a menu from which various initial system configuration and software installation tasks can be

performed.

41-001391-00 Rev 03 – 04.2012 3-2

Administration Web User Interface

Administration Web User Interface

Logging In and Out

The Web User Interface, or Web UI, is compatible with most web browsers such as Internet Explorer 6, Netscape 7, Mozilla

1.7, Opera 7, or more recent versions of these browsers.

The login screen and My BluStar pages of the Web UI can be viewed in either Simplified Chinese or Japanese in addition
to English. These alternate languages must be enabled via the Languages section of your web browser’s Preferences or
Options menu. For example, on Internet Explorer 6, select the Tools > Internet Options menu item; then click on the
Languages button to open the dialogue box where you can Add... Japanese [ja] or Chinese [zh] language support for
the browser.

To log in to the administration web interface, use a web browser to access the following URL:

https://servername

where servername is the hostname or IP address of the server to be administered.

Note:

If the administration web interface is accessed via the non-secure URL (http://servername), you will be automatically
redirected to the secure (https) URL

1. Enter the User Name and Password of the desired user. The default user name and password for the Web UI admin-

istrator are admin and blustar, respectively.

2. Choose a Role, or privilege level, for the user (see User Roles on page 11, for a description of all available roles in the

WebUI system).

Note:
web-platform-admin is the only role available to admin by default. This may be modified on the User Accounts page

using the process outlined in Security Panel on page 5.

3. Enter the Domain, or server name, of the Application Server.

4. Click the Login User button.

3-3 41-001391-00 Rev 03 – 04.2012

Web User Interface Navigation

INFORMATION

AREA

MENU BAR

NAVIGATION
BAR

MAIN

FUNCTIONAL

AREA

LOGOUT LINK

The welcome screen appears as shown in the annotated image below.

Administration Web User Interface

Note:

The normal Back, Forward and Reload buttons provided by the browser should not be used to navigate the web admin­istration interface.

This screen is comprised of the following main functional areas:

• The Menu Bar

• The Navigation Bar

• The Logout Link

• The Main Functional Area

• The Information Area

Menu Bar

The menu bar is the main launching point for all the administration web pages. The icons displayed on the Menu Bar vary
with the role the user uses to login (see User Roles on page 3-11). For the default admin user, all icons on the Menu Bar are
available. These are:

• My BluStar

• Users

• BluStar Devices

• Services

• Platform

• Tool s

41-001391-00 Rev 03 – 04.2012 3-4

Administration Web User Interface

When one of the Menu Bar icons is selected, the Main Functional Area displays a submenu of the options available for
the chosen Menu Bar item.

Navigation Bar

When the user selects an option from the Menu Bar or a submenu, the Navigation Bar changes, adding a link to the cho­sen menu (or submenu) item. This enables the user to jump back up the menu tree to a previous menu option. The user
can also click on the Home icon to be taken back to the Welcome screen.

Navigating to My BluStar, for example, then My Contacts, and finally Contacts Import would display the following hyper­link text:

[Home] My BluStar :: My Contacts :: Contacts Import

In this example, clicking Contacts Import would reload the current page.

Note:

Reloading a form discards all the data that has been entered on that form. The form is also returned to it's default mode.

Logout Link

Clicking this link logs out the current user and returns the user to the Login Screen.

Main Functional Area

The main functional area displays one of the following:

– The Welcome screen message
– A submenu
– A form

Submenu

A submenu contains icons that, when “clicked,” display either another submenu or a form.

Forms

Forms are used to display and edit data. There are a several types of forms, each of which is discussed in Section .

Information Area

This area provides information about the product the user interface is managing, the version of the product, the name
of the currently logged in user as well as the role the user is currently logged in with.

Form Basics

Forms may used to view, edit, filter, add, or delete data.

Navigation Bar

The Navigation Bar, a string of textual hyperlinks, displays a “breadcrumb” trail ([Home] My BluStar :: My Pass­word, for example) to the currently displayed form. Clicking on the My Password link causes the current form to

reload. Clicking on the My BluStar link has the same effect as if the user clicked on the My BluStar menu bar
option.

Logout Link

The Logout Link functions as previously described.

Form Heading

The heading of the form informs the user of the identity of the currently displayed form.

3-5 41-001391-00 Rev 03 – 04.2012

Administration Web User Interface

Form Messages

The messages section informs the user of current actions and their effects. This section appears only if there is a mes­sage that needs to be relayed to the user from the system.

There are four types of messages that can be relayed to the user, each of which can be identified by the icon at the
beginning of the message:

Icon Message

Help

Information

Warn ing

Error

The data area is where the data for the current menu option is displayed. This area changes depending on the mode
the form is currently in.

Control Area

The control area is where the buttons that take the form from one mode to another are displayed.

Field Icons

While using the web UI, the user will encounter the following Field Icons. Hovering oven a field icon with the mouse
pointer causes text information related to that icon to display.

Icon Description

Mandatory Field Icon – indicates that a field needs to be completed on a form.

Help Icon – provides help with reg ards to fields or forms as whole. Help icons always contain hover text which give the user short help

messages. Some help icons also provide a full help web page. These icons can be identified because the mouse pointer changes to a
hand pointer while hovering over the icon.

Refresh Icon – normally found next to a dropdown list field. Some forms need to refresh after an option is selected from the dropdown
list field. Most web browsers automatically refresh the form when an item in a dropdown list is selected. This automatic refresh is due
to the fact that the browser supports Java Script. If the browser does not support Java Script or if the user chose to disable it, it will be
necessary for the user to click on this icon to trigger the form refresh. All the pages that contain the refresh icon also have a button in
the control area that can be clicked to trigger the form refresh.

41-001391-00 Rev 03 – 04.2012 3-6

Administration Web User Interface

Form Types

Each of the following form types has its own basic set of operations and navigation:

Basic View Edit Form

An example of a Basic View Edit form is the Users :: SIP Authentication Support form. Forms of this type usually start in
Viewing mode.

Clicking the Edit button enables the user to edit the displayed fields.

Note:

If the Edit button is disabled, the user does not have privileges to edit the current information.

The above figure displays the form after Edit has been clicked. The user can now change the fields on the form. In the
case of the SIP Authentication Support form, there are only a few check boxes that can be edited. The user is now given
the option to click Save or Cancel in the Control Area.

Clicking Cancel changes the mode of the form back to Viewing mode without saving any of the fields that where
changed.

Clicking Save attempts to save the changes made to the fields. If the data save attempt fails, the user is informed of the
reason via an error message in the Form Messages area. The form will then remain in Editing mode to enable the user to
“fix” any data fields that may have caused the error. If the data save attempt succeeds, the user is informed via an infor­mation message. The form then reverts to Viewing mode.

3-7 41-001391-00 Rev 03 – 04.2012

Administration Web User Interface

Basic View, Edit, Add, and Delete Form

An example of a Basic View, Edit, Add, and Delete form is the Users :: User Accounts form depicted in the image below.
Forms of this type usually start in Filtering mode.

Filtering Mode

Some forms have a filter options section just beneath the form heading. Placing text in the field and clicking on Search
updates the filter result.

Note:

The [Refresh List] button name and the filter options might differ between forms, while other forms might not have
any filter options at all.

The user now has the ability to View, Edit, Add, or Delete records that appear in the filter results table.

Note:

If a user does not have the rights to perform an action that is available in the Control Area, the button for that action is
disabled.

The user must select record(s) before performing the View, Edit, or Delete actions. Select record(s) by checking the
box(es) next to the record(s).

41-001391-00 Rev 03 – 04.2012 3-8

Administration Web User Interface

The filter results table also contains a [>>] button to the left of each record. The [>>] button displays the record in Editing
Mode.

Note:

If the user is not allowed to edit a record, it will be displayed in Viewing Mode.

Viewing Mode

The user must select the records they want to view. If no records are selected and the View button is clicked, an error
message displays at the top of the page, reminding the user to select at least one record.

In the top control area there are normally three additional buttons:

The [-->>] button takes the user to the next selected record.

The [<<--] button takes the user to the previously selected record.

The Back to Filter button will take the user back to the filter result form. All previously selected records remain
selected. Any filter options are also retained

3-9 41-001391-00 Rev 03 – 04.2012

Administration Web User Interface

.

The user can now browse through the selected records. If the user has the right to do so, clicking the Edit button changes
the form to Editing Mode, while clicking the Delete button deletes the current record.

Editing Mode

As with Viewing mode the user should first select at least one record before pressing Edit.

In Editing mode, the fields of each record are editable. The user can change the fields, then click the Save button. If more
that one record was selected, the next record will be displayed for editing and a message in the message area confirms the
data update for the previous record. If an error occurred when the Save button was clicked, the current record remains on
the form, and a message displays in the message area to inform the user of the error.

This form also has additional navigation buttons in the top control area. The behavior of the buttons is as follows:

• The [-->>] button saves the data on the current form and returns the user to the next selected record for editing.

• The [<<--] button saves the data of the current form and returns the user to the previously selected record for editing.

• The Back to Filter button returns the user to the filter result form. The data on the current form is not saved. All the pre-

viously selected records remain selected. Any filter options will also be retained.

Adding Mode

The Adding mode is the only mode for which a record does not need to be selected. Clicking the Add button takes the
user to an editable form which has default values for a new record.

In Adding mode the user is only given the options to Save or go Back to Filter. As with editing mode, no data is saved for
the current record if the user clicks Back to Filter.

41-001391-00 Rev 03 – 04.2012 3-10

Administration Web User Interface

After the user completes the form and clicks Save, the data for the current record is saved. If the save attempt is not suc­cessful, the current record details remain on the form, and an error message informs the user of the error. If the save
attempt was successful, the user is informed with an information message and all fields on the form are reset to default
values to enable the user to add the next record.

Deleting Mode

Deleting records can be triggered from the Filtering mode as well as the Viewing and Editing modes. To delete multiple
records, select records in the filter results table and click Delete. A delete confirmation form will ask the user to confirm
the deletion of the selected records. The user can now deselect some of the records if those records should not be
deleted.

If the user clicks the Delete button without selecting individual records, all records on the confirmation form will be
deleted, and the user will be taken to the original filter result form (not including the deleted records).

Note:

The filter results will not contain the deleted records.

The user can also delete a single record while Viewing or Editing by clicking on the Delete button. This results in a confir­mation form containing only the current record.

User Roles

The concept of user roles is crucial to the administration of the Web UI. Administrators of varying degrees may be cre­ated and assigned for the following reasons:

• To avoid sharing a password between all administrators;

• To enable tracing of actions to individual administrators in audit logs;

• To choose a “level of expertise” based on the individual’s function.

Roles are assigned next to the text “Allowed Login Roles” in the “Security Information” table. Roles may be changed dur­ing the user edit or add processes (see section User Accounts on page 5-1).

Five user roles are available via the Web UI Login screen:

web-platform-admin

This role gives the administrator access to all the areas of the Web interface, with no limitations except those inherent in
the system.

Note:

This role is only to be used by users very familiar with the system.

web-service-admin

This role is to be used for configuring services (e.g. setting up the SIP configuration, configuring routing rules, and
making backups of the system). The web-service-admin also has access to the Users menu and can therefore cre­ate/edit/delete users, edit groups and user settings, and setup call forwarding.

3-11 41-001391-00 Rev 03 – 04.2012

Administration Web User Interface

web-user-admin

This role is designed specifically for the administrator to handle all user-related tasks (e.g. creating/editing users, set­ting up call forwarding and authentication, resetting forgotten passwords, and handling most queries by other users
on the system).

web-terminal-user

This role is for any user of a SIP device (such as a desktop terminal) that wants to manage their contacts, including
importing/exporting, change their password, and set up customized call forwarding. This role denies the user any
admin rights and is safe for any user the administrator sees fit.

Note:

The terminal-user field indicates if a user is allowed to use a BluStar 8000i terminal.

default-role

A user logging in with this role is given the highest role assigned to that user.
Two additional roles can be assigned to users when adding or editing a user account (refer to section User Accounts

on page 5-1).

Note:

The Terminal User role is not accessible via the Web UI Login screen.

Terminal User

This role allows the user to login to a BluStar 8000i terminal and to login from a PC using the PC Client software.

41-001391-00 Rev 03 – 04.2012 3-12

Chapter 4 My BluStar

The My BluStar section allows any user to manage contacts, change their password, set up call forwarding rules, and
download software to a PC. For the web-terminal-user, this is the only available section of the Web UI.

My Contacts

Contacts can be edited individually using the contact editor, or they can be imported from a file created by another pro­gram. My BluStar contacts can also be exported.

Contact Editor

The contact editor is used to search for existing contacts, modify and view existing contacts, and create new ones. It is a
standard example of the Basic View, Edit, Add, and Delete Form on page 3-8 discussed in Chapter 3, "System Administra-

tion Mechanisms".

For additional information regarding the contact editor, see the Aastra BluStar

Guide.

™

8000i Desktop Media Phone User

4-1 41-001391-00 Rev 03 – 04.2012

My Contacts

Contacts Import

From this page, a user can import a contacts file that is accessible on the local machine.

Import File

Press the browse button to locate the contacts file.

Field Delimiter

Choose the delimiter, a value that separates items in the contact file. This can be chosen from the drop-down menu
or specified as OTHER, with the delimiter to the right.

First Line in File are Headings

Check this box if the first line of the file contains headings, or leave blank (default).

Import File Character Format

Choose the character format used in the contacts file, either International, or the correct Chinese or Japanese format.

Import the contacts file by pressing Upload File. The imported contacts are now visible in the Contacts Editor.

41-001391-00 Rev 03 – 04.2012 4-2

My Contacts

Contacts Export

Contacts can be saved to an external file using this page.

Number of Contacts (uneditable)

Displays the number of contacts the user has in their contacts editor.

Export Headings

Choose whether or not to export the headings (Title, First Name, etc.) to the contacts file.

Export File Character Format

Choose the character format to be used in the exported file, either International, or the correct Chinese or Japanese
format.

Export Fields

Select fields that are to be included for each contact in the exported file.
Press the Export button to save the file. A pop-up window will prompt the user to either open or save the file (Inter-

net Explorer). Choose Save and select a location to save the contacts file.

4-3 41-001391-00 Rev 03 – 04.2012

My Password

My Password

My Password refers to the password used to log in to the Web UI. This subsection of the Web UI allows any user to modify
their password.

Password Change

To change your password, specify the old password, new password, and new password again.

41-001391-00 Rev 03 – 04.2012 4-4

My Call Handling Rules

My Call Handling Rules

Call Handling features can be configured for each user as required in User Call Handling Rules on page 5-25. The user can
add, delete, enable/disable, modify, and control the order in which rules are applied by accessing this section of the Web
UI. As an administrator accessing this page, these settings will affect only the call handling preferences of the administra­tor user.

Presence

True presence status of the user as set on the terminal. These include: Available, Busy, Do Not Disturb, Va cation,
Unavailable, Out of the Office, Presence Blocked, and the default All Presence.

Action

The action to be performed on the call. Choices include: No action, Forward unanswered calls, Forward all calls,
Forward declined calls, and Pretend to be busy.

Action Details

If any of the actions: Forward unanswered calls, Forward all calls, or Forward declined calls is chosen, this set-
ting allows the administrator to define the address to which the call is to be forwarded.

Enabled

This checkbox allows a rule to be enabled or disabled.

Insert Before

Allows the administrator to control the order in which rules are applied to calls. Rules are applied in top-down
order as they appear in the table.

The image below shows two Call Handling Rules. The first rule is set up so that if the user’s presence is “busy”, the BluStar
8000i will “forward all calls” to a user-defined SIP address.

The second rule states that regardless of the user’s presence, the BluStar 8000i will “pretend to be busy” and send out a
“busy” message to the caller.

4-5 41-001391-00 Rev 03 – 04.2012

PC Software Downloads

PC Software Downloads

PC software intended for use with the BluStar 8000i can be accessed and downloaded by clicking on the PC Software
Downloads icon. The image below shows a typical listing of software available for download by the currently logged-in
user.

The listing shows the software Product name, the Operating System on which the software can be installed and used, and
a Download link to the software package. Click on the software link to download the file.

Proxy Registrations

Proxy registration can be configured for each user as required in Proxy Registration on page 5-9. This screen shows the
user their Proxy Registration information.

Proxy Registration

The BAS will register the user to a remote server when the user logs in to their BluStar 8000i .

41-001391-00 Rev 03 – 04.2012 4-6

Chapter 5 Users

After installation, the default administrator is automatically created with a username of admin and a password identical
to that of the root user on the server.

User Accounts

BluStar 8000i or SIP phone user accounts (referred to as “end users” in this document) can be created, modified or
deleted via the Web UI.

When the User Accounts icon is selected, a list of all configured user accounts followed by View, Edit, Add, and Delete
buttons is shown below.

The User Accounts listing shows the User Name, Display Name, and SIP URL for each account.

From this screen, an administrator may filter the list of user accounts using the following parameters:

Name starting with

Enter the first few letters for filtering the list of names.

5-1 41-001391-00 Rev 03 – 04.2012

User Accounts

Max Records

Enter the maximum number of records to be shown on the filtered listing. Default value is 100.
Click on the Refresh List button to filter the list per the values filled in above.
Each entry in the listing has a check box next to it. If the box is checked, clicking on either the View or Edit buttons

displays the record for viewing or editing, respectively. If more than one check box is checked, the records are dis­played one-at-a-time. Forward and backward navigation buttons allow the user to cycle through the selected
records. The [>>] button next to a record take the user directly to the editing page for that record.

Viewing, Editing, Adding, and Deleting Users

To view a user’s account information without being able to change any settings or details, click the check box next to that
user’s name and click View. To edit a user account, either click the [>>] button next to the account name, or click the adja­cent check box followed by Edit. To create an additional user account, click the Add button. (New users are added to the
All Users group.)

When editing or adding a user account, the account information can be modified via the User Identity panel at the top of
the screen; and by a series of sub-panels that are accessed by clicking the appropriate button. For example, the image
below shows the account editing screen with the Contact Details and Folders buttons selected.

Additional buttons include: Groups, Security, Proxy Registration, Voicemail, Phone Numbers, Addresses, Organiza-
tion, and Email/Web.

Detailed descriptions of the various panels associated with this screen are given below.

41-001391-00 Rev 03 – 04.2012 5-2

User Accounts

User Identity

The User Identity panel is where the essential information for defining a new user is contained. This panel contains four
fields: User Name, Display Name, Home Server, and SIP URL.

Note:

Entries are required in both the User Name and SIP URL fields.

User Name

The name that the user must use to log into a BluStar 8000i terminal. This name typically is the same as the Win­dows username. This is a required field. (The field cannot be blank.) The User Name can only be composed of
alphanumeric characters, dashes, and underscores.

Note:

Do not use the “@” symbol in this field.

Display Name

The Display Name indicates the name of the user that is shown during calls and that appears in address books. The
display name may contain spaces.

Note:

For optimum compatibility with SIP devices from various third party vendors, using special characters (i.e., characters
other than letters, digits, or spaces) in this field is not recommended.

Home Server

Home Application Server hostname (not configurable)

SIP URL

The SIP address at which the user can be contacted. SIP addresses are similar to e-mail addresses, and have a similar
format: username@domain. The SIP URL for a user must be entered to call that user. SIP URLs should be entered with
lower-case letters to avoid case sensitivity issues.

By default, the SIP URL is displayed as sip:<NAME>@server.address.

If the account is saved leaving the SIP URL unchanged, the <NAME> portion will be copied from the User Name field
automatically. It is necessary to manually modify the SIP URL only if it is desired to make the user portion of the SIP
URL different from the BluStar User Name.

Note:

The domain part of the SIP URL (i.e., the part after the @ sign), must be the server name or IP address of the Application
Server. For a High Availability installation it should be the shared IP address or shared hostname.

Contact Details

This panel is where the contact’s basic information (name, phone number, etc.) is entered.

5-3 41-001391-00 Rev 03 – 04.2012

User Accounts

Phone Number

Enter the primary phone number for the user here. Select one of the categories from the pull-down menu to define
the type of phone number.

SIP Alias List

A user can be identified by the user’s assigned SIP URL, or can be identified by one or more aliases. If aliases have
been assigned, the user will also be reachable by placing a call to alias@domain in addition to the user’s assigned
SIP URL.

Note:

Each alias entry may only contain SIP URLs, e.g. sip:[e-mail] and no special characters (i.e., no control
characters or spaces).

Aliases may also be entered in a form containing only the SIP username part of the alias (i.e., omit the SIP:, @, and the
domain). The current server name will be appended automatically.

Save in Global Address Book

Check the box to ensure that this user’s information will be included in the Global Address Book.

Note:

If this box is unchecked, none of the fields below it appear on the form.

Contact Name

Optional fields where the user’s Title, First Name, Middle Name, Last Name, and Suffix may be entered.

A series of buttons below the Contact Name provides the means to enter additional optional information for the contact.
The Folders button displays a panel that allows the system administrator to assign the contact to existing folders via the
checkbox(es). New folders can also be created by typing the desired name in a text entry box. Similarly, contact Phone
Numbers, home and work Addresses, Organization (company information), and Email/Web addresses can be entered
on sub-panels displayed by clicking the appropriate button. Clicking one of these buttons automatically saves any infor­mation entered in the currently displayed panel before displaying the new panel.

Groups Panel

This panel allows you control membership of the user in any defined groups. For example, in the image below, to make the
user a member of the Friends group, click on the word Friends to highlight it; then click the [<<] button to move the
Friends category to the Member of column.

41-001391-00 Rev 03 – 04.2012 5-4

User Accounts

Security Panel

Security settings for the user, as well as the allowed login roles, are specified in the Security panel. The options presented
depend upon the Authentication Type (LOCAL or SMB) that is selected.

LOCAL Authentication Settings

When the Authentication Type chosen is LO CAL, a screen similar to the following is displayed.

Authentication Type

Type of authentication between the web user and the WebUI. Changing this field also affects other fields on the
page. The web page will reload to reflect this change.

LOC AL - Uses the local authentication of the Application Server.
SMB - Uses server message block (SMB) authentication.

Set Password

Specify the admin password, new user password, and confirmation of new user password. This field contains the
password the user will use to log in. The password is hidden when entered; and characters entered will be dis­played with asterisks (for security reasons) when typed.If only external authentication methods (e.g., SMB authenti­cation) will be used for this user, the password field should be left empty

Notes:

• Users for which empty passwords have been stored in the local database must provide a valid SMB password to log

in. Empty passwords will normally not be accepted as valid passwords.

• To indicate that a user does not have a BluStar database based password, delete all characters in the field. DO NOT
enter one or more spaces, as one or more spaces will be interpreted as a valid password.

5-5 41-001391-00 Rev 03 – 04.2012

User Accounts

Force Password Change

Forces the user to change the account password on next login.

Allowed Login Roles

Login roles the user is permitted to assume. The different roles are defined in User Roles on page 3-11.

SIP Authentication Type

Type of authentication between SIP device and server. The various types are detailed in Authentication Types on

page 5-23.

SIP Static URL

This setting is used for static SIP registration. Enter the SIP URL to which calls should be forwarded in this field.

Note:

To use static SIP registration, the account’s Authentication Type must be configured as STATIC.

Account Enabled

Specifies whether or not the user account is enabled. Unchecking this box will deactivate (prevent from logging in) a
user account until it is manually enabled again.

Security Settings

The settings shown in the lower portion of this panel are controlled by a series of buttons: Password Restraints,
Password Expiry, Account Lock, and Access Control.

Password Restraints

Allow User to Change Password

Permits the user to change the account password.

Enable CrackLib Password Testing

Prevents users from choosing easily guessed passwords.

Minimum Password Length

Sets the minimum number of characters that must be in a password. Setting this to “0” (zero) disables checking.

Minimum Number of Letters in Password

Sets the minimum number of letters that must be in a password. Setting this to “0” (zero) disables checking.

41-001391-00 Rev 03 – 04.2012 5-6

User Accounts

Minimum Number of Digits in Password

Sets the minimum number of digits that must be in a password. Setting this to “0” (zero) disables checking.

Minimum Number of Special Characters in Password

Sets the minimum number of special characters that must be in a password. Setting this to “0” (zero) disables
checking.

Special Characters Allowed in Password

Lists of special characters that are allowed to be entered in a password. Setting this to “All” enables any special
character to be used.

Password Expiry

Max Password Age

Sets the maximum number of days that the current password remains valid. Setting this to 0 (zero) disables check­ing.

Password History

Sets the number of previous passwords that are “remembered” by the system. New passwords cannot match any of
the passwords in the history.

Account Lock

Number of Invalid Login Attempts before User Account Lock

Sets the number of invalid login attempts that the system permits before locking the account. Setting this to 0
(zero) disables checking.

Account Lock Time

Sets the time (in minutes) that the account remains locked if the number of invalid login attempts is exceeded. This
setting is disabled if the Number of Invalid Login Attempts before User Account Lock field is set to 0 (zero).

5-7 41-001391-00 Rev 03 – 04.2012

User Accounts

Access Control

Allow User to Edit Call Handling Rules

When checked, permits the account user to make changes to the Call Handling Rules for that account.

Allow Execution of Remote Control Commands

Allows the execution of remote control commands. Setting this to “No” disables execution of remote control com­mands.

Allow User to Configure an LDAP Directory Source

Allows (or disallows) users to edit their LDAP directory configuration, which will override the configuration coming
from the configuration server.

Allow User to Configure an Exchange Personal Contact Source

Allows (or disallows) users to edit their Microsoft Exchange contact configuration. If users import Microsoft Exchange
personal contacts, they will not have access to their user directory.

SMB Authentication Panel

This panel displays the security settings for accounts whose Authentication Type has been set to SMB.

The Authentication Type, Allowed Login Roles, SIP Authentication Type, SIP Static URL, and Account Enabled fields
are the same as those appearing in LOCAL Authentication Settings screen. This panel also provides two Security Settings
buttons: Samba, and Access Control. The Samba settings are used to associate the account with the SMB Domain and

SMB Server that are to be used for authenticating the user upon login. (See Access Control on page 5-8 for details on
Access Control settings.).

41-001391-00 Rev 03 – 04.2012 5-8

User Accounts

Proxy Registration

The Proxy Registration panel is where you can set the proxy registrations for the user. When the user logs in to the BluS­tar 8000i , the BAS will login to the remote server on the user’s behalf. A user can have up to three proxy registrations.

Proxy Registration

The BAS will register the user to a remote server when the user logs in to their BluStar 8000i .

Remote Username

Username to login to the remote server.

Remote Registrar

SIP URL of remote server.

Voice Mail

The Voice mail panel stores the voicemail number for the user.

Voice Mail Number

The number users can use to login to their voice mail.

5-9 41-001391-00 Rev 03 – 04.2012

User Groups

The User Groups page allows the administrator to do the following:

• add and delete User Groups

• add members to existing User Groups

• edit User Group settings.

User groups can be used to:

• Apply configurations to specific groups of users.

User Groups

Creating a User Group

A User Group is created as a “child” of a group. To create a new group:

1. Click on the icon next to the parent of the new group.

2. On the resulting screen, type the name of the new group.

3. Click the Save button to complete the creation of the new group.

Deleting a User Group

To delete a User Group:

1. Click on the icon next to the group that is to be deleted. A confirmation screen displays to confirm the deletion.

The confirmation screen also displays any groups that are members of the group the user wants to delete.

2. Click the Delete Group button to delete only the selected group. All members of the deleted group now become

members of the All Users group.

3. Click Delete Group Tree to delete the selected group as well as all of its members that are groups.

Managing Group Members

To manage Group Members, begin by clicking on the icon next to the group whose members you want to manage.
The resulting Group Members panel allows the user to select multiple items from the Direct Members and Available for

Membership lists. The user can also move groups or users from being Direct Members to being Available for Member­ship by selecting them in the lists and using the [<<] and [>>] buttons. Once the user is satisfied with the configuration

click Save. The All Users are members of this group check box disables (hides) the User Members sub-panel if checked.

41-001391-00 Rev 03 – 04.2012 5-10

User Groups

User are not prevented from joining more that one group. A user is always a member of the All Users group as well as
any other group to which the user is assigned. The only instance where a group (A) will be disallowed from being a mem­ber of another group (B) is if B inherits from A (directly or indirectly).

Understanding Group Settings

A child group’s settings can be inherited from the parent group. However, the child group’s settings can also differ from
the parent group’s settings. For example, in the image below, a user who is a member of Group2 and All Users would
have the following settings:

– Number of Invalid Login Attempts before User Account Lock=5.

Configuration settings are a combination of the settings of all groups of which the user is a member. In the example
shown above, Group2 is at a deeper level than All Users. Consequently the Number of Invalid Login Attempts before
User Account Lock=5 setting takes precedence. The Minimum Password Length setting is inherited from the All Users
group.

If a particular setting is entered in multiple groups, the group priority setting determines the effective setting. The order
in which immediate child groups are displayed indicates the priority for the child groups. For example, in the image
below, Group2 is above Group1 in the list of groups that are immediate children of the All Users group. Consequently,
the Minimum Password Length=4 setting for Group2 would override the Minimum Password Length=3 setting of
Group1.

The priority of the child groups can be seen by clicking on the icon. The image below shows the current priority
(Order) of the child groups in the image above.

5-11 41-001391-00 Rev 03 – 04.2012

User Groups

The group priority setting is effective only if a setting is in conflict with another group setting at the same level. In the
image below, Group2 and Group1 are at level 2 (i.e., they are immediate children of the All Users group). Group1a is at
level 3 (an immediate child of Group1).

In this scenario, the effective setting would be Min Password Length=3. (Because Group1a is the longest path (level 3)
for the Min Password Length setting, its value becomes the effective setting.)

41-001391-00 Rev 03 – 04.2012 5-12

User Groups

Editing User Group Settings

The user group settings page contains panels similar to those found in the Security settings panels of the User
Accounts page. These include the following:

Password Restraints

Prevents users from choosing easily guessed passwords.

Allow User to Change Password

Permits the user to change the account password.

Enable CrackLib Password Testing

Prevents users from choosing easily guessed passwords.

Minimum Password Length

Sets the minimum number of characters that must be in a password. Setting this to “0” (zero) disables checking.

Minimum Number of Letters in Password

Sets the minimum number of letters that must be in a password. Setting this to “0” (zero) disables checking.

Minimum Number of Digits in Password

Sets the minimum number of digits that must be in a password. Setting this to “0” (zero) disables checking.

Minimum Number of Special Characters in Password

Sets the minimum number of special characters that must be in a password. Setting this to “0” (zero) disables
checking.

Special Characters Allowed in Password

Lists of special characters that are allowed to be entered in a password. Setting this to “All” enables any special
character to be used.

Password Expiry

Max Password Age

Sets the maximum number of days that the current password remains valid. Setting this to “0” (zero) disables
checking.

Password History

Sets the number of previous passwords that are “remembered” by the system. New passwords cannot match any of
the passwords in the history.

Voice Mail

Sets the voice mail number for all users in the group.

Account Lock

Number of Invalid Login Attempts before User Account Lock

Sets the number of invalid login attempts that the system permits before locking the account. Setting this to 0
(zero) disables checking.

Account Lock Time

Sets the time (in minutes) that the account remains locked if the number of invalid login attempts is exceeded. This
setting is disabled if the Number of Invalid Login Attempts before User Account Lock field is set to 0 (zero).

5-13 41-001391-00 Rev 03 – 04.2012

User Groups

Samba Authentication Settings

The Samba settings are used to associate the account with the SMB Domain and SMB Server that are to be used for
authenticating the user upon login. Refer to SMB Authentication Panel on page 5-8 for details.

Access Control Settings

Allow User to Edit Call Handling Rules

When checked, permits the account users to make changes to the Call Handling Rules for that account.

Disallow the User to Download and use the Monitor and Mouse Control Software

Controls the version of PC Client software available for download by users when logged into the Web UI. When
unchecked, the Monitor and Mouse Control version is enabled for download. When checked, the Standard version is
enabled for download.

41-001391-00 Rev 03 – 04.2012 5-14

Global Contacts

Global Contacts

Global contacts allows the system administrator to establish and maintain a contact list of all users on the BluStar system
that is readily available to users from the BluStar 8000i terminal. This list is referred to on the terminals as the Global
Address Book (GAB). GAB contacts can be assigned to categories (folders) if desired. The system administrator may also
control whether or not the GAB may be enabled for viewing - as well as which users or user groups may access the GAB
contacts. The system administrator can also populate the GAB by importing a delimited text file of contacts generated
outside of the Web UI. The Global Contacts main page contains three icons as shown below:

• Global Contact Editor

• Global Contacts Access Lists

• Global Contacts Import

• Global Address Book Sync

Global Contact Editor

Note:

GAB access is disabled by default. To allow users to view the GAB, click the [Enable Global Address Book Viewing]
button at the bottom of the Global Contact Editor page.

The Global Contact Editor main page provides the means to filter the list of contacts in the GAB. The list can be filtered
and sorted by either first or last name, and by folder name. The number of records listed per page can also be set. This
page also provides the system administrator with buttons to View, Edit, Add, and Delete contacts for the Global
Address Book (GAB).

Notes:

• Updating a large Global Address Book (greater than 2000 entries) can have a momentary adverse impact on BluStar

8000i terminals. BluStar 8000i users logging in will experience a brief delay.

• Updates to the Global Address Book are immediately reflected to all logged-in BluStar 8000i users and can momen­tarily impact call quality or cause delays in dialing operations. Updates to the Global Address Book should be done
off-hours to minimize the impact on BluStar 8000i users.

5-15 41-001391-00 Rev 03 – 04.2012

Global Contacts

Each entry in the listing has a check box next to it. If the box is checked, clicking on either the View or Edit buttons dis­plays the record for viewing or editing, respectively. If more than one check box is checked, the records are displayed one­at-a-time. Forward and backward navigation buttons allow the user to cycle through the selected records. The [>>] button
next to a record take the user directly to the editing page for that record.

Adding and Editing Global Contacts

The image below shows the default page for adding a Global Contact. In the Contact Name panel, the system administra­tor can enter the Title, First, Middle, and Last Names, and Suffix (e.g., Junior, Esquire, etc.) for the new contact. The Contact
Details field includes buttons that can be clicked to display sub-panels for entering additional contact information. (The
page for editing an existing Global Contact is similar in all respects to this page.)

The Folders button displays a panel (shown above) that allows the system administrator to assign the contact to existing
folders via the checkbox(es). New folders can also be created by typing the desired name in a text entry box. Similarly, con­tact Phone Numbers, home and work Addresses, Organization (company information), and Email/Web addresses can
be entered on sub-panels displayed by clicking the appropriate button. Clicking one of these buttons automatically saves
any information entered in the currently displayed panel before displaying the new panel. Clicking the Add Another Glo-
bal Contact button also saves the existing contact’s information prior to displaying a new, blank contact entry page.

41-001391-00 Rev 03 – 04.2012 5-16

Global Contacts

Global Contacts Access Lists

If additional Global Folders have been created, this page displays a listing of Users and User Groups that are Allowed to
access the folders that have been created in the GAB. A pop-up list allows the administrator to display the Allowed/Avail­able status for the selected folder name. The Available column shows Users and User Groups that are not currently able
to access the selected folder.

Clicking the Edit button displays a page that allows entries in the Available column to be moved into the Allowed col­umn (and vice-versa) by clicking a column entry to highlight it, then clicking the [<<] or [>>] button to move the
selected entry. (Shift-clicking and Ctrl-clicking can be used to select multiple entries.)

5-17 41-001391-00 Rev 03 – 04.2012

Global Contacts

If GAB viewing is enabled, all users are permitted to view contacts that are not associated with folders. The ability to
restrict access to contacts is possible only if the contact is associated with a folder.

Note:

The All Global Entries folder that appears on the BluStar 8000i terminal on the directories screen displays a combi­nation of unfiled contacts (contacts not associated with at least one folder) and filed contacts. If a contact is associated
with folders that a user does not have permission to view, that contact is not visible in the All Global Entries folder ­and that user will not see the folder associated with that contact.

Global Contacts Import

This page allows the administrator to import a delimited text file containing contacts that are to be added to the GAB. The
administrator can select the Field Delimiter used to separate field entries in the text file; and can also indicate that the
first line of text in the file should be treated as heading information when the file’s contents are imported. The Import File
Character Format used in the contacts file can also be selected, either International, or the correct Chinese or Japanese for­mat.

The Browse... button is used to select the file that is to be imported. Clicking the Upload File button initiates the import
process.

41-001391-00 Rev 03 – 04.2012 5-18

Global Contacts

Global Address Book Sync

This page allows administrators to sync up global address book. In order for BAS X to obtain contacts from BAS Y, BAS X
syncs from BAS Y. The first step is creating a connection between BAS X and BAS Y. Then BAS Y gives permission to BAS X
to obtain BAS Y contacts. Finally, BAS X syncs from BAS Y and obtains BAS Y contacts.

To Synch the Global Address Book:

1. Create a connection from BAS X to BAS Y:
a) Go to BAS X: Services :: Clustering :: Outbound BAS Connections.
b) Click Add.
c) Enter the shared host name of BAS Y.
d) Click Save.
e) Click “Back to BAS List.”

2. Check that a bidirectional connection is established:
a) O n BA S X, go to Services ::  Clustering :: Outbound BAS Connections. You must see BAS Y entry as “Connected”.

b) On BAS Y, go to Services :: Clustering :: Outbound BAS Connections. You must see BAS X entry as “Connected”.

5-19 41-001391-00 Rev 03 – 04.2012

c) On BAS Y, go to Services :: Clustering :: Inbound BAS Connections.

You must see BAS X entry as (Hostname: BAS X full-qualified-name, Certificate Common Name: BAS X IP-Address,
Account Status: Enabled, Login Status: Registered, Connection Status: Connected, Roles Granted to Server:

Remote BAS.

d) Check the same on BAS X.

e) On BAS X, go to Users :: Global Contacts :: Global Address Book Sync.

You must see BAS Y entry (Hostname: BAS Y full qualified name, Common Name: BAS Y IP Address, Frequency
(minutes): 30, Last Sync Time: Never, Status: Synchronization not permitted.

Global Contacts

3. On BAS Y, check the same at Users :: Global Contacts :: Global Address Book Sync.

41-001391-00 Rev 03 – 04.2012 5-20

Global Contacts

4. BAS Y must grant the GAB Sync role to BAS X:
a) On BAS Y, go to Services :: Clustering :: Inbound BAS Connections.

b) Select BAS X entry and click Edit.
c) Select the GAB Sync role and click Save.
d) You must receive the information message "Inbound BAS Connections :: Connected BAS account rights updated.”

Note that the connected BAS has been logged off in order for the access right to take effect. The connected BAS
will automatically login again within the next 10 minutes.

e) On BAS Y, Services :: Clustering :: Inbound BAS Connections the status of BAS X changes to (Login Status:

Unregistered, Connection Status: Disconnected).

f) On BAS X, Services :: Clustering :: Outbound BAS Connections select BAS Y remote connection and click Te s t

Connection. This will force BAS X to re-login to BAS Y.

5-21 41-001391-00 Rev 03 – 04.2012

Global Contacts

g) On BAS Y, Services :: Clustering :: Inbound BAS Connections the status of BAS X changes to (Registered, Con-

nected).

5. Enable Global Address Book Viewing on BAS Y. This will allow BAS X to obtain contacts from BAS Y. It will also allow

BluStar 8000i terminals on BAS Y to show the contents of BAS Y GAB:

a) If BAS Y has a fresh install (not upgrade), then on BAS Y Users :: Global Contacts :: Global Contact Editor, you

should see the button Enable Global Address Book Viewing.

b) If the previous step is seen, then on BAS X Users :: Global Contacts :: Global Address Book Sync, check that

(Last Sync: Never, Time Status: Remote BAS does not allow GAB Viewing).

c) On BAS Y, go to Users :: Global Contacts :: Global Contact Editor and click on Enable Global Address Book

Viewing.

6. If BAS Y does not have user accounts that BAS X can sync, create one:
a) Go to BAS Y Users :: Global Contacts :: Global Contact Editor and click Add (you can do the same s tep by g oing

to Users :: User Accounts and clicking Add but make sure that the Save in Global Address Book is checked).

7. Run the Sync on BAS X:
a) Go to BAS X Users :: Global Contacts :: Global Address Book Sync
b) Select BAS Y entry that you want to sync from and click Sync Now.
c) The values of Last Sync Time and Status should change.

41-001391-00 Rev 03 – 04.2012 5-22

SIP Authentication Support

SIP Authentication Support

These settings are used to define the type of authentication needed to access the server from a device that can make or
receive a SIP call. The authentication type for each user is specified in the SIP Authentication Type field in the Security
panel when adding or editing any user account (see image below).

Note:

BluStar 8000i terminals always attempt to log in using a Secure Sockets Layer (SSL) encrypted connection before reg­istering to the SIP Registration Service. The authentication process does not rely on SIP, therefore the SIP authentication
settings can be left at the default values for BluStar 8000i terminal users. Users attempting to register using other SIP
User Agents (e.g., third party SIP phones) use standard SIP authentication methods

Authentication Types

DISABLED

Prevents the user from accessing any SIP device.

NONE

When using a SIP device, the user does not need to authenticate to the Application Server, but still needs to be SIP
registered.

STATIC

The user is always SIP registered with the server and never needs to authenticate.

BluStar

Allows the user to use a BluStar 8000i terminal.

DIGEST

When using another SIP device, the user will need to authenticate on SIP registration.

5-23 41-001391-00 Rev 03 – 04.2012

Registered Users

Registered Users

Registered users are users who have logged in to their terminals. The registered users page shows a list of users that are
registered via SIP on the server. A list of user names, expiry times and registered addresses is shown. This page also shows
remote proxy registers and if the registration was successful or if it failed.

41-001391-00 Rev 03 – 04.2012 5-24

User Call Handling Rules

User Call Handling Rules

The User Call Handling Rules page allows the system administrator to configure call handling rules for each user. Once
configured, the system administrator can then control whether or not the user can modify, add, or delete rules via the
My BluStar :: My Call Handling Rules page of the Web UI.

This page contains a listing of all of the users administered by the server. It allows the administrator to filter the list by
name, and to control the number of user records shown on each page.

To view the call handling settings and rules for a user, click on the [>>] button. To view multiple user settings, check the
boxes next to the desired users, then click the Go to Selected Users Call Rules button. A screen similar to the following
displays:

This page contains a non-editable User Information pane that shows the selected user’s User Name, Display Name, and
SIP URL. It also contains a Call Handling Settings pane that allows the administrator to enable (default) or disable the
ability for the user to edit Call Handling Rules.

5-25 41-001391-00 Rev 03 – 04.2012

Troubleshooting

The bottom pane allows the administrator to view, edit, add, and delete rules for the selected user. It also allows the
administrator to change the order in which the rules for the selected user are applied to incoming calls. The figure below
shows the editing view for a user rule.

Please refer to My Call Handling Rules on page 4-5 for a detailed explanation of this pane.

Troubleshooting

If users cannot register from non-BluStar 8000i terminals, the problem may lie in the user settings:

• Check the username and SIP URL entered for errors

• Check that the Authentication Type is appropriate for the User Agent which is causing problems

• Re-enter the password and save the user settings to ensure that the password is correct and has been saved correctly.

If a user cannot make calls, the “Registered Users” page should be checked to determine whether the terminal has been
properly registered with SIP Services.

41-001391-00 Rev 03 – 04.2012 5-26

Chapter 6 BluStar Devices

The BluStar Devices section of the WebUI can be used to obtain information about BluStar Devices, or to configure BluS­tar Devices. BluStar Devices download settings and software releases from the BluStar Application Server (BAS). Third
party SIP devices (e.g. SIP Phones) are regarded as BluStar Devices.

BluStar Device Status

Specific BluStar 8000i devices can be viewed or modified from this page. This page also allows an administrator to reset
the device password of the device or enable automatic password reset. If auto password reset is selected, devices will
automatically have their registration accepted, therefore removing a layer of security. BluStar 8000i devices inherit set­tings from the Device Group Settings.

When using the View, Edit, or Reset Device Password buttons in the list screen, the action will be performed on all
marked items. While selecting multiple terminals and clicking the Reset Device Password button will immediately reset
the password on all marked terminals, pressing the View or Edit buttons will require you to go through each settings
page of the marked terminals by pressing the [<<--] and [-->>] buttons. When using Enable Auto Password Reset, all
devices displayed will have their registration accepted when the terminal tries to login to the server.

6-1 41-001391-00 Rev 03 – 04.2012

BluStar Device Status

BluStar 8000i Terminal Settings

The settings for any BluStar 8000i terminal are described below:

Notes:

• The inherited check box specifies whether or not that setting is inherited from Global Terminal Settings.

• The terminal settings listed below may differ depending on the specific software release that the respective terminal

is currently running.

Device Information

Displays information about the specific BluStar 8000i terminal. The account can also be enabled (checked) or disabled
from this subsection.

Software Upgrade Settings

Automatic upgrade start time

The time at which automatic upgrades will start, formatted as “YYYY-mm-dd hh:mm:ss”. Enter an hour, a time, or
both. For an upgrade to occur as soon as possible, enter ASAP in the same field.

The server can instruct a BluStar Device (or all BluStar Devices), to update software. This allows software updates to
be “pushed” to BluStar Devices by the BluStar Application Server.

Note:

Updating the software may require an hour or two to complete, as devices only check for software updates when they
are restarted, on login / logout, and approximately every hour.

Automatic upgrade window

Devices choose a random time after the start time, up to this number of minutes.

Allow manual software upgrading

Specifies whether or not the software may be upgraded manually. The manual software upgrade allows upgrades to
be “pulled” by BluStar Devices from the BluStar Application Server.

administrators or users can manually request that a BluStar Device update its software. Refer to the documentation
accompanying the BluStar Device for detailed instructions with regard to manual software upgrading.

Release to be installed

The software release to be installed by BluStar Devices can be selected from a drop-down list. The list is automatically
created from all the BluStar Device software releases which have been installed to the BluStar Application Server.

Note:

BluStar Device software releases are typically distributed as “rpm” or “tar” files. For instructions with regard to installing
software releases, see Download Software on page 6-17.

Security Settings

Allow local administrator login

Specify whether or not to allow a root login via the console.

Allow remote administrator login

Specify whether or not to allow a root login via SSH.

Administrator password

Create and confirm a new administrator password for the device.

41-001391-00 Rev 03 – 04.2012 6-2

BluStar Device Status

Force reboot time

Reboot device at specified time. Format is yyyy-mm-dd hh:mm:ss (for ASAP use current date and time).

Terminal Security Settings

Disable dialing when logged off

Specify whether or not to disable dialing when no user is logged in to the terminal. Disabling dialing will cause the
terminal to not display the dial pad.

Allow change of auto answer setting

Specify whether or not to allow users to change auto answer settings

Allow automatic presence changing

Specify whether or not to allow automatic presence changing. The BluStar 8000i can automatically adjust user’s
presence based on whether users are logged in (presence set to Available), logged out (presence set to Unavaila­ble), or in a call (presence set to Busy). This setting controls whether presence will be automatically changed this
way. Presence is never automatically changed if it has been manually set to a value other than Available, Unavaila­ble, or Busy.

Enable FIPS 140-2 Strict Security Mode

Not supported on BluStar terminals.

Screen lock on inactivity after

Can be set to disabled or a specified number of minutes. The screen lock facility can lock a BluStar 8000i terminal,
requiring the currently logged in user’s password to be re-entered before the terminal can be used again.

Disable remote camera control

Not supported on BluStar terminals.

Disable terminal services client

Not supported on BluStar terminals.

Require password to edit terminal identity

Enable or disable password protection for terminal identity changes.

Password to edit terminal identity

Specify password to edit terminal identity.

Allow XML remote control

Enable or disable XML remote control.

Screen Dimming Settings

Screen first dim time

Can be set to disabled or to a specified number of minutes. The screen partially dims after this number of minutes.

Screen second dim time

Can be set to disabled or a specified number of minutes. The screen further dims after this number of minutes.

Screen saver settings

Screen save time

Can be set to disabled or a specified number of minutes.

6-3 41-001391-00 Rev 03 – 04.2012

BluStar Device Status

Locale Settings

Time zone

Specify the time zone by selecting an appropriate value from the list. Set the time zone globally if it is the same for all
terminals. Otherwise select the appropriate time zone for each terminal.

Language

Specify the language to be used on the terminal user interface.

DiffServ or IP Type of Service Settings

IP TOS byte for audio

Specify the IP Type of Service (TOS) byte which should be used for audio packets in this field. Leaving the field empty
in per-device settings will instruct a device to use the globally specified parameter.

IP TOS byte for video

Specify the IP Type of Service (TOS) byte which should be used for video packets in this field. Leaving the field empty
in per-device settings will instruct a device to use the globally specified parameter.

IP TOS byte for low-res video

Specify the IP Type of Service (TOS) byte which should be used for low resolution video packets in this field. Leaving
the field empty in per-device settings will instruct a device to use the globally specified parameter.

LDAP Settings

LDAP server display name

The name to be displayed of the LDAP (Lightweight Directory Access Protocol) server

LDAP server hostname or IP address

The IP or hostname of the LDAP server. This will typically be the organization’s main LDAP server, which contains the
organization’s main directory (global address book). Users can add additional LDAP servers as desired. This parame­ter handles multiple values, the format is the following username:password@ldapserver:port

Where:

– username for Authentication (optional, if not provided anonymous connection will be used)
– password for Authentication (optional)
– ldapserver is the IP address or name of the LDAP server (mandatory)
– port is the LDAP interface port (optional, default is 389)

Example 1: LDAP_Server=ldap.acme.com, no authentication and using default port 389
Example 2: LDAP_Server=user:[e-mail]:3268, authentication and using port 3268

LDAP server base DN

The description of the top level of the directory tree. Usually if a company domain is company.com, the base DN (Dis­tinguished name) must be entered under the form “dc=company, dc=com”. For example, LDAP_BASE_DN=dc=acme,
dc=com for acme.com

LDAP server authentication

If authentication is set to “Y”, the username/password used for the LDAP authentication is the BluStar login user­name/password, overriding any authentication parameter set in the Server parameter. If it is set to “N”, the user­name/password, embedded in the Server parameter will be used.

41-001391-00 Rev 03 – 04.2012 6-4

BluStar Device Status

Advanced LDAP Settings

When configuring an LDAP directory the option is available to customize the directory using the advanced parameters
listed below. These advanced parameters are available for both active and non-active directories.

Note:

Advanced LDAP settings are optional and are not required for configuring the BluStar 8000i to use a LDAP server for
reading directories over an IP network.

Parameter Description

LDAP name title attribute list Specifies the LDAP name title (e.g. Mr.) for the attribute list. If this parameter contains more than one value, only

LDAP first name attribute list Specifies the LDAP first name (e.g. John) for the attribute list. If this parameter contains more than one value,

LDAP last name attribute list Specifies the LDAP last name (e.g. Doe) for the attribute list. If this parameter contains more than one value,

LDAP middle name attribute list Specifies the LDAP middle name (e.g. Allen) for the attribute list. If this parameter contains more than one

LDAP name suffix attribute Specifies the LDAP name suffix (e.g. Ph.D) for the attribute list. If this parameter contains more than one value,

LDAP company attribute list Specifies the LDAP company name (e.g. Aastra) for the attribute list. If this parameter contains more than one

LDAP job title attribute list Specifies the LDAP job title (e.g. Vice President) for the attribute list. If this parameter contains more than one

LDAP business street attribute list Specifies the LDAP business street (e.g. Snow Blvd.) for the attribute list. If this parameter contains more than

LDAP business city attribute list Specifies the LDAP business city (e.g. Concord) for the attribute list. If this parameter contains more than one

LDAP business state attribute list Specifies the LDAP business state (e.g. Ontario) for the attribute list. If this parameter contains more than one

LDAP business postal code attribute
list

LDAP business country attribute list Specifies the LDAP business country (e.g. Canada) for the attribute list. If this parameter c ont ai ns m or e th an on e

LDAP home street attribute list Specifies the LDAP home street (e.g. Internet Blvd.) for the attribute list. If this parameter contains more than

LDAP home city attribute list Specifies the LDAP home city (e.g. Frisco) for the attribute list. If this parameter contains more than one value,

LDAP home state attribute list Specifies the LDAP home state (e.g. Texas) for the attribute list. If this parameter contains more than one value,

the first matching value will be selected in the record.
For example, Setting_LDAP name title attribute list=title

only the first matching value will be selected in the record.
For example, Setting_LDAP first name attribute list=fname

only the first matching value will be selected in the record.
For example, Setting_LDAP last name attribute list=name

value, only the first matching value will be selected in the record.
For example, Setting_LDAP middle name attribute list=mname

only the first matching value will be picked in the record.
For example, Setting_LDAP name suffix attribute=suffix

value, only the first matching value will be selected in the record.
For example, Setting_LDAP company attribute list=organization

value, only the first matching value will be selected in the record.
For example, Setting_LDAP job title attribute list=jtitle

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP business street attribute list=waddress

value, only the first matching value will be selected in the record.
For example, Setting_LDAP business city attribute list=wcity

value, only the first matching value will be selected in the record.
For example, Setting_LDAP business state attribute list= wstate

Specifies the LDAP business postal code (e.g. L4K 4N9) for the attribute list. If this parameter contains more than
one value, only the first matching value will be selected in the record.

For example, Setting_LDAP business postal code attribute list=bcode

value, only the first matching value will be selected in the record.
For example, Setting_LDAP business country attribute list=bcountry

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP home street attribute list=hstreet

only the first matching value will be selected in the record.
For example, Setting_LDAP home city attribute list=hcity

only the first matching value will be selected in the record.
For example, Setting_LDAP home state attribute list=hstate

6-5 41-001391-00 Rev 03 – 04.2012

BluStar Device Status

Parameter Description

LDAP home postal code attribute list Specifies the LDAP home postal code (e.g. 75034) for the attribute list. If this parameter c ont ain s mo re t han one

LDAP home country attribute list Specifies the LDAP home country (e.g. U.S.A) for the attribute list. If this parameter contains more than one

LDAP business phone 1 attribute list Specifies the LDAP business phone 1 (e.g. 1-905-760-4200) for the attribute list. If this parameter contains more

LDAP business phone 2 attribute list Specifies the LDAP business phone 2 (e.g. 1-905-760-4201) for the attribute list. If this parameter contains more

LDAP home phone 1 attribute list Specifies the LDAP home phone 1 (e.g. 1-416-468-3266) for the attribute list. If this parameter contains more

LDAP home phone 2 attribute list Specifies the LDAP home phone 2 (e.g. 1-416-468-3267) for the attribute list. If this parameter contains more

LDAP mobile phone attribute list Specifies the LDAP mobile phone (e.g. 1-416-468-3268) for the attribute list. If this parameter contains more

LDAP other phone attribute list Specifies the LDAP other phone (e.g. 1-416-468-3269) for the attribute list. If this parameter contains more than

LDAP business fax attribute list Specifies the LDAP business fax (e.g. 1-905-760-4233) for the attribute list. If this parameter cont ains more t han

LDAP email 1 attribute list Specifies the LDAP email 1 (e.g. [e-mail]) for the attribute list. If this parameter contains more than

LDAP email 2 attribute list Specifies the LDAP email 2(e.g. [e-mail]) for the attribute list. If this parameter contains more than

LDAP email 3 attribute list Specifies the LDAP email 3 (e.g. [e-mail]) for the attribute list. If this parameter contains more than

LDAP web address attribute list Specifies the LDAP web address (e.g. www.aastra.com) for the attribute list. If this parameter contains more

LDAP cn attribute Used when both the first and last name of a record are empty.

LDAP dn attribute Used to perform the search request for the detailed view of an LDAP contact.

LDAP search filter Used to set search filters. This parameter format must follow RFC 4515, for example (sn=%). This parameter

LDAP search scope Used to set the search scope. A "base" search is performed only on the baseDN, a "onelevel" search is per-

LDAP search timeout Used to set the request timeout for LDAP requests. A range of 1 to 120 is applicable.

value, only the first matching value will be selected in the record.
For example, Setting_LDAP home postal code attribute list=hcode

value, only the first matching value will be selected in the record.
For example, Setting_LDAP home country attribute list=hcountry

than one value, only the first matching value will be selected in the record.
For example, Setting_LDAP business phone 1 attribute list=wphone1

than one value, only the first matching value will be selected in the record.
For example, Setting_LDAP business phone 2 attribute list=wphone2

than one value, only the first matching value will be selected in the record.
For example, Setting_LDAP home phone 1 attribute list=hphone1

than one value, only the first matching value will be selected in the record.
For example, Setting_LDAP home phone 2 attribute list=hphone2

than one value, only the first matching value will be selected in the record.
For example, Setting_LDAP mobile phone attribute list=cell

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP other phone attribute list=otherphone

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP business fax attribute list=fax

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP email 1 attribute list=email1

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP email 2 attribute list=email2

one value, only the first matching value will be selected in the record.
For example, Setting_LDAP email 3 attribute list=email3

than one value, only the first matching value will be selected in the record.
For example, Setting_LDAP web address attribute list=web

For example, Setting_LDAP cn attribute=display

For example, Setting_LDAP dn attribute=customDN

must include a '%' character at the place where it will be replaced by a*, b*, etc...
For example, Setting_LDAP search filter=(&(sn=%)(number=*))

formed on the baseDN and the first sublevel, and a "subtree" search is performed on the whole tree under the
base DN.

For example, Setting_LDAP search scope=onelevel

For example, Setting_LDAP search timeout=30

41-001391-00 Rev 03 – 04.2012 6-6

BluStar Device Status

Parameter Description

LDAP network timeout Used to set the network timeout for LDAP requests. A range of 1 to 120 is applicable.

For example, Setting_LDAP network timeout=50

LDAP initial download delay Used to set the LDAP initial download delay. Setting a value of 0 does not introduce any delay and the initial

To enter advanced parameters, log in to the BAS Web UI and navigate to the BluStar Devices :: BluStar Device Status
page. Select the applicable BluStar terminal device and enter the appropriate parameters in the Other Settings section
under the Own field.

download is performed synchronously during the login process. With all other values, the download is per­formed asynchronously, delayed by the value amount (in seconds) after the login process. A range of 0 to 120
is applicable.

For example, Setting_LDAP initial download delay=60

Login Banners

Specify pre- and post-login banner text.

Miscellaneous BluStar Terminal Settings

Maximum Video Bandwidth Limit

This setting limits the video bandwidth for the terminal to the selected value (either 6000, 5000, 1500, 768, 384, or
128 kilobits per second).

Enable H264 VBR Mode

Enables or diables H.264 Variable Bit Rate (VBR) mode.

Maximum videoShare Bandwidth Limit

This setting limits the videoShare bandwidth for the terminal to the selected value (either 3000, 1500, 768, 384, 128
kilobits per second).

Maximum Thumbnail Video Bandwidth Limit

This setting limits the thumbnail video bandwidth for the terminal to the selected value (either 256, 128, 64, 16, 8
kilobits per second).

Preferred Audio Bandwidth Limit

Specifies the maximum audio bandwidth limit.

Maximum Collaboration docShare (Image) Bandwidth Limit

This setting limits the bandwidth for docShare images sent by the terminal to the selected value ( either 4000,
2000, 1000, or 500 kilobits per second).

Display Mouse Cursor

Displays the mouse cursor.

6-7 41-001391-00 Rev 03 – 04.2012

BluStar Device Status

Generic
Blue Image

Show Collaboration Messages

Use “NO” to hide docShare state messages.

Enable Auto Reprogramming of Collaboration Firmware

Not supported on BluStar terminals.

Image Server URI

The Picture ID feature on the BluStar 8000i shows a picture ID of a caller on the LCD for all of the following events:

– Incoming calls (matched to caller ID numbers)
– Outgoing calls (matched to dialed numbers)
– Directory entries
– Callers list entries
– Redial list entries

The pictures are stored in a centralized picture repository and are dynamically retrieved from the centralized server
for each call and then locally cached in the BluStar 8000i to reduce network traffic.

If there is no picture on the central server for the dialed number and/or caller ID number, and direc­tory, callers list, and/or redial list entry, the generic blue figure image is shown.

Pictures can be in either “png”, “gif ”, or “jpeg” formats, but must be named “.png”, up to 320 pixels wide
x 320 pixels tall, and in 24 bit color.

The pictures must be stored using the phone number (either numeric or SIP address) for the filename
(for example, 9995551234.png or [e-mail]).

The picture ID feature supports the use of FTP, HTTP, and HTTPS protocols when downloading pic­tures. The parameter format is the following: image server uri: protocol://[username]:[password]@server.[port]
For example:

– image server uri: http://mypictureserver.acme.com
– image server uri: ftp://mypictureserver.acme.com (anonymous ftp connection)
– image server uri: ftp://user:[e-mail] (ftp connectionusing “user” and “password” for

the credentials)

BluStar Terminal Audio Settings

Terminal Line In Gain

Adjusts the volume of the connected PC’s audio signal. Values are in dB. (Negative values decrease volume.)

Force Mono Output

Select Yes form the pull-down menu to disable stereo output.

Other Settings

Enter additional settings, one per line, in the format

name=value

The release notes accompanying BluStar Device software, or other documentation supplied with each BluStar
Device, specify the names for the available settings, and the acceptable values.

41-001391-00 Rev 03 – 04.2012 6-8

BluStar Device Groups

BluStar Device Groups

This page is the starting point for managing BluStar Device groups. By default, the server is configured with the groups
shown above. The All BluStar Devices group is the top-level parent group and contains settings that affect all BluStar
8000i devices unless overridden for a particular device or child group. The remaining groups are child groups to the All
BluStar Devices group. These control settings for all devices of a particular type. The default groups cannot be deleted or
renamed.

Notes:

• For additional information on managing group settings, refer to Understanding Group Settings on page 5-11.

• The device group settings listed below may differ depending on the software releases available on the BAS server.

To the right of each device group is a group of icons. Clicking on these allows the following operations to be performed:

Icon Description

Create New Device Group as Child of this Group

Rename this Group

Delete this Group

View Group Members

Edit Group Members

Change Member Priority

Edit Settings

6-9 41-001391-00 Rev 03 – 04.2012

BluStar Device Groups

Creating a Device Group

A Device Group is created as a “child” of a group. To create a new device group:

1. Click on the icon next to the parent of the new group.

2. On the resulting screen, type the name of the new group.

3. Click the Save button to complete the creation of the new group.

Renaming a Device Group

To rename a Device Group:

1. Click on the icon next to the group that is to be renamed.

2. A screen displays with a text entry box in which the current name of the device group appears. Type the new name

for the group in the box.

3. Click the Save button to save the group’s new name.

Deleting a Device Group

To delete a Device Group:

1. Click on the icon next to the group that is to be deleted. A confirmation screen displays to confirm the deletion.

The confirmation screen also displays any groups that are members of the group the user wants to delete.

2. Click the Delete Highlighted Group button to delete only the selected group. All members of the deleted group

now become members of the All Devices group.

3. Click Delete Highlighted Group and Sub Groups to delete the selected group as well as all of its members that are

groups.

Viewing Group Members

To view the members of a Device Group:

1. Click on the icon next to the group that is to be viewed.

2. The resulting Members panel lists the Direct Members of the group, as well as those groups that are Available for

Membership. This panel also lists the devices that are either Direct Members of the group, or that are Available
for Membership.

3. Click the Cancel button to return to the main BluStar Device Groups page.

Editing Group Members

To ed it Gro u p Membe rs:

1. Click on the icon next to the group whose members you want to manage.

2. The resulting Members panel allows the administrator to select multiple items from the Direct M embers and Avail-

able for Membership lists. The administrator can also move groups or devices from being Direct Members to being
Available for Membership by selecting them in the lists and using the [<<] and [>>] buttons.

3. When satisfied with the configuration click Save.

41-001391-00 Rev 03 – 04.2012 6-10

BluStar Device Groups

Changing Member Priority

To change the priority of the members of a group:

1. Click on the icon next to the group whose members’ priority you want to change.

Note:

This icon is disabled if the parent group has less that two child groups.

2. The resulting panel allows the administrator to change the priority of the group members in either of two ways.

• Click the up or down arrow buttons next to a group member to move that member up or down the priority list.

• Select the desired priority number from the pull- down list (1 being the highest priority). Upon selecting a number

from the list, the associated group member is immediately moved to that position in the listing, and the members
below it on the list have their priority numbers adjusted accordingly.

3. When satisfied with the configuration click Save.

Editing Settings

To edit the settings for a group, click on the icon next to the group whose settings you want to edit. The resulting
page contains panels of settings that are specific to the type of device group that has been selected. A detailed discus­sion of the settings for the top-level All BluStar Devices group settings may be found in the paragraphs below. Detailed
information on the settings for the various device categories may be found in BluStar Device Categories on page 6-13.
When satisfied with the settings click Save.

Note:

For a detailed explanation of how device group settings function between a parent group and child groups, please
refer to Understanding Group Settings on page 5-11.

All BluStar Devices Settings

The settings for this top-level group can be inherited by all other groups.

Software Upgrade Settings

Automatic upgrade start time

The time at which automatic upgrades will start, formatted as “YYYY-mm-dd hh:mm:ss”. Enter an hour, a time, or
both. For an upgrade to occur as soon as possible, enter ASAP in the same field.

The server can instruct a BluStar Device (or all BluStar Devices), to update software. This allows software updates to
be “pushed” to BluStar Devices by the BluStar Application Server.

Note:

Updating the software may require an hour or two to complete, as devices only check for software updates when they
are restarted, on login / logout, and approximately every hour.

Automatic upgrade window

Allows devices to pick a random upgrade time (in minutes) after the Automatic upgrade start time. This setting sets
the “window” of minutes.

Allow manual software upgrading

Specifies whether or not the software may be upgraded manually. The manual software upgrade allows upgrades
to be “pulled” by BluStar Devices from the BluStar Application Server.

Administrators or users can manually request that a BluStar Device update its software. Refer to the documentation
accompanying the BluStar Device for detailed instructions with regard to manual software upgrading.

6-11 41-001391-00 Rev 03 – 04.2012

BluStar Device Groups

Release to be installed

The software release to be installed by BluStar Devices can be selected from a drop-down list. The list is automatically
created from all the BluStar Device software releases which have been installed to the BluStar Application Server.

Note:

BluStar Device software releases are typically distributed as “rpm” or “tar” files. For instructions with regard to installing
software releases, see Download Software on page 6-17.

Security Settings

Allow local administrator login

If set to Yes, allows administrator (root) login to the device via the console.

Allow remote administrator login

If set to Yes, allows administrator (root) login to the device via SSH.

Administrator password

Sets the administrator password needed for both local and remote login.

Force reboot time

Reboot device at specified time. Format is yyyy-mm-dd hh:mm:ss (for ASAP use current date and time).

Locale Settings

Time Zone

Sets the Time Zone used by group members.

DiffServ or IP Type of Service Settings

IP TOS byte for audio

Specify the IP Type of Service (TOS) byte which should be used for audio packets in this field. Leaving the field empty
in per-device settings will instruct a device to use the globally specified parameter.

IP TOS byte for video

Specify the IP Type of Service (TOS) byte which should be used for video packets in this field. Leaving the field empty
in per-device settings will instruct a device to use the globally specified parameter.

IP TOS byte for low-res video

Specify the IP Type of Service (TOS) byte which should be used for low resolution video packets in this field. Leaving
the field empty in per-device settings will instruct a device to use the globally specified parameter.

Other Settings

Enter additional settings, one per line, in the format

name=value

The release notes accompanying BluStar Device software, or other documentation supplied with each BluStar Device,
specify the names for the available settings, and the acceptable values.

41-001391-00 Rev 03 – 04.2012 6-12

BluStar Device Categories

BluStar Device Categories

The Device Categories page allows you to modify the various device categories, create new ones, or remove old ones.
Each device category has two options:

Auto Add Accounts of this Type

Specifies whether or not new accounts of this type will automatically be added.

New Accounts should be Enabled

New accounts of this type can enabled or disabled by default.

6-13 41-001391-00 Rev 03 – 04.2012

Telephony Devices

Telephony Devices

This interface is used for the configuration and update of telephony (PBX) devices that are integrated with the BluStar sys-
tem. It is used to specify and set all parameters of the device, and define telephone lines which are to be assigned tele­phone numbers that will be allocated to the BluStar users in the BluStar user configuration section of the Web UI.

The update of telephony devices does not happen automatically, but has to be done either as a device is being saved or
after. When users are assigned lines (telephone numbers), updates occur automatically, so the administrator must make
sure the device is updated before changes or additions are made to telephone numbers in the BluStar User configuration
section of the Web UI.

Telephony Device Configuration

The Telephony Device Configuration page lists all the configured (but not necessarily updated) telephony devices known
by the BluStar Application Server. In this section of the Web UI you can add, delete, or edit any telephony device.

Note:

The administrator will be asked to confirm all device deletions to prevent accidental loss of information.

Device Names

The descriptive name of the device, useful for telling apart similar type devices.

Device Type

Telephony device type. The type indicates to the telephony back-end how to update (program) the device, as well as
the number of lines available per device.

IP Address

The IP address of the telephony device, used for the update (programming) of the device and the routing of calls.

User / Password

The user name and password needed to be able to update the device.

Note:

User name and password are not SIP-related.

41-001391-00 Rev 03 – 04.2012 6-14

Telephony Devices

Telephony Device Line Allocation

Device Line Allocation allows an administrator to define telephone lines and allocate telephone numbers for later
assignment to BluStar users (see User Identity on page 5-3).

Start Line / End Line

These fields are the line number range (inclusive) that are to be allocated by the server. These line numbers will
later be added to users, and these users will then be automatically assigned a line on the telephony device. Line
ranges are subject to the type of device specified on the Telephony Device Configuration on page 6-14.

Note:

The saving of ranges happen incrementally from top to bottom, making it possible to specify lines 1-32 to be in a range
for the first item, and the second item specifying a different number for line 15-15 (line 15). The examples below will
yield the same result.

Device Line Configuration Example 1:

Stat Line End Line Start Phone Number

1 32 011 234 0001

15 15 011 111 1111

Device Line Configuration Example 2:

Stat Line End Line Start Phone Number

1 14 011 234 0001

15 15 011 111 1111

16 32 011 234 0016

Start Phone Number

The start phone number for the range specified above. It will increment by one on the extension part for every suc­cessive line in the range.

Note:

The last four digits need to be numeric so the server can correctly determine and process line ranges.

Enabled

Whether or not the device line is enabled

User Line Information

This page shows information related to the lines that are assigned to specific users and all remaining unassigned lines, or
pool lines.

User Assigned Lines (Incoming and Outgoing)

Change any user’s assigned line (phone number) by editing that user under User :: User Accounts (see User Iden-

tity on page 5-3).

Note:

Assigning a number that does not exist in the drop-down menu will assign an alias to that user. This number will only
be usable in the SIP domain—it does not belong to any real telephony device—and will not be listed under “user
assigned lines (incoming and outgoing)”.

Pooled Outgoing LInes

Lines that have been defined, but are not currently assigned to any user. Any user without an assigned line that
makes a call from the SIP domain to the PBX network will be routed out using one of the pooled lines.

6-15 41-001391-00 Rev 03 – 04.2012

Telephony Devices

Filtering User Line Information

Filter on may be set to one of three options:

Display Name

Not applicable to “pooled outgoing lines” and will therefore not filter that section.

Username

Not applicable to “pooled outgoing lines” and will therefore not filter that section.

Phone number

Affects both user assigned lines (incoming and outgoing) and pooled outgoing lines.

Other filter fields:

Starting With

Filters the list(s) based on the characters entered in this field and the option specified in “filter on” above.

Limit

Limits the number of lines shown in both fields to the specified number.

Telephony Device

Allows you to show only the lines of the checked device(s). All configured devices are shown with check boxes. Check
the devices you want to view and uncheck [All]. If no devices are selected, the page will refresh with [All] selected.

Press any of the three refresh buttons on the page to filter the lines based on the filter information above.

Errors and Diagnostics

When saving the configuration of a device, the “Device Settings” section is saved first, with validation done on the IP
address field. If this fails then nothing is saved. After the device details are saved to the database, the device lines are saved
one at a time in the order in which they are listed. If a validation error occurs when saving a line range, then saving stops at
that point and an error is displayed. Note that all prior range elements in the list have been successfully saved to the data­base, but the errors need to be corrected and re-submitted for it to be saved correctly.

When updating (programming) devices, errors are usually due to the device IP address not being configured correctly on
the telephony device itself, or there being some network routing/firewall problem. Also make sure that the correct Device
Type has been specified. If more advanced diagnostic information is required, view the BluStar system logs for error mes­sages generated by the ASDF or TELE BluStar modules. A failed update does not imply that the configuration has not been
saved, since this usually only happens after the save of the configuration to the database.

41-001391-00 Rev 03 – 04.2012 6-16

Download Software

Download Software

The Download Software page allows you to install terminal software builds onto the server. Once a terminal software
build is on the server, you can configure specific BluStar 8000i devices pointing to the server to upgrade/install the soft­ware (see Software Upgrade Settings on page 6-2 for BluStar 8000i Terminal settings, and Software Upgrade Settings on

page 6-11 for BluStar 8000i Device Group settings). Once software has been installed on the server, the information no

longer appears on this page. Administrators can view software currently installed on server on the View Software page.

Administrators can View, Edit, or Delete any terminal software builds that have been downloaded to the server (and not
yet installed on specified BluStar 8000i devices. When using the View, Edit, or Delete buttons in the list screen, the
action will be performed on all marked items.

WAR NIN G!
The filenames of the terminal software builds provided by Aastra should be left intact. Renaming the

terminal software build files and subsequently downloading/installing the software onto the server will
cause errors to occur.

6-17 41-001391-00 Rev 03 – 04.2012

Download Software

Adding Software to the Server

To add terminal software to the server:

1. Click Add. The following page appears:

1. Type in the file name.
Note:

The file type must be either a .rpm or .tar.

2. Type in the FTP server (e.g., “generic.hostname.com” or “100.200.1.2/ftppath”), user name, and password (if applicable).

3. Click Save.

You will see the following page appear.

4. Click Refresh to update the download status.

If the file name and FTP server credentials are correct, you will see the status go from Waiting to Download > File
Downloading > Download Complete.

If there is an error with the file name or the FTP server credentials, an error message will appear under the Download
Status.

5. Once the download is complete, select the terminal software build and click Install Software.

You will see the following message: “Are you sure you want to install the selected software files?”

6. Click Install Software again.

Your page no longer shows the software build

41-001391-00 Rev 03 – 04.2012 6-18

View Software

View Software

The View Software page displays all of the terminal software builds that are currently installed on the server.

6-19 41-001391-00 Rev 03 – 04.2012

Chapter 7 Services

This section of the Web UI provides the ability to configure high-level functions of the Application Server not accessible
from the command-line interface. The following sections provide details for these functions:

• Licensing

• SIP Service Configuration

• Routing Rules

• Presence Agent

• User Session Log

• Off-Server Backup

• Clustering

41-001391-00 Rev 03 – 04.2012 7-1

Licensing

Licensing

The Licensing page provides the means to Install Licenses for various BluStar 8000i devices; and to View Licenses’ sta­tus information for installed licenses.

The number of connected users is limited by the number of licenses for a BluStar Application Server. There can be up to
1000 users connected to a singular BAS at any given time.

Note:

A five (5) user license is enabled by default to provide functionality during installation and configuration. This prohibits
more than five devices from participating in the BluStar network until valid licenses are installed.

Install Licenses

The Install Licenses page allows the administrator to install licenses for the BluStar Application Servers (BAS)

To install a license, perform the following procedure:

1. Send an email containing the following information to [e-mail]:
a) Company name & UCID (if applicable)
b) Contact name
c) Contact phone number
d) Contact email address
e) MAC address of server
f) License serial number,
g) License type.

2. Your license file will be emailed back to you automatically.

3. Download the license file to your system.

4. Log into BluStar Application Server Web UI and navigate to the Services :: Licensing :: Install Licensing Page.

7-2 41-001391-00 Rev 03 – 04.2012

5. Click the Browse... button in the License to Install panel. In the resulting dialogue box, navigate to the license file

that you received from the email, select it, then click on the Upload License button to install the license on the server.

6. When the upload has completed, the License to Install panel refreshes and displays the uploaded license file name

and license details. Click on the Install License button to complete the license installation. Click Cancel to abort the
license installation.

Licensing

View Licenses

The View Licenses page lists the various product licenses installed on the system. The listing indicates the product, major
and minor version numbers, number of users supported by the license, and the status of the license (Valid, Invalid, Expired,
etc.).

Clicking the [>>] button next to a given product name displays detailed information for that license.

Note:

The BluStar Device Status page also contains a column that indicates the license status for each licensed device.

41-001391-00 Rev 03 – 04.2012 7-3

SIP Service Configuration

SIP Service Configuration

The SIP Service Configuration page, shown in the image below, provides the following options:

Administrative Domain Names

Calls with Request-URIs that exactly match the listed hostname(s) will be treated as local calls.

Administrative Domain IPs

Calls with Request-URIs that exactly match the listed IP address(es) will be treated as local calls.

SIP message logging

When checked, the Application Server enables logging of SIP messages.

Perform case insensitive SIP username searches

When checked, SIP username searches are case insensitive.

Preferred Protocol by Domain

The preferred protocol by domain is automatically updated when a call has been established. Domains can be
added manually to speed up call establishment if the supported protocol is known ahead of time.

Fallback Protocol Order

The fallback protocol order is for the BAS to reach out to other domains (like inter-domain calling) by trying those
protocols by the order listed.

7-4 41-001391-00 Rev 03 – 04.2012

Routing Rules

Routing Rules

The routing rules menu allows you to configure the server’s connections with other devices, manage bandwidth between
networks, and customize call routing.

There are two types of rules that are configured on the Routing Rules page.

• General SIP routing rules

These rules match “sip:” URL patterns.

• Telephony Specific routing rules

These rules match “tel:” or “sip:…;user=phone” URL patterns.

Note:

BluStar 8000i terminals and most other devices send plain “sip:” URLs, therefore normally use general rules.

User Interface

To add a new rule, enter the text to be matched, and the replacement text, then select Add.

To modify a rule, change the rule text, and select Save.

Note:

The system only accepts changes to one rule at a time. Modify a rule and select [Save] before starting to edit another
rule.

Because rules are order sensitive, buttons have been provided to move rules up or down. Specific rules should normally
proceed general rules.

Regular Expression Tester

A facility has been provided to test the configured set of rules. To test a set of rules, enter a test case SIP URL in the form
that it would be received by the BluStar Server. For example, enter:

sip:447021239876@169.144.50.48

The system will highlight the matching rules for the test case. It will also display the replacement text generated by each
matching rule.

41-001391-00 Rev 03 – 04.2012 7-5

Routing Rules

Regular Expression Rules

Regular expression rules perform pattern matching on SIP Request-URIs and can then create a new Request-URI based
on parts of the original Request-URI. This can be used for example to rewrite calls to telephone numbers to include pre­fixes for outside lines, area code or calling cards as appropriate. A brief summary of regular expression syntax is given
below.

• Characters not listed below as special characters match themselves.

• Special characters:

. Matches any character
[...] Character class: matches range(s) and/or list(s) of characters (e.g. [0-9a-zA-Z] matches a digit or letter)
[^...] Inverted class: matches all except a member of a class, (e.g., [^a-zA-Z] matches anything except a letter)
? Preceding item is optional (may occur zero times or once)
+ One or more of preceding item
* Zero or more of preceding item
{m,n} Between m and n occurrences (inclusive) of preceding item
^ Match the beginning of the URL
$ Match the end of the URL
() Used for grouping and for back-referencing
\ Quote the next special character, e.g. when trying to match a character such as a + sign.

• Back-references in replacement URL:

$1 refers to text matched by first set of () , $2 refers to second () , etc.

Examples

^sip:([0-9]+)@

Matches start of URL, “sip:”, one or more digits, and an “ @ ” sign. The administrator could ask the system to replace
this with e.g., “ sip:$1@1.2.3.4 ”- $1 will be what was matched by first set of () , i.e., the part between “ sip: ”and “ @ ”.
This would send all URLs containing digits to the SIP device at IP address 1.2.3.4.

^sip:([2-8][0-9]{9,9})@([a-zA-Z0-9\.]+)

Matches the “sip:” at the start of the URL, a ten digit number that starts with a digit between “2” and “8”, and an “@”
sign.

The replacement text “sip:91$1@$2;user=phone” will prepend the original number with a 9 (for an outside line),
and a “1” (to make a long distance call). The URL is converted into a telephony URL.

^(sip:)?\+([0-9]+)@

Matches start of URL, optionally “sip:”, a literal “+” sign (“+” is a special character so we need a “\” before it), one or
more digits, “@”.

The administrator could specify as replacement text e.g., “sip:9011$2@1.2.3.4:5060”. The effect is to replace the “+
country area number” format with the format appropriate for a US company (9 to obtain an outside line; 011 is
international prefix).

7-6 41-001391-00 Rev 03 – 04.2012