openUC Reach 2 assistance?

[mkitchi...@gmail.com]

Hey all, it I has been a while. I used to be very active here, but had to focus my time elsewhere a few years ago. Still see some familiar names in the group. We have a formerly eZuce supported Reach 2/17.10 install that is having some issues. Is there anyone out there that might have any tips on this? 

There was a bug in a call recording cleanup script, and it caused the files system to run out of space. We fixed that, and didn't realize for a few weeks that there was another problem. Reach reporting and listing to call recordings do not work properly. Call recordings are actually there. It just says "Audio file not available" when you try to listen to them. We accidentally found that if you access them by http instead of https, they do work. Reporting in Reach doesn't work at all. The progress indicator on the page just keeps going. Someone on our team found this in their research "The web browser makes repeated POST requests to an /auth endpoint which responds with an empty response and the cycle repeats."

I have tried everything I can think of on our end. I have resent profiles, I forced a reinstall of all openUC, Reach, etc. rpms, and updated everything else on the server. This is a dedicated Reach server with no other functions. We have plans to move off of this solution next year, but I need to get it fixed now if possible. 

Hopefully there is someone out there that has come access something similar. 

Thanks,

Matthew

[mkitchi...@gmail.com]

I installed a fresh 17.10 server with Reach, and did nothing else. Everything stock. The Reach reports tab on that one does the exact same thing....

[mkitchi...@gmail.com]

If anyone is interested, we got it at least semi-functional. We were able to extract some config files off of a fresh 17.10 build and recreate them on our production server. The only remaining issue is Reach call recordings can't be accessed over https, but it is possible that issue existed before our most recent problem. 

[Iuliu Blaga]

You should use the stage version, not the stable. It has many fixes over the 'stable'

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/6c3a6619-9ba2-4f2f-a410-c4afee43651dn%40googlegroups.com.

--

 

Iuliu Blaga Sr. Support Engineer 215.297.4400 x 751 Arbor Way, Arbor Crest I, Suite 150, Blue Bell, PA 19422 coredial.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

[mkitchi...@gmail.com]

Thanks for the reply! I believe that is what we have been using. It was installed with this repo file:

baseurl=https://***:***@download.ezuce.com/openuc-stage/17.10-unstable/CentOS_6/x86_64/

On Thursday, December 29, 2022 at 5:19:50 PM UTC-6 ibl...@coredial.com wrote:

You should use the stage version, not the stable. It has many fixes over the 'stable'

On Friday, December 30, 2022, mkitchi...@gmail.com <mkitchi...@gmail.com> wrote:

If anyone is interested, we got it at least semi-functional. We were able to extract some config files off of a fresh 17.10 build and recreate them on our production server. The only remaining issue is Reach call recordings can't be accessed over https, but it is possible that issue existed before our most recent problem. 

On Thursday, December 29, 2022 at 1:39:50 PM UTC-6 mkitchi...@gmail.com wrote:

I installed a fresh 17.10 server with Reach, and did nothing else. Everything stock. The Reach reports tab on that one does the exact same thing....

On Wednesday, December 28, 2022 at 12:03:02 PM UTC-6 mkitchi...@gmail.com wrote:

Hey all, it I has been a while. I used to be very active here, but had to focus my time elsewhere a few years ago. Still see some familiar names in the group. We have a formerly eZuce supported Reach 2/17.10 install that is having some issues. Is there anyone out there that might have any tips on this? 

There was a bug in a call recording cleanup script, and it caused the files system to run out of space. We fixed that, and didn't realize for a few weeks that there was another problem. Reach reporting and listing to call recordings do not work properly. Call recordings are actually there. It just says "Audio file not available" when you try to listen to them. We accidentally found that if you access them by http instead of https, they do work. Reporting in Reach doesn't work at all. The progress indicator on the page just keeps going. Someone on our team found this in their research "The web browser makes repeated POST requests to an /auth endpoint which responds with an empty response and the cycle repeats."

I have tried everything I can think of on our end. I have resent profiles, I forced a reinstall of all openUC, Reach, etc. rpms, and updated everything else on the server. This is a dedicated Reach server with no other functions. We have plans to move off of this solution next year, but I need to get it fixed now if possible. 

Hopefully there is someone out there that has come access something similar. 

Thanks,

Matthew

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/6c3a6619-9ba2-4f2f-a410-c4afee43651dn%40googlegroups.com.

[Iuliu Blaga]

Yes, this is the latest released version of Uniteme with Reach 2

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/59f8ef1d-9bbd-4cb7-a577-a098b1644a10n%40googlegroups.com.