Avaya Communicator for web and Skype for business both SIP 5060 3

[anon0101]

Is it possible to run a WebRTC/Avaya Communicator for web setup along side of a Skype For Business 2016 on premise install? I ask because we have service records SFB is using _sip._tcp... using port 5060 and isn't that what a WebRTC/Avaya Communicator for web setup will use too?

 

[Pepp77]

Never use 5060 for WebRTC/Communicator myself, I always change it within the IPO to something less obvious.

| ACSS SME |

 

[janni78]

Don't remember Communicator for Web using 5060.

But if several apps use the same ports you would need them to contact different IPs.

"Trying is the first step to failure..." - Homer

 

[pkdev]

WebRTC is not using 5060 ! it uses the port 9443 (1XP port)
Avaya Communicator for Windows is using 5060 (if port is default).

What your are mentioning (_sip._tcp) is a SRV DNS record. This may be used by one X mobile or Avaya communicator for Windows. But as this is not mandatory. I dont think you will have issue to work with both Avaya and Skype.

 

[sizbut]

It does and it doesn't.

Between the WebRTC client and the WebRTC Gateway it uses 56000-58000. Between the WebRTC client and the one-X Portal service is uses 9443.

However, between the WebRTC Gateway service and the IP Office service it uses a SIP connection to relay the audio stream so that's where 5060 (or whatever is configured for SIP on the IP Office) comes into play.

Normally all three services are on the same server so that SIP leg is invisible. Even when its an IP Office Application server supporting WebRTC for an IP500 V2 both will be inside your network.



Stuck in a never ending cycle of file copying.

 

[anon0101]

Ahhhhhh... Gotcha. So the sip/5060 connection is only between the WebRTC GW and the IP Office and the external dns sip records don't effect that? Avaya Communicator for web uses 9443 to connect to my WebRTC Gateway? If so, then I only need ports 9443 and the 56000-58000 open on the firewall for Avaya Communicator for web to make the connection?

 

[Pepp77]

You will probably find that for WebRTC you will also need 7443 open for it to actually work.



| ACSS SME |

 

[anon0101]

I appreciate the info everyone, I believe my issue is with the certificate. We loaded our wildcard cert on our app server but the external dns/ip still want to use the default iposerver-***** cert when you try to go to :9443.

 

[janni78]

You must tick "Renew automatically" when you import the certificate, otherwise it won't update it on all applications.

"Trying is the first step to failure..." - Homer

 

[anon0101]

Just wanted to post that everything is up and running now. The cert comment from janni78 was crucial for me along with making sure my DNS names were correct according to the word doc in this Avaya support article.

https://support.avaya.com/ext/index?page=content&id=SOLN271667

Thanks for all of the help!!