Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

System larger than 384 for 1 site - No IP

Status
Not open for further replies.

G0G3tt3r

Programmer
Nov 11, 2009
141
US
IP is not allowed for this customer.
Equinox mobile and portal for both systems
VMPRO duhh
No other packages

I have customer that would like to go to around 500 Digital and analog (Total 500)I know the restriction of the 500v2 but will an SCN tying 2 together be a viable solution?
Honestly, see no downside except web management for users between 2 ip addresses. I could solve that by having an analog only system and a digital only system.
Digital users will be the only ones wanting to access that feature anyway. What potential disaster am I missing here.
 
Add another ip 500 v2 and scn them together, have customers that have done just this.
 
For me this sounds like i would run far away.
No IP! in what year do they think they live?

BAZINGA!

I'm not insane, my mother had me tested!
 
+1 for the above comment , equinox and portal .......get ready for lots of shit storms.....but good luck

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.
 
Dot do it

Trying to bodge round system limitations is always a recipe for disaster.

unless you do this properly with a server edition (& ip500V2,s a expansion servers) It will rapidly become an ungodly mess & almost totally nu-maintainable




Do things on the cheap & it will cost you dear
 
Not sure how the equinox / portal thing will play out. I've done this (without the uc stuff) with 2 IP500's, I made all digital endpoints hotdesk users and taught them to login, that way they could deploy any digital phone to a live jack & move offices and simply log in over the top. After 10 years it's still working and only had to switch out the PSU on the IP500.

Equinox and portal? Why both? Just get them hooked up on Equinox (F*&$ OneX portal) Equinox is the direction Avaya is going. It's a little limited right now, but should be getting it's kinks worked out soon.
 
Equinox only is what I meant. I am not really sure why I would need a Server Edition on this. I don't see the benefit in this case.
 
We have a retirement community set up that way, mostly single line phones in residences, 2 IPOs SCNed together. Not really to much to manage, open the configuration with SCN discovery and it's very much like programming an SE
 
gog3TT3R said:
Equinox only is what I meant. I am not really sure why I would need a Server Edition on this. I don't see the benefit in this case.
come back in 56-12 months when you are experiencing maintenance hell due to all the moves changes &configuration modifications the customer requires.

TTT's example is probably OK as they are effectively separate offices & quite small, which is the original design intent for SCN.


it is never a good idea to install a system when it is already stretching capacity limits, check my signature


Do things on the cheap & it will cost you dear
 
This seems like a bad idea. Yes, technically it will work, but it sounds like it will be a pain to manage--especially with that many Equinox users. IPO can be wonky with just 100-200 users, let along 500.

IMHO, a system designed for a larger environment--a "real" PBX seems more appropriate. Like Aura/CM or similar.
 
What a bullshit.
The ipo is designed now for 3000 user and then it will not be wonkey if it is programmed as it should be.
It works fine except for some bugs which every system has.


BAZINGA!

I'm not insane, my mother had me tested!
 
My previous company had exactly this setup.
Around 600 phones between two systems.
No issues
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top