Sunday, August 25. 2002
XTAPI the first fully functional free JTAPI
implementation announces the Dialogic Service
Provider!
The Dialogic XTAPI Service Provider is built upon the
D4J (Dialogic for Java) open source project. XTAPI
already supported Dialogic cards via the MSTAPI
Service Provider, however this was only useful under
Microsoft Windows. By utilizing the D4J code Dialogic
cards can now be used with XTAPI under Linux. The
Dialogic Service Provider is written to work with
Analog Voice cards from Intel / Dialogic. The XTAPI
Dialogic Service Provider requires D4J version 0.5 or
later.
Many thanks go to Carlos G Mendioroz for providing D4J
and much hand holding while writing this code.
More information on D4J can be found at:
http://sourceforge.net/projects/d4j
Browse over to SourceForge and check it out!
http://sourceforge.net/projects/xtapi/
Steven A. Frare
http://xtapi.sourceforge.net/
XTAPI provides a working implementation of the Core
and Media packages for JTAPI 1.2.
implementation announces the Dialogic Service
Provider!
The Dialogic XTAPI Service Provider is built upon the
D4J (Dialogic for Java) open source project. XTAPI
already supported Dialogic cards via the MSTAPI
Service Provider, however this was only useful under
Microsoft Windows. By utilizing the D4J code Dialogic
cards can now be used with XTAPI under Linux. The
Dialogic Service Provider is written to work with
Analog Voice cards from Intel / Dialogic. The XTAPI
Dialogic Service Provider requires D4J version 0.5 or
later.
Many thanks go to Carlos G Mendioroz for providing D4J
and much hand holding while writing this code.
More information on D4J can be found at:
http://sourceforge.net/projects/d4j
Browse over to SourceForge and check it out!
http://sourceforge.net/projects/xtapi/
Steven A. Frare
http://xtapi.sourceforge.net/
XTAPI provides a working implementation of the Core
and Media packages for JTAPI 1.2.
Sunday, July
21, 2002
XTAPI the first fully functional free JTAPI implementation announces its first Beta Release 0.1!
A new Service Provider is available, the XOpenH323 Service Provider. This provider utilizes the H.323 stack from the OpenH323 project! You can now use the OpenH323 libraries from Java using the JTapi object model! H.323 is the international standard for IP Telephony.
He has found and fixed the following problems for this Beta release:
In the XTAPI JTapi implementation:
For the MSTAPI Service Provider:
Thanks Reggie!
More information on the OpenH323 project can be found here:
http://www.openh323.org/
Steven A. Frare
http://xtapi.sourceforge.net/
XTAPI provides a working implementation of the Core and Media packages for JTAPI 1.2.
XTAPI the first fully functional free JTAPI implementation announces its first Beta Release 0.1!
A new Service Provider is available, the XOpenH323 Service Provider. This provider utilizes the H.323 stack from the OpenH323 project! You can now use the OpenH323 libraries from Java using the JTapi object model! H.323 is the international standard for IP Telephony.
JSpeakerPhone from Linux to XP and from
Linux to NetMeeting on Win2K!
Note: The pictures represent
two seperate calls, XTAPI does not implement the Call Control Package of JTapi so there is no built in support for conferencing.
He has found and fixed the following problems for this Beta release:
In the XTAPI JTapi implementation:
- Duplicate state change events.
For the MSTAPI Service Provider:
- Make Call timeout.
- lineDeallocateCall not being called or being called at incorrect times.
Thanks Reggie!
More information on the OpenH323 project can be found here:
http://www.openh323.org/
Steven A. Frare
http://xtapi.sourceforge.net/
XTAPI provides a working implementation of the Core and Media packages for JTAPI 1.2.
Sunday July 7,
2002
Alpha Release 0.08 Caller ID, CODECS and more!
The Service Provider code has been separated from the main XTAPI implementation. There are now separate jar files for the MSTAPI and Serial Providers. The Serial Provider now requires an additional Audio jar file, which contains the audio format conversion routines used by the Serial Provider. This had been the plan for some time however it never materialized until now. The SourceForge CVS source trees have been re-arranged to reflect this segregation.
This means you must add the additional jar files to your class path! All documentation has been updated to reflect this.
For the MSTAPI Service Provider you need mstapisp.jar (included in the MSTAPI Service Provider package).
For the Serial Service Provider you need serialsp.jar and audiosp.jar, these are available in separate packages in the files section.
The Serial Provider has undergone a change to allow for the use of different CODECS so g.721 is no longer the only supported CODEC. 16-bit signed PCM is the required format for the Serial Provider it will convert as needed for the modem. This also removes the burden of decoding the file format from the application writer. JAnsweringMachine has been updated to reflect this change. See the “CODECs, Voice Modems, V.253 and XTAPI” paper in the documentation section for more on the design and CODEC support.
Caller ID is now implemented in XTAPI! The JSoftPhone example application has been updated to show the use of caller id. You can get the JSoftPhone example from the simple examples package in the files section or just pull it (JSoftPhone.java) straight from CVS.
Alpha Release 0.08 Caller ID, CODECS and more!
The Service Provider code has been separated from the main XTAPI implementation. There are now separate jar files for the MSTAPI and Serial Providers. The Serial Provider now requires an additional Audio jar file, which contains the audio format conversion routines used by the Serial Provider. This had been the plan for some time however it never materialized until now. The SourceForge CVS source trees have been re-arranged to reflect this segregation.
This means you must add the additional jar files to your class path! All documentation has been updated to reflect this.
For the MSTAPI Service Provider you need mstapisp.jar (included in the MSTAPI Service Provider package).
For the Serial Service Provider you need serialsp.jar and audiosp.jar, these are available in separate packages in the files section.
The Serial Provider has undergone a change to allow for the use of different CODECS so g.721 is no longer the only supported CODEC. 16-bit signed PCM is the required format for the Serial Provider it will convert as needed for the modem. This also removes the burden of decoding the file format from the application writer. JAnsweringMachine has been updated to reflect this change. See the “CODECs, Voice Modems, V.253 and XTAPI” paper in the documentation section for more on the design and CODEC support.
Caller ID is now implemented in XTAPI! The JSoftPhone example application has been updated to show the use of caller id. You can get the JSoftPhone example from the simple examples package in the files section or just pull it (JSoftPhone.java) straight from CVS.
Old News