Publisher for Call Processing?

[jneiberger]

I know the recommendation is to avoid using the CM publisher to do call processing, but I'm curious how many of you follow that guideline? If you use your publisher to call processing, have you noticed any performance issues because of it?

Thanks,
John

 

[jerake75]

I generally follow the guideline, but the only time I didn't was when we had local PRI's on a 6608 in the same building as our publisher CCM...the recommendation is (or was) to register your ports to a local CCM if possible, so I did. We did have a higher CPU/memory usage, and sometimes during failover the CPU did spike up to 100%. But, if your publisher is not only holding the master SQL database PLUS it's your TFTP server PLUS it's running MOH, etc. - performing multiple functions - the last thing it needs to handle is device registration and signaling.

TMH

 

[MG2005]

well it is your backup call processor in a 2 server cluster configuration, but I wouldnt want to use it daily as my primary call processor

all depends on how many phones registered, how much voice traffic and features are used, what hardware/server you are using...

you could prob get away with it in a small office or not so busy environment...