Capro Process?

[AvayaGuy1222]

What is, or what would describe the "Capro process" when it comes to CM? Anyone know? Have never heard of it but can't find a decent description of it online. Thx

 

[boristhespider2]

This process is responsible for call processing.

 

[boristhespider2]

or in more detail.

SOLUTION
Following are the different Communication Manager processes and thir functionality:
Capro: Capro is the Multivantage call-processing process. Capro is actually made up of many processes, including the user-manager the service dispatcher and the connection manager, each of which performs very different functions.
HMM (high level maintenance): This is the high level maintenance manager. The process that handles all maintenance in Multivantage. This process prints all proc-errors and is ultimately responsible for the initialization of the system. It's also the dispatcher of the maps (maintenance action processes) that handle much of it's work, including the initmap. Note that the hmm is merely responsible for printing proc-errors.
GMM (general maintenance manager): This is the general maintenance manager, responsible for ensuring that alarms are created and reported appropriately. The GMM receives alarms directly from platform processes. For Multivantage (O/P) processes, the MDM spawns an rma_mgr if an alarm is necessary.
Arbiter: This is the process on the system responsible for making decisions on server interchanges. The arbiter takes input from the pcd, the prc_mgr, GMM, and watchdog to make decisions on which server is healthier and thereby decides which server should be active.
watchd (watchdog): The watchdog keeps an eye on all processes in the system, maintaining heartbeats with both Multivantage and platform processes. The watchdog is responsible for stopping and starting processes when necessary. This process watches over the entire system, while the initmap essentially watches over only the Oryx/Pecos processes.
prc_mgr: This is the process manager, the piece of Definity partially responsible for creating and destroying all Oryx/Pecos processes. It ensures the system comes up correctly and manages what recovery actions to take (via the hmm and initmap) when a process has a problem.
rma_mgr:This is a process spawned by the MDM to call out an alarm to the GMM; rma_mgr's are created and immediately destroyed by the prc_mgr after performing their call.
pcd (packet control driver ): This process the packet control driver,is responsible for providing the interface between the Multivantage application software and the PKTINT. All packet bus communications coming up from the pktint travel through the pcd (over IP in Multivantage) to reach call-processing.
gip: The gip or gaz interface process, creates all sockets for the user_mgr to communicate with IP endpoints.One of it's primary purposes is to serve as the resource manager for the CLAN board.
fastmap: A map (maintenance action process) spawned by the HMM when high priority actions are required. The fastmap is usually allocated by the HMM to handle IPSI interchanges or various other SPECON recovery actions. It has a higher priority than capro.
border: This process is responsible for providing communications between platform processes and Multivantage processes for example, the arbiter requires the border process to relay messages to the PCD.
initmap: This process is spawned by the hmm and is responsible for creating all permanent processes and maintaining sanity with them. It also notifies the system when it's reached normal_op.
ndm (duplication manager): This process is essential for maintaining shadowing between an active and standby server. The dup manager performs tests to ensure that the duplication strategy is working as designed (i.e. shadowing and filesync) and verifies that the standby side is refreshed.
pam: The permissions and access manager prints all commands entered in a SAT into the logfile, it is very useful when troubleshooting to find out what commands were being issued on a system

 

[AvayaGuy1222]

Thank you Boristhespider2!