Will this hybrid AURA/IPO solution work?

[pullings]

This is the scenario:
40 campus locations, each campus has between 100 and 1000 users. Survivability is required at most locations.
At first I put together a CM6 solution (S8800 core) using G450/G430s (digital, analog, and PRI) w/S8300 at each campus.
But then I thought, why not just deploy an IPO at each campus, tie it all together with AURA at the core?
From a cost perspective it sure makes sense.

My question is:
What features and system functionality will I give up by going with the IPO solution glued together w/AURA?
Internal dial-plan is 5-digit.
Target campus architecture will be VoIP.
WAN connectivity to each campus is mix of IP and ISDN, and analog PSTN.
Campus needs to be survivable if AURA is down.

TIA,

P

 

[smokinjoe2938]

why not deploy gateways with an 8300 in each for lsp that way when the network goes down each site will register to its own lsp.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[dialtonebone]

It makes sense from a cost perspective, if you only are looking at the initial cost of the system. Long term that sounds like hell - managing each site individually, not being able to trace calls from one interface, losing all the features of CM at every single site. I don't know why you would purchase CM and then only put IPO out there at all the sites.

If you go all IP Office, just get a Session Manager to glue them all together, not CM though.

If it was my environment, I'd do CM end to end. It's hard to list all the features you lose or gain since they are essentially two different systems with completely different markets. Also, you hurt survivability. If an IPO controller goes down, you need to have another IPO Controller at the site ready to take over. With CM, everything works off the central server - if that fails, then an LSP will kick on locally.

 

[pullings]

Thank you all.
Great feedback so far....I'm sold.
I need to convince the penny pinchers now. I could ring the PM's neck for getting the contracts team all excited about it.
Anyway, each campus will have a central redundant IPO at it's core site. I believe survivability will be handled if a single IPO is installed at each edge building.
Other things I am concerned about:
end-to-end FAX (T.38) is not supported with h.323?
Session manager I will have to research to see how it would fit.
What about VM? Transfer/forward of VM messages outside of IPO?
Dial plan management could be a bear?....there are a lot of campus sites. I suppose each IPO campus will have to be managed independently?

I've been studying up on IPO all day. I'm spent!

 

[montyzummer]

The IPO can be built as a branch soloution by simply ordering a different sd card , you may well want to look at this option instead if cost is the true issue.

http://www.avaya.com/uk/resource/as...b5800 branch gateway - brochure final pdf.pdf

Have a look at the above link.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[dialtonebone]

Session Manager and System Manager would work best with that B5800. It's not really a "connect to CM product".

Yes - each site will need to be managed independently with IP Office. Dial Plans would need to either be strictly enforced by your admins, or you'll have a TON of overhead in day to day maintenance.

Session Manager - think of it as a voice router when you use it connect sites together. "Ext 52xx goes to IPO#5" "Ext 53xx goes to IPO#6" and so on. You could also use Session Manager with CM as an evolution server, which allows you to use some of CM's features but devices still register to SM.

 

[pullings]

I'll look into SM, sounds like the best approach.
PS: I'm new to this Avaya stuff. Their IP solutions have evolved into a nice technology option. Processor-Ethernet sparked my interest...before that I would not touch it with a 10-ft poll!

P
CCVP, CCIE#2xxx

 

[latitude12]

As some have mentioned there is an official version of what you're proposing, I think with IPO 9 the B5800 terminology is gone and it's called 'IP Office Enterprise Branch'. A few points:

1. You have to use SIP endpoints for the centralised model (which I think is what you want). In normal operation the phones register with SM, in a survivable scenario they register with the local IPO.
2. In SMGR 6.3 there is an option for centralised IPO management (but I've never used it).
3. You'll need a CM at the core at least. You can mix and match CM G4x0 gateways w/LSP and IPO for the remote sites depending on size/feature requirements.
4. It's possible to do this same model with other SIP gateways, e.g. Audiocodes gateways in place of the IPOs