Asterisk-Java

We have released milestone 3 of Asterisk-Java 1.0.0. Next to a few bug fixes this new milestone makes Asterisk-Java OSGi compliant, adds support for the modern SLF4J logging framework and makes debugging easier through built-in support for network tracing. You … Continue reading →

Up to now the preferred way to obtain traces of the communication between Asterisk-Java and Asterisk was using tcpdump, wireshark or ngrep as described in Debugging Manager API. Having a full log of the direct network communication is often the ... [More] only way to resolve issues related to problems in the Manager API or Fast AGI. To make it easier for our users to obtain these traces we have now included a tracing feature directly into Asterisk-Java. You can enable it at runtime by setting the system property org.asteriskjava.trace to true. On the command line: java -Dorg.asteriskjava.trace=true ... Trace files are written to the temp dir by default ("java.io.temp"). You can specify an alternate location by using the org.asteriskjava.trace.directory system property: java -Dorg.asteriskjava.trace=true \ -Dorg.asteriskjava.trace.directory=/opt/traces ... This new feature is already part of the latest Asterisk-Java 1.0.0-CI-SNAPSHOT and will be shipped with milestone 3. Please consider attaching a trace file to your bug reports in the future. It speeds up bug fixing considerably. [Less]

Up to now the preferred way to obtain traces of the communication between Asterisk-Java and Asterisk was using tcpdump, wireshark or ngrep as described in Debugging Manager API. Having a full log of the direct network communication is often the ... [More] only way to resolve issues related to problems in the Manager API or Fast AGI. To make it easier for our users to obtain these traces we have now included a tracing feature directly into Asterisk-Java. You can enable it at runtime by setting the system property org.asteriskjava.trace to true. On the command line: java -Dorg.asteriskjava.trace=true ... Trace files are written to the temp dir by default ("java.io.temp"). You can specify an alternate location by using the org.asteriskjava.trace.directory system property: java -Dorg.asteriskjava.trace=true \ -Dorg.asteriskjava.trace.directory=/opt/traces ... This new feature is already part of the latest Asterisk-Java 1.0.0-CI-SNAPSHOT and will be shipped with milestone 3. Please consider attaching a trace file to your bug reports in the future. It speeds up bug fixing considerably. [Less]

Up to now the preferred way to obtain traces of the communication between Asterisk-Java and Asterisk was using tcpdump, wireshark or ngrep as described in Debugging Manager API. Having a full log of the direct network communication is often the … Continue reading →

Up to now the preferred way to obtain traces of the communication between Asterisk-Java and Asterisk was using tcpdump, wireshark or ngrep as described in Debugging Manager API. Having a full log of the direct network communication is often the … Continue reading →

We are currently working on making Asterisk-Java OSGi compliant to make it easier for those users who want to use Asterisk-Java in an OSGi container like Equinox. This means Asterisk-Java will contain the proper bundle headers in its MANIFEST.MF ... [More] and will follow the OSGi rules for version names. The new version names for Asterisk-Java are similar to those used by Spring Framework: 1.0.0.CI-SNAPSHOT Continious integration snapshot releases 1.0.0.M3 Milestone releases 1.0.0.RC1 Release candidates 1.0.0.RELEASE Final release 1.0.0.SR01 Service release with emergency bug fixes The first OSGi compliant snapshots of Asterisk-Java are now available for download: Asterisk-Java 1.0.0.CI-SNAPSHOT. The old 1.0.0-SNAPSHOT releases will no longer be updated. For those developers that are not interested in OSGi nothing will change. The OSGi manifest headers added to Asterisk-Java are simply ignored when run in a non-OSGi environment. The new MANIFEST.MF looks like this: Manifest-Version: 1.0 Bundle-Description: The free Java library for Asterisk PBX integration. Bundle-DocURL: http://asterisk-java.org/ Bundle-ManifestVersion: 2 Bundle-Name: Asterisk-Java Bundle-SymbolicName: org.asteriskjava Bundle-Vendor: reucon Bundle-Version: 1.0.0.CI-SNAPSHOT Export-Package: org.asteriskjava;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.config;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.config.dialplan;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.fastagi;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.fastagi.command;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.fastagi.reply;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.manager;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.manager.action;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.manager.event;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.manager.response;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.manager.util;version="1.0.0.CI-SNAPSHOT", org.asteriskjava.live;version="1.0.0.CI-SNAPSHOT" If you are looking for a ready to use OSGi based framework to develop AGI scripts for Asterisk on SpringSource dm Server you may also want to check ajdmserver. [Less]

We are currently working on making Asterisk-Java OSGi compliant to make it easier for those users who want to use Asterisk-Java in an OSGi container like Equinox. This means Asterisk-Java will contain the proper bundle headers in its MANIFEST.MF and … Continue reading →

We are currently working on making Asterisk-Java OSGi compliant to make it easier for those users who want to use Asterisk-Java in an OSGi container like Equinox. This means Asterisk-Java will contain the proper bundle headers in its MANIFEST.MF and … Continue reading →

ADempiere is a collection of Open Source ERP applications. By leveraging Asterisk-Java the Asterisk integration for ADempiere provides support for calling contacts directly from within ADempiere.

ADempiere is a collection of Open Source ERP applications. By leveraging Asterisk-Java the Asterisk integration for ADempiere provides support for calling contacts directly from within ADempiere.