Help Request For Exacq VMS Customer Issue

Greetings IPVMers!

I am trying to assist one of our customers with an issue involving our servers and the Exacq VMS. We design and manufacture complete server systems so the hardware and OS comes from us. Many of our customers install Exacq on them but this one is a puzzle.

The system has cameras from many vendors installed and running, but the issue involves just three models from three different vendors. The specific issue being that it will not initiate a stream.

When I look at a Wireshark trace I can see see communication between the cameras and the server where it is collecting parameters but there is a segment right before the end of a sequence that indicates trouble to me...one which I pasted below and more at the end of this post.

WireShark trace:

Svr2cam>> GET /command/system.cgi?NtpServer=LCU - Waukesha HTTP/1.0
Authorization: Basic YWRtaW46YWRtaW4=

Cam2Svr>>HTTP/1.0 400 Bad Request
Content-Type: text/html
Content-Length: 155
Connection: close
Date: Tue, 10 Jun 2014 20:03:21 GMT
Server: gen5th/1.82.01
<HTML><HEAD><TITLE> 400 Bad Request</TITLE></HEAD>
<BODY><H1> 400 Bad Request </H1>
Your client has issued a malformed or illegal request.
</BODY>
</HTML>

This looks like an effort to establish the time between the camera and the server.

The odd parts in all this are many. In my lab I have a duplicate system and a sister camera model and I am unable to see the issue that the customer has. (user cam is CH140 and I have a CH120) Other cam vendors are Toshiba and Basler.

I can use RTSP and IE to get video streams a-ok from our server.

Below are the other camera segments with a similar ending:

SVR>> GET /cgi-bin/param_if.cgi?NumActions=3&Action_0=System.NTP.SetValue&Parameter_0_0=H_1&Action_1=System.TimeZoneDesc.SetValue&Parameter_1_0=UTC-0&Action_2=System.NTPServer.SetValue&Parameter_2_0=LCU - Waukesha HTTP/1.0
Host: 192.168.151.119
User-Agent: ExacqDVR
Authorization: Basic YWRtaW46YWRtaW4=


Cam>>HTTP/1.0 400 Bad Request
Content-Type: text/html
Connection: close
<title>Bad Request</title>Only HTTP 1.x supported

AND.....

GET /cgi-bin/admin/setparam.cgi?system_timezoneindex=0&system_ntp=LCU - Waukesha&system_updateinterval=3600&system_daylight_enable=0&system_time=auto&system_date=auto&di_i0_normalstate=high&do_i0_normalstate=open&di_i1_normalstate=high HTTP/1.0
Authorization: Basic cm9vdDo=

HTTP/1.0 400 Bad Request
Date: Tue, 10 Jun 2014 21:03:44 GMT
Server: Boa/0.94.14rc21
Accept-Ranges: bytes
Connection: close
Content-Type: text/html; charset=ISO-8859-1

<HTML><HEAD><TITLE>400 Bad Request</TITLE></HEAD>
<BODY><H1>400 Bad Request</H1>
Your client has issued a malformed or illegal request.
</BODY></HTML>

I could use some suggestions from the Exacq gurus out there.

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

********** ******** ** *** ********. **** ******** * ***** **** to *** *** ****** ******** *** ***** ******* **** *** controls ** ****.

** ** *** * **** *************** ***** / *******?

******* ** **** ******** *** **** **** **** *-*** *** brags '****, * **** ****' **** ***** ******* **** *** revealed *** ********. ** *** ******* **** ****** ****... *** 4 ** *?

...*** * ****'* ****. ** * **** *** ****** * had **** ****. *** ***.

*******, ***** ****** ** **** ******* ** **** **** **** all *** ********* ***** **** ****** **... * ******* *** word '*******' ** *** ***** *******.

********* **** ** ** **** ******* ****** *****, **** **** whispered '****' ** ** *** *'* ********* ** ****** *** ever **** **** **** (*******) ** ** ***** ******* ******... and ** **, **** *** ***** ** **** ** ******** something ****? (****** ***** ******** ****** ***** ** ****** *** loud; ********* *** ****** ****)

**** **** *** ****/***** ******* ******, ** ***** *** ** not ****** ******* ******** ** ***. *** ****** **** ****/***** support ****** ** ********* *** *** **** *** ******* ***** grown ** *** ********. *** **** *** ***, *** '*******' you ****** ** *** **** ******** (*** ** **), *** it ****** *** **** * ******** - *** ********* - problem ******.*

***'* **** ***** ***, *** ****'* **** * **** **** I **** **** **** *******.

**.... '*******'. ***** *******. ******?

----------

******* *****,********* ******* **** ** *** ************** * ****/**** ****** *** * ******* ******** **********.

* ******* **** ****** *** ** ******** **** ****** ****** :), **** ** ***** **** *** ***** ** ******* **illegal **********, notably an 'illegal' space or two in the url, caused by a bogus hostname manually entered for a timserver. But the error ***** ** *** **** ** *** ********* *********** *** **** ** ********, ** **** ********* ******* ** time *** *** ** *** ** **** ****.

****** *******... :)

!% *******.

** ***** *** **** *** ******** *** ****** *** ***** servers * ****** ***** **** ** ** ***** **** ****** in *** ****** ******* ** *** **** *****. ****** *** human **** *** '******' ** **.... ***** ** *** **** of ********* ** * ********* *** ******* ********* (***** ******).

***** *** * **** ******** ********** ** *** ****** ***** where *** *** ****** * ****** **** ****** ** ** intranet *** ******. ** *******, ***** **** *** ***** ****** at * **** ****** ****** *** ******** ** *******...***** *** the **** ****.

*** **** ******, *** **** ******* ** ****** ** *** the **** ** *** ***** ****** ** *** ******** ******** field.

* *** ***** ** * ********* ****** ** ** *** to ***** **** ********* *** **** * *** ********* ****** from ** *******, * *** * **** ********* *** ** parameters ***** **** *** ** *** ******. * ******** ************ with *** ******** ******** *** ******** ** ********** *** *** setting.

* *** **** ** ********* *** ***** ** ** *** system ** ***** *** **** ***** *** **** *** **** to ****** *** ******** *** ** *** *** ************.

***... *** **** ** *** **** ***** *** *********...."* **** been ***** ** **** *** *** * **** ****" **** in **** *** ******** ******** *** *********?