Really good info, thanks Jason. I will go back and look at the trace again, I remember two seperate "SetLamp" statements in the there for the particular handle along with the message that sets the "You have voicemail" text".. could be that the stimInst=0 is in the second one. definiately stickying this thread for future reference though, I couldnt find the what the SetLamp parameters indicated at least in the resources I was looking at (Troubleshooting book, google, etc)<br>
<br><div class="gmail_quote">On Thu, Dec 4, 2008 at 5:26 PM, Jason Burns <span dir="ltr"><<a href="mailto:burns.jason@gmail.com">burns.jason@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'd pay closer attention to the following message:<div class="Ih2E3d"><br><br>CCM|StationD: (3331359) SetLamp mode=2, stim=15 stimInst=1<br><br></div>Mode 2 = on<br>Stim 15 = VM<br>StimInst 1 = turn line 1 red for a newer model phone, and display the envelope next to the line on the LCD.<br>
<br>StimInst 0 = The big red light LED under the handset.<br><br>If you don't see StimInst=0 being turned to state 2 then the big red light wasn't told to turn on.<br><br>Pay close attention to the Message Waiting Policy settings under<br>
<br>CCM Service Parameters<br>Device Specific Config (in 4.X only)<br>CCMUser Device Line configuration<br><br>Message Waiting Policy settings can cause unexpected behavior.<br><br>Also, make sure no one has alternate extensions configured in Unity for their MWI settings. That can cause lights to turn on and off unexpectedly.<br>
<br></blockquote></div><br>Ed Leatherman<br>Assistant Director, Voice Services<br>West Virginia University<br>Telecommunications and Network Operations<br>