AWS hosting tips and tricks if any.

[stressed_technician]

I'm curious to know what size instances have been spun up on AWS for hosting an IPO and if there are any tips or tricks.

We do a lot of subscription systems and the majority of our clients are less than 10, our distributor spun a lot of these up and they said they are T2.small.
I spun one up yesterday but I'm getting a high CPU utilization with no phones connected and it's just idle.
I can't see what the difference is between what our distributor has done and what I've done.
What threshold counts as high and is it adjustable, when I did have a phone connected and made calls it was fine.

All of them have one-x disabled so it's not chewing up resources and when I check the platform view on 7071 the services aren't using many resources either.

Need to make this work as we had to swap distributors and they use T2.medium which works but is more expensive and since we have a lot running on t2.small that works I would like to still offer this.

 

[sizbut]

Its your choice and your risk. Avaya's own profiling figures (

https://documentation.avaya.com/bun...rver/page/Primary_and_secondary_servers.html)

say m5.large for a small 20 user system without one-X Portal.

That would come from testing that solution at full call capacity (those poor 20 users each somehow handling a 1000 calls per hour) and then I assume adding some fiddle safety factor like +20%. If your customers are happy on a lot less that's not a surprise, but it would be an issue if you ever needed to get support from Avaya.

Stuck in a never ending cycle of file copying.

 

[stressed_technician]

Thanks sizbut I have one client with 200 ends on an m4.large running for 3 years without a problem, we have ACR running on t2.micro for this amount of users as well and it hasn't missed a beat.
I was just curious to see what others have done regarding setups for their clients and particularly the smaller systems with 10 or fewer users.
I don't think we'd sell as many systems if we had to quote and sell an m5.large for a 10-user system.

 

[joul]

Would it be possible to let different small companies share a larger IPO?
I once worked at a company where we had an offer/service where all the users hade the same provider in a "shared trunk" with several number ranges in it. Users in the system would be Xdirectory, so the could not use the phonebook button and User Rights shortcodes preventing them to dial another company's internal extensions by mistake. We had about 20 customers in it with 3 - 30 extensions per customer.

 

[ipohead]

Joul that's called tenancy but this isn't a feature of IP Office although there are some workarounds.