06-20-2014 12:33 PM - edited 03-19-2019 08:18 AM
Hi Everyone
I posted a question a few weeks ago about sites that we have that currently are using CUCM 4.2 and I want to remove the older boxes and set us up with a centralized call processing model.So far I've modified the config of my first site which is small and has only 20 users and I've created the DP and the regions. I wanted to know how much more do I have to do to make this first sight ready to move over to our SUB in our data center. I googled how to add a remote site in CUCM and I found 1 link from the Cisco board. I want to know if someone could look at this and tell me is this all that I would have left to do in order to get my first site ready and if so I'll duplicate it for all of the others.Thanks in advance as always for the help and I look forward to your response.
Solved! Go to Solution.
06-21-2014 09:55 PM
Hi Eric,
Yes, you can assign site specific device pools, CSS and partitions so that the IP phones of a specific site have access to the route patterns defined for them. If you use 'Local Route group' option then even CSS-partition configuration for each site is not required, you can configure the Local route group for each device pool to specify which gateway to use to route the calls out. You can check cucm features and services guide for more details about Standard Local Route Group.
HTH
Manish
06-20-2014 09:50 PM
Hi,
With centralized call processing model you can have the following scenarios for remote sites.
1. Remote site with no SRST failover
In this case you just need the IP phones at the remote site to be able to download the tftp config from cucm at main site, along with ensuring that ports for rtp / signaling ( h323 / mgcp / sip etc ) are open.
2. Remote site with SRST failover
In this case you can configure the gateway on remote site for SRST so that in case of WAN link being down between remote site and main site, the IP phones in remote site will be able to register with SRST router to ensure call processing and other functions. Details of SRST configuration can be found below
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_5_1/ccmcfg/bccm-851-cm/b02srst.html
http://docwiki.cisco.com/wiki/Cisco_Unified_Survivable_Remote_Site_Telephony_Configuration
https://supportforums.cisco.com/video/11930926/configuring-basic-srst
HTH
Manish
06-21-2014 12:57 PM
Manish
We are going to deploy option 1 with no SRST failover, so pretty much I just need to make sure that all of my GW configs point to the SUB at our data center to get to the TFTP server for the phones and make sure RTP signaling is allowed. But do I still need to configure CSS's and PT's for each remote site to make sure that they use their GW for outbound calls?
Eric
06-21-2014 09:55 PM
Hi Eric,
Yes, you can assign site specific device pools, CSS and partitions so that the IP phones of a specific site have access to the route patterns defined for them. If you use 'Local Route group' option then even CSS-partition configuration for each site is not required, you can configure the Local route group for each device pool to specify which gateway to use to route the calls out. You can check cucm features and services guide for more details about Standard Local Route Group.
HTH
Manish
06-23-2014 09:02 AM
Thanks for the help Manish, I really appreciate it
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide