CUCM Process Types

[Ayodeji Okanlawon]

Hi Guys,

Does any know what the list of the process types is on CUCM.

EG in this PID

PID=SIPD(2,100,74,61)

The format of the PID= Process name (Node_id, Application ID, Process Type, Process Instance)

The 2 =node ID

100=CUCM

74= I believe is the sip trunk process or SIP

Can someone confirm this and do you have the lists of the other processes in CUCM.

[Rajan]

Hi Deji,

I guess "Process Type" is not fixed and might differ unlike Application ID which is fixed.

Application ID 100 - CUCM
200 - CTI

Prcoess type should be identified only with the keyword before like SIPD, StationD, STationinit, CC, CDCC etc..

HTH

Rajan

[Ayodeji Okanlawon]

Rajan,

Thanks for the response. from What I am seeing in the logs, it does look like it is fixed. I believe that process tyoe has to be fixed from a database point of view..

Examples:

RouteListControl(5,100,82,7)

All the RouteListControl process seem to have a process type of 82

LineControl(35,100,167,1240): Linecontrol has 167

DeviceManager(23,100,199,1) has a process id of 199

Cdcc is on 212 while CC is 213.

Cdcc(23,100,212,3433)          

 Cc(23,100,213,1

[Rajan]

Hi Ayodeji,

Thanks for the info. I dint noticed that it remained constant. The process ids are not much relevant and might not be that useful. Anyways as Leszek pointed out, we will be dealing with the process name mentioned before to find out whether its a global process or a call dependent one (generated on a per call basis).

Thanks,

Rajan

[Leszek Wojnarski · Accepted solution]

Hi Ayodeji,

In you example, 74 referes to SIPD process as you've noticed. So It's just number value for SIPD

SIPD(2,100,74,61)

For other processes it will be the same for example 212 is numeric for Cdcc so you can get name of the process from the traces:

Cdcc(1,100,212,5).

But I guess what you are asking is what this process does, there is a lot of processes, so I don;t have full list of all of them, but here is the list of common device processes for example:

StationD – controls one Skinny device
SipD – controls one Sip Trunk
SipStationD – controls one Sip phone
H225D – controls one H.323 gateway
MgcpPn9D – controls one mgcp gateway
MgcpTrunkD – controls one FXO, E&M or T1 CAS gateway

These processes are created and destroyed on a per call basis:
StationD -> StationCdpc
SipD -> SipCdpc
SipStationD->SipStationCdfc and SipCdpc (call dependent feature control)
H225D -> H225Cdpc
MgcpPn9d -> MgcpPn9cnet or MgcpPn9cuser (one side of a pri connection for mgcp is “network” and one side is “user”)
MgcpTrunkd->MgcpTrunkcdpc

And there is much more, not sure in which processes in particular you are interested in.

Leszek 

[Ayodeji Okanlawon]

Thanks for your response. I do agree and I found the process id after posting out here. I do know that the process does, I just wanted the processs ID.