yeti-web
yeti-web copied to clipboard
Yeti admin interface. Opensource SIP SBC with billing.
Currently pgq-processors still using email to notify engineer about exception. Email support should be removed and Sentry should be added
``` Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.181145 ] [ INFO]: Processing by Api::Rest::System::JobsController#run as JSON Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.181203 ] [ INFO]: Parameters: {"id"=>"EventProcessor"} Jun 6 20:26:01 host...
## Description add config to control the behavior of the CallsMonitoring job introduces new configuration options in yeti_web.yml to control the behavior of the CallsMonitoring job when dealing with disabled...
## Description ## Additional links https://demo.yeti-switch.org/doc/api/customer/v1/transactions/get_listing.html #### error with backtrace ``` Started GET "/api/rest/customer/v1/transactions?filter[created-at-gteq]=2024-08-11T18%3A37%3A39.583Z&filter[created-at-lt]=2024-08-12T18%3A37%3A39.583Z&include=service" for ::1 at 2024-08-12 21:37:39 +0300 System::ApiLogConfig Exists? (2.5ms) SELECT 1 AS one FROM "sys"."api_log_config" WHERE...
Currently CallsMonitoring terminating calls in case of disabled/deleted customer auth, origination gw, termination gw. We have to allow flexible configuration for this. 1. add configuration attributes in yeti_web.yml like teardown_on_disabled_customer_auth:...
when CDR replica connection present in database.yml then such resources should use it to fetch CDRs: - **/cdrs** page - **/api/rest/admin/cdr/cdrs** API controller - **/api/rest/customer/v1/cdrs** API controller - **/api/rest/customer/v1/incoming-cdrs** API...
Hi team, Under Realtime Data -> SIP options Probers Click on the "ID" Hyperlink, and the hyperlink appears to append "/1*(Prober ID)" to the URL. This results in redirection to...
we need ability to modify CDR metadata via API