[WM: See this post on the forum: http://nerd.bz/18RacP3%5D

After doing the above including installing AsteriDex I have a problem when dialling out using AsteriDex.

On dialling out using the soft-key ‘Dial’, L1 lights up but I hear nothing.

It turns out that the speaker has not been turned on and the call is going to the handset – which is still on-hook! Lifting the handset allows me to hear the call progress as does pressing the green speaker button.

How can I get it to go direct to the speaker?

Now I have to remember to use the green button rather than Dial.

Anyone know a way to do the above phone setup nowadays????

I did have one question though… with the 57i, does anyone know of a way to import a contact list I have from my mobile phone (just plain CSV) so I can see who is calling? Possibly import that into the directory of PBX in a Flash?

File: /var/www/html/aastra/register.php
Line: 37

Right now it is:
ecit
Which is not a valid php command.
I believe it was meant to be:
exit;

Love this for the 55/57s, would like to take advantage with 53i units too.

[WM: The buttons are different so you’d have a little work to do rearranging to get the things you really need. Otherwise, you should be good to go.]

See http://pbxinaflash.com/forum/showthread.php?p=14258#post14258

[WM: Agreed. Unfortunately, it’s an Asterisk problem, not an Aastra one.]

Oh, and to answer some questions I see posted here…

Reply to 28. The sixth button SPACE is reserved for the MORE button when programming MORE than five buttons. Yes, the 480i allows you to use that space until you program a seventh button, but on the 5xi this is obviously design intent.

Reply to 27. For those who may not know, there is no Transfer or Whatever button on the 57i (unlike the 53i) because the display in context sensitive. The Transfer or Whatever buttons appear when you need to answer the call and while you are talking. Just press the MORE key to see your normal screen options. Like you, though, I miss the ability to simply program Transfer or Whatever to whatever button I like. More design intent, I guess.

Reply to 26. How are you programming your phones? I’m interested, because I need to know when the phones don’t work in order to diagnose what will. Thank you.

Reply to 25. Careful there, there are actually two lines of display on the 5xi series, one of which doesn’t display if there is an error condition, but the second line of display really helps ID lines when available.

Reply to 14. (Sorry on the slow response, I have not been back here in a while) I found out that you can only one handset at a time by talking to someone in their TAC. There is, however, a "two line" option in the configuration which allows the base phone and wireless handset to call one another and I remember a blurb about not being able to transfer a call when both lines are in use, which implies they can both be used separately simultaneously.

If Aastra has arbitrarily denied me access to program this, I might need a sedative.

🙂

I read some where that that key (on both the top & the bottom of the LCD) is never programmable as it auto-magically becomes the "more" button as soon as you program more than 5 soft keys. As soon as you program more than 5, it lights up as "more" and your programs higher than 5 move under there.

Thanks all.

I am really in need of that button (we need to put parking slot 6 there).

Cheers.

On another note, I’ve created a nifty feature (I think 🙂 to take advantage of Aastra’s XML push messaging. What it does is send the incoming callerid to other phones in the pickup group. That way colleagues know whether to pick up the call and if so, in what language, etc. Ward, I’ll send you the scripts so you can modify for PBX in a Flash.

[WM: Sorry you’re having trouble with remote access from the Aastra phones. We actually use a 57i at our beach house that connects back to our home, and it works great. Take a look at this thread for some tips.]

[WM: Sure. Just change the following entries in the MACaddress.cfg file for the individual phones as shown below or use our Plug-and-Play Module.]

sip line1 display name: Ext-701
sip line1 screen name: Ext-701


If you make a macro named macro.Asterisk and place in the file the following:
#
# Shorewall – Macro Asterisk
#
# /usr/share/shorewall/macro.Asterisk
#
#
###############################################################################
#ACTION SOURCE DEST PROTO DEST SOURCE RATE USER/
# PORT PORT(S) LIMIT GROUP
PARAM – – udp 4569
PARAM – – udp 5004:5037
PARAM – – udp 5039:5082
PARAM – – udp 10000:20000
#LAST LINE — ADD YOUR ENTRIES BEFORE THIS ONE — DO NOT REMOVE

Then place in the rules file the following line:

Asterisk/DNAT net loc:192.168.1.250

This makes it easy to change for the IP address

1) PRO: That it is indeed a very programmable/manageable phone with proper firmware updates (we are 100% Cisco 7960/7971’s so this is a big point) — very easy to adjust config files & phone’s web interface (although sometimes a little unclear).

2) PRO: Build quality is pretty good, not quite Cisco, but fairly close overall.

3) PRO/CON: Cordless is a bit chintzy (480i unit simply carried over as the LCD states & the non-matching fascia reminds), but appears to do the job decently.

4) CON: Buttons are small & close together (you’re not doing anything fast on this handset!) — Dialpad is a bit awkward to dial as buttons are wide/narrow and require extra finger pressure to activate (no breezy/quick dialing on this phone folks!) — for a handset manufacturer I’m surprised they haven’t picked up plastic buttons with lighter key pressure as virtually all PBX handset manufacturers have done for decades (Cisco has very nicely/ergo placed buttons and perfect feedback/pressure – just like a traditional PBX/Key handset — quick to use)? This is a a real bugger for anyone coming off a traditional key system or PBX, as dialing is the #1 thing you do on the phone!

5) CON: The Up/Down arrow is small/awkward to use to navigate menus and features.

6) CON: Speakerphone can’t be toggled to hangup (most handsets do), you have to hit the "hang up" button– minor inconvenience.

Overall, it is probably Aastra’s best handset to date – however, it is still an Aastra handset — not quite a competitor to Cisco in terms of quality or usability (in my humble opinion). I think on par with the Linksys handsets in that area, but with better programmability.

Not sure if this will help anyone, but if you want to get the features this is your handset — if you want a Key/PBX replacement handset this may not be your handset, I’d evaluate one personally & consider your audience before forcing them into it.

Thanks

Thanks,

Brian

A few suggestions for the above instructions to help others.

Intercom/Paging. 3 comments

1. The administrator needs to create a Paging Group Extension (e.g. 111).
2. Users then simply dial extension 111 to Page the Group
3. It might also help to explain the difference between Intercom and Paging.

Parking Lot. 2 comments

1. Your instructions reference an extension 70. You might want to note that the extension needs to be created.
2. The other "no kidding" is that Parking Lot feature needs to be enabled.

[WM: Great tips. Thanks.]

The length and breadth of what can be changed in this phone’s configuration is nothing short of mind boggling. I thought that I was pretty sharp with this stuff, and found settings that I had to scratch my head about. At least my wife has decided to get over yelling at me for staying up late playing with PBXinaFlash and all this other cool phone stuff…

After installing the applications you provided everything worked great except Voice Mail.

With VM I kept getting an "Authentication failed – wrong user and/or password" message AFTER listening to a voice mail.

It turned out that I was missing the /var/cache/aastra directory. To resolve the problem I did the following:

1) mkdir /var/cache/aastra
2) chown asterisk.aserisk /var/cache/aastra
3) chmod 700 /var/cache/aastra

Thanks for all your great work!

JT

[WM: JT, thanks for the heads up. We’ve fixed the tar ball for future downloaders.]