Dear All,   I have the same problem. In my network there are more than 100 spa 500x devices. All have 7.6.2d firmware. The hardware versions are difference but the problem appears on all. So I think this is firmware bug. The reboot is not enough. The power cable should be removed for 30 sec and then the link will be restored. On one device I tried to update a firmware ( 7.6.2e ) while the pc port was down. The update was success but after reboot the link was still down. I had to remove power cable.   Do somebody have solution? ... View more

Hi All,  I've tried to set up the report rules on an SPA504G (7.6.2e). I've read the article about provisioning and some article from community. The conclusion is that the documentation is not up to date.  From the documentation The possibilities: tftp://tftp_server_address/config_$MA.xml [--status]tftp://tftp_server_address/status_$MA.xml [--delta]tftp://tftp_server_address/delta_$MA.xml [--content a]tftp://tftp_server_address/book_$MA.xml [--content p]tftp://tftp_server_address/config_$MA.xml [--content h]tftp://tftp_server_address/hitory_$MA.xml You can use more rules separat them with semicolon (;), like this: "[--delta]tftp://tftp_server_address/delta_$MA.xml; [--content a]tftp://tftp_server_address/book_$MA.xml" In the real You should not use semicolon (;) because the SPA will add it to the end of the filename. <Report_Rule group="Provisioning/Configuration_Profile">[--status]tftp://tftp_server_address /status_MAC.xml; [--content a]tftp://tftp_server_address /book_MAC.xml</Report_Rule> spa_address → tftp_server_address TFTP 107 Write Request, File: /status_MAC.xml;, Transfer type: octet, blksize=126, timeout=10, tsize=x spa_address → tftp_server_address TFTP 107 Write Request, File: /book_MAC.xml, Transfer type: octet, blksize=126, timeout=10, tsize=x  You can't use more than two rules. <Report_Rule group="Provisioning/Configuration_Profile">[--content p]tftp://tftp_server_address /config_MAC.xml [--status]tftp://tftp_server_address /status_MAC.xml [--content a]tftp://tftp_server_address /book_MAC.xml</Report_Rule> spa_address → tftp_server_address TFTP 107 Write Request, File: /config_MAC.xml, Transfer type: octet, blksize=126, timeout=10, tsize=x spa_address → tftp_server_address TFTP 152 Write Request, File: /status_MAC.xml [--content a]tftp://tftp_server_address/book_MAC.xml, Transfer type: octet, timeout=10, tsize=x  If you want to backup the whole configuration without bracket and the status, you should put the rule without bracket to the end. <Report_Rule group="Provisioning/Configuration_Profile">[--status]tftp://tftp_server_address /status_MAC.xml tftp://tftp_server_address /config_MAC.xml</Report_Rule> spa_address → tftp_server_address TFTP 107 Write Request, File: /status_MAC.xml, Transfer type: octet, blksize=126, timeout=10, tsize=x spa_address → tftp_server_address TFTP 107 Write Request, File: /config_MAC.xml, Transfer type: octet, blksize=126, timeout=10, tsize=x  If you want to backup the address book and the status but the address book is empty the second rule won't be executed. <Report_Rule group="Provisioning/Configuration_Profile">[--content a]tftp://tftp_server_address /book_MAC.xml [--status]tftp://tftp_server_address /status_MAC.xml</Report_Rule> No tftp log  When the tftp server does not response to the writing request and the SPA receive a new SIP NOTIFY message the SPA freezes. In this case the power cable should be removed. Can anyone use report rule? Regards, Szabolcs ... View more