[cisco-voip] 7960 w/7914 BLF no alerting of monitored lines

[Bill Talley]

That's correct, no flashing.  Pickup is checked on all BLF lines and the
same pickup group is  configured on all directory numbers. Call pickup
works as expected using the soft keys as well, we're just not getting the
alerting/flashing on the sidecars.

Thanks for your questions Nate.

Bill

Sent from an Apple iOS device with very tiny touchscreen input keys.
 Please excude my typtos.

On Feb 25, 2013, at 2:15 PM, Nate VanMaren <VanMarenNP at ldschurch.org> wrote:

  So you’re not getting the flashing lights for BLF Pickup?  Is the Pickup
box checked on the specific BLF you’re testing?



*From:* cisco-voip-bounces at puck.nether.net [
mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
*On Behalf Of *Bill Talley
*Sent:* Monday, February 25, 2013 11:07 AM
*To:* cisco-voip at puck.nether.net
*Subject:* [cisco-voip] 7960 w/7914 BLF no alerting of monitored lines



Hi all,

I recently performed an install of CUCM 9.1(1) and am having an issue with
BLFs on a 7914 not lighting up when a monitoring DN is in alerting state.
The BLFs on the 7914 light solid red when the monitored line is in use.  I
have a TAC case opened up on the issue and am awaiting feedback, but
nothing has jumped out at TAC as the obvious cause.

I have the subscribe CSS set on the 7960 to a CSS that has visibility of
the monitored lines (hence the busy lights).  Phones and sidecars are
running the latest firmware.   Since the BLFs light up when the monitored
line is in use, I'm guessing everything is configured correctly.

Does anyone have 7914s with BLFs that correctly reflect alerting state of a
monitored line with a flashing or solid line button the 7914 on any linux
version of CUCM?

TIA
Bill



NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130225/5b30467a/attachment.html>