SIP Server internal modules [DRAFT]

SIP Server when working in Cluster mode uses special ports that give access to the internal modules that provide the cluster functionality. These modules include:

• T-Controller — Responsible for:

• • Registration operations (register/unregister DN)
  • Agent-level operations (login/logout, ready/not ready)
  • DN-level operations (call forward, DND, call supervision)
  • Query operations
  • Agent reservation
• Interaction Proxy — Responsible for load balancing interaction events (call monitoring) to SIP Server clients from the same pool.
• Session Controller — Responsible for maintaining call sessions.
• ISCC Proxy — Responsible for multi-site transactions.

Note from Barry: TController and Interaction Proxy are exposed as ports to the user. Instead of calling them modules, we should just call them ports, and describe the functionality as offered by SIP Server generally, not through the module. "By connecting to the T-Controller port, SIP Server is able to do such and such." As opposed to "... T-Controller will be able to do such and such." As for Session Controller, it may be enough to describe that SIP Server keeps track of all session information. We might not need to talk about the module that provides that.