Reply To: RE: Polycom firmware update

VitalPBX Community Support General Discussion Polycom firmware update Reply To: RE: Polycom firmware update

    CoryEakins
    Participant
    Up
    0
    Down

    I worked around the missing feature with a small hack.  This will also allow for overriding phone configurations to work around other provisioning problems currently present in the VitalPBX interface (Properly layout of the polycom color expansion module for instance – monitored extensions not mashed on the main phone display and spilled over to the expansion module).

    For the work around, you will need to setup a local FTP server (either on the PBX or another system).  I install vsftpd on the local pbx.

    • create a local user for the polycom phone login (default is PlcmSpIp/PlcmSpIp)
    • create a directory to house the phone software and extra configuration files (i.e. /ftproot)
    • Change ownership of the directory to the user/group created for the phones
    • Configure the ftp server to not allow anonymous login, use the newly created directory, and allow reading and writing, and the appropriate umask to give files permissions of rw-rw-r–

    These are the settings I’m using for vsftpd:

    # Turn off Anonymous user access
    anonymous_enable=no

    # Enable local system users, and give write access.
    local_enable=YES
    write_enable=YES

    local_umask=0113
    chmod_enable=YES
    file_open_mode=0777
    connect_from_port_20=YES
    async_abor_enable=YES
    listen=YES
    pam_service_name=vsftpd
    tcp_wrappers=YES
    max_clients=20
    max_per_ip=5
    userlist_deny=no
    local_root=/ftproot

    # Turn on Logging
    xferlog_enable=YES
    dual_log_enable=YES

    # log file location
    xferlog_file=/var/log/xferlog
    vsftpd_log_file=/var/log/vsftpd.log

    # Turn on Debugging – set xferlog_std_format=NO and log_ftp_protocol=YES
    log_ftp_protocol=YES
    xferlog_std_format=NO

     

    unpack your firmware in to the directory (I used the split version of the polycom firmware to decrease the file size sent to the phone), and edit 000000000000.cfg

    Change the APPLICATION section to point to the VitalPBX provisioning system for the individual config files using the substitution commands from the Polycom documentation.  Here is the section from my cfg file:

    <APPLICATION APP_FILE_PATH=”sip.ld” DECT_FILE_PATH=”3111-17823-001.dect.ld” CONFIG_FILES=”http://VITALPBX_IP/xepm-provision/ext-%5BPHONE_MAC_ADDRESS%5D.cfg, http://VITALPBX_IP/xepm-provision/sip-%5BPHONE_MAC_ADDRESS%5D.
    cfg, http://VITALPBX_IP/xepm-provision/feature-%5BPHONE_MAC_ADDRESS%5D.cfg&#8221; SERVICE_FILES=”” MISC_FILES=”” LOG_FILE_DIRECTORY=”” OVERRIDES_DIRECTORY=”/” CONTACTS_DIRECTORY=”” LICENSE_DIRECTORY=”” USER_PROFILES_DIREC
    TORY=”” CALL_LISTS_DIRECTORY=”” COREFILE_DIRECTORY=””>

    set option 66 in your DCHP setting to point to the address of your ftp server and not the VitalPBX provisioning site.

    This will allow for local firmware and other configuration files not provided by VitalPBX to be used while still utilizing the built in VitalPBX provisioning.

     

    0