[cisco-voip] Disabling placed call history on 7841's

[Matthew Collins]

Ok,

Thanks for the pointer Steven, I have now kind of got this working on the Idle URL, but after the phone request the idle URL the phone is stuck in the following state until I go off hook. The Cancel softkey button doesn’t seem to do anything

[cid:image002.png at 01CF4375.4DDDCD50]

It has requested the Init:CallHistory as the call history is cleared.



Regards

Matthew


From: Stephen Welsh [mailto:stephen.welsh at unifiedfx.com]
Sent: 19 March 2014 10:40
To: Matthew Collins
Cc: cisco-voip (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] Disabling placed call history on 7841's

Hi Matt,

Just tested on our 7841 (sip78xx.10-1-1-9) by sending Init:CallHistory using PhoneView and it worked fine.

Error 4 is usually an authentication Error, if you are pushing (HTTP POST) the CiscoIPPhoneExecute object to the phone I suspect their is something wrong with the Authentication URL or an ITL issue?

The CiscoIPPhoneError section here details the error codes:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/all_models/xsi/9_1_1/CUIP_BK_P82B3B16_00_phones-services-application-development-notes/CUIP_BK_P82B3B16_00_phones-services-application-development-notes_chapter_011.html#CUIP_RF_C22B2EF6_00

Assuming you will be hosting that XML file on a web server and pointing the Idle URL to it I would expect it to work fine as authentication does not apply to that scenario.

Kind Regards.

Stephen Welsh

[cid:image003.png at 01CF4375.4DDDCD50]


On 19 Mar 2014, at 10:20, Matthew Collins <mcollins at block.co.uk<mailto:mcollins at block.co.uk>> wrote:


Hi All,

I have a requirement to disable the call history on a selected amount of 7841 handsets.

To start with the call history has now been moved under the services button and not the directory’s button.

I know I can disable the logged calls under the line settings and this stops all received and missed calls appearing in the call history but the placed call still appear..

I know I can put a dummy URL in the service URL on the specific phone to stop user getting to the call history on the phone but the user can still access the call history using the up button. This will also disable all other services.

I did have a XML file that worked on the 79XX series phone that cleared down the call history, I used to out the URL in the idle timeout and the phone would clear down the call history whenever the idle timers expired

<CiscoIPPhoneExecute>
<ExecuteItem URL="Init:CallHistory" />
</CiscoIPPhoneExecute>

But this doesn’t seem to work on the newer sip models. As I get a “xml error 4 parse error” returned. When I browse to the webpage I get the following returned so think the XML is right (for a 79XX phone)

<?xml version="1.0"?>
<CiscoIPPhoneExecute><http://10.1.13.12/clear_phone.xml>
<ExecuteItem URL="Init:CallHistory"/>
</CiscoIPPhoneExecute>


Regards

Matthew Collins
Collaboration Principal Consultant

ǀ BLOCK ǀ
Cisco Global EMEAR Partner of the Year 2013
Visit our dedicated Healthcare site at www.block.co.uk/health<http://www.block.co.uk/health>

D   +44 (0) 203 0053032
F    +44 (0) 844 9671642
W  www.block.co.uk<http://www.block.co.uk/>







_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140319/77632c47/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2252 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140319/77632c47/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1420 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140319/77632c47/attachment-0001.png>