Shortlog of dahdi-linux changes since v220.127.116.11:
Oron Peled (3):
xpp: deprecate dahdi_autoreg
xpp: continue xpp.dahdi_autoreg deprecation
sysfs: new device attribute: registration_time
Russ Meyerriecks (6):
wcte13xp: wcaxx: Fix broken devicetype attributes
wcte13xp: Update firmware to 0x780017
wcte13xp: Add support for te131 and te132 products
Revert "dahdi: Change auto_assign_spans default from 1 to 0."
wcte13xp: wcaxx: wcte43x: Remove VPM_SUPPORT compile option.
wcte13xp: wcxb: Add delayed reset firmware feature
Shaun Ruffell (10):
wctdm24xxp: Reset module specific type information on probe.
dahdi: Move clearing of DAHDI_ALARM_NOTOPEN to __dahdi_assign_span().
dahdi: Change auto_assign_spans default from 1 to 0.
wcaxx, wcte13xp, wcte43x: Honor max_latency module parameter.
wcte13xp: Export max_latency module parameter.
wcte43x, wcte13xp: Use MSI interrupts if possible.
dahdi: Do not access invalid memory if invalid local span number is passed to spantype attribute.
wcte43x: Trivial drop of unnecessary local variables.
wct4xxp: Trivial drop of unnecessary local variables.
wcte43x, wcte13xp, wcaxx: Bump irqmisses counter when there are DMA underruns.
Tzafrir Cohen (4):
README: xpp.dahdi_autoreg is deprecated
README: the new registration_time device attribute
README: The sysfs class now includes no channels
sysfs: registration_time: use ktime_get_ts
Shortlog of dahdi-tools changes since v2.8.0:
Oron Peled (6):
Makefile: do install all man-pages
hotplug modularization: move sources to a subdir
hotplug modularization: split logic to scriptlets
new "dahdi_waitfor_span_assignments" tool
dahdi_span_types: allow defaults + overrides
Change span-type.conf generation policy
Russ Meyerriecks (2):
wcte13xp: Teach tools about te131 te132 products
dahdi.init: Don't exit on lack of /etc/dahdi/system.conf
Shaun Ruffell (8):
dahdi_cfg: Wait for all spans to be assigned.
dahdi_span_config: Do not run auto span configuration if spans are auto assigned.
dahdi_handle_device, dahdi_span_config: Check for auto_assign_spans only when ACTION is add.
dahdi_genconf: Add 'modules', 'spantypes', and 'assignedspans' to list of available generators.
dahdi_span_types: Show location of configuration file in help message.
dahdi_handle_device: Auto assign only the device being added.
dahdi_cfg: Add semaphore to prevent parallel execution.
dahdi_cfg: Allow dynamic spans to handle udev based span assignment.
Tzafrir Cohen (16):
dahdi.rules: Replace SYSFS with ATTRS
dahdi.rules: use += for RUN
.gitignore: more generated files
README: indentation level for config samples
README: document initialization
README: Update the install targets
span_types/assignments: no * in device list
dahdi_genconf: don't generate spantypes by default
dahdi_span_types: hush warning of missing attribute
programmable bash completion for some commands
dahdi_perl: fix regression with an AB with no modules
bash_completion: fix dahdi_genconf
hyphen/minus fixes in man pages
hotplug: document asterisk scriptlet
README: udev hooks run scripts from directories
The diffstat from the dahdi-linux v18.104.22.168 release:
Asterisk 12 is the next major release series of Asterisk. It is a Standard release, similar to Asterisk 10. For more information about support time lines for Asterisk releases, see the Asterisk versions page:
As a Standard Release, Asterisk 12 contains many new major architectural improvements and features. A short list of some of these features includes:
A new SIP channel driver and accompanying SIP stack named chan_pjsip has been added. This new channel driver is based on the PJSIP SIP stack by Teluu. It includes support for the vast majority of features currently in chan_sip, as well as numerous architectural improvements that alleviate pain points present in the legacy SIP channel driver. Users who wish to use the new SIP channel driver are encouraged to read the instructions on installing and configuring PJSIP for Asterisk on the Asterisk wiki at https://wiki.asterisk.org/wiki/x/J4GLAQ. Detailed instructions on configuring the new SIP stack in Asterisk can be found on the Asterisk wiki as well, at https://wiki.asterisk.org/wiki/x/hYCLAQ.
The Asterisk REST Interface (ARI) has been added. This interface lets external systems harness the telephony primitives within Asterisk to develop their own communications applications. Communication with Asterisk is done through a RESTful interface, while asynchronous events from Asterisk are encoded in JSON and sent via a WebSocket. More information on ARI can be found at https://wiki.asterisk.org/wiki/x/lYBbAQ
Major standardization of the Asterisk Manager Interface and its events have occurred within this version. In particular, the names of Asterisk channels no longer change and are stable throughout the lifetime of the channel. More information on the changes in AMI can be seen in the AMI v2 Specification at https://wiki.asterisk.org/wiki/x/dAFRAQ
All bridging within Asterisk is now performed using the Asterisk Bridging API, which previously was only used by the ConfBridge application. This affords Asterisk users greater stability, and has resulted in the abstraction of channel masquerades, renaming, and other internal implementation details. It also allows for the seamless transition between two-party and multi-party bridges using core features.
And much more!
Please note that Asterisk 12 went through both an alpha and a beta testing process. During this time, many bugs were fixed, features enhanced, and improvements made. If you participated during the alpha and beta testing process, thank you! Please note that Asterisk 12 has changed as a result of the testing, and the UPGRADE and CHANGES notes should still be reviewed.
Information about the new features and changes in Asterisk 12 can be found on the Asterisk wiki:
Ok, so I am really behind! I missed this one. There is a new mailing list for Asterisk App Development. Matt Jordan wrote a post about it:
Hey all -
After much discussion at AstriCon, it became clear that the Asterisk project could use a mailing list dedicated specifically to application development. This new mailing list should be used specifically for discussions regarding the development of applications using AMI, AGI, or ARI - or any other interface exposed by Asterisk in the future. Today, we're pleased to announce the asterisk-app-dev mailing list, now available on lists.digium.com:
This new list is not a replacement for asterisk-dev or asterisk-users. The asterisk-dev list should continue to be used for discussions regarding development directly in the Asterisk project itself or the Asterisk Test Suite. The asterisk-users list should continue to be used for discussions regarding deployment and usage of Asterisk itself. As we expect the amount of questions and discussions regarding application development and API usage to grow, it makes sense to provide a dedicated forum for those discussions outside of -users and -dev, and this new mailing list serves that purpose.
Of course, there's bound to be some cross-over between mailing lists, and sometimes it might not be clear where to post your question. As always, please do not cross post between lists. If your question on asterisk-app-dev is more appropriate for asterisk-users or asterisk-dev, someone will kindly ask you to direct your question to the other mailing lists, where a wider audience may be available to assist you.
Thanks - and we all look forward to lots of productive discussions on the new mailing list about building applications that use Asterisk as their communications engine!
Digium, Inc. | Engineering Manager
Aldo Bergamini has posted details of four new iOS apps for Asterisk:
Four newly released applications are available in the Apple App Store to drive your customer's Asterisk PBX. iBat Pro, iBat User, iBat Access and the free iBat Setup run on any IOS device, see more at: http://www.pxc.biz.
They cover a wide range of basic needs, always making it easy for users to do what they need:
to act as their convenient 'BLF sidecar' to originate calls: without limits to the number of targeted extensions.
to let the user get the called party's phone number from the iPhone's contact list, choose the outgoing line and originate calls with ease from his/her Asterisk extension
to keep track of calls originated to an external destination (a quick way to keep a lively one touch phone numbers list)
to monitor their own extension, even when away from the desk
to monitor a centrally managed, per user defined list of extensions, with far more information about the state than a colored LED
they offer a clean and simple call transfer interface, far beyond what even the most advanced phones can do - perform a transfer to external destinations choosing the outgoing line in a flash
Further, both iBat Pro as well as iBat User offer a mix of advanced ways to originate calls:
The Operator Access function lets users bypass the PBX operator to get connected to any Asterisk extension, saving time and with ease of knowing when to call (the allowed extensions state is displayed in real time, thus avoiding to call somebody who's already on the phone). [iBat Pro] [iBat User]
The BLF Callback function acts as the Operator Access, but lets Asterisk call the user's iPhone, as opposed to the automated call from the iPhone to any phone line served by Asterisk. [iBat Pro]
Again iBat Pro offers a way ('Callback Dialer') to place double originated calls to any external destination; Asterisk thus bridges the connection to the iPhone on one line to the destination over a second channel. This can be used for many purposes (from keeping the user's mobile phone number private, to saving money using convenient operators from the PBX).
Finally the purposely inexpensive iBat Access app makes the Operator Access functionality available to external calling partners, people not directly served by Asterisk (they have no extension, but do just call the PBX from the public network). This is a way to bring preferred business partners closer to a company, by letting them see when the desidered callee is available and thus getting a quick connection bypassing the operator with ease from their iPhone.
39 Free Softphones August 14, 2009 Average Vote: 17.6
I decided to do another round up article, this time focusing on the 39 best free softphones.
Asterisk 11.0.0-beta1 Now Available August 11, 2012 Average Vote: 10
The Asterisk Development Team is pleased to announce the first beta release of Asterisk 11.0.0 (the first Long Term Support release since 1.8).
oFono 1.0 has been released November 10, 2011 Average Vote: 10
Steve Totaro has forwarded details of the latest release of a project called oFono.
Discount for Astricon 2012 August 31, 2012 Average Vote: 10
Astricon 2012 is rapidly approaching and will be held in Atlanta between October 23 and 25. The Daily Asterisk News has secured a 20% discount on all tickets if you use the discount code.
Asterisk 10.0.0-rc1 Now Available November 11, 2011 Average Vote: 10
The Asterisk Development Team is pleased to announce the first release candidate of Asterisk 10.0.0.
New SIP channel driver project page November 23, 2012 Average Vote: 10
Mark Michelson has posted details of a wiki page that has been created to guide the development of a new SIP channel driver for Asterisk.
Asterisk and Google August 26, 2011 Average Vote: 10
Malcolm Davenport has posted a request on behalf of Digium for someone to help maintain the Google channel driver when Google makes changes.
espeak module for Asterisk August 22, 2011 Average Vote: 10
Lefteris Zafiris has posted details of a new version of the app_espeak application for Asterisk - another speech synthesizer.
Video on New Digium Phones March 5, 2012 Average Vote: 10
Digium have created a video that explains a bit more about the new phones they have created.