{"id":792,"date":"2012-10-19T01:00:00","date_gmt":"2012-10-18T23:00:00","guid":{"rendered":"https:\/\/www.fussylogic.co.uk\/blog\/?p=792"},"modified":"2012-10-19T10:59:27","modified_gmt":"2012-10-19T09:59:27","slug":"asterisk-and-cisco-7940","status":"publish","type":"post","link":"https:\/\/www.fussylogic.co.uk\/blog\/?p=792","title":{"rendered":"Asterisk and Cisco 7940"},"content":{"rendered":"

There are a number of guides out on the Internet for getting Cisco phones working with Asterisk. I didn\u00e2\u20ac\u2122t particularly find any of them 100% thorough. This then is my guide, documenting the moment I ordered the phone to the moment I made a call on it.<\/p>\n

I bought a Cisco 7940 phone from eBay. It was a brand new boxed version. I\u00e2\u20ac\u2122ve changed the MAC to 00:18:b9:ff:ff:ff<\/code> in this document in case the real MAC could be used by an attacker (paranoia is good for security).<\/p>\n

I\u00e2\u20ac\u2122d suggest beginning by running Wireshark and set it to filter on the phone\u00e2\u20ac\u2122s MAC so that you can follow what it\u00e2\u20ac\u2122s doing more easily (I used 'ether host xx:xx:xx:xx:xx or broadcast'<\/code>). Leave that running for the whole of this guide.<\/p>\n

Power Supply<\/h2>\n

The main difference between the 79×0 and 79×1 phones from Cisco is that the \u00e2\u20ac\u02dc0\u00e2\u20ac\u2122 are pre-standard power-over-ethernet, so unless you want to buy a Cisco power over ethernet supply, you\u00e2\u20ac\u2122ll probably need a power block for the 79×0 phones. They\u00e2\u20ac\u2122re 48V with a slightly unusual connector.<\/p>\n

Prerequistes<\/h2>\n

I\u00e2\u20ac\u2122m going to assume you\u00e2\u20ac\u2122ve already got a DHCP server on your network, and I\u00e2\u20ac\u2122m assuming you\u00e2\u20ac\u2122re already running a working Asterisk system.<\/p>\n

First Boot<\/h2>\n

Here\u00e2\u20ac\u2122s the sequence:<\/p>\n

    \n
  • Green headset light<\/li>\n
  • Red Mute light<\/li>\n
  • Green speaker light<\/li>\n
  • \u00e2\u20ac\u0153Cisco Systems, Inc. Copyright 2000\u00e2\u20ac\u009d<\/li>\n
  • \u00e2\u20ac\u0153Configuring VLAN\u00e2\u20ac\u009d<\/li>\n
  • \u00e2\u20ac\u0153Configuring IP\u00e2\u20ac\u009d<\/li>\n
  • \u00e2\u20ac\u0153Configuring CM List\u00e2\u20ac\u009d<\/li>\n
  • \u00e2\u20ac\u0153TFTP Timeout\u00e2\u20ac\u009d<\/li>\n
  • \u00e2\u20ac\u0153Configuring IP\u00e2\u20ac\u009d<\/li>\n
  • \u00e2\u20ac\u00a6 repeat \u00e2\u20ac\u00a6<\/li>\n<\/ul>\n

    Here\u00e2\u20ac\u2122s the syslog for the \u00e2\u20ac\u0153Configuring IP\u00e2\u20ac\u009d period:<\/p>\n

    11:44:37 dhcpd: DHCPREQUEST for 10.10.202.71 from 00:18:b9:ff:ff:ff via eth0: ignored (not authoritative).\n11:44:41 dhcpd: DHCPREQUEST for 10.10.202.71 from 00:18:b9:ff:ff:ff via eth0: ignored (not authoritative).\n11:44:49 dhcpd: DHCPREQUEST for 10.10.202.71 from 00:18:b9:ff:ff:ff via eth0: ignored (not authoritative).\n11:45:05 dhcpd: DHCPREQUEST for 10.10.202.71 from 00:18:b9:ff:ff:ff via eth0: ignored (not authoritative).\n11:45:37 dhcpd: DHCPDISCOVER from 00:18:b9:ff:ff:ff via eth0\n11:45:37 dhcpd: DHCPOFFER on 192.168.1.12 to 00:18:b9:ff:ff:ff via eth0\n11:45:37 dhcpd: DHCPREQUEST for 192.168.1.12 (192.168.1.3) from 00:18:b9:ff:ff:ff via eth0\n11:45:37 dhcpd: DHCPACK on 192.168.1.12 to 00:18:b9:ff:ff:ff via eth0<\/code><\/pre>\n
    It\u00e2\u20ac\u2122s trying for one minute to get a preprogrammed address, 10.10.202.71, then it falls back to DHCPDISCOVER and gets a valid IP for my internal network, \u00e2\u20ac\u0153192.168.1.12\u00e2\u20ac\u009d. My suggestion is to configure your DHCP server to allocate a fixed address to the phone (at least for now).<\/p>\n
    Even though the phone is booting, you do have access to the settings page (the bottom right button on the cluster above the volume button). On that, you\u00e2\u20ac\u2122ll find menu options for<\/p>\n
      \n
    • Contrast<\/li>\n
    • Ring Type<\/li>\n
    • Network Configuration<\/li>\n
    • Status<\/li>\n<\/ul>\n
      Status->Firmware Versions<\/code> will show you a useful set of data you should note down. Here\u00e2\u20ac\u2122s what I saw.<\/p>\n
      App Load ID:\n  P0030301MFG2\nBoot Load ID:\n  PC0303010200\nVersion:\n  3.1(MF.G2)\nExpansion Module 1:\n\nExpansion Module 2:<\/code><\/pre>\n
      My network configuration page was locked, but it did show that 10.10.202.71<\/code> address.<\/p>\n
      On the top settings page there is also a \u00e2\u20ac\u02dcmore\u00e2\u20ac\u2122 option. Under which you\u00e2\u20ac\u2122ll get a \u00e2\u20ac\u0153factory\u00e2\u20ac\u009d option. It\u00e2\u20ac\u2122s not unreasonable to push that. It won\u00e2\u20ac\u2122t do much anyway.<\/p>\n
      TFTP<\/h2>\n
      The \u00e2\u20ac\u0153TFTP Timeout\u00e2\u20ac\u009d isn\u00e2\u20ac\u2122t a surprise as I\u00e2\u20ac\u2122ve not installed a TFTP server. Use whatever you like. I tried the Debian package, tftpd<\/code> first, but found it wasn\u00e2\u20ac\u2122t verbose enough in logs to help debugging. I settled on atftpd<\/code>. Debian defaults this to inetd mode, so you can configure it in \/etc\/inetd.conf<\/code>.<\/p>\n
      It defaulted to using \/srv\/tftp<\/code> as its root directory. Change this to whatever you\u00e2\u20ac\u2122d like (or just use this default).<\/p>\n
      Now we need to tell the DHCP server to tell the phone about our TFTP server. I did this by matching on MAC address:<\/p>\n
      host cisco7940 {\n    hardware ethernet 00:18:b9:ff:ff:ff;\n    fixed-address cisco7940.example.com;\n    option tftp-server-name "192.168.1.3";\n    next-server 192.168.1.3;\n}<\/code><\/pre>\n
      Obviously you should put your own TFTP server IP address in this section.<\/p>\n
      After you\u00e2\u20ac\u2122ve done this, your syslog will show you that the phone is requesting the following files via TFTP:<\/p>\n
      12:45:17 atftpd[1483]: Serving OS79XX.TXT to 192.168.1.12:52578\n12:45:17 atftpd[1483]: Serving SEP0018B9FFFFFF.cnf.xml to 192.168.1.12:52579\n12:45:17 atftpd[1483]: Serving XMLDefault.cnf.xml to 192.168.1.12:52580\n12:45:17 atftpd[1483]: Serving SEP0018B9FFFFFF.cnf to 192.168.1.12:52581\n12:45:17 atftpd[1483]: Serving SEPDefault.cnf to 192.168.1.12:52582<\/code><\/pre>\n
      They don\u00e2\u20ac\u2122t exist yet so the phone issues a TFTP error message.<\/p>\n
      Firmware<\/h2>\n
      You\u00e2\u20ac\u2122ll need to find yourself the appropriate firmware. Officially that firmware is only available from Cisco and is copyright. You therefore shouldn\u00e2\u20ac\u2122t go to Google and make any efforts at all to locate it.<\/p>\n
      The OS79XX.TXT<\/code> file on your TFTP server tells the phone which file it should TFTP-fetch to use as a firmware.<\/p>\n
      The suggested order of firmware installation is as follows (note, after version 5 the binaries are signed so you will only be able to upgrade to Cisco signed versions):<\/p>\n
        \n
      • Version 5: P0S3-05-3-00<\/li>\n
      • Version 8: P003-8-11-00<\/li>\n<\/ul>\n
        For each, you should edit the OS79XX.TXT<\/code> and fill in the name of the firmware binary without its extension. The phone will use that name to fetch from the TFTP server and will install it:<\/p>\n