Activating a PEP

[rheine]

All,

I have a stand-alone signaling server off a CS1000 release 4.5.88 that I needed to replace last night. I built it from scratch and loaded all 100 PEP's via element manager on that S.S.

One of the patches did not get activated and it is a critical patch related to remote message waiting lamps. The users are complaining that their message waiting lamps are lit with no messages.

I looked at that patch(25540) and it it out of service. I believe that the S.S. needed to be rebooted in order to activate that patch.

Can I activate this in element manager with the PINS command? I was about to do that and the system asked me if I was sure. I did not click submit because I did not want to risk the S.S. rebooting on it's own plus have this not work.

Is there a better way to activate this PEP without needed to complete a full reboot?

Thanks

 

[Reusser]

You can use the PINS command in element manager

Remember though, if patch has special requirements, you need to follow the special requirments. If that mean reboot - wait to load patch until you can also reboot.

 

[rheine]

Reusser, I do recall that the S.S. needed to be rebooted when I did this in the past. I did activate that patch but it forced me to deactive another one due to a conflict. Do you suppose the reboot was required because of this conflict?

That patch is in-service(25540) now and I tested the message waiting lights at another site and their lights are working.

What bothers me is that I have a MsgInd and MsgCancel buttons on my phone and when I type in the extension of the person that I want to turn the message waiting on light for the number still shows on my screen and I need to press my goodbye button to clear my screen. Normally when I press the MsgInd button and the extension number(press this MsgInd button twice) the extension clears from my screen. I do not need to hit my goodbye button, normally.

I guess the bottom line is this S.S. should probably be reboot even though things appear to be working fine now?

 

[Reusser]

If the patch special instructions require a reboot - schedule a reboot.

The reboot though has nothing to do with a patch conflict. Most likely this patch was a result of two or more patches merged and the one taken out of service was one that was merged into this patch.

as far as the MIK and MCK keys go

they should operate such as:
press MCK key - indicator goes on, dial ext to light lamp, press MCK key again - indicator goes away

If after pressing MCK again and indicator does not go away - lamp may not have been lit or pBX did not get an acknowledgment which then prompts more questions

Is phone trying to light lamp on or off campus
if off - using T1 or Virtual trunk
if off - any Digit manipulation?
if off - can you get DCH messages
if VTRK -H3232 or SIP

Also what RLS PBX and patches up to date?

 

[rheine]

Hello, we have one centralized call-pilot system located within a CS1000E and there are many remote locations that are using this same voice mail system. This patch was created specifically(25540) to activate the lights at these other locations. Actually one of the sites is a release 5.0 site and the rest are 4.5.88 sites so Nortel had created this PEP specificially for the message waiting lights to work at these remote sites via "D" channel and SIP channels.

I did activate that PEP and the message waiting lights appear to be working. I am going to wait a few days to see if we get anymore compalints and if so I will reboot the S.S. If not I will not reboot and leave as is.

I had believed that there were special instructions if this PEP was loaded in the PBX to INI or sysload but I do not believe that to be the case in the signaling server. I am not able to find my notes and am not able to get on the Avaya website to confirm.

Thanks