1. Skip to navigation
  2. Skip to content
  3. Skip to sidebar

How to set up scheduled FTP events in your Axis 207 network camera

From the setup pages in your Axis 207 camera you may be forgiven for thinking that it’s only capable of sending images by email based on motion detection, but can it send a constant stream of images to a server using FTP? Well, yes it can, it’s just a little trickier to achieve but we are here to help.

Let’s get started.

Our example will help you configure an Axis 207W to continuously send 1 image per second to an FTP server, the image being continuously overwritten.

This guide will be suitable for the following Axis Network cameras:

  • Axis 207
  • Axis 207W
  • Axis 207MW

It may also work with the Axis 206, however this is untested.

Note that this will also work for all Axis cameras above the Axis 207 but they have the facility to configure scheduled FTP events through the built-in web pages.

Before you start you may like to delete all previously configured events in the camera so the Events, Servers and Actions all have the same identifiers as our example below.

Step 1 – Adding an FTP server

  • Log in to your camera and enter the ‘Setup‘ pages. Choose ‘System Options >> Advanced >> Plain Config‘.
  • Select ‘Event Servers‘ from the drop down box.
  • Click ‘Add FTP Eventserver‘. This should give you a new FTP server titled F0.

Now, enter your server details in the form and save. You can see an example image below. Of course, you will have to populate the fields with your own server details.


Step 2 – Adding an Event

  • Log in to your camera and enter the ‘Setup‘ pages. Choose ‘System Options >> Advanced >> Plain Config‘.
  • Select ‘Event‘ from the drop down box.
  • Click ‘Add Event Type‘ button. This should give you an event titled E0.

A lot of the values will already be populated. Match the values as shown in the image below for the correct configuration (although the name is not important), and save.


Step 3 – Adding an action to the event

The event won’t work without an action and unfortunately there is no way to add an action using the web pages. We need to put a command directly into the camera using the API (Application Programming Interface).

To add an action enter the following line in your browser’s address bar:

http://[camera IP]/axis-cgi/admin/param.cgi?action=add&group=Event.E0.Actions&template=ftpaction

Where [camera IP] is the address of the camera and E0 represents the newly created event in Step 2.

You should recieve the message “A0 OK” if successful.

Now go back to the event as in Step 2 and you will notice that action A0 has been added to the bottom.

See the image below for the correct values to enter for the action.


That’s all there is to it. Now restart the camera and keep an eye on your FTP server to see your image.

If you have any comments or questions about this guide please leave them below and we will do our best to answer them as soon as possible.

Published on February 27th, 2007 by Greg

111 Responses to “How to set up scheduled FTP events in your Axis 207 network camera”

  1. Jan says:

    Hello, I want to ask.. “max sequence number” means that when camera achieved sending frxmpl. 10000 frames, than starts to rewriting oldest pictures (like FIFO)? thanks a lot.

  2. Lars says:


    Great guide – I used it on a 207w a year ago, and it has been working like a dream. However, I am currently working with yet another 207w, and this time i cannot get it working… The problem is that the image never gets uploaded to the ftp server. Except for a time out notice in the log, I find no errors. I tested ftp settings, which returned a success message. I tried adding several identical events, but it did not help. I tried altering the settings a little bit, but that didn’t work either. IS there another way (scripting) to do this, or a way to fix this?

    NB: when I tested the FTP connection settings, a test file was successfully uploaded, so it appears something is wrong with the event.


  3. Evert says:

    Id did enter the line http://[camera IP]/axis-cgi/admin/param.cgi?action=add&group=Event.E0.Actions&template=ftpaction

    two times extra and it came back with a A1 OK and A2 OK. I see the camera did add two extra events A1 and A2.
    But how can I remove these two events A1 and A2. What command line do I have to use?

  4. amelia says:

    Hi Greg, I actually bought the 207w and it really has the option to create a folder (it’s running fw 4.44.2), but when I set the folder option to %y-%m-%d the camera creates the folder but it doesnt upload any image to it (or to any folder on my server). Do you have access to a 207w to test this option of creating a folder and saving images on it?

  5. Greg says:


    Web mail servers which require SSL connections won't work with any Axis camera I'm afraid but most email accounts which are offered by your ISP should not require SSL. Try that.

    Otherwise yes, using FTP is another way of getting around this problem.

  6. Chris Murphy says:


    I just recently got a 207-MW. I am interested in setting up an event to email images when motion is detected, but I think all web mail servers (gmail, for example) require SSL, right?

    Test messages are not received by my gmail account when I use the smtp address. Is there a way to get around the SSL issue to be able to email? I thought about running an SMTP server on my Windows XP PC, but that’s a little complex.

    Also, is email the best way to accomplish this, or should I try the FTP or http/web server options under the Axis settings?

    Thanks for any help!

  7. Greg says:

    @Daniel, @M.Houry:

    The first thing that comes to mind from that message is that you are using incompatible firmware for the model of camera you have?

    My advice would be to ask the question over at the Axis helpdesk. You'll find that on Axis.com

  8. M. Houry says:

    Hello Daniel,

    I have the same problem as you, you found a solution yet for it??

    Wrong HWID! The uploaded firmware cannot run on this hardware

  9. Giancarlo says:

    I want simply say "Thanks" for this HowTo guide!
    much better than the Axis support!

  10. daniel says:

    Hi, I’m trying to upgrade my axis 206 ip camera but no firmware seems to works, it’s shows me this:
    Preparing system for upgrade …
    Entering run level 4 …
    Waiting for processes to be stopped in runlevel 4 …
    … waiting …
    … waiting …
    … waiting …
    … waiting …
    … waiting …
    … waiting …
    … waiting …
    … waiting …
    In run level 4.
    Stopping remaining processes.
    sending TERM signal …
    All processes stopped.
    The file system will be upgraded after reboot.
    Unmounting file system /var …
    Unmounting file system /mnt/flash …
    File systems successfully shut down.
    Receiving new firmware …
    Wrong HWID! The uploaded firmware cannot run on this hardware.
    The system upgrade failed.
    The unit will now reboot.
    To continue, please connect to the unit again.
    There may be a short delay before the new connection is accepted.
    This connection will now close.

    I was uploaded three firmwares availables but nothing and ACS can’t add the camera.

    Any tip?

  11. Thomas says:

    Thank you Greg, it works great!

    Now I have two new questions if it’s ok.
    First, is it possible to view the status of an event parameter? For example, is it possible to check if an event is enabled or disabled and display the result somewhere?

    Second, is it possible to change an event parameter without beeing an administrator? At the moment I have two links on the live view page to turn an event on or off, but I have to log in as an administrator to use it. I would like viewers to be able to do it too. I use this to set the parameter: http://[IP-adress]/axis-cgi/admin/param.cgi?action=update&Event.E1.Enabled=yes

    Thanks again! 🙂

  12. Greg says:


    Yes it is possible. You need to enter some variable in a string of characters to specify this. So use the following example in the "Image URL settings" field and change to suit your requirements:

    camera=1:resolution=320×240:compression=50:color=yes:overlayimage=0:date=0:clock=1:text=1:textstring=#r #b:textcolor=white:textbackgroundcolor=black:textpos=top

    Also, you must check the box that says: "Image URL settings enabled" or it won't work.

  13. Thomas says:

    Thanks for a nice howto!
    I’m wondering if it’s possible to specify the resolution of the image beeing uploaded?

  14. amelia says:

    Thanks for the reply Greg.
    I am probably selling it and buying the 207w then.

  15. Greg says:


    I double-checked this with Axis and they told me:

    "This isn't possible in the 207 as it has limited event possibilities. However in the 207W (4.44), 210, 211 etc, this is possible. More information can be found in the "Help" of the product."

    So with the Axis 207, I'm afraid it's not possible although it will be possible using higher models.

  16. amelia says:

    Thanks greg it really worked.
    Is there a way to improve it through plain text sending a command to create a new folder every day naming it with the date and pointing the ftp uploading process to that folder?
    I have the axis 207.

  17. Yesterday, I tried to configure AXIS 211M and AXIS 207M to store video on FTP using motion detector.

    It was very easy to setup on AXIS 211M, because there you have Evens menu. But you know, as a Michael H I have not found the FTP option in 207M. Thanks a lot for your explanation. Now it is easy.

  18. Michael H says:

    What a great guide. This would have helped me enormously had I found it when I was struggling to get scheduled events working on a 207W when they first came out. When I finally got an answer from Axis support, I gave up because they insisted that even in plain config it was impossible in the 207W and I needed a 210 instead!

  19. Pieter says:

    Hi, is there also a script that does not overwrite the image on the server, but with which I can store let’s say a full day’s worth of images? So I can look back in time?

  20. Andre says:


    I have a problem with my „Axis 207“. With a script I made the camera uploading an image to a ftp-server every minute. Normally this works without any problem or mistakes. But then, mostly after a time of some days, the camera suddenly stops the upload for no clear reason and without an error in the server-report list before. If that happens, I start the Axis software (which I normally not use, because I only watch the uploaded jpeg pictures in my browser) with the login and the “Live view” window … and from this moment on mostly the upload automatically starts again and works normally for a few days until the next crash. A restart mostly isn´t necessary.

    Has anybody an idea what goes wrong or what I could do to prevent this crashes?

    Thank you very much and sorry for my (German) English! 🙂


  21. Greg says:

    Thanks for that. Yes, the Axis 206 really is an entry-level model. Great for live monitoring or perhaps used as a streaming IP webcam but perhaps not so feature-packed for the home security market.

  22. Nicke says:

    Sorry, I mean Axis 206 above.

  23. Nicke says:

    Hi, I can confirm it doesnt work on Axis 207, there is no event handler at all. Wish I bought 207 instead.

    I have been using Axis 211 before and then ftp upload is available.

  24. Greg says:

    Hi Marc,

    What settings are you trying to use for your FTP server?

  25. Marc says:

    Dec 26 21:15:46 axis-00408c91d580 /bin/parhandclient[601]: #Error -1 getting param in group ‘root.EventServers.FTP.’!
    Dec 26 21:15:46 axis-00408c91d580 /bin/ssid[604]: Starting.
    Dec 26 21:15:46 axis-00408c91d580 /bin/sftpclient[600]: 530 Login incorrect.
    Dec 26 21:15:46 axis-00408c91d580 syslogd 1.4.1: restart.
    Dec 26 21:15:46 axis-00408c91d580 time_handler[342]: Reading configure file.
    Dec 26 21:15:46 axis-00408c91d580 time_handler[342]: NTP small time adjustment 5520 usec.
    Dec 26 21:15:46 axis-00408c91d580 /etc/event/event[519]: Error getting parameters for server

  26. Marc says:

    I have a problem with the setting of the FTP Server.
    How must i write the FTO in the field.
    Please will you check the log:
    RITICAL> Dec 26 21:08:11 axis-00408c91d580 /bin/parhandclient[576]: #Error -1 getting param in group ‘root.EventServers.FTP.’!
    Dec 26 21:08:11 axis-00408c91d580 /etc/event/event[491]: Error getting parameters for server
    Dec 26 21:08:11 axis-00408c91d580 /bin/sftpclient[570]: 530 Login incorrect.
    Dec 26 21:08:12 axis-00408c91d580 /bin/ssid[392]: Exit on signal 15
    Dec 26 21:08:12 axis-00408c91d580 /bin/ssid[621]: Starting.
    Dec 26 21:08:12 axis-00408c91d580 /bin/ssid[621]: /usr/html/

  27. Kevin says:

    Ich würde vorschlagen, Kontakt mit Axis sich über diese. Ihre Kunden-Helpdesk ist die beste Option. Siehe http://www.axis.com/login/login.cgi?oldurl=/reg/mycases/

  28. peterpan72 says:

    Hall o Kevin,

    unter welchem Punkt im Scripteditor muß der reboot eingetragen werden und wie muß das Script aussehen?
    Werde auch an Axis schreiben und nachfragen,ob der connect verlust ein Problem mit der Kamera ist und unter warrenty repariert werden kann.

  29. Kevin says:

    Hallo Peter,

    You can use the script editor in the camera to tell the camera to reboot every hour as a solution. There might be a problem with the camera which can be fixed under warranty.

    Sorry, Google translation: Sie können den Skript-Editor in die Kamera zu sagen, die Kamera neu zu starten jede Stunde als eine Lösung. Es könnte ein Problem mit der Kamera, kann behoben werden, unter Garantie.


  30. peterpan72 says:


    Habe diese wirklich spitze Anleitung genutzt und meine Kamera danach eingestellt. Sendet regelmäßig Bilder per ftp an meine Webseite.
    Es gibt aber ein Problem: Die Kamera hängt sich mehrmals am Tag in unregelmäßigen Abständen auf und ist dann nicht mehr erreichbar. Nach einem Neustart der Kamera läuft alles wieder prächtig. Angeschlossen ist die Kamera per Wlan an meinem Router. In dessen Logdateien ist außerdem zu sehen, daß sich die Kamera ca 1 mal pro Stunde ab und gleich wieder anmeldet. Woran kann das liegen und wie kann man den Fehler beseitigen? Aud der Kamera ist übrigens die aktuellste Firmware vorhanden und wurde zur Sicherheit auch nochmal aufgespielt. Schon mal besten Dank für die Hilfe!

  31. Greg says:

    Sending images 1 per second by motion detection doesn't make sense.

    The camera will send images when it detects motion. The amount of images it sends can be fully configured, with pre-/post-buffer images included. The Axis 207 models of camera can also send video files (with audio) to an FTP server when motion is detected.

  32. r2 says:

    “From the setup pages in your Axis 207 camera you may be forgiven for thinking that it’s only capable of sending images by email based on motion detection.
    but send a constant stream of images to a server using FTP?”

    r2 say: but send images (1 per second) by FTP based on motion detection? (no constant)

  33. Greg says:

    The Axis 207, 207W or 207MW has an RJ45 Ethernet connection which must be attached to a router.

    And yes, this guide describes how to have the camera send an image by FTP every second.

  34. r2 says:

    I have tested with cameras (no axis)
    and not send an image 1 per second by FTP.


    Axis 207/W/MW have connection PPPoE?
    Axis 207/W/MW send 1 image per second by FTP?


  35. Greg says:

    Almost every IP camera will have the functionality to send an image by FTP every second. This guide shows how to do just that using an Axis 207/W/MW.

  36. r2 says:


    I need to know if you have a model of ip camera that sends a “one” (1) image per second to ftp server.
    in the manuals do not specify this information



  37. Georg says:

    Greg, you are great – it works!
    But why is the unit setting needed at all?
    And how’s the logic? I don’t get it 😉
    Anyway, thank you for your help.

  38. Greg says:

    Try setting the following:

    Best Effort Interval: 3600000, Best Effort Duration: 0, Best Effort Interval Unit: h, Best Effort Duration Unit: s

  39. Georg says:


    thank you for this great tutorial.
    i’ve tried to set the effort-interval to 1 hour (3600000, unit s), but it doesn’t work!
    Setting to 60 (unit m), or 1 (unit h) has no effect..
    How can i set the event interval time to one hour?

    Thanks in advance for your comments

  40. Greg says:

    I'm glad you got it sorted and found my guide useful. We will already have the API documents from Axis but thanks for the offer.

  41. Alexis says:


    I’ve asked AXIS support for this scheduled event problem and they answered me (in less than 12 hours!) sending me some PDF explaining how to set up different scheduled events. If you want I could send you these files.

    Kind regards

  42. Alexis says:


    I was able to configure my Axis 207MW using this howto (thanks to its author!).

    However I don’t really understand how to delay the upload and that it upload a file, say, every five minutes. In fact I don’t really understand what’s the difference between:

    post/pre trigger size
    post/pre trigger interval, interval unit
    best effort interval, duration, interv. unit, duration unit

    I tried different settings and the results are:

    – without any settings it uploads a file as much as possible
    – with 300 seconds in post/pre trigger it sometimes send a
    file every seconds, sometimes every 5 minutes. But after
    some unpredictable time it stops sending files. Once it
    was after 6 hours and another time after 20 minutes.

    It’s a little sad that this webcam offers high level events, but not a simple as timeout…

    Anyway thanks in advance for your comments

  43. Tif says:

    Thank you Greg.
    I will try and let you know. My Livebox (french wifi modem) is actually off …

  44. Greg says:

    Yes, such a possibility does indeed exist.

    Under the entry for filename you will see an entry for 'suffix'. This allows you to add a suffix to the filename making each image unique.

    Input the following to add a date/time suffix to each image filename:


  45. Tif says:

    Dear Greg,

    Thank you very much for such an explanation.
    What i would like to do, is to keep a serie of images on my server. So is there a possibility to not overwritte the last pictures send to the FTP server. And have for instance a serie like :
    image1.jpg; image2.jpg; … image900.jpg…

    imagedatehour.jpg; imagedatehour+1hour.jpg, etc …

    It would be wonderfull if such possibility exists. Indeed is to keep an eye on my babies (i am installing the 207w in their room), and at the end of the day, be able to check the pictures.

  46. Greg says:

    Hi Marc,

    I'm not sure if there is an easy way to just delete an action but have you tried using the 'plain config' tool and deleting the event? Does this not also delete the action?

  47. Marc says:

    How can i delete the actions like A1, A2, A3….
    everytime i paste this: http://[camera IP]/axis-cgi/admin/param.cgi?action=add&group=Event.E0.Actions&template=ftpaction
    i get a new action.


  48. Jeff says:

    Glad you guys figured out that the script stops running if the connection goes down temporarily. Still looking for a script to initiate the FTP periodically. Any suggestions?

  49. Steinar says:

    More try and fail, and as usual the error was between the chair and monitor. In Event E0 Actions A0 I had set order to 1 instead of 0 – Setting it to 0 (As your guide said) made the trick. Thanks again Greg for this guide and your input.

  50. Steinar says:

    Thanks Greg.
    I guess the script stop running if internet connection is lost. I have tried with 2 different 207 and 1 207w camera. I noticed a couple of other people posting have similar problems – Camera at random stop uploading. At my current location it's been working with no problems, but at the other location where it fails I know the internet connection fail several times a day. Tested setting the camera to upload every 1 minute – Working OK – Disconnected the network cable for 2 minutes and reconnected, but then camera refuse to upload unless I restart it. Ill try to make a script as you suggested and will report back the result (Script also if it work)

  51. Greg says:

    As far as I was aware the script shouldn't stop running if you just lose your Internet connection temporarily but if it does you would need to look at creating a second script in the camera which will initiate the FTP script say once every 15 minutes. This would get around the problem.

  52. Steinar says:

    If internett connection is lost for a while, the
    camera does not resume uploading pictures when connection
    is back – Any idea how to fix this ?

  53. Jeff says:

    Very helpful site Greg. Well done. I have a problem similar to [John March 5th, 2008] above, where my timed ftp uploads just stop every day to two and the camera has to be restarted. Does anyone know what might be causing this or, as a workaround, how can I get the camera to restart automatically at a set time of day or interval?


  54. Greg says:

    If I understand you correctly you wish to know if you can access the live images from the camera without entering the username and password?

    Yes this can be done very simply. On the setup pages click the "users" link in the menu under the "basic setup" heading. You will see a checkbox titled "Enable anonymous viewer login (no user name or password required)". Check this box and save to enable anonymous access. Note that every user who knows your camera's IP address will now have access to live images but they will not have access to the admin setup pages.

  55. jullio says:

    Hi Greg,

    Im use this http://www.axis.com/techsup/cam_servers/tech_notes/live_video_medium.htm
    template to access my cam.

    As I can validate the username and password entry through the browser for a camera axis 207 w without put this data?

  56. Leo says:

    Okay thx, will do that. I alsow want to schedule only on weekdays monday/friday. I think that i have to use the “weekdays” setting. Like: 1111100, or if the first day is sunday: 0111110. What to use?

  57. Greg says:

    Sometimes it's ok, yes, but I prefer to just reboot the camera after adjusting any event settings as sometimes the camera needs it.

    Remember you can reboot the camera remotely using the interface, you don't need to actually kill the power to reboot it.

  58. Leo says:

    Why do you have to reset the camera after changing event settings? the changes you made are all ready active before the reset.

  59. Leo says:

    Great thx!

  60. Greg says:

    It would depend how much time you want to see 'before' the event (pre trigger) or 'after' the event has passed (post trigger).

  61. Leo says:

    Hello Greg,

    Thx voor de fast response. What sould i set in de pre/post trigger interval value?

  62. Greg says:

    Hi Leo,

    Try increasing the value stored in Best Effort Interval. If it's 1000 for 1 second then it would be 3600000 for an hour.

    Remember to reboot the camera after changing any event settings.

  63. Leo says:

    How can i configure an event that uploads a picture every hour? I changed the interval fields to 1 and unit to “H” but that doesn’t work..

  64. Greg says:


    You'll find the API for Axis cameras at the following address:


  65. John says:

    After all my complaining, the 207W has seen the light and uploads images via FTP faithfully now. It has been a week now without issues. Don’t really know, maybe Greg did something remotely to make it work so well . I think the secret for me is to stay in ‘plain config’ exclusively (well, seems to have worked so far anyway). This has been an extremely helpful thread… Thanks Greg

  66. Greg says:

    Hi Laurie,

    You should be able to call an image from the camera using the following command through HTTP:


    Links to the API language can be found here:


    Hope that helps.


  67. laurie says:

    Doh, I found the trigger URL: http://**mycam**.dyndns.org:8013/axis-cgi/io/virtualinput.cgi?action=6:\

    Still seeking the API guide!

    [ed – url edited out to protect commenter]

  68. laurie says:

    Very helpful thread!

    I’m hoping to occasionally trigger my 207W to take a picture (& email it to me) remotely, ideally via a HTTP request or an email. I can trigger from the LIve View site, but I can’t figure out the HTTP GET command which could do this automatically. Any clues?

    I also haven’t found the much-mentioned API guide – does anyone have a URL for it?

    Many thanks,


  69. Al Berto says:

    I found a new firmware (4.40) in the Axis site.
    Looking at this description, I think my problem has been fixed since 4.20 version:

    4.20:27 A problem with gaps in the file name sequence during FTP upload has been corrected.

    I should try this on my camera.
    Thank you anyway, maybe this post can help other users.


  70. Al Berto says:

    Hi Greg,
    I ask you as you seem to be quite expert with Axis cameras. I searched the forum but I can’t find anything.
    I got a Axis 211 sending image to an FTP server every 5 seconds. I chose to number the images from 0 to 24 then restart, but it seems to be a bug in images numberings.
    What I got is image00001, image00003.. to image00023 (all odd numbers). But sometime they are named image00002, image00004.. to image00024 (all even numbers), resulting in a sequence of newer and older images…
    All I would like to have are images numbered from 0 to 24, not so hard!
    This camera seems to have an old firmware (4.11 dated 2004) but I can’t find any never one. Maybe other firmware version can resolve this problem?

    Many thanks

  71. John says:

    I spoke too soon. It will upload .jpg’s for anywhere from minutes to hours at the interval I specify while also detecting motion and uploading those images to a separate FTP server, but the ‘timed’ uploads soon stop.

    This is very frustrating, especially as the cheapo Panasonics I’ve got will perform up to 5 seperate actions using any combination of timed, motion, or sensor triggers at the same time without flaw.

    All I want the 207 to do is upload images or mpeg4 to one FTP server when triggered by motion, while always uploading a jpg in overwrite mode to a different FTP server every 5 seconds. Doesn’t sound like too much to ask, but after weeks of trying everything, I can’t get it done.

    If anyone has accomplished this, I’d be very grateful to hear the details.

    Keep in mind, the above directions seem to work perfectly for 1/2 of what I want, as long as I don’t ask the 207 to upload jpg’s or mpeg4’s upon motion detection.

    John F

  72. Greg says:

    Glad to hear it works for you now. Take a look on Axis.com/support for information about scripting in the cameras.

  73. John says:

    Greg, I have gotten it to work (fingers crossed, limited testing.) Seems wierd, but creating an event 1 as a ‘dummy’, then an event 2, then running the action http command thrice to create a E2-> A2, then deleting the dummy E1 event and blanking out the server settings for the unused E1 -> A0 and E1 -> A1 actions created by the http command, just leaving the final E2 -> A2 action, it works.

    Why it wouldn’t work with E1 -> A1 action is a mystery yet to be determined, and I’ll play with it more as time allows.

    Thanks so much for your help. I’d still like to know what the various ‘type’, ‘order’ and ‘priority’ fields do. Is there a document that explains all of the plain text stuff?

    John F

  74. John says:

    Greg, I’ve tried this, but after entering the “http://[camera IP]/axis-cgi/admin/param.cgi?action=add&group=Event.E1.Actions&template=ftpaction”
    (notice I’ve replaced E0 with E1) then go back to step 2, it shows (correcly) event E0 attached to Action 0, but also even E1 attached to Action 0) – I’ve setup a seperate FTP server F1 and specified it in ‘Event E1 Action 0’ but this routine still has problems.

    Do I not need to get an ‘Event E1 Action 1’ or something like that for the step 3?

    What is the meaning of the ‘type’ and ‘priority’ field entries for the Action?

    What are the meanings of the ‘type’ and ‘order’ fields in the Event.

    Thanks for your help.

    John F

  75. Greg says:

    Maybe what is happening is that the event you create using the plain config is overwritten when you create a second using the wizard.

    Try creating the motion detection event using the wizard first then set up a second event using plain config bearing in mind that the details that will already be populate will be the details for your motion detection event so create a NEW event E1 and follow the instructions above but for your E1 event.

  76. John says:

    Greg, I’ve not been able to get multiple events working – if I enable image or mpeg4 FTP uploads triggered by motion, the process described here quits working. Could you possibly provide more info for a relative ‘newbie’ on how I can do both simultaneously? (I’d like to send an overwrite jpg file every 5 seconds to one FTP server, and a few seconds of mpeg4 video triggered by motion.) Thanks.

  77. Greg says:

    Absolutely. You can set up multiple events such as transferring an image every X seconds to an FTP server to display a live image on a web-page while also having an event to email you an image or video clip if the camera detects movement.

  78. Iynkaran says:

    Very useful guide

    Would it possible to have a multiple actions to an event, i.e. one to FTP server and other to mail server?


  79. Jan-Paul says:

    Hi Greg,

    i,m not looking for alarm events. Just want an image to be uploaded through ftp to a website every minute. The options i have now are or with a tool like this http://sourceforge.net/projects/imagelogistix/ (needs a PC which is not at this location) or by getting the html to pull the image from the camera. This means i need to have my router NAT enabled. This is not what i want to do. FTP straight from the camera would be the ideal solution. I hoped maibe it could be done by using the scripts inside the camera ….

  80. Greg says:

    Hi Jan-Paul,

    Unfortunately this is not possible with an Axis 206. The Axis 206 does not support any alarm management features as far as I'm aware.

  81. Jan-Paul says:

    Hi, great info,
    unfortunately this doesn’t work on a 206.
    The menu’s simply are not available.
    Is there anyone who can help me doing the same thing with a 206 ?

  82. Greg says:

    Hi David,

    Could be the DNS settings in your camera. It might not be able to resolve a domain type address such as "ftp.myftpserver.com" into its IP address. Check your DNS settings or simply use the IP address instead. You can find the IP address of your FTP server by using the "ping" command from a command prompt.

    Also check the log files in the camera for more information about what it's trying to do. You'll find them in the setup pages.

  83. David says:

    Still having problems. Followed the instructions to the letter and the camera is at least trying to upload but the log says my ftp server is an “unknown host”. Now I now that my ftp site is valid as I have been working on my website today so I’m not sure what my problem is.

  84. Kevin L. says:

    Any ideas how I might use curl from a linux command line to program these settings listed in the how to?

    Thanks for this post!

    Kevin L.

  85. Dan says:

    Having followed the above, what do you put in the suffix field (in plain config settings) to stop the image being overwritten and build up files as they are sent to the ftp server in sequence?

  86. Deryk says:


    I’ve found two problems with handling MPEG-4 in the camera:

    1) Eats CPU to generate the MPEG4 file
    2) You can’t stream “continuous” MPEG4 to a file

    From what I understand of how buffer_handler_mpeg4 works, it has a pre-trigger duration and a post-trigger duration. Once you send a USR1 signal to the buffer handler (ie, a motion event occurs) it then buffers for some additional seconds, then generates an MPEG-4 file which you can FTP or email.

    However I’m interested in starting MPEG4 archiving when an event happens, and generating a stream for a minimum of x seconds with the possibility of streaming for longer if motion continues. This may result in a 5-minute MPEG-4 stream (or longer), which would likely be too big to fit in the camera’s memory _and_ would take a long time for the camera to process.

    This can be easily accomplished (I think) by having an external process connect to the camera by RTSP and record the MPEG-4 stream. I’d tell that process when to start and stop by sending HTTP or TCP actions. FFMPEG may be a part of this solution.

  87. Greg says:

    Hi Deryk,

    I think you'll find if you use the 'interface-based' event manager in an Axis 207(W/MW) camera you can record MPEG-4 video for storage via FTP (or email).

  88. Deryk says:

    Great info here. I don’t know if keven still checks this blog, but it _is_ possible (theoretically) to upload images via HTTP. But you have to use scripting, specifically the shttpclient program.

    Unfortunately I couldn’t get the web-based event manager to bend to my will so ultimately I’ve written custom scripts for all of my events. The most frustrating bug seemed to be that the video wouldn’t be captured before AND after a motion event, regardless of the values in the “MPEG trigger duration” fields. It seems that parhand wouldn’t create the task.list file correctly, so the MPEG4 buffer handler never had the -b option (for seconds to record after the trigger, ie “MPEG post trigger duration”)

    What I’d really like now is to find a command-line RTSP client that I can call on a remote computer (through a TCP or HTTP action to a program like Girder) so that I can record MPEG4 streams off the camera and store them on the network. Can anybody point me in the right direction?

  89. Steve says:

    I had no router ip specified – argh. What a freshman! 😉
    Works now.

  90. Steve says:

    It does not work. Log says:

    Jan 1 00:00:44 axis-00408c77e9c9 /bin/sftpclient[729]: connect error: No route to host

  91. Greg says:

    Yep. You can restart the camera by cutting the power for 60 seconds or you can restart it from the camera setup menus. 'System Options > Maintenance > Restart'.

    You can also see camera logs in the setup menus.  Choose 'System Options > Support > Logs & Reports'.

  92. Steve says:

    Is “Now restart the camera” pulling the power cable and plugging in back in? Maybe that’s my mistake.

  93. Steve says:

    I tried this with no success. The “action=add&group=Event.E0.Actions&template=ftpaction” gave me a correct “A0 OK” and I changed the settings to “F0” – but no image on our ftp server.

    Any ideas? How can I see that the axis is at öleast “trying” to upload an images? Error logs somewhere?

    Thanks for any help,

  94. Greg says:

    Sounds like when adding the action the camera couldn't find a corresponding event. This could mean a couple of things I think, 1. When you configured the event it somehow didn't save. or 2. The Event number did not tally with the number in the command you typed. In the command you typed you are adding an action to the event E0. If your configured event is E1 then you should change it to read E1 in the command.

    Hope that helps.

  95. Jerry Russell says:

    I believe it was: No action specified.

  96. Greg says:

    Hi Jerry,

    The syntax looks ok to me, what error are you getting?

  97. Jerry Russell says:

    Here is what I used and I get an error message. Did I do something wrong?

  98. Andi says:

    This is a great manual – it actually was the only useful source I found to make the FTP upload work as I planned within a reasonable amount of time. I set an interval of 36000 seconds (new pic every 6 minutes).

    There are just two problems left:

    – I got my router and cam attached to a ON/OFF timer. The power is switched on and off 5 times a day when I’m not home. The first image, however, always shows the time and date of 1 january 1970, 00:00 – the cam makes a NNTP update only when the 2nd image is ulpoaded after 6 minutes. Not too bad – but this means I have to leave the power on for at least 7 minutes, and sometimes even this is not enough. Does anybody know how this could be solved? Can I force the cam to make a NNTP update before the first upload?

    – What is the meaning of the “duration” field: Does it mean (see screenshot above) “start the job and stop after 24 hrs” or “do the job permanently, never stop”?


  99. Greg says:

    Hi Paul,

    I would guess this is more to to with permissions on the server than anything wrong with the camera configuration. Make sure you have the correct permissions before attempting to delete/overwrite files.

  100. Paul Craven says:

    Great “How To”!!!
    I’ve just set it up on a 207W with the latest 4.40 firmware, and the FTP upload is only working if the image does not exist.
    Camera Log:
    Jul 26 18:46:06 axis-00408c77d499 /bin/sftpclient[3527]: 550 Rename/move failure: File exists
    Jul 26 18:46:06 axis-00408c77d499 /bin/sftpclient[3527]: Rename [email protected] -> image.jpg failed
    Jul 26 18:46:06 axis-00408c77d499 /etc/event/event[547]: Action A0 for event E0 failed, status 1. Will retry for a while.

    The only setting I have changed from your example is the Best Effort Interval = 60000

    Any ideas?



  101. Kris says:

    For file name use suffix field:


  102. Greg says:

    Hi Tom,

    Thanks for your enquiry.

    The reason behind this tutorial was to show camera owners that it was possible to set up a 'scheduled' event in the 207 model camera. I didn't cover events based on motion because this can be done in the main setup pages of the camera without resorting to the complicated 'plain config' pages.

    However I think it would probably be beneficial to create a tutorial for this too so we have all bases covered.

    I'll add it to my list. Keep an eye on the blog.

  103. Greg says:

    Hi Kevin.

    As far as I'm aware you would use FTP to upload files.

  104. Tom says:

    Thanks for the informative writeup… noticed however, that this is tailored for constant FTP upload. Can you tell us how to config the camera for motion-detection, then upload via FTP?


  105. kevin says:

    Quite simply i was hoping to upload an image to an apache webdav folder, like ftp but without the extra ports hassle of active or passive ftp. Havent’t done or read anything since my previous message, but I’m guessing the http eventservers the axis cams refer to are only meant for a ping-like message from the camera, not full uploading. Pointing a http eventserver to a webdav folder only gave me a 301 (Moved Permanently) error in the logs, but first attempts rarely bring home any bread. (Hey, I don’t want to hijack or derail this comment thread, btw..)

  106. Greg says:

    Hi Kevin,

    Thanks for the additional tips.

    With regards to your new question, what is it you're trying to achieve? It would be easier for us to advise a possible solution if we know the end goal.

  107. kevin says:

    And now a new question: any experience with http eventservers? I assumed that this was DAV, but that does not seem to work. Will read the cryptic api docs from Axis, but would be very happy if someone had hands-on for this. (I’m looking into this since it would (i hope) simplify firewall circumvention)

  108. kevin says:

    Adding a warning here. On some cameras, after following this recipe, you can also change event settings in the normal setup pages. Useful for customising the image (overlay, resolution, compression). BUT! Immediately after, go back to plain config and check “Best effort interval” (and others too, maybe). I have my cams set for a 180000 (3 mins) b.e. interval, but after changing image settings in normal setup, it was back to 1000. So my cam was uploading every second, or certainly its “best effort” to meet that…

  109. Greg says:

    Glad we could be of some help Kevin. Yes, this guide will work in any Axis network camera but it's worth noting that in the higher-end models such as the 211 or greater, setting up scheduled events can be done from the cameras built-in setup pages. And you are right! It is possible to add a bit of scripting to a PTZ camera to ensure it returns to a particular spot before taking a snapshot. I will make a note to do a guide on this in the future.

  110. kevin says:

    I can confirm that this works with the Axis 211 as well. I would guess that this works with the 210, 211A and other (recent) fixed cameras too. For PTZ cameras, why not, but you’d have to add something to pan-tilt-zoom to a defined position somehow. If you want the same view in each snap, that is.

  111. kevin says:

    Excellent, excellent, excellent! The scripting guide from Axis is messy and seems a bit outdated, which is a crying shame since these cameras are so flexible.

    This guide worked perfectly on a 207mw. I will test shortly with an axis 211.