Services on CUCM PUBLISHER and SUBSCRIBER.

[Ritesh Desai]

Hey folks,

i went though SRND but still I remain unanswered regards to services activation or running on CUCM PUBLISHER & SUBSCRIBER.

Am installing CUCM in 2:1, 2 sub and 1 pub where Call mgr, TFTP, DHCP would be activated on SUB. Phone would be registered to Sub.

My doubt is on Publisher which services should I need to activate which makes Publisher handle both SUBSCRIBERs database.

Correct my statement, installing First node in cluster is only important for Publishers functionality. All services except TFTP, DHCP, CM services wil run on PUBLISHER.

[Mohammed Khan]

Database replication is independent of service activation, No need to activate an service in Publisher. To answer which service to start. Its upto your IPT design. In your case you can also have Pub also acting TFTP Server.

[Ritesh Desai]

Chris and M.Khan,

Thanks for your answers. My design consist of Single Site deployment where Servers and Agents remain on same site i.e. on LAN. I have considered 2:1 design as I said above.

Its a Contact Center deployment. I just want Publisher to maintain both Subscribers database.

thanks...

regards,

Ritesh Desai

[Chris Deren]

So, how many total CUCM servers do you have? 1 Pub and 2 Subs? If that is the case you cannot really build 2:1 redundancy as that would require 2 primary subs and 1 backup sub, and I would not advise using Pub as only backup "subscriber". So, in this case I would load balance traffic between the 2 subs and have them backup each other with Pub being the third option. Such as:

CUCM Group 1: Sub1, Sub2, Pub

CUCM Group 2: Sub2, Sub1, Pub

[Ritesh Desai]

Chris sir,

I correct my statement its 1:1 deployment. Its my 1st Contact Center deployment. Studying SRND. Working hard for smooth deployment.

Just to correct my understanding, on Publisher I would only activate Network services and on 2 Subscribers I would activate rest services Cisco CM Services, TFTP, Media services, etc. I just want Publisher to maintain both Subscribers database.

Any suggestions would be appreciated.

regards, Ritesh Desai.

[Chris Deren]

Like I said earlier it depends on your deployment size. You may want to run TFTP on the Publisher, Extension Mobility, etc.  Smaller clusters may also have the CallManager, CTI Manager, Media streaming services enabled if there are only 2 or 3 total nodes in a cluster. How many total devices, agents and sites do you expect to have on this cluster?

[Ritesh Desai]

Chris,

400 agents we have planned to have in cluster.

regards,

Ritesh Desai

[Chris Deren]

That does not really affect CUCM sizing that much. How many total phones/analog devices and remote locations?

[Ritesh Desai]

Hi Chris,

Appreciate your interests! Thanks. :)

Setup consists of 50nos of 7821 and 350 CIPC SIP Phones. No Analog devices. There is no remote site in our setup.

Later, in new setup there will be 3 remote sites with total 1500 agents.

regards,

Ritesh Desai

[Chris Deren]

When you say agents I am assuming phones as CCX can only support 400 mass agents per system. If it going to scale up to 1500 phones, then here is how I would build the cluster:

1 Pub

2 call processing Subs/media servers

1 TFTP server - needed whenever you go beyond 1250 phones

[Ritesh Desai]

Chris,

Yes... I have gone through SRND. 1500 agents setup is totally different then current one.

Thanks for guidance...

regards,

Ritesh Desai.

[Chris Deren]

It boils down to what features and integrations you are planning on enabling on CUCM nodes.

In larger clusters it is only recommended to run: DirSync, SNMP, Serviceability reporter, AXL, BAT, CAR, and DNA, perhaps Extension Mobility on the Pub. Call processing Subs would run service such as CallManager, CTI Mgr, IP Media Streaming, Serviceability reporter. You may or may not have dedicated TFTP node (needed for deployments with 1250+ phones).

There are obviously other services that may or may not apply to your deployment.