Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5330 settings control

Status
Not open for further replies.

kenny5445

Technical User
Apr 17, 2008
82
GB
Hi, I've got ~350 5330 phones over 2 sites.

I've been playing with this


Which lets you create a nice screen saver for the phones which is working fine!

Does anyone know anyway of controlling centrally the 5330 menu options centrally (i.e. to turn on the screen saver across the board).
 
I used the ingenius software to make my screen saver. It was really easy. I noticed it doesnt automatically turn on for my 5330's. I had to use desktop companion to program a screen saver button on the phones. Though all of my 5340's work fine.
 
Yeah got the screen saver working (and working on a html GUI replacment thats nice and branded) but from what I've read you have to go round each phone and enable the screen saver....

Got 350 5330's just now and will be getting about 250 in the summer :(
 
I don't yet have many 5340s, but in less than 12 months I could have several hundred at one location and I'm sure the cust. will want this rolled out system wide. I guess the guantlet has been thrown for Prod. Design to come up with a way to blow this out to every user.
 
A guy at ingenius came back to me saying that mitel support had said there is no central mechanism for rolling these changes out....

Getting my supplier to raise with Mitel on my behalf, the html stuff seems nice but with tonnes of phones its a real pain to admin.
 
I agree it'd be awful nice to have, but raising it as a DCR means you've got to be able to cost-justify Mitel's engineering and design cost to implement it. How do you do that when it's a freebie? Maybe that's why it's a freebie, that way it's unlikely to reach the DCR stage ;-)
 
If you use the HTML tool that is downloadable from Mitel Online, a relative novice with web tools (AKA me) can set this up and push it out to all phones.

It can be defined as to whether it is pushed to 5330's, 5340's or both.

Not mentioned anywhere obvious is a required maintenance command. (htmlappupgrade)

The screen saver overrides the setting on the phone and is automatically turned on.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Hi, I've got the app rolled out but on the 5330's the screen saver is off by default and needs to be activated.
 
There also seems to be a possible bug. Can anyone else verify this?

Scenario: With the screensaver "active" (displaying) on the 5340 instrument, voice mail messages will not light the MWI indicator. Even if the MWI indicator was previously 'on', activating the screensaver will cause the MWI indicator to stop flashing until the screensaver is deactivated.

I promise you, this is going to make the tech support/Help Desk phones ring. If this is how it's supposed to work then somewhere in the KB we better say so.

System: 3300 MX clustered
S/W: 8.0.8.8
VM: Octel Overture 350 (Aria 3.10.09-1)
Integration: COV (because it works!)
 
OK more info on the dupe scenario (MWI conflict w/screensaver)

IF:
- the mwi indicator is OFF
- the screensaver is ACTIVE
THEN:
- a call rings the set (deactivating the screensaver)
- the call goes CFNA to VM
- the caller leaves a message
- the mwi indicator is activated and flashes as it should
HOWEVER:
- when the screensaver times out again the MWI lamp will extinguish
- if you then deactivate the screensaver the MWI lamp will come on

Ball's in y'alls court
 
There seems to be some more adverse interaction between the screensaver and the MWI indicator.

- MWI ON (lamp flashing)
- Screensaver activates
- MWI extinguishes (no more flashing)
- User goes Off hook
- MWI still not flashing
- User then goes On hook
- MWI starts flashing
- Screensaver activates
- MWI extinguishes (no more flashing)
- New call rings set
- User answers
- MWI still not flashing
- User goes on hook
- MWI begins flashing

Does not seem to matter whether the PC-APP software is loaded and linked up or not.

 
WOW, Thanks for all the effort.

I don't like the screen saver personally but at least I have an argument against it.

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

IF:
- MWI not already true
- But the Screensaver = true (Active & displaying)
- MWI-Enable command is subsequently sent to the set (as in overnight MWI refresh)
THEN:
- MWI Lamp (primary) comes on & flashes as it should
- Although the Screensaver still = true
UNTIL:
- Screensaver interval timer expires again
THEN:
- MWI Lamp extinguishes
- Screensaver still = true

Throughout all of this, a keyline MWI indicator displays ONLY when screensaver = false. Anytime screensaver = true and MWI also = true, only the VM hotkey and prime MWI indicator flash. The keyline MWI is not visible unless screensaver = false

Gosh how I love new software!!!
 
More issues.

It's like the gift that just keeps on giving:

Once "enabled" on the instrument with the Display Image toggle, you cannot subsequently disable it. You can un-tic the display image check box, but the screensaver still displays, even after a full reset of the phone.

I suppose next someone will tell me I have to reset the Controller ;-)

The screensaver display is neat all right but I'm somewhat less than enamoured by all the baggage that comes with it.

 
Stepping in the Cow Pies while avoiding the land mines.

Stinks like heck but you're still alive.

;-)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top