[cisco-voip] Child Process & Clarification

[Daniel Pagan]

Folks:

I'm curious if someone can tell me the purpose of creating child processes, specifically LineCdpc and StationCdpc?

I ask about LineControl because my understanding was that it handled both Max Call & Busy Trigger management AND call dispatch to associated phone devices, but now I see it's actually LineCdpc and I'm curious if there's logical reasoning behind this. I ask about StationCdpc because I see (for calls sourced from a JTAPI client) that both StationD and StationCdpc process are talking to CTIDeviceLineMgr. What I can't figure out is the need for creating these Cdpc's and how their responsibilities differ from their parent process.

Does StationCdpc handle application-level updates that result from transmitted StationD and received StationINIT events? Kind of like acting as an intermediary between actual SCCP events and internal SDI/SDL communication to other processes involved?

Also, am I correct in saying LineControl handles management over busy trigger and max calls per line instance whereas LineCdpc handles the dispatch of calls to the StationD process? Or should there be only one LineControl process per DN while another process handles max calls & busy trigger management on a per line instance basis? Tests in a 9.1.1 lab shows the latter - one LineControl instance while StationD handles the active calls/max calls/bt values... but tests also show issues where shared line appearances with varying MaxCalls/BT values cause voicemail forwarding due to these values being prematurely reached. Trace entries and behavior don't line up with actual configurations so I'm hoping for some clarification. All devices are registered to a single node in this lab environment.

Sorry for the long winded e-mail and I hope you don't mind the brain picking.

- Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131024/7e4917bb/attachment.html>