CallBridge Collection is a Commercial software in the category Miscellaneous developed by Siemens AG. OpenScape Business V1, CallBridge Collection V2.3, Installation Guide, Issue 1 - Download as PDF File (.pdf), Text File (.txt) or read online. Mar 16, 2015 - OpenScape Business V2 – Internet Telephony Configuration Guide 3 History. Release Note page 1 (of 14) CallBridge Collection V2 R3.7.0.
Hello, I need to start to develop an application to Siemens HIPATH 3000. I planned to use the C# in VS2005.
But I never used before the TAPI. I read a lot of stuff in the net, and I know that it's necessary use the TSP provided by the manufacturer. I downloaded the CallBridge Collection V2.0. But after installing and doing some testing, I discovered that the CBC 2 is just a 1st. After trying to find the links, or some material about the 3rd.
Party TSP, I found some material related to the HiPath CAP. But I'm facing the following problems: - The Siemens web site changed. A lot of links are invalid now. I read some docs but it's not clear to me if its necessary install any additional driver or software to connect to HIPATH using the 3rd.
I have some docs (TAPI 170 V2 Dev Guide, CBCV2 Program Guide and the HP2k3kCSTAP3.zip with some PDFs inside). But I could't find any driver or additional software to install.
The application enviroment is Windows XP. The default TAPI version for this OS is 3.0 but the HIPATH only works with TAPI 2.1. How can I solve this issue? - I need change some configuration in HiPath to accept connections and monitor the calls through the application? Some help will be very appreciated. Thank you in advance.
Oscar Andreas Marschall exMVP TAPI 10/2/2010, 16:27 น. 'Oscar Menezes' schrieb im Newsbeitrag news:[email protected].
I need to start to develop an application to Siemens HIPATH 3000. I planned to use the C# in VS2005. But I never used before the TAPI. Oscar, Regarding TAPI and.NET see KB article '841712 - Telephony Application Programming Interface (TAPI) functionality is not supported from managed code'. Please have a look at the following freely available TAPI2 (#2,3,4) / TAPI3 (#1) wrappers: #1) JulMar's ITAPI3 - TAPI 3.0 wrapper for.NET 2.0 existing TAPI3.0 code based on TAPI3 interop can easily be ported #2) JulMar's. TAPI 2.x managed library for application development #3) Helen Warn's C# TAPI2 Wrapper is now available as version 1.2.0.1 with a small TestApp both for Visual Studio 2005.
Helen agreed that I put the wrapper and sample on my server for download: #4) Angus Comber's Cuba Control: I read a lot of stuff in the net, and I know that it's necessary use the TSP provided by the manufacturer. I downloaded the CallBridge Collection V2.0. But after installing and doing some testing, I discovered that the CBC 2 is just a 1st. After trying to find the links, or some material about the 3rd.
Party TSP, I found some material related to the HiPath CAP. But I'm facing the following problems: - The Siemens web site changed. A lot of links are invalid now. - I read some docs but it's not clear to me if its necessary install any additional driver or software to connect to HIPATH using the 3rd.
All you need is the HiPath TAPI 170 product. HT170 is the 3rd party TSP for the HiPath 3000 PBX family. It installs all required components to communicate with the PBX. The latest released version of HT170 is build 61.
Please note that you need licenses for each line device. So I suggest contacting your local Siemens dealer on this. For limited testing it is possible to enter DEMOMODE as license string and get running 3 line device for 2 hours. After 2 hours you need to reboot the PC to get the next 2 hours for testing. - I have some docs (TAPI 170 V2 Dev Guide, CBCV2 Program Guide and the HP2k3kCSTAP3.zip with some PDFs inside). But I could't find any driver or additional software to install. Where do you got the 'TAPI 170 V2 Dev Guide' from?
Ii is usually bundled with the HT170 setup. - The application enviroment is Windows XP. The default TAPI version for this OS is 3.0 but the HIPATH only works with TAPI 2.1.
How can I solve this issue? This is no problem: all TSP that support TAPI 2.x are automaticall supported by TAPI 3.x via the OS-internal mapping by the Telephony Service. Do you want to develop with TAPI2 or TAPI3? - I need change some configuration in HiPath to accept connections and monitor the calls through the application? What HiPath 3000 version do you have? Do you have the HiPath 3000 Manager E software? What type of CSTA-link are you using?
IP, S0, or V.24? - Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK / Visual C 2003-2008 TAPI / TSP Developer and Tester My TAPI and TSPI FAQ: My Toto Tools (a collection of free, mostly TAPI related tools): TAPI development around the world (Frappr! Map):. Please post all messages and replies to the newsgroup so all may. benefit from the discussion. Private mail is usually not replied to.
This posting is provided 'AS IS' with no warranties, and confers no rights. Andreas Marschall exMVP TAPI 26/2/2010, 4:41 น. 'Oscar Menezes' wrote: Hello AndreasThanks a lot for your help. Oscar, you are welcome.
I will try to contact a local Siemens dealer. But I have some questions: - Here in my company has a software 'XYZ' that is already connected to HIPATH. I checked the machine where this software is installed, and it is not using any additional DLL or Driver to communicate to HIPATH device.
Are you referring to a TAPI based software or is directly using CSTA? What is actually your question on this? - Using some utillities to inspect the EXE, I could verify that it is using a Winsock connection to communicate directly with the device. Is this 'device' the HiPath 300 PBX itself? Then the software is probably directly using CSTA.
- I checked the previous donwloaded documents, and I found this: CSTA Interface Manual V1.1.7 CSTA Phase III CSTA-Link for HiPath 3000/5000 and HiPath 2000 and HiPath OpenOffice EE Part 1: Establishing the CSTA Link Connection via LAN (TCP/IP) IMHO the software 'XYZ' is using this method to connect to HIPATH: ACSE Protocol and Cornet-IP. ACSE is only used for the login/logoff procedure on the CSTA-link. CSTA bill be used after login via ACSE. I don't think CorNet-IP is related to this. Is it possible? What the license issues to use this solution? On a HiPath 3000 PBX you don't need licenses for direct CSTA-link usage, but the numer of possible concurrent CSTA-links is limited depending on the actual PBX model/version.
The licenses I was referring to are for HT170 TSP (3rd party) only. There are different licenses when usin HT120 TSP (1st party) along with CMD.
Its necessary use TAPI and the Cornet-IP protocol together or I can use only one I don't think CorNet-IP is related to this. What is the easiest solution?
With TAPI and the HiPath TAPI 170 TSP you get a solution that does handle the CSTA-links to the PBXs itself (including error checking and handling). With you own CSTA application you would have to do that on your own.
In addition, in your own CSTA application you would have to do the hole ASN.1 encoding/decoding for ACSE/CSTA. Where do you got the 'TAPI 170 V2 Dev Guide' from? Ii is usually bundled with the HT170 setup. I got this doc here: Only PDF files are available at this page.
You local Siemens dealer should be able to order the latest HT170 build (61) on CD. If there are any problems with that, please let me know. This is no problem: all TSP that support TAPI 2.x are automaticall supported by TAPI 3.x via the OS-internal mapping by the Telephony Service. Do you want to develop with TAPI2 or TAPI3? I read in a document that HIPATH 3000 is not compatible with TAPI3. If its true, I will use only TAPI2.
What documnet are you referring to? This statement is simply wrong. HiPath 3000 PBX is internally only supporting CSTA. The TSP is using CSTA internally to communicate with the PBX.
The TSP is using TSPI to communicate with the Telephony Services (TAPISRV) of the Windows OS. TAPISRV is mapping this to TAPI2 or TAPI3 according to each TAPI app. Hence you see that the PBX itself has no direct to TAPI protocols and can therefore not be limited to either TAPI 2.x or 3.x. So with HT170 TSP you can use either TAPI2 or TAPI3. However, for a 3rd party TAPI application TAPI2 is recommended because it is more powerful than TAPI3. What HiPath 3000 version do you have? Do you have the HiPath 3000 Manager E software?
What type of CSTA-link are you using? IP, S0, or V.24?
The HIPATH model is 3700/3750 V5 or higher (I need to check the correct version). The CSTA-link will be IP.
Ok, if you have access to the HiPath 3000 Manager E software (i.e.e the administration tool for the PBX) then it is fairly easy to read ot the actual version. Just trasnfer/read the database (KDS) and go to System status System-wide and see the value in Software Version field in the tabs Cards and System.
Your HiPath administrator should be able to retrieve this easily. Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK / Visual C 2003-2008 TAPI / TSP Developer and Tester My TAPI and TSPI FAQ: My Toto® Tools (a collection of free, mostly TAPI related tools): TAPI development around the world (Frappr! Map):. Please post all messages and replies to the newsgroup so all may. benefit from the discussion. Private mail is usually not replied to. This posting is provided 'AS IS' with no warranties, and confers no rights.
![]()
Andreas Marschall exMVP TAPI 26/2/2010, 4:48 น. Oscar, you are welcome. Is it possible? Where do you got the 'TAPI 170 V2 Dev Guide' from? Ii is usually bundled with the HT170 setup. I got this doc here: Only PDF files are available at this page. You local Siemens dealer should be able to order the latest HT170 build (61) on CD.
If there are any problems with that, please let me know. This is no problem: all TSP that support TAPI 2.x are automaticall supported by TAPI 3.x via the OS-internal mapping by the Telephony Service.
Do you want to develop with TAPI2 or TAPI3? I read in a document that HIPATH 3000 is not compatible with TAPI3. If its true, I will use only TAPI2. What documnet are you referring to? This statement is simply wrong. HiPath 3000 PBX is internally only supporting CSTA.
The TSP is using CSTA internally to communicate with the PBX. The TSP is using TSPI to communicate with the Telephony Services (TAPISRV) of the Windows OS. TAPISRV is mapping this to TAPI2 or TAPI3 according to each TAPI app. Hence you see that the PBX itself has no direct to TAPI protocols and can therefore not be limited to either TAPI 2.x or 3.x.
So with HT170 TSP you can use either TAPI2 or TAPI3. However, for a 3rd party TAPI application TAPI2 is recommended because it is more powerful than TAPI3.
What HiPath 3000 version do you have? Do you have the HiPath 3000 Manager E software? What type of CSTA-link are you using? IP, S0, or V.24? The HIPATH model is 3700/3750 V5 or higher (I need to check the correct version).
The CSTA-link will be IP. Ok, if you have access to the HiPath 3000 Manager E software (i.e.e the administration tool for the PBX) then it is fairly easy to read ot the actual version. Just trasnfer/read the database (KDS) and go to System status System-wide and see the value in Software Version field in the tabs Cards and System. Your HiPath administrator should be able to retrieve this easily.
Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK / Visual C 2003-2008 TAPI / TSP Developer and Tester My TAPI and TSPI FAQ: My Toto Tools (a collection of free, mostly TAPI related tools): TAPI development around the world (Frappr! Map):. Please post all messages and replies to the newsgroup so all may. benefit from the discussion. Private mail is usually not replied to. This posting is provided 'AS IS' with no warranties, and confers no rights.
Ok, so I've been the sysadmin for the hospital I work at for a little over 2 years. I have learned quite a bit from exploring the switch and from our vendor who installed it. I do however have a question that no one seems to be able to answer. Here is a rundown of our setup. HiPath 4000 RMX V4 R2.1.88 / UW7 V4 R3.0.11 We do NOT use VoIP for our phones (whole other arguement, don't get me started cause I have tried to get the approvals and its a dead horse) We use both the OptiPoint standards and the Openstage 40 T.
Here is my question, and please, read this twice before answering, cause if you don't understand it, you will give me the response I keep hearing.:) Why does the Openstage 40 T have a USB port on it if it is not supported in Openstage Manager? It is NOT for putting a Phone directory on it, it is not for updating it, and there is no software that I can find that will allow a PC to see it due to lack of drivers. I have heard a number of things and not a single one has been useful and/or true. I am very technical, having numerous PC based certifications, as well as having gone through the HiPath Admin training. Well versed in windows and linux, so unofficial uses is fine if that is what it takes to get it to be seen.
Sorry to type such a book, but I have been all over, looking for even a shred of help for this question and even Siemens techs cannot give me anything more than a canned response that is meant for the 60 T and up. Thanks for any help. RE: HiPath 4000, Openstage 40T and USB. Thank you VERY much, Iamnothere. Would not have been hard for someone to put that in some documentation somewhere that makes sense, but that is above my pay grade.:) You don't know how many people keep insisting that it is so you can upload a directory to the phone, or that it is so you can use it to load custom rings.
All features that the 60T has, but no one seems to really read that I am talking about a 40. I have found the CallBridge Collection and have downloaded it. Will report back once I have had time to install and play with it. Thank you once again. RE: HiPath 4000, Openstage 40T and USB (TechnicalUser) 24 Sep 10 08:31. I tested CallBridge TU with OpenStage 40 T.
The CallBridge Collection zipped package includes everything needed to establish a TAPI connection from PC to phone. During the installation of the USB drivers on my WinXP desktop PC, an error occurred - due to a timestamp problem on the certificate. On a hunch, I set the clock back to 2009., re-ran the installation, and it was successful.
Then I installed CallBridge TU, connected the PC with the OpenStage 40 T via USB cable, and the TAPI connection was successfully established. CallBridge TU is only a TAPI connection, which provides the path for a CTI application to remotely control the phone. There is no internal CTI functionality provided. The customer must install their desired CTI application. I used the Microsoft freebie: 'dialer.exe', which is included within XP. (Siemens offers their own CTI application called 'SimplyPhone'.) I installed 'dialer.exe', configured a few settings, and voila, I was able to place calls and answer calls via my PC.
(.Ran out of time. I plan to change the date back to 2010 and see if everything works OK.) RE: HiPath 4000, Openstage 40T and USB (MIS).
Hmm, would you mind pointing me to where you found that install? Seems the one I have does not contain any driver info despite having the USB folder and the inf files inside of it. XP just does not see them as a valid driver for any of the devices I choose.
Have tried all options now and still refuses. It is weird though, XP says that I plugged in an Oopenstage T but says no drivers can be found, both on the web or within any folder of the CBC software that I have. On a side note, I did not get the certificate error about the date being off. I ran the setup just fine, though it did not find any USB modems (as expected). RE: HiPath 4000, Openstage 40T and USB (TechnicalUser) 24 Sep 10 22:43. I assume that you used SEBA.
You would not have access to the site that I use. The USB driver is contained in a directory named: USBWindowsXPVista720032008.
The executable file inside that directory is named: USB2.1.1.0Setup.exe. Note: there was a more recent version. I used this one after I received the weird error message during the USB Driver installation. But this version also had that same problem. If you can provide your email address, I will be glad to share more info away from this public forum. If not, I certainly understand.
RE: HiPath 4000, Openstage 40T and USB (MIS).
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |