Comments on: 32-bit Version of the PreCallDiagnostic Tool Available

By: Curtis Johnstone

Curtis Johnstone — Fri, 16 Oct 2009 01:56:34 +0000

I think it is safe to assume this tool just doesn’t work externally (through the Edge) right now. I’ve tried many things including tweaking the PreCallDiag.xml file with no luck. I think the problem is the tool doesn’t have the ability to prompt or supply credentials to present to the Edge. I would just use it internally until will get an update from Microsoft.

By: Ben

Ben — Fri, 16 Oct 2009 00:11:44 +0000

I’m getting the “There was an error signing into the SIP server using the sip URI you’ve configured” error as well when connecting externally. I’m on my laptop that’s joined to the domain, and logged in with the AD account that is associated with the SIP URI I’m testing against. From the same PC INSIDE the corporate network, this tool works great, but who the hell wants to test the INTERNAL network quality? This tool would be most useful to troubleshoot problematic Internet connections, but doesn’t seem to work when connecting through the Edge server as others have posted above. Any solution to this would be much appreciated!

By: Domenic

Domenic — Sat, 26 Sep 2009 19:25:12 +0000

In my experience the tool has a lot of issues when you are running with a user not associated with the SIP account you are testing with….
Thanks,

By: Curtis Johnstone

Curtis Johnstone — Fri, 25 Sep 2009 00:59:10 +0000

I am getting a similar error when running external (outside of my firewall). The exact error message is: “There was an error signing into the SIP server using the sip URI you’ve configured. Please double check that the SIP URI is correct for the logged-on user”.

In your case, it looks like it is having trouble passing those credentials through the Edge (using MRAS). Are you using TLS and automatic sign-in? Are you external?

When I try this over a VPN on XP, I get a Windows firewall warning (i.e. “Firewall has blocked some features of this program”).

One suggestion is to temporarily turn off your Firewall on the client and see if it works (remember to turn it on again).

My next step was to try the undocumented XML keys . I tried setting “UseDefaultCredentials” to “false”, with no luck.”UseDefaultCredentials” to “false”, with no luck.

When I get some more information, I’ll post it.

By: Luis

Luis — Thu, 24 Sep 2009 19:32:41 +0000

I always get the message of MRAS credentials,
With both 32 or 64-bit version in WinXP, 2003, Vista or Win7

I tried also to use undocument xml keys, but
on the log file reports a null GRUU:

20:08:23 : RegisterEndpoint
20:08:23 : RegisterEndpoint, already registered, returning
20:08:23 : RegisterAndRetrieveCreds : Registered sip endpoint
20:08:23 : Got Exception in RetrieveMRASCreds, aborting : System.Exception: got null MRAS GREE from server.
at PreCallDiagTool.SipCommunicationManager.RetrieveMRASCredentials(Int32 credsDurationMins)
at PreCallDiagTool.MediaTestController.RetrieveMRASCreds()
20:08:23 : StartTestChannel : Exception : PreCallDiagTool.PreCallDiagException: There was an error recovering MRAS credentials for the current SIP user. This might be a temporary problem with the server. Please try again in a little while

Any good ideais?

By: Audio and Video Client Issues with Live Meeting « Inside OCS

Audio and Video Client Issues with Live Meeting « Inside OCS — Thu, 24 Sep 2009 14:32:41 +0000

[...] Microsoft also makes a free tool available called “PreCallDiagnostic”, which is a small Win32 application that installs on the client PC and helps assesses whether network conditions will affect audio quality. You can read about more about this tool in my post: “32-bit Version of the PreCallDiagnostic Tool Available“. [...]