On 12/24/2010 03:00 AM, Rob Hillis wrote: > Hi guys, > > I have no idea at this stage whether the problem is with Astlinux 0.7.4, > a hardware/software conflict or something else, but at the moment it's > about the only common factor that I can see. > > My home phone system has a collection of analogue phones connected to > ATAs along with a Zultys 4x4, Snom 320 and a Yealink T28P. The T28P and > the 320 have both been configured with BLF buttons that until recently > have worked just fine. > > However, around the time that I started development on a PABX product > for work (Astlinux running on a SuperMicro 5015A-H with Yealink T26 and > T22 phones) I noticed that I couldn't get BLF working on the Yealink > phones and turned my attention to my home system to find out what the > configuration differences were - only to discover that BLF had stopped > working there as well. > > Both systems are running Astlinux 0.7.4 - my home system on an ALIX2-3 > that was originally built back when Runnix was a brand new feature. > (can't remember whether it was 0.4.8 or 0.6.0) > > "core show hints" shows the following on my home system:- > > pbx*CLI> core show hints > > -= Registered Asterisk Dial Plan Hints =- > alist...@hints : IAX2/alistair > State:Idle Watchers 0 > p...@hints : SIP/PSTN > State:Idle Watchers 0 > 2...@hints : SIP/210 > State:Idle Watchers 0 > 2...@hints : SIP/209 > State:Idle Watchers 0 > 2...@hints : IAX2/fax0&IAX2/fax1& > State:Idle Watchers 0 > 2...@hints : SIP/205 > https://192.168.1.254/index State:Idle Watchers 0 > 2...@hints : SIP/204 > State:Idle Watchers 0 > 2...@hints : SIP/203 > State:Idle Watchers 0 > 2...@hints : SIP/202 > State:Idle Watchers 0 > 2...@hints : SIP/201 > State:Idle Watchers 0 > 2...@hints : SIP/200 > State:Idle Watchers 0 > ---------------- > - 11 hints registered > > I get similar output from the development system from work (though the > hints are in the default context in that instance). The Yealinks are > set up with purely the extension number (which used to work) though I > have tried with @hints at the end as well. The Snom has always been set > up including the context. I also tried X-Lite - again to no avail. > > The firmware on the Yealinks has changed several times recently (between > versions *.50.0.* and *.60.0.*) though the Snom hasn't changed firmware > in several months. > > Setting SIP debug on gives me a headache, but I don't think I'm seeing > any presence traffic. > > Has anyone had any problems with BLF recently with Astlinux? Where > might I look to figure out what's going on? I've Googled for answers, > but can't find anything relevant to 0.7.4 or Asterisk 1.4.36.
Rob, I can confirm that this works correctly with Asterisk 1.4.36 (AstLinux 0.7.4). Have several customers using that with no problem or changes from previous versions (with Aastra and Polycom phones). I would look at the phone configs. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
