======= Devices ======= Devices allow you to manage RingRx connected telephones and other endpoints. .. contents:: :local: Supported Devices ----------------- ``Polycom VVX Obi Edition`` =========================== :VVX 150: `Polycom VVX 150 `_ :VVX 250: `Polycom VVX 250 `_ :VVX 250: `Polycom VVX 350 `_ :VVX 450: `Polycom VVX 450 `_ :VVX D230: `Polycom VVX D230 `_ ``ObiHai 1000/2000 series`` =========================== :Obi1000 series: `Obihai `_ :Obi2182: `Polycom 2182 `_ ``Polycom Soundstation`` =========================== :Soundstation IP5000 series: `IP5000 `_ :Soundstation IP6000 series: `IP6000 `_ ``Poly Trio Conference phones`` ================================== :Poly Trio series: `Trio `_ ``Yealink W52/W56`` ========================== :W56P: `Yealink W56 `_ :W52P: `Yealink W52 `_ Device Parameters ----------------- ``Name`` ======== This is just a description of the device. ``Device Type`` =============== What type of device is this we are configuring. IF this is not correct it will likely not work. ``Signaling`` =============== How the device should communicate with RingRx In most cases this will be TLS ``Mac Address`` ================ This is the unique MAC address of the phone. ``User`` =============== This user account will be bound as the phones primary account. The primary account will: * Control the MWI status for the phone * Voicemail keys will access this accounts mailbox * Will be the source account for all other feature keys. ``Display Name`` ================ This is display text that will appear on the phone for the phones primary line Device Bindings ----------------- Bindings are filled by their type from top to bottom. You can drag and drop bindings to re-order them on the phone. For example if you add 3 left line keys and 1 line key you will get: * Line key 1, 2 and 3 on the left populated * Line key 1 on the right populated Binding Types ============= Not all phones will support all types. :Line Key: This indicates a key on the right side of the display :Left Line Key: Indicated a key on the left side of the display :Feature Key: Keys below or not near the display Binding Behaviors ================= ``Empty`` =================== This will make a key slot empty. Useful if you wish to remove config or leave aesthetic gaps between groups of keys Empty keys take no arguments ``Line Appearance`` =================== This binds another line to the phone. You can make and receive calls from this just like the primary. Line appearances take the following arguments: :Binding Display: Any alternate text you want on this key. If none, the name from the binding user is used :Binding User: The user account to be bound. ``Busy Lamp Field`` =================== A BLF key is bound to a different user. When that user: :Not on a call: The key is dark. Pressing it will speed dial that user :On a call: The key will be solid. Pressing it will speed dial that user :Has An inbound call is ringing: key will be blinking. Pressing it will execute a directed call pickup against their extension. This is described `here `__ BLF Keys take the following arguments: :Binding Display: Any alternate text you want on this key. If none, the name from the binding user is used :Binding User: The user account to be monitored ``Speed Dial`` =================== This makes a single key press perform a dial sequence Speed dial keys take the following arguments :Binding Display: Any alternate text you want on this key. If none, the name from the binding user is used :Binding Argument: Anything you want dialed. If a user is also selected, the argument is pre-pended to the user :Binding user: If you want to map a user directly to a speed dial. For example A prefix of \*99 with a user of jsmith will dial \*99jsmith executing the Intercom feature against the user jsmith ``Park Orbit`` =================== This binds a park orbit to a key. Call parking is described `here `__ When the park orbit: :Has no calls: The key is dark. Pressing it will transfer the active call to that orbit :Has a call: The key will be lit. Pressing it will retrieve the call from the orbit Park orbit keys take the following arguments :Binding Display: Any alternate text you want on this key. If none, the name from the binding user is used :Binding ParkingLot: Which park orbit we should monitor. ``Mailbox`` =================== This will bind a 3rd party mailbox to your phone key. When the mailbox: :Has no messages: The key is dark. :Has messages: The key will be lit. Pressing this key will check this mailbox (PIN still required) Mailbox keys take the following arguments :Binding Mailbox: Which mailbox we should monitor ``Page Group`` =================== This will create a Push-To-Talk group on that key. Push-To-Talk groups will broadcast from all other devices on the same LAN sharing the same group. * Push to talk uses Multicast so announcements will not leave the local network and will not appear as CDR's, and will not leave the network * You can silence a group by tapping the key (this will un-join the phone) * To speak press and hold the key :Binding Display: Any label display text (will default to pge group and the id) :Binding Argument: Which page group (1-10), if not specified its page group 1 .. note:: Use Push-To-Talk to create ad-hoc PA systems using speaker phones around the facility