I am looking for and explanation or a document around expected behavior for how the Call Log works within the Jabber for Windows client. Our customers setup has Jabber for windows deployed in Deskphone Control mode, where the Jabber clients control a single physical phone. Predominantly a 7945 series phone. How in Sync is the "CALL HISTORY" (missed call, placed call, received call) lists within the Jabber client with the physical phone itself. Examples:
If we miss a call on the physical phone and Jabber is opened, we noticed that both the physical phone and Jabber client report a missing call.
If we miss a call and Jabber is closed, we notice the physical phone reports a missed call, but when Jabber sign's in the "MISSED Call" is not reported on the Jabber client.
Is this expected behavior?
if anyone can provide context or has a document that explains the expected behavior this would be very helpful to me.
Just for clarity, I'm not talking about a CSF registered phone, I'm talking about Jabber running in Deskphone Control mode. So yes in a hopeful way I would expect the call history from the physical phones to be in sync since deskphone control is just remotely controlling the phone. I suppose the call history on a physical phone is likely stored locally on the phone itself and this is why they call logs do not remain in sync but i just wanted to confirm that this is a fact vs an assumption.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...