Remote worker via SBCE

[mjm23]

Hello Avaya experts! I am setting up remote workers via our ASBCE and planning to use AAfD and IX Workplace. I am already done with the SBC and SM integrations and now in the testing stage.

1. I first tried with the IX Workplace. I can see that my endpoint is trying to register to SM but the SM is sending a 404 Not Found (No route available) response to the SBCE. What could be the reason that causes this? Not sure if I missed something but I already have a SIP station configured. It is working when I register it within the internal network.
2. For Avaya Agent for Desktop, what should be the IP address of the license server? Should I assign another public IP for my SMGR (License server)?

Thanks in advance!

 

[kyle555]

You'd want to use a reverse proxy on the SBC - you'll have one for PPM and you'll have another other web services - presence, AADS, WebLM, etc.

I'm sure there's a way to make everything work with 1 IP but I never got around to it.

If this is a lab and you don't plan on registering any hard phones or if you read AAfD docs already (I haven't) and webLM can work on 52233, then 1 IP is fine.

You'll probably need to rejig the SBC's port ranges if you want to build a reverse proxy on 52233 as that port is typically reserved for RTP. Somewhere in the SBC you define which ports are eligible to be used for signaling interfaces or media interfaces and you'd need to free up 52233.

Otherwise you'd use 443 for webLM which probably works too.

But to have 2 reverse proxies for PPM and webLM on the same IP and port, you need to configure listen domains on them.

Say you got sm1.xxx.com and webLM.xxx.com, you'd have 2 reverse proxies with the same listen port and IP but you'd have to put the FQDNs in the listen domain.

When the SBC gets the web request for PPM from either client, it'll see

HTTPS://sm1.xxx.com/...

and it will trigger the PPM reverse proxy. If it seems webLM in the URL of the HTTP request, well then it'll trigger that proxy.

The problem I've always had with hardphones is that they always seem to request PPM on the IP and not the FQDN - I'm sure there's some way around that - but, if a request comes in on a IP, it won't trigger any reverse proxy. You'd have to have the listen domain blank. BUT if you have the listen domain blank for the PPM proxy, that will override any other proxy on the same IP and port with a listen domain defined.

That's why I'm saying if you're just using softclients, it should be fine on 1 IP on 443.

Just make sure to regenerate your cert for the SBC so it has the SM fqdn and the SMGR one for the WebLM request.

 

[mjm23]

Thanks for the inputs! I think I map a plan and try different scenarios based from your recommendations. I appreciate it!

Can you help on my 1st inquiry as well please? Thanks in advance!

 

[kyle555]

compare a working register vs a non-working register.

If you goofed a domain in a topology hiding profile, maybe the @domain part is wrong and causing SM to 404 on you.

Otherwise, you can't have an entity link to SM from the SBC on the same IP/port that you're registering from. If there's an entity link on that IP/port, then it must be a trunk.

 

[mjm23]

I did figure this out. Apparently, the extension information wasn't saved when Workplace is trying to register. I updated the fields and got through. Thanks for the inputs!