[cisco-voip] CUCM VCS DNS SRV Registration and URI Dialing

[Florian Kroessbacher]

Hy out there

what about 2 ucm clusters and one vcs, vcse.

--
Florian Kroessbacher
gmail: florian.kroessbacher at gmail.com

Am 22.06.2012 um 16:18 schrieb Ryan Ratliff <rratliff at cisco.com>:

I'll defer to the 9.0 SRND when it's out but I believe you will be ok with
the same domain on both.  Expressway can send incoming calls to both VCS
and UCM.  On UCM 9.0 the service that takes care of sharing URI information
among clusters is ILS.  VCS can't talk directly to ILS yet but ILS does
support importing data from VCS so that UCM will know exactly which URIs
should route to VCS.  What this doesn't help with is shared URIs on both
VCS and UCM.   Is there a reason you'd have dan at test.com in both systems?


-Ryan

On Jun 22, 2012, at 7:54 AM, Daniel wrote:

Hi All,

There’s a lot of acronyms in that subject!!

We’re currently looking at integrating VCS into our CUCM and H323 Tandberg
environment to migrate our VC/Tandberg/Telepresence gear to SIP and enable
external IP video conferences.

We're on CUCM 8.5 with the new VCS being VCS-C 7.1 we will have VCS-E also.

My question is on the strategy for our domain name and what to use for DNS
SRV and URI Dialling.
When we upgrade to CUCM 9.0 and have URI dialling within CUCM do the domain
names need to be different on CUCM and VCS?

How will it work, how will the call route if I'm dan at test.com on CUCM and
VCS.?
Does it need to be dan at test.com on CUCM and dan at video.test.com on VCS?
This would be eaiser with a SIP route pattern of "@video.test.com" to VCS
etc...
External DNS (VC calls form the internet) would then be transformed from "@
test.com" to "@video.test.com" on the VCS
Calls from VCS to CUCM would use DNS SRV, zones, and search rules pattern
matching @test.com to be sent to CUCM. CUCM would be configured with a
cluster wide FQDN as "test.com"

Right now its 1234@<CUCM IP> on CUCM and dan at test.com (@test.com external
also) on VCS which is very simple.

I think I understand how it works for registration but not for call routing.

I just want to make sure we configure the correct domain name now so we
don't have to change it in the future when upgrading to CUCM 9+.

Does anyone have any experience with this?

thanks

Dan

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120622/a37741ea/attachment.html>