C-series - Hide call history?

Answered Question
Jun 1st, 2012
User Badges:

Hi all,


Have a question regarding the call history function on C-series.


Is it possible to hide, remove, reset or to disable the call history?


Customer doesn't want others using the same conference room to view the call history/who they've been in contact with.


Thought about using a MCU as middle man, but would like to know if it's possible to do something on the codec instead.


//Johan

Correct Answer by Tomonori Taniguchi about 5 years 2 months ago

C-series Endpoint support startup script and you able to add your script with API that support by Endpoint.

Therefore if you shutdown/restart after finished the call or end of business day, then you can manage to delete the logs.


Step 1: Make"scripts.d" directory under /user (mkdir /user/scripts.d)


Step 2: Create startup file and first line must contain “#!/usr/bin/env tsh”.

Sample: script_delete_calllog

================================================

#!/usr/bin/env tsh







xCommand CallLog Clear


xCommand CallLog Recent Delete


xCommand CallLog Outgoing Delete


xCommand CallLog Received Delete


xCommand CallLog Missed Delete


xCommand CallLog Missed Dismiss

================================================

Adding the extra line between commands to give a break.


Step 3: Make file as executable by executing “chmod +x script” command on scripts.d folder.

Example:

================================================

[C90:/user/scripts.d] $ chmod +x script

  [C90:/user/scripts.d] $ ls -al

  total 8

  drwxr-xr-x 2 root root 1024 Feb 4 23:57 .

  drwxr-xr-x 8 root root 1024 Feb 4 23:50 ..

  -rwxr-xr-x 1 root root   78 Feb 4 23:06 script

  -rw-r--r-- 1 root root 5120 Feb 5 00:03 typescript\

================================================

Correct Answer by Teck Chye Tang about 5 years 2 months ago

Hi,


I am afraid you are not able to hide or disable the call history.  But you can certainly delete them.


you can use the API command below to delete them.


xCommand CallLog Clear

    LogTag: <0..2147483647>

xCommand CallLog Recent Delete

    LogTag: <0..2147483647>

xCommand CallLog Outgoing Delete

    LogTag: <0..2147483647>

xCommand CallLog Received Delete

    LogTag: <0..2147483647>

xCommand CallLog Missed Delete

    LogTag: <0..2147483647>

xCommand CallLog Missed Dismiss

    LogTag: <0..2147483647>


For example : xCommand CallLog Clear  - this will clear all the call history.


Maybe you can write a script that runs on a pre-determined time each day to clear the call history


Hope this is what you are asking.


Regards,

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Correct Answer
Teck Chye Tang Fri, 06/01/2012 - 08:43
User Badges:
  • Cisco Employee,

Hi,


I am afraid you are not able to hide or disable the call history.  But you can certainly delete them.


you can use the API command below to delete them.


xCommand CallLog Clear

    LogTag: <0..2147483647>

xCommand CallLog Recent Delete

    LogTag: <0..2147483647>

xCommand CallLog Outgoing Delete

    LogTag: <0..2147483647>

xCommand CallLog Received Delete

    LogTag: <0..2147483647>

xCommand CallLog Missed Delete

    LogTag: <0..2147483647>

xCommand CallLog Missed Dismiss

    LogTag: <0..2147483647>


For example : xCommand CallLog Clear  - this will clear all the call history.


Maybe you can write a script that runs on a pre-determined time each day to clear the call history


Hope this is what you are asking.


Regards,

Correct Answer
Tomonori Taniguchi Sat, 06/02/2012 - 04:36
User Badges:
  • Cisco Employee,

C-series Endpoint support startup script and you able to add your script with API that support by Endpoint.

Therefore if you shutdown/restart after finished the call or end of business day, then you can manage to delete the logs.


Step 1: Make"scripts.d" directory under /user (mkdir /user/scripts.d)


Step 2: Create startup file and first line must contain “#!/usr/bin/env tsh”.

Sample: script_delete_calllog

================================================

#!/usr/bin/env tsh







xCommand CallLog Clear


xCommand CallLog Recent Delete


xCommand CallLog Outgoing Delete


xCommand CallLog Received Delete


xCommand CallLog Missed Delete


xCommand CallLog Missed Dismiss

================================================

Adding the extra line between commands to give a break.


Step 3: Make file as executable by executing “chmod +x script” command on scripts.d folder.

Example:

================================================

[C90:/user/scripts.d] $ chmod +x script

  [C90:/user/scripts.d] $ ls -al

  total 8

  drwxr-xr-x 2 root root 1024 Feb 4 23:57 .

  drwxr-xr-x 8 root root 1024 Feb 4 23:50 ..

  -rwxr-xr-x 1 root root   78 Feb 4 23:06 script

  -rw-r--r-- 1 root root 5120 Feb 5 00:03 typescript\

================================================

johan.alkarp Mon, 06/04/2012 - 04:23
User Badges:

Thanks to both of you for nice answers!


Follow up question:


Would it be possible to use a custom command from a persistant template from TMS to do this?


And how would that command be in that case

?????



// Johan

Tomonori Taniguchi Mon, 06/04/2012 - 04:32
User Badges:
  • Cisco Employee,

Unfortunately Persistent settings with template if for configuring the endpoint with first register or boot up. Therefore won’t help to delete the logs on Endpoint.

Actions

This Discussion

Related Content