1 / 8

Device Management on the MX250

Device Management on the MX250. A brief introduction. Managed vs. Unmanaged. Phones and soft phones are devices Managed devices added to the MX by an administrator configuration can be controlled from MX software can be updated from MX Unmanaged devices

Télécharger la présentation

Device Management on the MX250

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Device Management on the MX250 A brief introduction

  2. Managed vs. Unmanaged • Phones and soft phones are devices • Managed devices • added to the MX by an administrator • configuration can be controlled from MX • software can be updated from MX • Unmanaged devices • registered to a user’s SIP address or extension • not added by an administrator • configuration not controlled by MX • software not updated by MX Device Management on the MX250

  3. Managed Devices — Mechanism • Administrator adds device (phone) in Admin UI • Admin UI automatically creates a configuration file • file is identified by MAC address of device • File is saved on a TFTP server • Device obtains its address using DHCP • DHCP server provides address of TFTP server • Device reads configuration file on boot up • downloads from TFTP server Device Management on the MX250

  4. Deployment Possibilities • DHCP server internal or external to MX250 • MX250 can supply IP addresses for PCs and phones • TFTP server internal or external to the MX250 • holds configuration files and software Device Management on the MX250

  5. Internal DHCP and TFTP Servers Administrator selects TFTP and DHCP servers to be internal to MX250 MX250 1) DHCP request 2) DHCP response (specifies address of TFTP server) 1 Switch 5 3 3) TFTP request 4) TFTP response (retrieve configuration file) 2 4 5) SIP Registration (identifies device to MX250) Device Management on the MX250

  6. 2) MX250 sends configuration files to external TFTP server 3) DHCP request 4) DHCP response (specifies address of TFTP server) 2 5 5) TFTP request 7 6 6) TFTP response (configuration file) 3 4 7) SIP registration External DHCP and TFTP Servers 1) Administrator selects TFTP and DHCP servers to be external to MX250 MX250 TFTP Server Switch DHCP Server Device Management on the MX250

  7. Managing Devices at Remote Site • Remote site may have its own DHCP server • Site may also have a TFTP server • DHCP server will provide invalid TFTP address • phone at remote site would not get its configuration • phone would be unmanaged by Admin UI • Overcome by using TFTP override • Fix address of TFTP server on phone • ignores address provided by DHCP server Device Management on the MX250

  8. Each site has its own TFTP server Two sites with unique IP address ranges Full IP connectivity between sites using routers 1 2 3 4 5 6 7 8 9 1 0 1 1 1 2 C O N S O L E C O L - 1 2 3 4 5 6 7 8 9 1 0 1 1 1 2 C O N S O L E H S 1 H S 2 O K 1 O K 2 P S C O L - A C T - H S 1 H S 2 O K 1 O K 2 P S A C T - S T A - S T A - TFTP Override MX250 TFTP Server DHCP Server 5 1 Switch Switch 4 2 Router Router 3 1) DHCP request ZIP 2 ZIP 4x4 2) DHCP response (specifies TFTP server) ZIP 4x4 ZIP 2 TFTP Server DHCP Server Remote site 3) TFTP request (uses server specified by admin) Main site 4) TFTP response (configuration file) 5) SIP registration Phone at remote site uses TFTP override • phone ignores address of TFTP server received by DHCP • uses fixed IP address of TFTP server set by Admin UI Device Management on the MX250

More Related