Table of Contents

CCME Presence

Monitor mode for shared lines provides a visible line status indicating whether the line is in-use or not. A monitor-line lamp is off or unlit only when its line is in the idle call state. The idle state occurs before a call is made and after a call is completed. For all other call states, the monitor line lamp is lit.

A line button that is configured for watch mode on one phone provides Busy Lamp Field (BLF) notification for all lines on another phone (watched phone) for which watched directory number is the primary line. Watch mode allows a phone user, such as a receptionist, to visually monitor the in-use status of an individual phone.

Configuration Local Presence

Enabling Presence for Internal Lines.

SIP-UA Presence

sip-ua
  presence enable

Presence

presence
  presence call-list
  max-subscription 128

EPhone DN Presentity

SCCP

ephone-dn 2
  allow watch

SIP

voice register dn 2
  allow watch

EPhone Watcher

For SCCP

ephone 1
  blf-speed-dial 1 <dn-number> label <label> [device]
  presence call-list

For SIP

voice register pool 1
  blf-speed-dial 1 <dn-number> label <label> [device]
  presence call-list

<note>May need to reboot the router if there is problem with displaying presence in call list</note>

Configuration Remote Presence

To enable internal watchers to monitor external directory numbers on a remote Cisco Unified CME router, perform the following steps

Presence

presence
  server <remote-ccme-ip>
  allow subscribe
  watcher all

Voice Register (Optional)

voice register global
  authenticate presence 
  authenticate credential 1 flash:cred1.csv 

Debug

Router# show presence global 

Presence Global Configuration Information: 
============================================= 
Presence feature enable : TRUE 
Presence allow external watchers : FALSE 
Presence max subscription allowed : 100 
Presence number of subscriptions : 0 
Presence allow external subscribe : FALSE 
Presence call list enable : TRUE 
Presence server IP address : 0.0.0.0 
Presence sccp blfsd retry interval : 60 
Presence sccp blfsd retry limit : 10 
Presence router mode : CME mode 
Router# show presence subscription summary 

Presence Active Subscription Records Summary: 15 subscription 
Watcher Presentity SubID Expires SibID Status 
======================== ======================== ====== ======= ====== ====== 
6002@10.4.171.60 6005@10.4.171.34 1 3600 0 idle 
6005@10.4.171.81 6002@10.4.171.34 6 3600 0 idle 
6005@10.4.171.81 6003@10.4.171.34 8 3600 0 idle 
6005@10.4.171.81 6002@10.4.171.34 9 3600 0 idle 
6005@10.4.171.81 6003@10.4.171.34 10 3600 0 idle 
6005@10.4.171.81 6001@10.4.171.34 12 3600 0 idle 
6001@10.4.171.61 6003@10.4.171.34 15 3600 0 idle 
6001@10.4.171.61 6002@10.4.171.34 17 3600 0 idle 
6003@10.4.171.59 6003@10.4.171.34 19 3600 0 idle 
6003@10.4.171.59 6002@10.4.171.34 21 3600 0 idle 
6003@10.4.171.59 5001@10.4.171.34 23 3600 24 idle 
6002@10.4.171.60 6003@10.4.171.34 121 3600 0 idle 
6002@10.4.171.60 5002@10.4.171.34 128 3600 129 idle 
6005@10.4.171.81 1001@10.4.171.34 130 3600 131 busy 
6005@10.4.171.81 7005@10.4.171.34 132 3600 133 idle 
Router# debug presence errors 

*Sep 4 07:16:02.715: //PRESENCE:[0]:/presence_sip_line_update: SIP nothing to update 
*Sep 4 07:16:02.723: //PRESENCE:[17]:/presence_handle_notify_done: sip stack response code [29] 
*Sep 4 07:16:02.723: //PRESENCE:[24]:/presence_handle_notify_done: sip stack response code [29] 
*Sep 4 07:16:02.791: //PRESENCE:[240]:/presence_handle_notify_done: sip stack response code [17] 
*Sep 4 07:16:02.791: //PRESENCE:[766]:/presence_handle_notify_done: sip stack response code [17] 
*Sep 4 07:16:04.935: //PRESENCE:[0]:/presence_sip_line_update: SIP nothing to update 
*Sep 4 07:16:04.943: //PRESENCE:[17]:/presence_handle_notify_done: sip stack response code [29] 
*Sep 4 07:16:04.943: //PRESENCE:[24]:/presence_handle_notify_done: sip stack response code [29] 
*Sep 4 07:16:04.995: //PRESENCE:[240]:/presence_handle_notify_done: sip stack response code [17] 
*Sep 4 07:16:04.999: //PRESENCE:[766]:/presence_handle_notify_done: sip stack response code [17] 
Router# debug ephone blf 

*Sep 4 07:18:26.307: skinny_asnl_callback: subID 16 type 4 
*Sep 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION 
*Sep 4 07:18:26.307: ephone-1[1]:ASNL notify indication message, feature index 4, subID [16] 
*Sep 4 07:18:26.307: ephone-1[1]:line status 6, subID [16] 
*Sep 4 07:18:26.307: ephone-1[1]:StationFeatureStatV2Message sent, status 2 
*Sep 4 07:18:26.307: skinny_asnl_callback: subID 23 type 4 
*Sep 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION 
*Sep 4 07:18:26.307: ephone-2[2]:ASNL notify indication message, feature index 2, subID [23] 
*Sep 4 07:18:26.311: ephone-2[2]:line status 6, subID [23] 
*Sep 4 07:18:26.311: ephone-2[2]:StationFeatureStatV2Message sent, status 2 
*Sep 4 07:18:28.951: skinny_asnl_callback: subID 16 type 4 
*Sep 4 07:18:28.951: ASNL_RESP_NOTIFY_INDICATION 
*Sep 4 07:18:28.951: ephone-1[1]:ASNL notify indication message, feature index 4, subID [16] 
*Sep 4 07:18:28.951: ephone-1[1]:line status 1, subID [16] 
*Sep 4 07:18:28.951: ephone-1[1]:StationFeatureStatV2Message sent, status 1 
*Sep 4 07:18:28.951: skinny_asnl_callback: subID 23 type 4 
*Sep 4 07:18:28.951: ASNL_RESP_NOTIFY_INDICATION 
*Sep 4 07:18:28.951: ephone-2[2]:ASNL notify indication message, feature index 2, subID [23] 
*Sep 4 07:18:28.951: ephone-2[2]:line status 1, subID [23] 
*Sep 4 07:18:28.951: ephone-2[2]:StationFeatureStatV2Message sent, status 1