Slow Dialing from Outlook

[libellis]

Under Windows XP we're using click-to-dial from the MS Outlook contacts directory to dial out via 5224 phones on a 3300ICP Release 7.1. Click to dial capability in some cases was added by installing MiTSP Desktop edition, and in other cases by installing YA 3.0.9 Lite (both of these suggested or provided via responses to a question on this forum awhile back - still appreciate that!!). YA functionality itself is not currently being used.

We're finding that from the time the "Start Call" button is clicked to the time that the phone begins to dial varies on different user PC's, but is running from around 10 seconds to more than 20 seconds (might be dependent on number of open apps).

Anything obvious we should be looking at? Network performance is good, and I would think that the amount of data involved here is small.

 

[Canuckvoip]

Interesting...
I have seen similar results from Outlook and other apps.
I have used YA since its original inception (serverless) but only with Outlook 2K.
I know that if you installed YA and imported the contacts, dialing from that app would happen very quickly.
So it got me to thinking...
Are you using vlans? If so would there be a difference if the pc/laptop were on the voice network?
If the results were positive, what is the router between the vlans?
What version of Outlook are you using?
I'll see if I can try that...

Dave

You can't believe anything you read... unless of course it's this.

 

[libellis]

Outlook 2002. Voice and data VLANS are on a Cisco 3750 and are routed between each other on the 3750. Didn't try a PC on the voice network yet - security/policy issues make even simple experiments a chore, but will see.
Did ping the 3300 without significant delay. Longest dialing delay was with a user who had the most applications running. Thanks.

 

[libellis]

Not really sure if it's related to the number of open applications or the type (or if this is just a false path). The user with the shortest delay just has some MS Office applications while the user with the longest delay has Bloomberg (streaming financial data). Got to thinking about Windows process priorities. Outlook runs at "Normal" priority. YA processes run at "Realtime" priority. Still the size of the delay makes it hard to believe that would be the reason. Could experiment with raising Outlook's priority, but have to be careful.