Replies: 4 comments 4 replies
-
|
This automatically generated reply acts as a friendly reminder. Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them. If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines. |
Beta Was this translation helpful? Give feedback.
-
|
Wireshark trace maybe helpful |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jbadu3 , doorbell 408 doorbell 408.zipHTTP/1.1 408 Request Timeout
Date: Thu, 12 Dec 2024 14:34:22 GMT
Server: Apache/2.4.62 (Unix) OpenSSL/3.0.15
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'self'; frame-ancestors 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.axis.com mediastream: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.googletagmanager.com https://www.google-analytics.com https://ssl.google-analytics.com https://*.axis.com; style-src 'self' 'unsafe-inline'; img-src 'self' https://*.google-analytics.com https://*.googletagmanager.com https://*.axis.com data: blob:; media-src 'self' mediastream: blob:; object-src 'none'
Authentication-Info: rspauth="50717a803f04dbc6c9ca6d7206d4e811", cnonce="e38a3407c795dab0", nc=00000002, qop=auth
Upgrade: h2
Connection: Upgrade, close
Content-Type: text/html
Transfer-Encoding: chunked
<HTML><HEAD><TITLE>408 Request Timeout, The server timed out waiting for the request.</TITLE></HEAD>
<BODY><H1>408 Request Timeout</H1>
The server timed out waiting for the request.</BODY></HTML>lab 400 lab 400 pcap.zipHTTP/1.1 400 Bad Request
Date: Thu, 05 Dec 2024 18:43:08 GMT
Server: Apache/2.4.62 (Unix) OpenSSL/3.0.15
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'self'; frame-ancestors 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.axis.com mediastream: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.googletagmanager.com https://www.google-analytics.com https://ssl.google-analytics.com https://*.axis.com; style-src 'self' 'unsafe-inline'; img-src 'self' https://*.google-analytics.com https://*.googletagmanager.com https://*.axis.com data: blob:; media-src 'self' mediastream: blob:; object-src 'none'
Authentication-Info: rspauth="dac6bab3c2d4e7e5deb2a49c4e934456", cnonce="e92d8248803b8513", nc=00000001, qop=auth
Upgrade: h2
Connection: Upgrade, close
Content-Type: text/html
Transfer-Encoding: chunked
<HTML><HEAD><TITLE>400 Bad Request, The request had bad syntax or was inherently impossible to be satisfied.</TITLE></HEAD>
<BODY><H1>400 Bad Request</H1>
The request had bad syntax or was inherently impossible to be satisfied.
</BODY></HTML> |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to re-open it OR share the solution/alternative/comment if already resolved👁️🗨️ |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I am working on an integration of Axis two way audio features with my company's ecosystem. We connect Axis cameras through our streamed video recorders through ONVIF/VAPIX. However, for several different models (I8016, M2036 paired with Horn, P3268LV paired with Horn, etc) I see various errors when I try to talkdown for audio out through the camera. Sometimes when I start talking, I'll see
400 Bad Requesterrors as I click on the microphone to speak, random408 Request Timeouterrors in the middle of talking sessions, or extremely garbled audio quality. My team is trying to investigate why the camera might be getting these bad requests or timing out mid session, but haven't been successful to find the root cause. The camera event logs and SSH logs have not told us any useful information, nor do any packet captures. Any knowledge on these errors would be greatly appreciated, thanks!Beta Was this translation helpful? Give feedback.
All reactions