i'm resizing my IPX-4000 and would like some opinions. i have attached the new sizing and the goal was to make sure we have enough stations now and into the future(i more than doubled what's in our current system on keysets, groups,ip and trunks) and flexibility. don't what to leave anything out that we may decide to use in the future, but don't want to create any limitations. my company has a history of doing some strange things so i had that in mind when it was sized. is something has to be changed, i rather do it now than later.
i understand all keysets 120,121,280,281 should all go under KEYSETS3 and to leave
KEYSETS1 and KEYSET2 at 0

thanks,

3703765 BYTES LEFT IN MEMORY

max ports (6000)

max stations (6000)

max slts (4000)

SLT (4000) - 672

SLT_IP (4000) - 75

max keysets (3400)

- NOTE:
keyset1 represents FlexSet 120/120D/120L/120S, CPA, DKT21XX,
DKT1XXX, DST, EKT1XX and VDK121 units.
keyset2 represents EKT2XX and VDK221 units.
keyset3 represents FlexSet 280/280D/280D-Z/280S/80S/80P, APDL,
GKT, iCMC, DKT23XX, EKT3XX and VDK321 units.
keysets quantity is transportable between the various set types.

KEYSETS1 (3400) - 0
KEYSETS2 (3400) - 0
KEYSETS3 (3400) - 240
KEYSETS_IP(3400) - 250
SIP_TERMINAL (3400) -150
WIRELESS (3400) - 24

max trunks (3400)

LGS (3400) - 48
E&M (3400) - 96
DID (3400) - 96
PRI (3400) - 360
TBR (3400) - 32
LGS_IP (3400) - 48
NET_IP (3400) - 100
SIP_TRUNK (3400) - 50

max libraries (14096)

PRIVATE (10000) - 1500
PUBLIC (4096) - 4096
LARGE_PUB (65000) - 5000
LARGE_NPL (1000) - 1000
LARGE_PUB_DIGITS ( 51) - 28

DIRECTORY (Y/[N])- Y

ENTRIES_PER_USER - 10

GROUPS :
BELL/UNA (6) - 6
ZONE PAGE (250) - 60
ELA(3000) - 300
Note: max_simultaneous_ela_calls and boss definition can not exceed 1024
MAX_SIMULTANEOUS_ELA_CALLS ( 1024) -96
BOSS (1024) - 250
PICKUP (512) - 100
HUNT (500) - 500
GRP_CALL (250) - 50
MAX_SIMULTANEOUS_GRP_CALLS ( 50) - 50
TRUNKS (250) - 75

PEM/DPEM/TEM (240) - 72
Turret Console (50) - 20
8DRCF/8DRCM/RMI/ASU (6) - 6
NUM_PLAN (32000) - 20000
OFFSET_FILTER( 250) - 72
N_FILTER_ELEMENTS PER OFFSET FILTER ( 64) - 64
COS (250) - 48
SMDR_BACKUP(950) - 950
TBCT_SMDR (10000) - 1000
4IAA_PORTS (128) - 32
TOLL_BAR_DIGITS_(AVG) ( 51) - 28
TOLL_BAR_ELEMENTS_(AVG) 1680) - 96
CONF_CKTS ( 100) - 50
DYNAMIC_CONF( 100) - 12
DVMS_PORT ( 960) - 4
PAGE_Q (2000) - 2000
VFAC_ACCT(65000) - 1000
WAIT_QUE ( 128) - 48
CALL_SERVICES(500) - 250
CAMP_ON ( 500) - 75

INTERNAL TRAFFIC:
NO_OF_TRAFIC_EVENTS_AND_FEATURES (MIN=0/MAX=27)- 14
TOTAL_NO_OF_DAYS_TO_STORE_TRAFFIC(MIN=0/MAX=7)- 5

IP:
EXTERNAL_GW( 250) - 24
ZONE ( 32) - 16

SIP:
MAXIMUM_PERSONAL_PASSWORD_LENGTH( 20) - 10
FOREIGN_PROXY ( 30) - 8

NETWORK (Y/[N])- Y
NET_NODES (250) - 20
NET_FEATURES ( 9000) -2118

ISDN:
NETWORK_FACILITIES (250) - 20
NUMBER OF ALTERNATE ID (10000) - 750
N_SPID_DN_PER_DSL ( 8) - 8

ROUTING:
ROUTING ACCESSES ( 4) - 4
DIAL SERVICES (255) - 60
ROUT ELEMENTS (250) - 60
COST ELEMENTS ( 50) - 10
ROUTING_ELEMENT_NPL_SIZE - 12
ROUTING_NPL_ELEMENTS - 250

CHECK MEMORY(Y/N)? N

Well, you are learning this is THE most important step in programming a Coral switch. You would be amazed how many tech's I follow that don't get this. Unfortunately, you did what anyone would and doubled everything hoping it wasn't too weird and off the wall in the future. If you are using that many libraries for routing make sure you have enough. It's pretty amazing how many you can burn with a ton of DID numbers doing special things. Also, do you really need 2000 page q's? Also, if you have a CLA with a telephony server wait ques are important.

other than the #of page Q's anything else that may look really strange. i maxed some things out that didn't use much memory. as i said my company has a habbit of doing some really strange things. i set call services to 250 since i would be using OAI and CSTA pretty heavily. should i increase wait q's to be on the safe side.

other than the #of page Q's anything else that may look really strange. i maxed some things out that didn't use much memory. as i said my company has a habbit of doing some really strange things. i set call services to 250 since i would be using OAI and CSTA pretty heavily. should i increase wait q's to be on the safe side.

Everything else looks sound, but of course you cannot predict unusual use.

You have lot of memory.
Double all your station and trunks (all types).
If you thik big, tripple it.

How much available memory should i leave?

As less as you can,
200-300K is OK

Using up all you memory can get in the way of using CVD for live authorization updates. I believe Tadiran recommends 1 M.

The 1M or more is for upgrade into higher versions without sizing, this usually consume larger memory with the same sizes.

Bill, if you plan to upgrade major version,
tech cheap remark is to the point.