[Index]

Model: relation/PRS_MultiVendorPhone_REL

VOSS Phone

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

From the Subscriber Management > VOSS Phones menu item (default), phones are associated with the VOSS Phone Server (see: VOSS Phone Server Overview and Managing VOSS Phone Servers)

These parameters are used to determine the template to use when creating the phone configuration file on the TFTP server.

Adding Phone Types

New phone types (brands) can be created by creating a new phone type definition. This phone type defines the behavior of the Admin Portal when adding a phone, and defines sample configuration files and configuration templates to apply to this configuration file.

The sample file provides the layout of the phone configuration file but does not have values specific to each phone. Values such as the telephone number to apply are populated with a default value.

The configuration template allows access to any parameter in the sample file, and can be used to set the correct value for each phone, such as setting the telephone number. VOSS Automate has sample files and configuration for the SNOM D120 and D717 phones. This provides full configuration for these phones so that a new "out of the box" phone can be connected to the network and reach an operational state with no user intervention.

Adding a new phone type requires firstly creating a sample file. Many SNOM phones allow the export of the configuration which has been previously created through the phone web interface. This file can be used as the sample file, although values should be changed to make the file anonymous prior to uploading as a sample file. Once loaded, a configuration template can be created or cloned from the existing templates. This will allow modification of any value in the sample file, setting a value suitable for each phone. Using this technique, new phones types may be evaluated and added to VOSS4UC without the need for software updates or patches.

Model Details: relation/PRS_MultiVendorPhone_REL

Title Description Details
Vendor *
  • Field Name: phoneVendor
  • Type: String
Model *
  • Field Name: phoneModel
  • Type: String
Phone MAC Address *
  • Field Name: mac
  • Type: String
  • Pattern: ^[A-Fa-f0-9]{12,12}$
Config File Name *
  • Field Name: filename
  • Type: String
Number of Lines *
  • Field Name: lineCount
  • Type: String
typeDeploymentMode
  • Field Name: gui_typeDeploymentMode
  • Type: String
Reject anonymous calls
  • Field Name: acr
  • Type: Boolean
Display ACR
  • Field Name: gui_acr
  • Type: String
Display DisplayName
  • Field Name: gui_DisplayName
  • Type: String
Display BusyTrigger
  • Field Name: gui_BusyTrigger
  • Type: String
Display MaxCalls
  • Field Name: gui_MaxCalls
  • Type: String
Group
  • Field Name: groupName
  • Type: String
Inventory Filter INI Inventory filter Default: lines_unused_only_local
  • Field Name: line_filter1
  • Type: String
  • Default: lines_unused_only_local
  • Choices: ["Default", "Show Unused Numbers with Associated E164's (Site Only)", "Show Unused Numbers with Associated E164's"]
Number
  • Field Name: line1Name
  • Type: String
Display Name
  • Field Name: line1DisplayName
  • Type: String
Busy Trigger
  • Field Name: line1BusyTrigger
  • Type: String
Max Calls
  • Field Name: line1MaxCalls
  • Type: String
Class Of Service
  • Field Name: line1Cos
  • Type: String
Inventory Filter INI Inventory filter Default: lines_unused_only_local
  • Field Name: line_filter2
  • Type: String
  • Default: lines_unused_only_local
  • Choices: ["Default", "Show Unused Numbers with Associated E164's (Site Only)", "Show Unused Numbers with Associated E164's"]
Number
  • Field Name: line2Name
  • Type: String
Display Name
  • Field Name: line2DisplayName
  • Type: String
Busy Trigger
  • Field Name: line2BusyTrigger
  • Type: String
Max Calls
  • Field Name: line2MaxCalls
  • Type: String
Class Of Service
  • Field Name: line2Cos
  • Type: String
Noinstance
  • Field Name: noinstance.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: noinstance.[n].name
  • Type: String
  • MaxLength: 1024