If it would be of use in FOP2 development, I'd happily contribute a SCCP deskset for testing, etc. My intention is to keep our SCCP extensions on CME, but support in FOP2 for SCCP presence info is quite desirable.

SCCP registration/presence support was tweaked/fixed already. You can install FOP 2.27 and see extension buttons greyed out if they are not plugged in/registered into asterisk. I do not have any idea on how to integrate that with CME? I do not think FOP2 will work besides or outside the asterisk manager (AMI), as FOP2 does not talk sccp, it just talks to asterisk via AMI.

Best regards,

Problem is resolved and i think these changes will be included in next stable version.

Best regards,

Have you any updates relatively to this issue?

Im upgrade 2.26->2.27j (x86_64) and nothing changed. Because im cannot find how to attach the debug output here, i put it on online storage:
[url:3t852f4o]http://rapidshare.com/share/4BB2F210D5B5DB0D87FBBCD7E5F31410[/url:3t852f4o]

Some comments to debug (-X 1):
phone 1384 off and never on - incorrectly show in FOP2
phone 1342 off and on then debug is collected (comments marked in log OFF and ON).

Also (im already read other topics) UTF-8 (russian language support) in my configuration is broken after upgrade. Phone labels is showing as: label=Бехер Вера instead of Russian characters. Im attached screenshot to debug logs.
Its perfectly work in 2.26 without SET NAMES and other 'hacks'. UTF-8 in my configuration stored in FreePBX database with default settings (collate latin-1) and correctly showed by fop2. Im try different things (SET NAMES and other), but cannot find the solution (i can create another topic if needed).

Many thanks for future reply.

I do not need more information... anyways, without the ATTACHED addition, the PeerStatus with DETACHED should result in a greyed out button anyways. Not sure why it did not work in your case. You can try the above version and see how it goes. If there are still problems, you will have to capture complete output when running fop2_server in debug level 1 and send that to me so I can rerun those events through and see how fop2 reacts to them.

Best regards,

I have added "ATTACHED" to the "ok" states,
Where i can download latest version of FOP2 for check this (we use 2.26 from official site).

Unless the PeerStatus is not fired when the phone is unplugged, but when you request status...
Im wait this messages on console output and dont click anything after phone on/off.

What additional information needed for resolve this?

127.0.0.1 <- Event: PeerStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775220.353184
127.0.0.1 <- ChannelType: SCCP
127.0.0.1 <- ChannelObjectType: DeviceLine
127.0.0.1 <- PeerStatus: DETACHED
127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
127.0.0.1 <- SCCPLine: 1342
127.0.0.1 <- SCCPLineName: �ени� ��ликов
127.0.0.1 <- SubscriptionId:
127.0.0.1 <- SubscriptionName:
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: DeviceStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775220.353880
127.0.0.1 <- ChannelType: SCCP
127.0.0.1 <- ChannelObjectType: Device
127.0.0.1 <- DeviceStatus: UNREGISTERED
127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: ExtensionStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775220.358130
127.0.0.1 <- Exten: 1342
127.0.0.1 <- Context: ext-local
127.0.0.1 <- Hint: SCCP/1342&Custom:DND1342
127.0.0.1 <- Status: 4
127.0.0.1 <- Server: 0

Events after on phone: 1342

127.0.0.1 <- Event: DeviceStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775367.905977
127.0.0.1 <- ChannelType: SCCP
127.0.0.1 <- ChannelObjectType: Device
127.0.0.1 <- DeviceStatus: PREREGISTERED
127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: PeerStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775368.887042
127.0.0.1 <- ChannelType: SCCP
127.0.0.1 <- ChannelObjectType: DeviceLine
127.0.0.1 <- PeerStatus: ATTACHED
127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
127.0.0.1 <- SCCPLine: 1342
127.0.0.1 <- SCCPLineName: �ени� ��ликов
127.0.0.1 <- SubscriptionId:
127.0.0.1 <- SubscriptionName:
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: ExtensionStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775368.887237
127.0.0.1 <- Exten: 1342
127.0.0.1 <- Context: ext-local
127.0.0.1 <- Hint: SCCP/1342&Custom:DND1342
127.0.0.1 <- Status: 0
127.0.0.1 <- Server: 0

127.0.0.1 <- Event: DeviceStatus
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Timestamp: 1384775369.125328
127.0.0.1 <- ChannelType: SCCP
127.0.0.1 <- ChannelObjectType: Device
127.0.0.1 <- DeviceStatus: REGISTERED
127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
127.0.0.1 <- Server: 0

service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 1
(log into fop2, then make a phone available or unavailable)
ctrl-C
exit
service fop2 start

At that point you have the capture.log file with AMI events related to your environment. You can send that to me telling me what phone got offline or online that was not shown in the fop2 display, so I can trace for related events and see if this can be added as a new feature or not (lack of events means fop2 won't be able to tell the change of status)

Best regards,