Time Frame To install 30,000 stations

[learn2shoot]

Yes you read that correctly - 30 thousand phones.

I am a contractor at a client site and may need to install 30,000 Avaya phones. I wanted to get a few ideas on how long this would take, this time frame would need to include programming the station (assuming a dup sta), unwrapping the phone, placing the phone, establishing a connection and assigning a number and removing old phone and tossing it into a tub/dumpster.

This is spread over 40 sites ranging in size from 6 seats to over 6200 seats. I am putting together a project plan and need to at least throw out a few figures for date frames. How many people would it take to install and spot test 6,200 phones in a weekend? I could stage phones all week but the placement would likely need to be done on a weekend.

Do you by chance know how many 9620s fit on a pallet?

 

[learn2shoot]

@wildcard - hijack no problem - We are likely deploying to a single CM however I think my situation is simpler because all 40 locations are located in a single metropolitan area, so nothing is longer than 20 miles from the main CM.

I believe that most sites will have an ESS, some with a remote shelf, others will simply hang off the main via IP. No sense installing an ESS for 6 phones.

 

[wildcard100001]

Thanks Mitch, thanks learn2shoot.

Learn2shoot, if you go all IP isn't there a CM limitation of 12,500 IP phones? Perhaps that is an old stat... it does not include max number of TDM phones with it. Something to think about or at least look into. I'm wondering about this myself.

Mitch, architecturally speaking I'm hesitating to integrate any locations cabinet signaling traffic across continental boundaries. I'm wondering if others feel the same way. Example I have a few sites in South America and in the Asia PAC region... really not enough users or locations to create a Core in the region. And I don't have confidence in our data network links to those locations. I'm already at 260ms RTT or greater. So far I've suggested to my Latin American and Asia PAC friends to go to CM 5.2.1 for each site and link them into the N. American core or Europe Core via SIP. I assume this is my best option at the moment. I'm thinking a weak link that has a G450 on the end of it will result in a very poor experience. Even with QOS in play I envision phone features such as hold, transfer etc all of sudden stop working... then starting to working on short intermittent network outages. Do you have any guidance in this area? Such as don't do this if x is this and y is that.

thanks,

Wildcard

 

[Mitch672]

260ms is too long, you are going to get echo/delay, not to mention dropped UDP (voice) packets as well. anything over 150ms is problematic, and can be detected by even casual users.

I would say keep those sites as independent switches, with local PRI/POTS lines and try the SIP trunks to a few other sites, see how those calls sound. I suspect even SIP will not save you in your situation, and the phone call quality will be poor. You might just have to use the local PRI for long distance/international calls to/from those remote sites, and I bet even then you might have some issues as well (even the carriers use satellites/fiber and have echo/delay issues sometimes)





Mitch

AVAYA Certified Expert