Weird Park Issue - Park Indicator not illuminating on the phone that originally parked the call

[dsm600rr]

Hello all,

I have a Client that has the Main Location, and 2 remote locations. The remote locations have VPN Phones that VPN back to Home.

This customer has a lot of issues with clients calling the wrong location, so I have programmed park buttons as such:

Main Location:

Remote Location 1:

Remote Location 2:

When the main location parks a call on its normal park buttons (1-3) everything works as it should.

If the main location parks a call on: Park 1-3 WF, or Park 1-3 Pon - The call parks, however the phone that parked the call, the park button does not illuminate (however the parked call can be retrieved). All of the other phones at the main location show that parked call and illuminated button. Thoughts?

ACSS /ACIS

 

[Nortel4Ever]

Software level? I remember seeing this on a release of 10.something a few years ago, but it was fixed with a later release.

 

[dsm600rr]

Hi Nortel4Ever

They are on R11.1.0.1.0 build 95

Phones are 9611's w/button modules.

ACSS /ACIS

 

[cjjb]

So everyone else's call park button illuminates but the person who puts the call on park? IS it just the main location phones having this problem? All remote phones work fine?

 

[dsm600rr]

cjjb: Correct - all phones show the parked call for the remote location, aside from the phone that actually parked the call - the button does not illuminate. However, you can still press the button and retrieve the call from the phone that parked the call. Same thing happens on the remote locations parking a call for the main location. Otherwise, all remote phones work fine.

ACSS / ACIS

 

[derfloh]

Even if it probably makes no sense... Did you try to change the DSS status settings?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[dsm600rr]

derfloh: I have not, I am not familiar with this setting. Where is it at on the IPO? I see this option:

ACSS / ACIS

 

[derfloh]

Yes. This one.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[dsm600rr]

derfloh: Thank you, I will test and report back

ACSS / ACIS

 

[RocketJTech]

I seem to vaguely remember a similar issue using a 9611. When I swapped it for a 9608, the issue went away. I don't know if there is a 9611 issue with this, or if mine was an isolated incident. I always used 9608, but had a 9611, for some odd reason. Just a thought.

Please remember... If it's not the way that YOU would do it, that does not necessarily mean it's wrong. EVERYONE knows SOMETHING that you do not.