Talk:CallBridge Collection

Hello, we could add a table like the one below, valid for the three types of CallBridge providers:

Currently supported phones

Workpoint	Operating mode	Connection	CallBridge TA	CallBridge TU	CallBridge IP	Note
optiSet E basic	Up0/E	V.24	Yes	No	No	1
optiSet E advance	Up0/E	V.24	Yes	No	No	1
optiSet E advance plus	Up0/E	V.24	Yes	No	No	2
optiSet E conference	Up0/E	V.24	Yes	No	No	2
optiSet E memory	Up0/E	V.24	Yes	No	No	2
optiPoint 500 basic	Up0/E	USB	No	Yes	No	1
optiPoint 500 standard	Up0/E	USB	No	Yes	No	2
optiPoint 500 standard SL (USA only)	Up0/E	USB	No	Yes	No	2
optiPoint 500 advance	Up0/E	USB	No	Yes	No	2
optiPoint 600 office	Up0/E	USB	No	Yes	No	2
optiPoint 410 entry	HFA	IP	No	No	Yes	1
optiPoint 410 economy	HFA	IP	No	No	Yes	1
optiPoint 410 economy plus	HFA	IP	No	No	Yes	1
optiPoint 410 standard	HFA	IP	No	No	Yes	2
optiPoint 410 advance	HFA	IP	No	No	Yes	2

• Note 1: These workpoints have the On-Hook Dialing feature, but not Handsfree. This means that user can only answer an incoming call or establish a connection to the remote station by manually lifting the handset.

• Note 2: These workpoints have both On-Hook Dialing and Handsfree features as well as a loudspeaker key. This means that user can make a call without needing to operate the phone manually.

--Kimera 11:23, 16 November 2006 (CET)

---

Have a look on the Phone supporting matrix. And the optiPoint SIP phones - are they also applicable? ... and I think, we should put in another row with optiPoint 600 as HFA device. --Horemu 16:01, 16 November 2006 (CET)

---

Hi, added optiPoint 600 office HFA (CorNet IP), it was left behind ;-).

About CallBridge Collection V2.0 and optiPoint 410/420 S: yes, it should support those SIP versions (Obiouvsly only via an IP TSP like CallBridge IP that relies on CorNet TS TSP over IP) but it's not explicitly stated anywhere.

On the optiPoint 410/420 V6.0 S (Either available via optiGuide or phone's WBM), there are two CTI-related configurable parameters:

* Auto Answer CTI

* Auto Reconnect CTI

those parameters let SIP workpoints interworking with a (Not well defined) CTI application running on a PC on the same LAN.

This argument it's interesting: SIP CTI it's quite a bit a new approach, SIP can potentially reduce or replace complex CTI integration (And application using it are doing that) with a simple and open standard to implement 3rd Party call control through its Call Control Extensions; moreover, because SIP is based on the concept of intelligent endpoints, advanced call control scenarios can be invoked with relatively simple SIP call methods.