Eric, this is great and just what I've been looking for. Could you say more about how to use it, though? For instance, it seems I can not run it in Visual Studio (I get the error that we can't make an outgoing call as "the current state is incoming" --> "Unable to establish session with remote party. Response Code 486."

Do I need two SIP lines dedicated to my dev machine?

The low-level SIP stuff is not my province, so I need a little guidance there, if you could . . .

Thanks!

Well, Eric's disappeared, but I did finally get this working. For anyone who wants to use this, I encourage you to really go through the ReadMe.htm file in the UnitTesting project. However, it does assume a good bit of knowledge that I didn't have, so I am posting here a more detailed version of the "To run the demo" section (sorry for the formatting, but no HTML allowed):

[SydneyOs: Modified instructions below]
To set up the demo:
Set the CallingParty on the MakeCallActivity - not sure why this isn't in there, but I couldn't get it to work without it. So, add the following line of code in OutboundCallsWorkflow.OnEntry:
makeCall.CallingParty = new SipUriTelephonyAddress(new SipUri("sip:OutboundCalls@localhost"));
Register the LoggingInstrumentation and OutboundCalls applications in the Speech Server Admin console
When you register the Logging Instrumentation app in the Admin Console, remove the Called Party "*" designation and add a "LoggingInst" Called Party to match that in the Sip Uri
Note: If the Target App is on a different server, you need to do the following:
Deploy the LoggingInst app to the Target Server (create IIS App for it), register in Admin Console and set the Called Party to LoggingInst
In Admin Console, add the Target Server as a Trusted Peer on your Dev/Test machine.
Make sure to check "Allow outbound calls"
In Admin Console on the Target Server, add your Dev/Test machine as a trusted peer
In OutboundNumbers.xml, change the sip uri to reflect your target server's IP
To run the demo:
Run the OutboundCalls.aspx page from IIS (will not work to run from Visual Studio)
Click "Send Trigger"
I added trace statements in both apps to know that it was running properly. If the target server is on a different machine, you can also run WireShark with a display filter of "sip" to see that the call is working. You won't see any sip traffic if running locally.

By the way, I initially got this running on a separate server, which is why I have the bit about a two server setup, but to get the call log for use in generating a test script, I'm pretty sure you want a single machine setup so all the logging is in one place.

Hi... I have newly taken a managed service from service provider in CA. from.. http://www.onthenetoffice.com/overview.html its working good for me.