Skype For Business conflict with One-X Attendant

[marcsuttle]

Our receptionists currently use One-X Attendant (rel. 4.08.030.000). They also use Lync 2013 for IM only. We are converting Lync to cloud based Skype For Business. When testing this new configuration we discovered a conflict between Skype and 1XA.

With Skype signed out all calls to/from 1XA go idle as soon as call is answered (verified with List Trace).

With Skype signed in all calls complete but two things happen >
#1 the Skype For Business app "pops" for every 1XA call in or out.
#2 the attendant receives a 2nd dial-tone from CM that is heard simultaneous with the attendant call. This 2nd dial tome eventually times out and the CM handset off-hook alarm is heard.

Removing Skype For Business feature from Windows set up solves the problem.

I'm guessing that Skype is trying to grab some Windows telecom resources that 1XA needs.

We can live without Skype on the attendant machine but I'd like to understand the issue.

We are on CM 6.2 run One-X Communicator (rel. 6.2 SP4) with Skype For Business without any problem.

 

[kyle555]

Yeesh. Sounds like you've got 2 conflicting programs grabbing the same drivers or something underlying in the OS.

Could you not just have a desk phone for the receptionist and have 1XA in telecommuter to that phone so you don't take the audio from the PC anymore?

Also, Avaya Communicator for Lync is supposed to support Skype for Business imminently if it doesn't already - might be a decent way to replace the One-X Communicators if you're not too heavily reliant on the keys on the phones.