Talk:CallBridge Collection - Revision history

Gunnar.boll at 21:16, 23 November 2006

2006-11-23T21:16:53Z

Davide.poletto at 23:16, 20 November 2006

2006-11-20T23:16:04Z

Davide.poletto at 21:02, 16 November 2006

2006-11-16T21:02:43Z

Davide.poletto at 20:44, 16 November 2006

2006-11-16T20:44:27Z

Davide.poletto at 20:44, 16 November 2006

2006-11-16T20:44:07Z

Davide.poletto at 20:14, 16 November 2006

2006-11-16T20:14:37Z

Davide.poletto at 19:58, 16 November 2006

2006-11-16T19:58:33Z

Davide.poletto at 19:57, 16 November 2006

2006-11-16T19:57:46Z

Horemu at 15:08, 16 November 2006

2006-11-16T15:08:48Z

Horemu at 15:02, 16 November 2006

2006-11-16T15:02:21Z

← Older revision		Revision as of 21:16, 23 November 2006
Line 159:		Line 159:

	--Kimera 21:44, 16 November 2006 (CET)		--Kimera 21:44, 16 November 2006 (CET)
		+
		+	oP410/420 SIP phones do not support 1st party CTI, just uaCSTA to control the phone by an 3rd party CTI apps like ComAssistant via HiPath 8000 --[[User:Gunnar.boll\|Gunnar.boll]] 22:16, 23 November 2006 (CET)

@@ Line 149: / Line 149: @@
 :: Hi, added optiPoint 600 office HFA (CorNet IP), it was left behind ;-).<br \>
-:: 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.<br \>
+:: About CallBridge Collection V2.0 and optiPoint 410/420 S: yes, it ''should'' support those SIP versions (I think via an IP TSP ''like'' CallBridge IP) but it's not explicitly stated anywhere.<br \>
-:: On the optiPoint 410/420 V6.0 S (Either available via optiGuide or phone's WBM), there are two CTI-related configurable parameters:
+:: 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.<br \>
-:: Related arguments: see ECMA TR/87 (June 2004).
+:: Related arguments: see ECMA TR/87 (June 2004) see [CSTA] page.
-:: Probably optiPoint 410/420 S implement the uaCSTA (User Agent CSTA) and so CSTA messages over SIP session.
+:: Probably optiPoint 410/420 S implement ''a'' uaCSTA (User Agent CSTA) and so they implement CSTA messages over SIP session.
 --Kimera 21:44, 16 November 2006 (CET)

@@ Line 154: / Line 154: @@
 :: * ''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.
+:: 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.<br \>
 --Kimera 21:44, 16 November 2006 (CET)

← Older revision		Revision as of 20:44, 16 November 2006
Line 155:		Line 155:
	:: those parameters let SIP workpoints interworking with ''a'' (Not well defined) CTI application running on ''a'' PC on the same LAN.		:: 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.		:: 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.
		+	--Kimera 21:44, 16 November 2006 (CET)

@@ Line 141: / Line 141: @@
 --Kimera 11:23, 16 November 2006 (CET)
 : Have a look on the [[CallBridge Collection#Phone supporting matrix|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. --[[User:Horemu|Horemu]] 16:01, 16 November 2006 (CET)
@@ Line 147: / Line 149: @@
 :: Hi, added optiPoint 600 office HFA (CorNet IP), it was left behind ;-).<br \>
-:: 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) but it's not explicitly stated.<br \>
+:: 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.<br \>
-:: Moreover, on the optiPoint 410/420 V6.0 S (Either available via optiGuide or phone's WBM), there are two CTI-related configurable parameters:
+:: 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.
-:: Need more investigation/test.
+:: 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.

@@ Line 147: / Line 147: @@
 :: Hi, added optiPoint 600 office HFA (CorNet IP), it was left behind ;-).<br \>
-About CallBridge Collection V2.0 and optiPoint 410/420 S support it ''should'' be possible (Obiouvsly only via an IP TSP application, in that case the CallBridge IP ''or'' the HiPath TAPI 120 V1.0).<br \>
+:: About CallBridge Collection V2.0 and optiPoint 410/420 S support it ''should'' be possible (Obiouvsly only via an IP TSP application, in that case the CallBridge IP ''or'' the HiPath TAPI 120 V1.0).<br \>
-Moreover on the optiPoint 410/420 S (Either available via optiGuide or phone's WBM), I'm referring to V6.0, there are two CTI-related parameter likes:
+:: Moreover on the optiPoint 410/420 S (Either available via optiGuide or phone's WBM), I'm referring to V6.0, there are two CTI-related parameter likes:
-* Auto Answer CTI
+:: * Auto Answer CTI
-* Auto Reconnect CTI
+:: * Auto Reconnect CTI
-those let the phone interworking with ''a'' (Not well defined) CTI application running on ''a'' PC on the same LAN.
+:: those let the phone interworking with ''a'' (Not well defined) CTI application running on ''a'' PC on the same LAN.

← Older revision		Revision as of 19:57, 16 November 2006
Line 143:		Line 143:

	: Have a look on the [[CallBridge Collection#Phone supporting matrix\|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. --[[User:Horemu\|Horemu]] 16:01, 16 November 2006 (CET)		: Have a look on the [[CallBridge Collection#Phone supporting matrix\|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. --[[User:Horemu\|Horemu]] 16:01, 16 November 2006 (CET)
		+
		+	----
		+
		+	:: Hi, added optiPoint 600 office HFA (CorNet IP), it was left behind ;-).<br \>
		+	About CallBridge Collection V2.0 and optiPoint 410/420 S support it ''should'' be possible (Obiouvsly only via an IP TSP application, in that case the CallBridge IP ''or'' the HiPath TAPI 120 V1.0).<br \>
		+	Moreover on the optiPoint 410/420 S (Either available via optiGuide or phone's WBM), I'm referring to V6.0, there are two CTI-related parameter likes:
		+	* Auto Answer CTI
		+	* Auto Reconnect CTI
		+	those let the phone interworking with ''a'' (Not well defined) CTI application running on ''a'' PC on the same LAN.

← Older revision		Revision as of 15:08, 16 November 2006
Line 142:		Line 142:
	--Kimera 11:23, 16 November 2006 (CET)		--Kimera 11:23, 16 November 2006 (CET)

−	: Have a look on the [[CallBridge Collection#Phone supporting matrix\|Phone supporting matrix]]. And the optiPoint SIP phones - are they also applicable? --[[User:Horemu\|Horemu]] 16:01, 16 November 2006 (CET)	+	: Have a look on the [[CallBridge Collection#Phone supporting matrix\|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. --[[User:Horemu\|Horemu]] 16:01, 16 November 2006 (CET)

← Older revision		Revision as of 15:02, 16 November 2006
Line 142:		Line 142:
	--Kimera 11:23, 16 November 2006 (CET)		--Kimera 11:23, 16 November 2006 (CET)

−	: Have a look on [[CallBridge Collection#Phone supporting matrix\|Phone supporting matrix]]. And the optiPoint SIP phones - are they also applicable? --[[User:Horemu\|Horemu]] 16:01, 16 November 2006 (CET)	+	: Have a look on the [[CallBridge Collection#Phone supporting matrix\|Phone supporting matrix]]. And the optiPoint SIP phones - are they also applicable? --[[User:Horemu\|Horemu]] 16:01, 16 November 2006 (CET)