Specifications

Maintaining the System Generating ShoreTel Client Provisioning file
17
ShoreTel Mobility Router Administration Guide 260
provisioning, the ShoreTel Mobility Client does not need to prompt users for information during
provisioning. If any of the field is missing or empty in the provisioning file, the Client prompts the user
for the missing information. Table 11 describes the fields of the ShoreTel Provisioning file.
Table 11: ShoreTel Provisioning File
States Description Description
silent_install If Yes, the ShoreTel Mobility Client does
not enforce user acknowledgement before
provisioning.
no
local_address This field is the local address of the
ShoreTel Mobility Router. This address
should be reachable by the client when it
is on the Enterprise Wi-Fi Network.
192.168.3.101
remote_address Remote Access IP address of the mobility
router. The client uses this address to
connect to the mobility router when the
user is not within the enterprise Wi-Fi
coverage area.
12.101.91.48
remote_udp_port Remote Access UDP Port for DTLS tunnel 443
remote_tcp_port Remote Access TCP Port for TLS tunnel 443
remote_provisioning If yes, the ShoreTel Mobility Client first
tries provisioning the user through the
remote access connection. If this value is
no, the Client first tries local provisioning
and if it cannot reach the mobility router, it
fallbacks to remote access provisioning.
no
user_id End User’s user ID user8057
full_name End User’s full name test user 8057
directory_num User’s Enterprise Extension 8057
enterprise_num User’s Enterprise Full Number 4089198011
cellular_num User’s Cellular Number 14089198057
authorized_userid If provisioning is performed by an admin
user, this field contains the user ID of the
admin user performing user provisioning.
admin
password For admin provisioning, this is the
Authorized admin user’s password. For
end user provisioning, this is end user’s
password.
12345
delete_on_complete If yes, the ShoreTel Mobility Client deletes
this file from client upon successful
provisioning. If no, the file is left behind
and can also be used for future
provisioning.
yes