First Lync call of the day is slow to start appear or never shows or heard in client

Our first call of a new day has this behavior a lot.  Anyone have any thoughts on how to troubleshoot this or a fix to try?  I can't seem to make it fully go away.

  • Call inbound can ring on the far end for say 15 seconds, but never shows on the workstation's toast or Lync
  • or inbound will ring and ring, but our internal users only sees or hears that last few seconds of the 15 to 20 second ring
  • outbound this first call of the day, clicking call, then for about 15 seconds or so it will say 'calling...' but the familiar lync ring outbound won't occur until about 20 seconds or so have passed
  • Then after this first call of the day - ALL of the calls are always instantaneous.  inbound & outbound are heard and answered instantly
  • Even after rebooting the PC in the middle of the day after having done a call, the first call after a reboot is instantaneous (only the very first call of a new calendar day seems to be the most problematic)
  • Most people experience this only on the very first call of a new day
  • Mostly inbound though also on outbound (but outbound is less noticeable)

To me it feels like the lync server or lync client is taking a really long time to setup the very first call or to find the user device / lync endpoint/client for the first time each day.

Additional info:

  • This actually has seemed to go for the past few years with Lync 2010 & OCS 2007 R2 (we have used enterprise voice since 2010)
  • no PBX installed at all just lync
  • 1 lync 2010 Front End server
  • 1 lync 2010 Edge Server
  • lync 2010 clients
  • occurs both on win7 & winXP workstations
  • occurs regardless of endpoint type [USB deskphones like Polycom CX300/snom UC600 & wireless headsets of various models from Plantronics]
  • from personal experience seems like after 1st turning on my workstation in the morning -- if I toggle on the on/off hook button on my headset or from a USBdeskphone that seems to either eliminate or reduce this effect.

Thanks & totally flummoxed by this & would love to get this one behi

April 12th, 2013 6:57pm

Hi,

It is so strange. 

Do you use the gateway to connect the PSTN network?

Please run the lync server logging tool on the mediation server to get more logs about this issue.

Free Windows Admin Tool Kit Click here and download it now
April 15th, 2013 2:51pm

Yes we use a Sonus/NET VX1200 gateway to an intelepeer SIP trunk.

Can you give me some insight into what I should watch out for in the mediation server logging?  Also can you tell me which options to log? 

  • ExumRouting
  • Mediation Server
  • S4
  • Sip Stack

I have a trace from this morning when this occured, but there are no errors & I don't know what to look for.

Thanks

April 26th, 2013 5:21pm

Same here. Always the first call in the morning, regardless if outbound or inbound (direct or via RGS). Not sure how to tackle this, but at least now I know I'm not the only one with the issue.

Our set up is similar, Enterprise Voice since 2009, direct to PSTN via AudioCodes M1K. But it's definitely not related to that, because we see it with PC-to-PC calls as

Free Windows Admin Tool Kit Click here and download it now
May 17th, 2013 9:45am

dsidler, I'm sorry to hear you have the same problem, yet it's somewhat reassuring to know that it's not just me either. 

I tried running lync server logging tool on the mediation server, but nothing in them stood out or contained any errors that I could see.

If you or anyone else has ideas of what to look at in the logs or other ideas, please do post them.  This is still happening here with no resolution yet.

May 17th, 2013 4:36pm

Also getting this problem.  Anybody found a solution?

Free Windows Admin Tool Kit Click here and download it now
August 8th, 2013 3:03pm

Hi, did you find a solution? We have the same problem 
November 21st, 2013 7:38pm

It's nearly 2015 and I still have this problem and have yet to find or hear of a solution.  Who else is having this issue and has anyone ever been able to resolve this?  Thanks
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2014 8:03pm

Strange that the issue is there for many people here. When u enabled the logs from Server and also from the client and when the first call happens... Did you check the time frame from the logs about the first invite .. when it was sent and whether the delay was from the server to reach the client or from Mediation to FE.. since you have a 15 to 20 Sec gap i guess we can isolate this with log timings.

Also we could utilize Monitoring report to see if there  is a TAT delay and which leg its showing 


  • Edited by Akampa 45 minutes ago
February 12th, 2015 6:05am

Strange that the issue is there for many people here. When u enabled the logs from Server and also from the client and when the first call happens... Did you check the time frame from the logs about the first invite .. when it was sent and whether the delay was from the server to reach the client or from Mediation to FE.. since you have a 15 to 20 Sec gap i guess we can isolate this with log timings.

Also we could utilize Monitoring report to see if there  is a TAT delay and which leg its showing 


  • Edited by Akampa Thursday, February 12, 2015 11:02 AM
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 1:59pm

Strange that the issue is there for many people here. When u enabled the logs from Server and also from the client and when the first call happens... Did you check the time frame from the logs about the first invite .. when it was sent and whether the delay was from the server to reach the client or from Mediation to FE.. since you have a 15 to 20 Sec gap i guess we can isolate this with log timings.

Also we could utilize Monitoring report to see if there  is a TAT delay and which leg its showing 


  • Edited by Akampa Thursday, February 12, 2015 11:02 AM
February 12th, 2015 1:59pm

Strange that the issue is there for many people here. When u enabled the logs from Server and also from the client and when the first call happens... Did you check the time frame from the logs about the first invite .. when it was sent and whether the delay was from the server to reach the client or from Mediation to FE.. since you have a 15 to 20 Sec gap i guess we can isolate this with log timings.

Also we could utilize Monitoring report to see if there  is a TAT delay and which leg its showing 


  • Edited by Akampa Thursday, February 12, 2015 11:02 AM
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 1:59pm

Strange that the issue is there for many people here. When u enabled the logs from Server and also from the client and when the first call happens... Did you check the time frame from the logs about the first invite .. when it was sent and whether the delay was from the server to reach the client or from Mediation to FE.. since you have a 15 to 20 Sec gap i guess we can isolate this with log timings.

Also we could utilize Monitoring report to see if there  is a TAT delay and which leg its showing 


  • Edited by Akampa Thursday, February 12, 2015 11:02 AM
February 12th, 2015 1:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics