413 - Improved AES/DMCC Functionality for SIP firmware Devices
Nick Kwiatkowski
Aaron -- In CM 10.x, the 3PCC protocol was enhanced to allow you to do full control of remote SIP devices assuming that (a) it is registered as an AST device in Session Manager (b) the phone is TLS encrypted for signaling and (c) the phone is getting UPDATE SIP packets.
You are not able to control individual buttons, nor can you monitor lamps -- but that is a limitation of SIP, rather than the protocol. SIP assigns features, not buttons, so this is not something that can be pushed out, since Session Manager/CM has no way to determine what is on the display or assigned to each "button"
Is there a particular use case you are looking at? It's most likely that what you are looking to do already exists with the current protocol stack.