Darrick Hartman wrote:
John Novack wrote:
You are most welcome.
What these lists are supposed to be all about.
If only the asterisk-users list were populated with members that are as
nice as this group.
You mean like the posting I made this afternoon with regards to the change in parked calls? If you haven't already noticed call parking has changed significantly in 1.4.23.1. Most of the changes are good. (like
parking the same call twice actually works now). However, if a parked call reaches it's timeout, the parked call is no longer returned to the
device that parked the call. It's returned to the 's' extension in the context of the device that parked the call. Totally whacked. I posted this to the Asterisk-users mailing list this afternoon and have yet to have anyone reply to it.
Consider yourself lucky that some ego maniac wasn't really rude to you,
as they often are to those who are new to Asterisk, Linux or have
English as a second language.
Perhaps because it was a Friday afternoon in the US, postings were slow,
or more probably because many are much more interested in the newest,
latest and "greatest" rather than getting 1.4.xx working correctly.
Also there seems a rather large community using Asterisk for call
centers, and other applications aren't of interest.
One reason many in my group are reluctant to even move to 1.4 was the
bitter experiences as it made its way through versions that fixed one
thing and broke two others. 1.4.14 through 1.4.18 or beyond were REALLY
broken!! Most of our group uses Asterisk and Astlinux as a private
network, worldwide, to connect electro-mechanical switches in private
collections, so many of the features are never used.
On a side note, those who have PSTN connections to Asterisk need to be
REALLY careful to have a secure dialplan, as we have seen more and more
attempts at break-ins for the purpose of toll fraud. Certainly not a
new issue in telephony, but poor dialplan programming can result in a
real surprise weeks later when the bill arrives.
About the only way to 'fix' this behavior is to have each phone have it's own
context (which is just lame).
I didn't really see a detailed explanation in the Changelog either. I knew there were some significant changes to res_features.so (and features.conf) only because of a bug in the parked call logic. By
default in prior versions, someone who was parked could initiate a transfer if they pressed the blind transfer feature key (# by default).
Which is another sore point with me. In other PBX's there is, and
shouldn't be, any difference between an attended or blind transfer. for
the last 30 plus years, they have been part of the same function, in
switches with POTS phones ore modern digital sets with hands free
answer. Initiate the transfer, announce the call if possible or desired,
or simply hang up. One function, not two that start with different codes.
Enough of a rant this sunny morning.
John Novack
--
Dog is my co-pilot
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
