3300 MXe - BLF QTY of records limit

[gotrojans]

Is there a limit to the QTY of BLF records on the 3300 MXe v9.x? I was adding some this morning, and then, I started to get an error message indicating that there wasn't anymore room to add records.

Thanks

Ron

 

[Bigsin]

A device or directory number may not exceed a total of 16 local and remote busy lamp appearances.

Up to 5000 extensions can be programmed as a Dss/BLF key depending your flexible dimensions.

 

[gotrojans]

What about remote BLF's? We are centralizing our receptionist desk so that one receptionist will answer incoming calls for our remote offices.

So for the receptionist to see the the BLF of a remote directory number, I have been adding the remote BLF's to a local directory number. We have just over 400 directory numbers for 8 3300's. Should this be a problem?

Thanks

Ron

 

[Bigsin]

No problem.

Check your flexible dimensions

 

[kwbMitel]

I wouldn't exactly say "No Problem".

If you're only creating the BLF on the system local to the 5550 and not configuring the remote BLF form on the host then you're missing a required step.

Keeping all the systems synch'd with the BLF's manually is a headache I wouldn't wish on my worst enemy.

You're creating a lot of network traffic for minimal gain.

Also, the BLF update isn't exactly realtime (low priority).

I think you're setting yourself up for failure.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[gotrojans]

Theoretically, the Remote BLF form has already been completed. I've been creating BLF's on the 3300 local to the 5550. Basically, we are testing the idea of having one receptionist answering all of the incoming calls for each office.

Yes. This is a lot of freakin work.

Since we are a heavy VMWARE environment, we are seriously looking at the Vmware version of the MCD to centralize our current 3300's and convert the existing 3300's to PRI gateway's in the remote offices. This Vmware version fits nicely with our current Vmware business continuity plans.

At the surface, it seems to solve the BLF problem. But do you see any gotcha's?

Thanks

Ron