The following table outlines the expected 24x7 call journaling functionality with dual registered extensions:
SIP client |
H.323 client |
Scenario |
Call Logs |
Logged in |
Logged in |
Answer and end an incoming call from the H.323 client. |
Incoming call entry in the SIP client and the H.323 client. |
Logged in |
Logged in |
Answer and end an incoming call from the SIP client. |
Incoming call entry in the SIP client and the H.323 client. |
Logged off |
Logged in |
Answer and end an incoming call from the H.323 client. Log in to the SIP client. |
Incoming call entry in the SIP client and the H.323 client. |
Logged in |
Logged off |
Answer and end an incoming call from the SIP client. Log in to the H.323 client. |
Incoming call entry only in the SIP client, not in the H.323 client. |
Logged off |
Logged off |
Incoming call is missed as no client is logged in.
Log in to the SIP and H.323 clients. |
Missed call entry only in the SIP client, not in the H.323 client. |
Logged off |
Logged in |
Answer the incoming call from the H.323 client. Log in to the SIP client. The SIP client displays the active call on the H.323 client. End the call from the H.323 client. |
Incoming call entry in the SIP client and the H.323 client. |
Logged off |
N.A. |
Delete all call logs from the H.323 client. Log in to the SIP client. |
Call logs not in sync. Logs that are available in the SIP client before logging in are displayed though all call logs were deleted from the H.323 client. |
N.A. |
Logged off |
Delete all call logs from the SIP client. Log in to the H.323 client. |
The H.323 client synced with the SIP client. Displays no call logs, as all entries were deleted from the SIP client |
