Shared SIP Domain - VCS and NO lync integration

[CHRIS KALETH]

We currently have a lync 2010 sip domain of first.lastname@abc.com and don't plan to integrate lync with our new VCS environment. I want to use the same domain first.lastname@abc.com for our video environement (ex90s, VCSc 8.x, VCSe  8.x, Jabber (cloud IM/Presence), CUCM 9.1.x). Yes, we have lync in production and testing Jabber with UC integration.  What are the options and ramifications of using the same domain for both assuming no lync integration into our CUCM/VCS environment? 

[Wayne DeNardi]

Where is someone going to connect to when they try to connect to you.name@abc.com - is that supposed to go to Lync, or supposed to go to your VCS?  Unless you ahve a single gateway that can differentiate between and send the traffic to each of the environments correctly, you're going to have issues.

I'd go with (and have in my environment) the standard my.name@abc.com for Lync and my.name@vc.abc.com for the proper VC world.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

[Patrick Sparkman]

If I'm reading this right, there are no identical DNS SRV records for TelePresence and Lync.

Lync 2010 SRV records:

http://social.technet.microsoft.com/Forums/lync/en-US/b383a55c-022a-4211-9a0e-b9e2180262ee/lync-2010-how-to-create-srv-records-in-public-dns-for-auto-login?forum=ocsplanningdeployment

VCS X8.1 SRV records (page 40):

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-1/Cisco-VCS-Cluster-Creation-and-Maintenance-Deployment-Guide-X8-1.pdf

So, you could possibly use the same domain.

[Wayne DeNardi]

They both use the _sip._tcp DNS entry... so there would be an issue if you were trying to use the same thing for both...

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

[Martin Koch]

Regards the technical part I agree with Patrick.

On the inside its not required and if I see it right on the outside its not used, on lync its

mainly _sipfederationtls._tcp and _sip._tls.

If the SRV records would be an issue, not only a single domain split set up would not work

but neither an integrated one.

That said, though the technology might be fine and does not get confused, the people

who are using it might, I expect him to hear: "Why cant I reach whoever@abc.com when I dial from video/lync".

So it is better to have a plan regards that.

Please remember to rate helpful responses and identify helpful or correct answers.

[Patrick Sparkman]

Take a look at this document, bottom of page 60 and top of 61, it shows the DNS SRV records that are used for video and Lync.

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/X8-1/Cisco-VCS-Microsoft-Lync-Deployment-Guide-X8-1.pdf

[Paul Woelfel]

As Patrik said, the DNS SRV rcords do not overlap, so it is possible to use the same domain for Lync and VC. For integrating both systesm you must check your call rules, so they won't overlap.

[Martin Koch]

One thing regards the understanding of the SRV lookups, most clients have some kind of serial processing

of the lookup process. Meaning, if a client for example uses and can lookup and connect to tls it will

not try tcp anyhow. Also not all SRV records are neccessaily needed to be present and again inside and outside

lookups can be different as well.

Please remember to rate helpful responses and identify helpful or correct answers.