9 thoughts on - Asterisk 14.0.0-rc1 Now Available

• Hey dev team, kudos for the good job.

  Just one information.

  When I started Asterisk after upgrade to version 14, I received this information:

  [Sep 19 19:40:57] WARNING[22694]: res_odbc.c:525 load_odbc_config: The
  ‘pooling’, ‘shared_connections’, ‘limit’, and ‘idlecheck’ options are deprecated. Please see UPGRADE.txt for information

  I know that odbc configuration changes, but there is no UPGRADE file containing this information. In fact, there is no UPGRADE-14.txt file.

  Regards, Marcelo H. Terres
  IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres

• Marcelo Terres wrote:

  This actually happened between Asterisk 13.7.0 and 13.8.0, with a subsequent change reverting it somewhat and moved back into Asterisk. I’ve created an issue[1] to clean this up, both the upgrade and the sample config.

  [1] https://issues.asterisk.org/jira/browse/ASTERISK-26389

  — Joshua Colp Digium, Inc. | Senior Software Developer
  445 Jan Davis Drive NW – Huntsville, AL 35806 – US
  Check us out at: http://www.digium.com & http://www.asterisk.org

• I noticed another different behaviour.

  In older versions, when I call rasterisk, I receive some informations about it. Fox example:

  [root@pbx2 ~]# rasterisk Asterisk 11.22.0, Copyright (C) 1999 – 2013 Digium, Inc. and others. Created by Mark Spencer
  Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’
  for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type ‘core show license’ for details.
  ========================================================================Running as user ‘asterisk’
  Running under group ‘asterisk’
  Connected to Asterisk 11.22.0 currently running on pbx2 (pid = 1461)
  pbx2*CLI>
  Disconnected from Asterisk server Asterisk cleanly ending (0). Executing last minute cleanups

  But after upgrade to Asterisk 14 rc1, even if I use the sample configuration files, I didn’t get any information when call rasterisk.

  root@rtc:/usr/local/src/asterisk-14.0.0-rc1# rasterisk rtc*CLI>

  Is that expected?

  Regards, Marcelo H. Terres
  IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres

• Thanks Joshua. Marcelo H. Terres
  IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres

• Marcelo Terres wrote:

  I don’t know of anything which explicitly disabled this. Please file an issue[1].

  [1] https://issues.asterisk.org/jira

• Great! Thanks, team, but just before I file a bug..

  No matter how many v and d I put, when I now do “dialplan reload” in v14, it just says “Dialplan reloaded”.

  Previously, it used to give some info, and I could scroll back and see if there were any obvious errors in the dialplan.

  Is this and intended change, something I’ve done wrong, or a bug that needs filing?

  Thanks!

• That’s the same behavior that I noticed.

  I’ll open an issue about it soon. Marcelo H. Terres
  IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres

• Hello Jonathan,

  https://issues.asterisk.org/jira/browse/ASTERISK-26391

  Regards, Marcelo H. Terres
  IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres

• Thanks, Marcelo. I just subscribed to that bug; you’re right, I also noticed the lack of info when attacking to asterisk. I just forgot to mention it here!