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

[Daniel]

thanks Ryan much appreciated


On Mon, Jun 25, 2012 at 11:18 PM, Ryan Ratliff <rratliff at cisco.com> wrote:

> Inline..
>
> -Ryan
>
> On Jun 22, 2012, at 7:02 PM, Daniel wrote:
>
> Thanks for the reply Ryan,
>
> The reason for "dan at test.com" on both systems is that if I was called
> from CUCM, Expressway, or Control that all my devices would ring, people
> would just ring that one URI. Maybe I should use SNR on CUCM and Findme on
> VCS to achieve this. Have different endpoint names but still have the same
> FQDN.
>
>
> This is how we do it today on the alpha cluster I'm using but we don't
> have URIs configured in UCM yet.  I have a remote destination for
> rratliff at cisco.com on my main phone that routes to a VCS (via sip route
> pattern) and my video endpoint there will ring.
>
>
> My other question is that if both systems are using "@test.com" when a
> call comes from a CUCM endpoint to a VCS endpoint if the URI "dan at test.com"
> doesn't exist on CUCM will it use the catch all "@test.com" SIP route
> pattern to route the call to VCS? Same thing for VCS to CUCM would it use
> the search patterns so that any "@test.com" calls with the endpoint that
> don't exist go to CUCM?
>
>
> Most users dialing from UCM endpoints will still be dialing DNs.  Full
> user at domain URIs will most likely get routed via call history (if
> present) or by desktop apps in deskphone mode.   I haven't tested
> overlapping domains on UCM but I would expect the behavior you describe
> with the sip route pattern picking up for any calls to URIs that don't
> exist locally.
>
>
> Next question about registration and DNS SRVs, is CUCM 9+ going to change
> the way endpoints register at all? What if both CUCM and VCS utilise SIP
> DNS SRV to register the endpoints? You would not be able to use the same
> FQDN then would you? Or is it as simple as using another subdomain. CUCM
> would have an SRV of "_sip._tcp.cucm.test.com" and VCS would have "_sip._
> tcp.vcs.test.com" for registering endpoints?
>
>
> Phone registration won't change (Cisco phones still use option 150 and
> register via DN).   I'm not familiar enough with the Tandberg endpoints to
> recommend a solution regarding the SRV records.  I think you'll want to
> look closely at feature parity between native UCM registration and keeping
> them on the VCS and go from there.  A subdomain very likely could reduce
> the complexity.
>
>
>
>
> On Sat, Jun 23, 2012 at 12:17 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
>
>> 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.comexternal 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
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120626/640c9eda/attachment.html>