User Portal - Remote Access through ASBCE

[vtt2019]

Hi Sirs:
Please someone could give me a guide how to configure USER PORTAL (WebRTC service - TLS port 7444) through ASBCE r10.x to access IP Office 12.0?
I tried to create an APP RELAY in ASBCE but it doesn´t work and there is no info in Tech Docs about this scenario.

 

[derfloh]

Does it work internally?

 

[vtt2019]

Yes, in the LAN is working ok as expected.
My question was about how to access remotely through ASBCE, could you guide me please?

 

[derfloh]

I would configure it as a reverse proxy configuration. You will be able to see the traffic in traceSBC with HTTP monitoring enabled. If the requests are forwarded to IPO you have to watch the SysMon trace with default filters plus http and DNS.

 

[sizbut]

Never done it but done you need to be using the TURN/STUN configuration within the ASBCE.

Avaya Documentation

documentation.avaya.com

 

[Albus2]

TURN/STUN is needed if you plan to allow the user to make WebRTC calls via this browser session.
But first, the user needs to log in. This is where it stops for me. (I just want to allow users to configure personal options, i.e. without WebRTC as they have Workplace)

This is what I did:
In SBC, create a Reverse Proxy.
Listen IP is your public side, protocol is HTTPS with a public certificate.
Connect IP is the internal Interface, again HTTPS and the ID-Cert from the system.
Listen Domain is a FQDN for that purpose, like userportal.customer.com
Server Address is your IPO with port 7444, i.e. 192.168.42.1:7444 and Whitelist URL is just /

Effect: I can reach the login page of User Portal.
But no matter what user and password I try, there is a system responds "System not available at the moment".
This does not change with correct/invalid usernames.

The user shall open a webbrowser for userportal.customer.com which is then connected to https://userportal.customer.com/userportal/index.html
Of course, when trying the same from inside the LAN, all is OK. However, https://192.168.42.1:7444 must be used.


If someone can comment on that, or is able to successfully log in via SBC, please let me know!
As a second step, I could also try to enable WebRTC, but that makes no sens until a simple login is possible.

 

[derfloh]

I would configure it as a reverse proxy configuration. You will be able to see the traffic in traceSBC with HTTP monitoring enabled. If the requests are forwarded to IPO you have to watch the SysMon trace with default filters plus http and DNS.

Check what happens in Monitor. Maybe the IPO sees a connection to the FQDN but cannot resolve the FQDN itself