Axis Customer Forum

It is currently Mon Aug 19, 2019 2:16 pm

All times are UTC




Post new topic Reply to topic  [ 7 posts ] 
Author Message
PostPosted: Tue Jan 22, 2019 4:49 pm 

Joined: Mon Feb 11, 2013 1:45 am
Posts: 4
I am testing Action Rules on an Axis M1054. A pushbutton closure on the I/O input is used to perform two simultaneous actions:

The first one just plays a sound file on the camera loudspeaker, that works immediately.

The second is an https notification to an asterisk pbx to play a multicast message.
That takes 7 seconds to start. From its log, the pbx can be seen to receive the notification 7 seconds after the event is initiated and the multicast audio is heard at that time.

The camera system log shows both local sound file playback and https notification starting at the same time.

This latency appears to be coming from the camera itself as other https triggers don't have it. Sometimes 7 seconds can be too long, has anyone else experienced this?


Top
 Profile  
 
PostPosted: Fri Feb 08, 2019 6:48 pm 

Joined: Fri Nov 14, 2014 1:38 am
Posts: 740
M1054 is an entry level camera with a lot of functions (audio, LED), it may be having a high load from all the tasks its doing resulting in the delay. An optimised unit may shorten the latency.

However without the unit's server report, it is hard to tell.

If you are interested in further discussion, please contact me via Skype @ Cheng.Xin.SG


Top
 Profile  
 
PostPosted: Mon Feb 11, 2019 10:46 pm 

Joined: Mon Feb 11, 2013 1:45 am
Posts: 4
Hi Cheng. I guess you are right, can't expect too much from this camera. Later on I noticed that the camera admin webpage was similarly slow to load. The video itself (800x600@10 fps) isn't too demanding, and the only additional tasks are the events mentioned previously so I dont think its the load, but to be honest I didn't check the log.


Top
 Profile  
 
PostPosted: Thu Feb 14, 2019 10:35 am 

Joined: Fri Nov 14, 2014 1:38 am
Posts: 740
Without the unit’s server report, I cannot do much to help. By default, axis camera is already running a lot of services to make it plug and play. So the load and get pretty high for a basic camera


Top
 Profile  
 
PostPosted: Fri Feb 15, 2019 3:47 pm 

Joined: Mon Feb 11, 2013 1:45 am
Posts: 4
I did what you suggested initially and checked the log. The pbx that the camera communicates with has a self-signed certificate that expired in 2017.
I did have the "Validate Server Certificate" unticked, though
Quote:
<CRITICAL> Jan 24 18:50:06 axis-00408cc6b54a httpnotifywrapper.sh: curl failed with status '60': 'curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Can you tell me how to do what the log suggests?
Quote:
If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.', arg: "-s -S -f -L -g --anyauth --connect-timeout 90 --ssl-reqd --capath /etc/certs/event/client/http/0 https://192.168.xxx.xxx/mcast2/index.php?i


Top
 Profile  
 
PostPosted: Sat Feb 16, 2019 11:51 am 

Joined: Fri Nov 14, 2014 1:38 am
Posts: 740
By right with validate cert unchecked, the warning should not even be there. Try generating a new cert


Top
 Profile  
 
PostPosted: Sat Feb 16, 2019 12:18 pm 

Joined: Fri Nov 14, 2014 1:38 am
Posts: 740
The issue is will contribute to the load of the camera CPU. However it is not likely to resolve the issue. Without the server report to analyse the camera activities, I cannot comment much.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

All times are UTC


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
cron
Powered by phpBB® Forum Software © phpBB Group