On 11/10/14 20:48, Peter Slow wrote: > both of the defect posted here appear as internal and can't be viewed, > at least at the moment,with the bug search tool...
CSCtq36901 is 3905s not supporting JTAPI, for which the workaround is to use HTTP control. Now I'm hitting the problem of the 3905 not respecting the URL Authentication/Secured Authentication URL enterprise parameters. Which again I can work around by manually assigning the 3905 to the informacast application user's controlled devices, but it'd be nice to not have to do that too. > On Fri, Oct 10, 2014 at 9:42 AM, James Andrewartha > <[email protected]> wrote: >> Hi Ryan, >> >> After setting some more LLDP options from that URL I managed to get it >> working. I then spent the rest of the day trying to get paging working, >> which turned out the be the documented CSCtq36901, for which there is >> fortunately a workaround that I'll test on Monday. -- James Andrewartha Network & Projects Engineer Christ Church Grammar School Claremont, Western Australia Ph. (08) 9442 1757 Mob. 0424 160 877 _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
