406v2 Maximum file size

[jmbjmbjmb]

Customer is a small inbound call centre with an IPO 406v2.
Current config' file size is around 190k. Theoretical max file size is 256k.

Question is...how closely can we get to 256k without running into reliability issues ?? Does anyone have any practical experience here ?

They have won a new contract which will involve a new PRI and a couple of hundred new incoming call routes and hunt groups.

I am thinking that i can get the new config' in under 256k, but with not too much to spare. As i mentioned before, reliability is THE issue.

Thanks in advance

 

[intrigrant]

256k
Why that many DDI's and huntgroeps?
Smart programming can save a lot of memory:
you can setup 400 Incoming call routes costing about 11.8kb
and a huntgroup for each number costing about 39.1kb.

For the incoming call route you can use just one if the groupnumber matches the DDI number:
DDI = 123456XXX
Destination = #
Saves 10 kb

If you need the groups for naming only then use 4.2 software and make a incoming route for each DDI and fill in the TAG for each number.
Route all calls to one group with the same agents, saving you 39kb
Getting rid of the unused shortcodes saves yo memory and there are a lot of entries the customer never use, erase them.

PASMI-500 PA - Implement: INDeX Core
PASMI-600 PA - Implement: INDeX CCM
PASMS-500 PA - Sales: INDeX Core
PASMS-600 PA - Sales: INDeX CCM

132-S-100.3G_R Communication Networking Associate Exam

PASMI-100 PA - Implement: Avaya IP Office Core
PASMI-101 PA - Implement: IP Office Standard Edition
PASMI-102 PA - Implement: IP O

 

[Bas1234]

Or check here IP Office Configuration Size Calculator;

http://marketingtools.avaya.com/kno...light=IP+Office+Configuration+Size+Calculator

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[jmbjmbjmb]

Thanks for the tips. Pruning the shortcode list will definitely be of benefit.

The incoming Call routes/huntgroup setup is a requirement of their 3rd party CallCentre software. This dates back to the early IPO 3.2 days so we may need to stick with this. I'll check with the developer as to whether we can move to 4.2 as suggested.

 

[kholladay]

Even if they can support 4.2 it does not mean that they will reference the call tag in their reports so you will want to check that as well.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M,
ACE Implement: IP Office
TIA-CTP, MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford