cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
260
Views
0
Helpful
3
Replies
Highlighted
Beginner

CMS 2.9 - Web App "System is currently unavailable. Please try again later"

I have deployed CMS 2.9 in our lab to have a look into the new Webbridge3 component, however when browsing to the web page to join a meeting i receive:

 

"

System is currently unavailable.

Please try again later

 

Anyone else had this during their upgrade/deployment?

 

Webbridge3 and Callbridge certs configured accordingly - these are self-signed for now.

 

Thank you

Everyone's tags (2)
3 REPLIES 3
Highlighted
Beginner

Re: CMS 2.9 - Web App "System is currently unavailable. Please try again later"

can you post the webbridge3  configs and status?

Highlighted
Beginner

Re: CMS 2.9 - Web App "System is currently unavailable. Please try again later"

Sure,

join.lab> webbridge3

Enabled : true

HTTPS Interface whitelist : a:443

HTTPS Key file : lab.key

HTTPS Full chain certificate file : lab.crt

HTTP redirect : Enabled, Port:80

C2W Interface whitelist : a:9999

C2W Key file : lab.key

C2W Full chain certificate file : lab.crt

C2W Trust bundle : lab.crt

Beta options : none

 

API config:

 

<?xml version="1.0"?>
<webBridge id="fd32edc4-5c11-4f54-9e28-6dc9c4d5cd74">
  <url>c2w://join.lab.cloudrooms.co.za.lo:9999</url>
  <resourceArchive></resourceArchive>
  <resolveCoSpaceCallIds>true</resolveCoSpaceCallIds>
  <resolveLyncConferenceIds>true</resolveLyncConferenceIds>
  <idEntryMode>legacy</idEntryMode>
  <allowWeblinkAccess>true</allowWeblinkAccess>
  <showSignIn>false</showSignIn>
</webBridge>

Highlighted
Beginner

Re: CMS 2.9 - Web App "System is currently unavailable. Please try again later"

can you turn on detailed logging, Sip trace, api , and dns and webrtc logs.

 

and then try to go to that webbridge link, basically reproduce the issue and then post the log bundle here?

 

also i imagine you did the below already too:

 

A port must be opened on an interface (using webbridge3 c2w listen) to allow the
callbridge to connect to the webbridge3 (the webbridge listens on that port). This is why
you have to give the address with this port when you do the APIrequest to tell a callbridge
about this webbridge. This connection must be secured with certificates.