IPOffice with SBCE 1

[Jerom]

hi,
i have IP Office 11.1 FP2 with SBCE 10.
ix workplace is configured and internally working fine. can see feature and able to call each other.

when connecting through SBCE the Phone getting Registered and we can Call each other. but not showing the features and showing the errors like below.

Contact Service Problem
Voip Service Limited
call history could not be updated.

5061 and 443 Ports are open.
can anybody advise why this may be happening.

 

[derfloh]

IPO probably blocks connection to port 443. Or the reverse proxy isn't configured correctly.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[derfloh]

Or a certificate issue

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

@ derfloh
Reverse proxy Configured with port FQDN:443

 

[derfloh]

All URLS allowed?

Valid Certificate?

WebSocket allowed?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

@derfloh
All URLS allowed? dint get that!

Valid Certificate? Yes

WebSocket allowed? Yes(SBCE)

 

[derfloh]

In Reverse Proxy do you Filter for specific URLs or do you have just an entry with /

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

its entry entry with /

 

[derfloh]

What does a traveSBC with HTTP enabled tell you? What does a IPO SysMon trace with HTTP filter enabled look like.

We need more information.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

Appreciate your quick reply derfloh.
i am new to SBC and not much idea about this to explain. Sorry

can you please let me know, from Internet what are the ports should be opened and is there anything we need to add in the 46xx settings of IPO ?
PPM should be configured in SBC ?

 

[derfloh]

No PPM. You need to forward Ports 5061 and 443 TCP and a valid RTP port range (UDP) to the public interface of the SBC.

Then you need to configure Server and Subscriber flows as well as reverse proxy with valid certificates.

Hard to solve it by guessing what you all did or didn’t… The SBC is not a beginner‘s device

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

Hi derfloh
it was Port Issue and fixed by the Firewall Team(wrong port Opened).
now when we access from outside we have to NAT the IPO FQDN to the Public IP. 193.22.xxx.13 --> ipofffice.comany.com .
when we access the FQDN(

https://ipofffice.comany.com/46xxsettings)from

outside we can get the 46xx settings file and Application is working fine ( Configured with web URL). but the customer don't want to do the FQDN to be accessed from out side(as anybody can access to the 46xxsettings), instead they want to manually configure the Public IP in IX Application to make the application work.

if we do the "Manually Configure" in IX workplace, it will not work properly.. it again gives the Contact Service Problem error.

any solution for this...?

 

[jamie77]

Using the just public IP will not work for TLS. The certificate will not match, as the public IP is not part of the cert (and is not allowed on a cert from a public provider).

It will not do what the customer wants. You need to allow it to work using the FQDN.

Just turn on "Avaya HTTP Clients Only' in the system page. Then only devices showing themselves to be an Avaya device will get the 46xxsettings etc.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[derfloh]

You can also copy the contents of the autogenerated 46xxsettings.txt into a new abcde12345.xyz file and enter this filename into the client. The ASBCE can allow acces to specific URLs so that 46xxsettings.txt will not be accessible from outside.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

Thanks jamie77 and derfloh for the input.

@derfloh > in that case, if we do any change in IP Office, this renamed settings file(eg: IPOSETTINGS.txt) will go get updated right ?

 

[derfloh]

It will not be updated. But in the reverse proxy config you can also forward your own filename to 46xxsettings.txt

But this file will not be reachable if you are in the local network and bypass the SBC.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Jerom]

Hi ,
the Registration through SBC to IPO is Happening now. the IX clients are working fine in Windows, Android, iOS.
when Login with Windows Clients after 1 minute we can start calling to other number and can receive calls.
BUT from android and iOS, once we login with the Extension, after 6 minutes only we can make calls. but we we can receive calls immediately after registration.

any idea why this 6 - 7 minutes delay after registration to make a call..?

 

[Jerom]

Hi,
can i get a help on the above please..

 

[G van Hamburg]

Hi Jerom,

Sorry for what I am about to say, and I am not trying to be rude. All the questions you ask are not really SBCE questions. Using the (or any) client through the SBCE is the next step. You first need to understand how the workplace client works in combination with the IP Office. Once you understand that, you will have better understanding how to configure that on the SBCE. And as I read this thread the SBCE security is not set, so that is a real big risk.

If you are an Avaya Business Partner who will do this work, make sure you understand the provisioning part before you start with the SBCE and SBCE security.

Freelance Certified Avaya Aura Engineer