similar to: Issue with Asterisk & Aastra 57i at v3.2

Hello All, I have a need for a wireless solution and have been looking at the Aastra 57i CT phone that have the wireless handset with them. Aastra says they will cover "up to 300,000 square feet". I am finding this hard to accept. I was also wondering about the "secure WDCT cordless technology" Could this be a form of DECT? Any one using these that can shed some lite?

I'm in the process of converting our current hybrid key system to Asterisk and Aastra 57i phones. One of the features that seems to be a show stopper for almost everyone in the office is the inability to see who is on the phone. Can someone point in the right direction to setup an XML app on the phone so they can press a soft-button and get a list of extensions and their statuses? I know I can

Hi, I'm currently trying to connect an Aastra 57i to our Asterisk Server. The strange thing is, that altough I have definitely entered the correct IP address of the server, the phone doesn't even attempt to register. Here is the configuration file (local.cfg) of the phone: firmware md5: dee6e938b469e217a87138076f47fe41 boot count: 1 tone set: Germany language 1: German time server1:

I am currently testing a 57i unit. No problems configuring the phone's config via phone/web UI. We are trying to avoid using the web UI, the reason is it will take a long time typing the softkey xml applications URIs on each phone, so we chose TFTP. Tried configuring the phone via a TFTP config server, but no changes took effect. I wonder why it doesn't work with TFTP even if I was able

Hello, Please consider including upstream commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea in the next v3.2.y release. It was included upstream as of v3.3-rc1. It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1154608 . commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea Author: Laszlo Ersek <lersek at redhat.com> Date: Sun Dec 11 01:48:59 2011 +0000

Hello, Please consider including upstream commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea in the next v3.2.y release. It was included upstream as of v3.3-rc1. It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1154608 . commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea Author: Laszlo Ersek <lersek at redhat.com> Date: Sun Dec 11 01:48:59 2011 +0000

I am migrating the llvm/clang derived compiler for our processor from the v3.1 to v3.2 codebase. This has mostly gone well except that instruction latency scheduling is no longer happening. The people who implemented this previously sub-classed 'ScheduleDAGInstrs' and implemented the virtual methods 'computeLatency' and 'computeOperandLatency'. However, these methods

On Apr 26, 2013, at 3:53 AM, Martin J. O'Riordan <Martin.ORiordan at movidius.com> wrote: > I am migrating the llvm/clang derived compiler for our processor from the > v3.1 to v3.2 codebase. This has mostly gone well except that instruction > latency scheduling is no longer happening. > > The people who implemented this previously sub-classed 'ScheduleDAGInstrs'

Hi, Has anyone had experience with the Aastra 57i / 57i CT phones? The problem I'm having is that the phone isn't re-registering itself with the Asterisk server. As a result, the phone loses the registration with the server and is no longer able to receive incoming calls. Outgoing calls work fine. Right now, I have the following sip registration settings: sip registration period: 180

hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com

My old machine started getting a bit flaky, so I have kicked it off my desk, but still wanted to get some nouveau bugs fixed on it. (In fact it's easier now that I can reboot it more easily.) So I put a spare old hard drive on it and rebuilt it, but I'm having a heck of a time getting it working. Whenever it tries to load the nouveau module, it blows up. What's funny is that it

Sorry for being a little off topic, but I'mconsidering a few new phones for my Asterisk installation. I have a mix of Polycom 500/600s and an Aastra 480i CT. I'm considering adding a couple of Aastra 57i or 57i CT. Does anyone here have experience with the 480i CT and the newer 57i CT? I'm curious as to the real differences. Thanks, Michael Graves Sr Product Specialist Pixel Power

I have a 536i expansion module attached to a 57i-CT. The BLF lights on the 536i will light up and work fine for a while... however after a bit they seem to loose their ability to see if someone is on a phone. They still work to dial, if I try to dial, however, they don't light up when someone makes a call, or if their phone rings. If I reboot the phone, the lights start working again

Upgraded from 16.2.14 to 1.6.2.15 on Fedora 13, with aastra 9133i and 57i. On 9133i and 57i: #<extension># works for a blind transfer. Xfer<extension>Xfer doesn't! All this worked on 1.6.2.14. Nothing useful on cli, verbose 3, DEBUG. Here extension 169 answers an outside call, and tries to transfer it to 145 using the Xfer button: -- SIP/169-0000009c answered

We are installing Aastra phones (480's and 57i's) into a fairly simple asterisk setup. Although call park & pickup work fine using xfer to 700 (to park), dial 701 (to pickup), we are unable to make the park/pickup softkey feature work on the aastra's. Although we've programmed the softkeys per the manuals, they seem to have no effect (just dead). For example, our 57i is

Quoth: OCG Technical Support <support at ocg.ca> > >Although we've programmed the softkeys per the manuals, they seem to have no >effect (just dead). For example, our 57i is setup like this: I had similar problems and ended up using the speeddial inband functionality. FWIW, my 57i's setup like so: softkey4 type: speeddial softkey4 label: "*Park" softkey4

Hi. Does anyone have a patch or workaround for the 50 BLF limit of Aastra phones? I have a couple 57i with the 560M console and only the first 50 BLF lines get registered. I am using the latest firmware from Aastra but I read that this limit was imposed because of a memory leak. Obviously my customer is complaining about these last 10 lines not showing their status. -- Telecomunicaciones

Hi, We have a few Aastra 480ci phones and we've noticed that in order to get the phone to receive a call, qualify must be = no. Apparently the Aastras do not respond to the qualify message (or respond in a way Asterisk doesn't understand) and Asterisk thinks the phone is unreachable. However, this now prevents MWI from working properly on the phones. Does anyone know how to get MWI

Hi, I'm a Polycom user who have just been trying out the Aastra phones. I`ve run into a bit of an issue. I cannot configure the voicemail dialout correctly on one of the two phones I am using, even if the documentation seems to state that it should work in the same manner on both phones. I have both a 9143i and a 57i CT. I`ve set both up with provisioning from config files. Both

Hi, I have 2 phones AASTRA 57i with Asterisk 1.6. When the internet connection for some reason fall down the 2 phones go to "NO SERVICE", searching on internet i found that this is due to DNS service. Has someone solve this problem? or suggestions? Thanks in advance Antonio Supera i limiti: raddoppia la velocit? da 10 a 20 Mega! Risparmia con Tutto Incluso: telefono + adsl 20