Zultys Technologies 771 Vaqueros Avenue Sunnyvale CA USA Tel: Fax: Device Management on the MX250 A brief introduction

January 2004Device Management on the MX2502 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

January 2004Device Management on the MX2503 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

January 2004Device Management on the MX2504 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

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

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

January 2004Device Management on the MX2507 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

January 2004Device Management on the MX2508 Main site Remote site Router ZIP 2 ZIP 4x4 MX250 DHCP Server TFTP Server ZIP 2ZIP 4x4 Router TFTP Override Switch TFTP Server DHCP Server Switch 1) DHCP request 2) DHCP response (specifies TFTP server) 3) TFTP request (uses server specified by admin) 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 Two sites with unique IP address ranges Full IP connectivity between sites using routers Each site has its own TFTP server