New Aastra XML scripts 2.2.0 for PIAF

[aastra1]

The new version of the XML scripts (2.2.0) is now available from the PBX in a Flash repository.

Big thanks to Ethan Schroeder at Schmooze Communications who provided most of the core new scripts and to some users who submitted some bug fixes found in 2.1.1.

What has changed

Enhancements

• Support for new Aastra 6730i and 6731i SIP Phones
• Presence application (initially provided by Ethan Schroeder at Schmooze Communications)
• Meet-me applications now displays conference room name
• Internal lookup on outgoing calls (configurable) with presence information
• Directory, Parking and Visual Voice mail application now available for 9112i and 9133i
• ACD agent login/logout (initially provided by Ethan Schroeder at Schmooze Communications)
• ACD queue statistics
• LED of the Parking application now slow flashes if at least one call is parked.
• Environment variables including phpagi credentials are now directly taken from FreePBX configuration.
• Enhanced localization with date/time format and all labels outside of the code
• Simplified initial setup with most of the configuration parameters available from the setup-aastra-xml command.
• DND state is now reflected on BLF monitoring (FreePBX 2.5 and DEVSTATE module needed).
• Some parsing protection against external hacking.
  Visual parking now displays the parking orbit.

Bug fixes

• Race condition in the sync mechanism corrupting user context files
• Auto-config fails on some extensions with password using symbol characters
• Auto-config fails on some extensions with extensions starting with 0
• SIP Notify sent to more than 50 extensions
• Display parking lot now works if Find-me Follow-me is enabled or call from a ring group (thanks to Ethan Schroeder at Schmooze Communications)
• Visual voice mail crashes if caller ID has symbol characters
• In device and user mode, speed dial is now common for users connected on multiple devices
• Visual voice mail authentication in device and user mode

Installation

Logged as root on a console

1. cd /tmp
2. wget http://pbxinaflash.net/source/aastra-xml-2.2.0/install-aastra-xml.x.gz
3. gunzip install-aastra-xml.x.gz
4. chmod +x install-aastra-xml.x
5. ./install-aastra-xml.x
6. setup-aastra-xml
7. reboot

If you made some configuration changes or developped auto-configuration profiles (.prf) in the previous version make a backup before upgrading as the files might be overwritten.

aastra-ipphone 2.4.1 which is the latest firmware for the Aastra SIP phones is automatically installed during the process as it is a dependency of the package.
The reboot is needed in order to launch a new daemon task listening for Asterisk events.

Documentation and complete source code

Our Web site www.aastratelecom.com will be updated very soon with this new version, in the meantime:

• Documentation is available here
• Source code is available here (.tar.gz)
• Spec file used to generate the RPM is available here

Feedback

Please use this thread to provide your feedback on the scripts and report bugs. This is the most efficient way, so please don't contact Aastra support as the XML scripts are not directly supported by them.
We are always open to requests for new features.

Enjoy! Thanks again for your help.

Regards

aastra1

 

[Speedy2k]

first of all I would like to say thanx to the Aastra guy, they have done a very good job once again. but I have to requests. the first one is, is there any way,when I put a call in a parking lot, then the phone show me the parking lot number, not tell me. and they other one is: is it possible to incorporate the cnam lookup script into the xml, so as soon as we dial an external number, it will use the script to retrieve the name. thanx

 

[aastra1]

Thank you for your support!

the first one is, is there any way,when I put a call in a parking lot, then the phone show me the parking lot number, not tell me.

Actually, when you park a call and hang up a script is triggered to try to display the parking orbit, I say try because it is not that simple, it works for extension call, queue and ring group and most combination of them. There are cases though where the orbit number is not displayed.

and they other one is: is it possible to incorporate the cnam lookup script into the xml, so as soon as we dial an external number, it will use the script to retrieve the name. thanx

Right now, when you dial out a script does an internal lookup to display the callerID name of the dialed extension as well as its status. This could easily be extended to external numbers as long as we have a reliable source. Which cnam lookup script do you refer to?

aastra1

 

[Speedy2k]

Here is a direct link to the site i can't find the post in this forum that talk of it, but i have it running on my server and it is working pretty well.

http://code.google.com/p/freepbx-utils/wiki/Introduction

Let me know if you can incorporate in, it would be really sweet! thanx!

 

[deano]

Acd

Hey,

Great Script and Documentation. Worked great.

The only thing I am trying to find the ACD and presense parts on the phone and can't seem to see them. I had the old scripts loaded so I just installed over. Don't know if that is the issue or I just don't know were the button is.

Some direction would be much appreciated.

For a wish to have, is there anyway to see the status of a phone when you dial that extension. Avaya's Quick Edition has some nice icon's showing off hook before you dial the extension. Just a though.

Thanks

 

[jehowe]

Very nice work and excellent documentation. One nice surprise is the 2.4.1 firmware adds G722 support!

 

[deano]

soun quality

Since this upgrade, I have noticed a slight echo on call starts with a head set. it quickly goes away, but I was wondering if there was a change to something that would cause this. The overall sound quality is much better though.

This new echo is present only on speaker phone and the head set.

The head set is a plantronics Blue tooth unit.

Anyway, just some feedback.

 

[bulldog]

After a number of problems, mainly finding a free machine capable of running PiaF, I ran the system, loaded the scripts and the whole thing went like a dream. Loads of improvements, a number of newies but the one niggle; thing I was really hoping to change has remained the same, namely the Park button.

I don't know whether it is us Brits who are lazy, or just that we cannot see the sense in complicating a simple task with more buttons to push. If anyone else wants to try it simply set a key up as a Speeddial/Xfer with a value of 70 and you will see what I mean - the call is immediately put on Park the channel is dropped and the screen displaying the position the call has been parked is displayed. You are also spared the voice telling you what you are about to find out anyway.

I know what the immediate response of anyone who has read this so far is likely to be;

"So what's your problem, you already given the answer!"

However it is not that easy, the Park button in the lower screen of the 57i is about the only bit of the phone that is hardcoded and although I know it can be disabled and hidden, there is absolutely no way of replicating it in the lower part of the screen so that it appears where and when you want it. Unless of course I am missing something in which case I would be more than happy to have someone put me in my place.

As I have mentioned before I know I am not the only person on the trawling the internet and hammering Google, trying to find an answer to this problem. I just cannot believe that all the other users are happy with the way the Park key works.

All hail to Piaf though, love it!

Pip Pip

 

[gregc]

I don't understand what you are trying to do. Do you want to just move the park button?

Mine has the functionality you described. Press park, hang up, the parking spot is then displayed.

 

[dobbs]

Resetting phones after the initial installation?

I have a question regarding the auto-configuration routine.

If someone (i.e. a client) changes their mind and decides they want features (i.e. reday/night service, dnd, etc...) they didn't want at first, is there a way to reinitiate the auto-config routine?

I tried a few things like deleting the corresponding .cfg file in /tftpboot and resetting a phone to factory defauts. When I tried that though, I got the message that the extension was "already in use." Where is that information being stored?

 

[euser4life]

Add the changes you want back into the corresponding .prf file and simply use the logout function on the phone. The logout function will clear out the corresponding directories on your pbx provided you have the correct owner and group (aka asterisk) and permissions.

The phone will reboot and you will be asked for the extension and v/m password. It will create the new "mac".cfg for the phone with the options you specified in the .prf file.

 

[tel0p]

which .prf

I've read the doc's and still can't seem to see which .PRF file to edit. I don't want user, just device. I realize it's 2 of 3 but which of the 2?

 

[Speedy2k]

I have a little question about that too, is it possible to make every phone use it's own .prf file like as soon as the phone try to register, you copy a .prf or create a prf file with the extension in it, so when you want to make modification to only one phone, it is possible? I don't understand very well how these .prf file works thanx!

 

[dobbs]

My understanding is that the config files are created from the /var/www/html/aastra/asterisk/demo-user.prf file.

I still don't understand where the specific used extensions are being stored. Once a phone is configured for an extension, even deleting the corresponding .cfg file doesn't seem to clear it out. There's nothing in the .prf files I've found that's keeping track of used/unused extenstions.

 

[tel0p]

@dobbs/Speedy
The .prf file is just a template for the phones. The PHP (startup.php) handles the 'first time' the phone is provisioned (dobbs: the init.php goes into freepbx's extension table and gets its info) then takes the template PRF files and outputs a configuration (on a per-endpoint basis) stored in /tftpboot .. ala [MAC].cfg .
..sorry for the runon

@all/aastra1
I've read the docs (link in OP) and I'd like to say they are very well written. Nice. The only question that arises (for me) was which of the 3 prf (templates) to edit as I want to remain in DEVICE mode.. no login's, so editing demo-USER.prf seemed backwards.. maybe it's just me. in ref to docs Chap 3.1 (pg 25 of the .pdf).

 

[dobbs]

That was pretty much my understanding too, but deleting the <macaddress>.cfg file in /tftpboot doesn't seem to clear an extension if one wants to reinitiate the auto-provisioning. The same phone will just say "that extenstion is already in use". It's that cache or log file I'm trying to find.

I've just been creating new extensions in my tests, but that won't work in production!

 

[tel0p]

@dobbs:
I recreated your issue on one a 9143i. I went into /tftpboot and deleted the corresponding [MAC].cfg then when prompted for login was told the same thing, extension in use. http://'ing to the phone itself seems to show clear'ed lines as well.

This appears to be a small bug in the startup.php application. I was only able to drop to the 'options' menu once, now I'm stuck in a loop on this phone too. Hah. The startup.php references the /*-user.prf so that's a starting point. I'll update when I get a chunk of time.

Also, when I did get to Options > Admin Menu > Reset Internal CFG > REBOOT#, I still got the issue.

UPDATE: I figured out how to break from the 'Login Loop': Enter another existing extension, it will throw an error but now you can hit 'Options'. From Options > Admin Menu you will have to do a factory reset on the phone to clear the settings. Then reboot phone.
Presumably this is just a little bug with the startup.php not giving the 'option' to get to 'Options' and wouldn't really be seen in production as long as the phones are in a factory default state.

UPDATE2: Even this didn't solve the issue. On line 416 of startup.php I found the file we want.. it's /var/cache/aastra/startup_asterisk.cfg .. edit it and remove the offending extension and you'll be back in business.

 

[dobbs]

Yep...that's it. Nice work! My remaining hair thanks you.

Interesting that it's logging the ip address of each extension as well!

I would gather from this that this same process is involved in any Aastra model.

 

[aastra1]

You need to logout/login the extension

If you have installed the scripts on top of the previous version you will need to logout the user then login again to apply the new template with the new feature.

The template is the demo-user.prf file which describes how to build the MAC.cfg file.

As your phone has been build with the previous template the new features are not activated.

Hope this helps.

aastra1

 

[tel0p]

ahh

noprobb dobbs.

So logout.php handles it. lol, I had removed the key for this deployment as I don't want the end-user being able to logout (and not know the VM password to log back in).

I'm using a [custom]-user.prf now and it seems to be working great/making things easy. Now I'll attempt an XML/php app...