Axis Camera Problem

TTy547TTy547
I am having issues integrating an Axis P5512 camera with the software. I have the camera setup and works great on its own http page but when I add it to the ServersCheck monitoring program with the correct IP address, port, username and password, I get a "400 bad request" when I try to view the video. When I leave the username and password blank and reload the page, I get prompted for the username and password of the camera, so, I know it is talking to the camera but still fails to load the image. I am just trying to use the http 80 port, but I also tried an alternate http port (8282) and 554. All fail. For ServersCheck, I am using 10.1.6. and I have the latest firmware and AMC suite for Axis. Tried using Firefox and IE in Windows 7 and Server 2008R2. Is there a setting that needs to be enabled/disabled in Axis or is there an incompatibility with the P5512 and ServersCheck? Or is there a Windows setting that is causing the issue?

Comments

  • AdministratorAdministrator
    Hello,



    Could you run this in debug mode? Also, this is an older version of the software, is there a reason you aren't upgrading?
  • TTy547TTy547
    Sorry for the slow reply. It took me a bit of time to upgrade and I was trying to get my boss to approve the purchase of a newer Axis camera (did not happen). I had purchased 10.1.6 a few days before 10.2.0 was released so when I originally posted my question, I did not know 10.3.0 was out. I have since upgraded but continue to have the same problem. I tried running it in debug mode but nothing was getting written to the file. I posted another topic a little bit ago expanding on this as well as a whole list of other items I have encountered while using the software.
  • AdministratorAdministrator
    something should get written to the file. if nothing gets written then your debug command was wrong.



    1) stop all monitoring services

    2) run following from command prompt

    monitoring_cameratcp.exe > debugcamera.log

    3) run in a second window following command

    monitoring_manager.exe

    4) trigger a motion that initiates a TCP call on port 1274



    Make sure that port 1274 inbound is open on your server
This discussion has been closed.