Generic net structure inclusive CT-iq Public Network (PN) Customer internal Network (CiN) CTI(option)CT-iq Company LAN IN LAN  Caller INoperator(IN)MobileOperator(MO)  MO LAN Desktop

What is CT-iq ?  Platform to exchange information between Public Network (MO or IN), CiN and internal applications in CiN  Process which exchanges information with (MO or IN), and at the same time can be connected to CiN with CTI (Computer Telephony Integration)

CT-iq process control with IN Public Network (PN) Customer internal Network (CiN) CTI(option)CT-iq ISDN Company LAN IN LAN  Caller INOperator(IN) MobileOperator(MO)  Desktop Tcp/ip

Intelligent Network (IN) information flow IN  Call arrives at IN from PN, where caller presses DTMF choices and optional customer ID (ex.)  IN sends received information to CT-iq which maps information on CiN with CTI  CT-iq associates IN information with actual call and then synchronises voice and data at the application level, so we can do database lockup based on information received at IN level

Intelligent Network (IN) information flow OUT  Call overflows in queue system after timeout, or can also overflow without queue system, internally controlled by CiN solution  CT-iq sends information to IN about the call, IN takes control of the call by information sent by CT-iq and thereby tromboning is avoided at CiN side  Releases resources in CiN and calls can be handled more professionally in mixed and/or decentralised environments

CT-iq process flow with MO Public Network (PN) Customer internal Network(CiN) ISDN  Caller INOperator(IN)MobileOperator(MO)  MO LAN CTI(option)CT-iq Customer LAN DesktopOperator Tcp/ip

Mobil Operator process flow  Status and control of mobile users is sent back/forth to CT-iq which exchanges these information with CiN operators  CiN operator can call mobile users directly from status client application with CTI  CT-iq can request to MO that MO transfers the incoming CiN call on public side to avoid tromboning in CiN

Mobile operator client application CiN  Can establish busy lamp fields which is updated by CT-iq process  Status on mobile users is exchanged between MO and CT-iq (busy, free, outside coverage and more but depends on MO  Call or transfer can be done by CTI, first party or third party  CT-iq can request MO to transfer incoming call in public network to avoid tromboning (depends on MO)

IN/MO vs. CT-iq Information flow  IN/MO communicates with CT-iq by secure RAS which is secured by MO/CiN  Direct or called connection must be evaluated by means of traffic load between CiN and MO  Any network which can send and receive tcp/ip can be used

CT-iq openess  CT-iq is purely based on tcp/ip between IN or MO and CT-iq  CT-iq uses open CTI platform which is independent of voice solutions on CiN. CTI can also be optional  CT-iq can simply communicate with other LAN elements by tcp/ip or CTI  CT-iq is based on MS technology so all MS methods can be used (DLL, COM/DCOM, ODBC/ADO el.l.). This can be done without to much integration work

CT-iq real iq? Open and scalable independent of CiN platforms/solutions, IN operators and CiN applications (ex. CRM solutions) Quick payback because effectiveness of internal resources and better customer service Future but yet available now...

CT-iq on the net …... for everyone and all over  On the net  For the users  Computer Telephony Intelligence (iq)=CT-iq 