Jump to content

wolfru68

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by wolfru68

  1. 14 hours ago, mc_ said:
    I can embroider a question on architecture ?
    1.ACM is the core of PBX. Used to control media Gateway (G650) and communication protocols. It implements the logic of routing the queue and connecting agents connecting trunks. This logic is limited to very specific capabilities.
    2. AES integration server with ACM. For routing control and agent management, the protocols cvlan, tsapi, dmcc are used. AIC uses - CVLAN. NICE (communication conversation recording) - TSAPI and DMCC. SDK JAVA. too, the function is limited by the possibility of protocols. In ASTERISK interface AGI, AMY, CGI.
    3.VP (voice portal) uses G650 ports. All IVR application logic for voice menus uses VP ports. SDK IVR allows you to run SOAP. functions are limited. there is no logic for routing and queue processing (PBX)
    4.AIC is the processing logic with mail,sms or return to dialplan PBX.it has its own queue logic and connections to external LDAP, SMTP servers.workflow look like (callflow kazoo). Customer database and processing logic inside AIC. I read about the possibility of integrating kazoo with CRM systems. For example SuiteCRM.
    5. Statistics is a separate component of AVAYA IQ. Connector to ACM.
    template build real-time reports and chronological
    (minimum interval 15 minutes). here the main elements are queue, agent, routing point. The entity group of the agent group, the queue group, the routing point group is added.
    feature the ability to trace calls by points.
    6. Each component uses clustering. AIS is built on a CORBA broker. NPP duplicates connections .VP media nodes servers.
    7.To test agent management there are utilities. for example DMCC client. It is possible to send requests in the CML format to see the response or message error code. Does kazoo have debugging tools or such an option only in the SDK and logs?
    8. The similarity of the architecture of Avaya and Kazoo in the cluster architecture of components and the use of the CML format for exchange. But Avaya's architecture is built by adding new components while preserving the main components (core). With this model, there is duplication of functionality in different components for compatibility. My task at the first stage is to configure kazoo using the API, but taking into account the peculiarities of the interaction of the main components (kammailio, Freeswitch, Haproxy, Rabbitmq and bigcouch).
     

     

     

     

     

  2. I managed to disable Kazoo from RPM. Now you need to find out how this software works. those. interconnection of system components at a high level. The purpose of each component is clear. How they interact in practice. Diagnose streaming calls and what happens in each component.
    tell me where to start?
    I manage the AVAYA contact center. The architecture is different from kazoo in AVAYA. You can find examples of the implementation of various schemes for constructing clusters.
    thank you in advance !!
  3. Добрый день! 

    Мне удалось отключить Kazoo от RPM. Теперь вам нужно выяснить, как работает этот программный комплекс. т.е. взаимосвязь компонентов системы на высоком уровне. Назначение каждого компонента понятно. Как они взаимодействуют на практике. Диаграммы потоков вызовов и что происходит в каждом компоненте.

    подскажите с чего начать?

    Я управляю контакт-центром AVAYA. Архитектура отличается от казу в AVAYA. Можно найти описание примеров реализации различных схем построения кластеров.

    заранее спасибо !!

×
×
  • Create New...