What are config limitations for 412??

[mwiddows]

Loading a very large config onto a 412 version 3.069 as follows:

1200 users
1100 ICR's

Most of the users are "phantom" users with no physical phones. After adding users and ICR's with manager, we run it through Wizard to check for errors and get a weird error (sorry in advance for the size of this post, just want all of the info there):

************** Exception Text **************
System.ArgumentException: '1152' is not a valid value for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at IPOffice.Wizard.DialPlanForm.ReadData()
at IPOffice.Wizard.DialPlanForm..ctor(SmallOfficeContent soContent)
at IPOffice.Wizard.HardwareForm..ctor()
at IPOffice.Wizard.MainForm.UpdateUI()
at IPOffice.Wizard.MainForm.wizardTreeView_AfterSelect(Object sender, TreeViewEventArgs e)
at System.Windows.Forms.TreeView.OnAfterSelect(TreeViewEventArgs e)
at System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
at System.Windows.Forms.TreeView.WmNotify(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
Wizard
Assembly Version: 3.0.24.0
Win32 Version: 3.0.24.0
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/Wizard.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
FullConfig
Assembly Version: 1.0.2080.25697
Win32 Version: 1.0.2080.25697
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/FullConfig.DLL
----------------------------------------
Utilities
Assembly Version: 1.0.2080.25692
Win32 Version: 1.0.2080.25692
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/Utilities.DLL
----------------------------------------
ValidatingConfig
Assembly Version: 1.0.2080.25695
Win32 Version: 1.0.2080.25695
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/ValidatingConfig.DLL
----------------------------------------
IPOffice
Assembly Version: 1.0.2080.25694
Win32 Version: 1.0.2080.25694
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/IPOffice.DLL
----------------------------------------
ConfigServer
Assembly Version: 1.0.2080.25696
Win32 Version: 1.0.2080.25696
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/ConfigServer.DLL
----------------------------------------
Controller
Assembly Version: 1.0.2080.25697
Win32 Version: 1.0.2080.25697
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/Controller.DLL
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
n1bw-fwi
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
TFTP
Assembly Version: 1.0.2080.25694
Win32 Version: 1.0.2080.25694
CodeBase: file:///C:/Program%20Files/Avaya/IP%20Office/Wizard/bin/Release/TFTP.DLL
----------------------------------------
System.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
6kglpguy
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------

ANY HELP WOULD BE APPRECIATED!

 

[intrigrant]

IP 412 : max of 360 users ( equals extensions )

So 1200 users and 1100 ICR's do mess up the IPO and will bring up erros like yo have.

Why so many users and/or ICR's.

If the ICRs are used for DDI numbers send to extensions were the last three digits of the DDI match with a user/extension then you can do with one ICR :
Line ID = 0
DDI =123456XXX
Destination = #
Then all DDI numbers will be send to the extension matching the XXX value.

Maybe you could bring down the users to a lower number if you tell us why you have this many users.

 

[latitude12]

360 is the limit for physical extensions, I guess the limit for users would be 500 (as per the rules for VM and SCN). The largest config I ever dealt with was a 412 with 800 or so users and the same for ICR. Avaya are aware of this config and have never questioned it (it was one of their case studies), and it works. The file size is around 250k, the limiit for the 412 is 1024k. Does this config exceed that size?

 

[sizbut]

Its wizard that has the problem. Wizard has all kinds of weird rules about what constitutes a valid config. On the whole loading a real world working config built on a real system is always going to give Wizard a shock, in this case it appears Wizard had a heart attack.

 

[h382]

http://marketingtools.avaya.com/knowledgebase/

If you browse the tree on the left(hiarchy structure, may take a minute to load), and click on Tools & Other Information, there is a Config Size Calculator. If you want an idea of how much of certain things the IPO can handle.

 

[mwiddows]

The reason for the users is that we have DID's that are used for voicemail only with fax capability. No physical extensions. So basically when a call comes in it goes directly to a voicemail box. We are using 3rd party voicemail (Duvoice) and no other features of IPO.

What's the point in having 1mg of memory if you can't use it? I would think that the users would be unlimited provided that your config doesn't exceed the memory allocation.

 

[mwiddows]

BTW - The config size is around 500k...

 

[latitude12]

As mentioned by sizbut, the Wizard is unpredictable at best. You should be able to error check the config manually, that's what the help file is for. Upgrade the system to 3.1.56 and upload the config, that's the only way to find out whether or not it will work. It certainly is within the size limit.

On the other hand, if you want official input, go to your distributor and ask them to open a case with Avaya so they can examine the config and state whether or not they will support it.

 

[sizbut]

What your doing, lots of virtual users just for mailbox services is fairly common. But Intrigrants first reply about using ICR wildcards should help ease some of the strain on the system.

 

[mwiddows]

So help me out here. If our voicemail coverage is at 7770, and we use 4 digit extensions, DID number is 602889xxxx,the short code would be? And I assume with different DID prefixes ie. 602602349xxxx we would have to make a short code for each prefix, no?