I have implemented the feedback channel with the KeyedAppStates in my application.
I'm calling KeyedAppStatesReporter.setStatesImmediate(hashSetOf(state)) where state is a keyedAppState created with the builder, but nothing is reported on the AMAPI side.
The profile/policy is set correctly, the ApplicationReports are activated, the application can receive managed configurations correctly when send from the EMM and apply them.
I tried with the Test DPC following the tutorial "Test app feedback". And the Test DPC received the feedbacks send by my application.
Screenshot of the Test DPC notifications
What could be blocking the reporting of the keyedAppStates to the AMAPI with the real DPC ?
It was an issue on the DPC/AMAPI side.
The issue was resolved with a DPC update not long after, and now it works with the example from the documentation.
Related
We have a Multitrack web conference implementation using AMS 2.4.1 version. Its working great for our use case, except in one scenario. When there are N (< 3) number of users and they on there camera simultaneously, then few remote users are not rendered as we don't receive the video tracks for those users in newStreamAvailable. We only receive the audio track for those users. We are able to reproduce this quite frequently.
As a backup, I am trying to poll AMS using getTrackList with the main track Id to get all available streams, but I am not getting any message trackList
var jsCmd =
{
command : "getTrackList",
streamId : streamId, // this is roomId or main track id
token : token
}
Any insight would be helpful.
Thanks,
We were able to resolve the issue, posting here to help anyone who might be facing a similar issue.
With push notifications from the server, we might encounter issues when for some reason push operation doesn't succeed. In that case, it's better to have a backup plan to pull from the server and sync.
The Ant Media Server suggests pulling the server periodically for the room info. The server will respond with active streams and the application should synchronize.
For reference, please refer to following link https://resources.antmedia.io/docs/webrtc-websocket-messaging-reference
I often use Firebase phone auth in my applications. I have one user who religiously sends "STOP" to all text messages. Big oops. Now she can not login to any application using the system...
Short code phone # = 44398
If the user types "STOP" to that short code, the system responds with:
Firebase: You are opted out and will receive no further messages. For
HELP, reply HELP. Msg & Data rates may apply
Type "HELP", the response is:
Firebase: For more info: https://firebase.google.com/support/ -
Msg&Data rates may apply.
My question. How do you "RESTART" the service? The Firebase support page offers no help here.
I've tried "GO", "RESTART", "UNSTOP". All of those fail.
Here's a posting on how Twilio addresses the topic. Twilio uses START, YES and UNSTOP to restart a service (on long code source). Each of those fail here.
Twilio also provides a link to standards for short code expressions., but I'm not seeing anything on restarting a service.
Here is a screen shot (of my phone):
I am using spring-boot-1.4.0. In my project i am using sentry for logging, sometimes log events are not reflected in sentry.While browsing google about this issue i saw something called "Raven-Sentry" but it was written using Python. Is there any Raven-sentry available for spring-boot.I am using following Raven-callback but still I am unsure how to curl or create a rest endpoint which would let me know the status of sentry whether it is up or down. Please let me know for any more details even i am ready to provide a code samples if needed.
Your help should be appreciable.
As per Brett comments I have updated my question by providing Python Sentry connection test link:
Python-sentry-test
In the above link they are running the test to find out connection to sentry is successful or not. Similarly i want to check the connection to sentry is successful or not via spring-boot.Also i would like to add sentry status to health check, so that when ever my logging events are not reflected in sentry, immediately i will flip the health of sentry to down.
I'm trying to use the PayPal Express sandbox (which I have to over 5+ years) and all of a sudden, I'm getting this error. I'm running the latest Chrome on a Windows 2012 server that's up to date. It's happening on the first call to PP using SetExpressCheckout. Where do I start looking for the cause?
After a week of trying to get help from PayPal support, I accidentally came across this link: https://www.paypal.com/webapps/mpp/ssl-security-update that let me to the fix. Support never mentioned it.
The key is to actively use TLS 1.2 in your code. It's not enough to just have your server hardened (we were showing an "A" rating on SSLlabs.com). I put the following immediately before the instantiation of WebClient:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
Connected to PayPal without a problem after that.
I'm trying to follow Solomon Messing's guide to using MTurkR to programmatically create Turk HITs. While I seem to successfully create HITs from my MTurk Requester sandbox, they don't appear on my Worker Sandbox. In fact, the Account Tab on the Worker Sandbox says 'This data is temporarily unavailable' and the HITs tab displays 'Your request was not completed successfully'. Any thoughts on debugging this are appreciated.
The issue here is how you're specifying the sandbox parameter. Note that every MTurkR function can operate on the sandbox or the live server. The default is the live server, unless you tell it otherwise. Your code creates the HIT in the sandbox but then you check to see its status on the live server (by not including a sandbox = TRUE argument in HITStatus).
As you can see here, your HIT is posted to the sandbox so the CreateHIT operation was successful.
You either need to pass sandbox = TRUE to all function calls, or use the global option options(MTurkR.sandbox = TRUE), which will allow you to operate in the sandbox without specifying it explicitly in each function call. This is helpful if you want to run your code on the sandbox to try it out and then run the same code on the live server: you can just change the global option and then everything will run as intended on the live server.