API saveEventRule not creating new event rule in the system

Answered

Permanently deleted user

November 24, 2020 12:59

I am creating a new event with saveEventRule API. Using the Body parameter gets from

getEventRules API.I am receiving response code 307 and the event is not created on the system.

 

I have tried without Id parameter in the body also tried with Id. The passed Id of the event is created from this link. here

 

Here is the Body I am using.

 

 

"actionParams": "{\"allUsers\":false,\"authType\":\"authBasicAndDigest\",\"durationMs\":5000,\"forced\":true,\"fps\":10,\"needConfirmation\":false,\"playToClient\":true,\"recordAfter\":0,\"recordBeforeMs\":1000,\"requestType\":\"\",\"streamQuality\":\"highest\",\"url\":\"https://3527cf917aa0582b58491d964012a01b.m.pipedream.net\",\"useSource\":false}",

"actionResourceIds": [],

"actionType":"execHttpRequestAction",

"aggregationPeriod":2,

"comment":"",

"disabled":false,

"eventCondition":"{\"eventTimestampUsec\":\"0\",\"eventType\":\"undefinedEvent\",\"metadata\":{\"allUsers\":false,\"level\":\"0\"},\"omitDbLogging\":false,\"reasonCode\":\"none\"}",

"eventResourceIds": [],

"eventState":"Undefined",

"eventType":"softwareTriggerEvent",

"id":"{5ee7ad5d-46f4-4cf3-8d78-7061a6890f87}",

"schedule":"",

"system":false

 

 

Please share solution for this issue

 

0

• 

  Wendy Chuang

  • Network Optix team

  November 25, 2020 06:44 Edited

  Hello @...,

  The API payload looks correctly and the rule could be created on my test server.
  Based on your description, the HTTP status code is 307 Temporary Redirect.
  It might be caused by the URI or network environment.

  Could you please collect the Wireshark packet when you calling the API and share it with us?
  You may find out the instruction here to capture the packet file. 

  Thank you.

  0
• 

  Andrey Terentyev

  • Network Optix team

  November 27, 2020 19:40

  Hello Deep,

  What version of Nx Witness are you using?

  Could you share, please, the full URL of your request of the full code you request with?

  0
• 

  Permanently deleted user

  November 30, 2020 06:05

  Hi Andre

   

  This issue is beacuse of  VMS URL I check this on get API and my VMS proxy URL got change from "relay-ny.vmsproxy.com" to "relay-la.vmsproxy.com". And this issue not showing now can you tell why this URL got change.

  0
• 

  Permanently deleted user

  November 30, 2020 09:25

  URL is chosen dynamically between several servers based on availability and optimal connection

  0
• 

  Permanently deleted user

  November 30, 2020 10:25

  So if in future if URL change again then I will get the same error how can we avoid this in future.

  0
• 

  Anton Babinov

  • Network Optix team

  November 30, 2020 16:57

  When responding with status code 307 "Temporary redirect", Cloud sends you 'Location' header with the URL you should use for your request. This is how the Cloud handles load/geo balancing for incoming connections. This shouldn't be considered as an error, it's part of normal communication flow between API Client -> Cloud API Relay -> VMS server.
  I would suggest implementing a separate handler for 307 responses in your HTTP client. Upon receiving HTTP status code 307, the HTTP client should repeat the request without changing the request method to the URL, specified in the Location header of the server's response.

  0

Please sign in to leave a comment.