Static bookmarks are no use when you want users to be able to set their own bookmarks to their own desktop PCs... ... View more

@cbarcellos wrote: We don't have a firm date yet on when Apple will post the software on the App Store. It should be posted on their App Store around mid to late July 2010. Should we infer from this response that the software has been submitted to Apple for approval? That is the conventional interpretation of "we're waiting on Apple", although we should be beyond the four-week application approval cycle these days :) Thanks, --Chris ... View more

Well, that's useful confirmation that the softphone's good with NC. As it turns out, I've only just got to the point where I can test it myself. Cheers, --Chris ... View more

We're a little behind - 8.1 - so our milage may differ! ... View more

I've not tried this yet - we're still deplying the Juniper infrastructure. However, I'll give it a try as soon as I can and see what happens. What ShoreTel version are you on? With your scenario, once the call is set up, audio will go direct between endpoints, whereas when you call out using your PSTN trunk, audio will go between your softphone and the switch to which the trunk is connected. Distributed call routing may change that, but we haven't had to turn that on yet. Cheers, --Chris ... View more

"A address of 127.0.x.x is a loopback address which does mean your PC. You should not use this address to connect but use the FQDN or shortname instead." Ummm, really? Really really? When you use the FQDN, it resolves to 127.0.1.x, assuming JSAM has modified the local hosts file or you've entered the mappings in your external DNS. I'm not sure why you're telling the OP not to use those addresses directly. ... View more

Mark, I'm assuming your questions were directed at me, so... First off, no it doesn't seem to emulate the /span argument to mstsc. This is most likely due to the fact that my browser (Firefox) is using the current monitor's dimensions to populate the values fetched in that little Javascript segment. Secondly, the HTML fragment that you supply on the resource profile page is wrapped (and stored as a string) in Javascript. Before being sent to the browser, the "<<THING>>" tokens are substituted for corresponding real values. The HTML is then written out into the page body - still using Javascript - for the browser to actually render. Someone who's a real web author can explain all that using the proper terms - I'm just a hacker :) I'm not completely clear, however, on why Javascript is used in this way, instead of values being directly transposed into the stored HTML fragment before sending it to the browser. (Edit: thinking about it, I wonder if it's to reduce the risk of something server-side mashing the HTML in some undesirable way?) I'm also not clear on why the resource profile page suggests you have parameters like <WIDTH> and <HEIGHT> available, when this seems patently not to be the case... Hey ho. ... View more

Whoa, that's way more engineering than I could be bothered with :) I took the easy way out, and added this:- <script language="javascript"> document.write('<param name="geometry" value="' + (screen.width - 16) + 'x' + (screen.height - 128) + '">'); </script> after my last <param name= in the HTML. I think it's what we classily refer to, here in the UK, as a bodge. But it is at least pseudo-full-screen, with a fudge-factor for keeping the user's main taskbar/dock somewhat visible, and not-quite-hitting the screen edge. Just throwing it out there in case anyone wants something that requires less helpdesk ticketing :) --Chris ... View more