Aastra XML scripts 2.2.1 now available

aastra1
Posts: 287
Member Since:
2006-11-06

The new version of the XML scripts (2.2.1) is now available from the Trixbox yum repository. Thanks a lot for all the feedback we got for this beta trial.

The main changes are:

  1. leveraging the dynamic sip stack in the phone firmware 2.5.0, no more reboot needed for login/logout in 'extensions' mode
  2. a lot of changes around the Visual voice mail which now allows the user to record/modify its greetings and to listen to its messages on the handset
  3. new follow-me application which allows the user to change some parameters of its configuration (initial ring time, list of phones,...) but not the ring strategy which must be configured via freePBX
  4. more complete localization with Spanish and Portuguese
  5. special keys for LED monitoring are now detected from MAC.cfg when the phone register, application relocation is now trivial.

Release content
Enhancements

  1. Visual voice mail-User configurable auto-answer mode
  2. Visual voice mail-User configurable auto-login option
  3. Visual voice mail-Greetings record from the application
  4. Visual voice mail-LED indication for messages (2.x phones only)
  5. Visual voice mail-Monitoring of other mailboxes
  6. Visual voice mail-Now available on non softkey phones (except 9112i/9133i)
  7. Localization-Support for Spanish and Portuguese
  8. Localization-Multiple languages addition
  9. Localization-Date and time format is now automatically detected from aastra.cfg
  10. Call Forward-New toggle mode
  11. Call Forward-Last entry cached
  12. aastra.cfg generation-Auto detection of Network interfaces and VLAN support
  13. aastra.cfg generation-Multiple concurrent languages
  14. aastra.cfg generation-User can select language
  15. aastra.cfg generation-User can select timezone
  16. Self-configuration-in ‘extensions’ mode, a configurable ‘admin’ password can be used instead of the user voice mail password.
  17. Self-configuration-no more reboot needed for login/logout in ‘extensions’ mode for phones running 2.5.0 firmware
  18. Self-configuration-new tool to reapply a profile on all configured phones
  19. Self-Configuration-capability of applying custom templates based on user extension ranges
  20. ACD Agent/Queues-Automatic refresh of the queue list every 10 seconds (2.x phones only)
  21. Day/Night control-Configuration control to check if the index configured in asterisk.conf is configured via freePBX
  22. Day/Night control-If more than one day/night configured, the application can now toggle day/night for other indexes but day/night status is propagated only for the configured index.
  23. New Find-Follow me application. For softkey phones, complete configuration control (ring times, list of phones and call confirmation). For non softkey phones only activate/deactivate is available
    LED management to indicate if feature is activated.
  24. Directory-New Intercom softkey
  25. New and improved Horoscope application using a daily RSS feed.
  26. Location of the CSV file for the Contacts application is now configurable

Bug fixes

  1. Parking daemon was blasting SIP Notify every minute
  2. Spec file post uninstall script
  3. Visual Parking, user can now pickup the park call going off-hook
  4. In ‘deviceanduser’ mode, for a fixed device with a default user, the logout key was available
  5. Special characters in SIP password now supported.
  6. Caller ID can be more than 2 words
  7. Logout no more allowed in ‘deviceanduser’ mode if device is ‘fixed’.
  8. Custom menu does not allow moving up the first element
  9. Translation issues for the softkeys using 'Done' as a label

Installation
Assuming that your platform already has the previous version of the scripts, please backup your configuration files as well as your profiles if you have changed the ones we provide before performing the update.

If you had installed the beta versions you must first perform a

rpm -e aastra-xml-scripts

So logged as root on a console

yum update aastra-xml-scripts
setup-aastra-xml
reboot

The scripts have a dependency on the 2.5.0 firmware, so it has to be installed before the XML scripts.
The reboot is mandatory in order to launch daemon tasks.

Documentation
The updated script documentation is available here

Versioning
The beta rpm as well as the GA rpm are tagged 2.2.1-1, identification will be done using the build date using the following command
rpm -q -i aastra-xml-scripts | grep 'Build Date' | gawk '{print $6,$7,$8,$9,$10,$11,$12}'
4/14/09 Beta 1 (Build Date Tue 14 Apr 2009 03:34:01 PM CDT)
4/20/09 Beta 2 (Build Date Mon 20 Apr 2009 01:04:47 PM CDT)
4/24/09 GA (Build Date Thu 23 Apr 2009 04:37:23 PM CDT)

Enjoy! Thanks again for all your inputs.

Regards

--

---
aastra1
Aastra XML scripts 2.3.0 now available



mag
Posts: 135
Member Since:
2006-05-31
Awesome! Thanks for the

Awesome!

Thanks for the great work and listening to the people on the forums - this is why we recommend and use the Aastra phones.

Will keep you posted on our testing.

M



necits
Posts: 419
Member Since:
2008-02-23
Aastra is top notch. You

Aastra is top notch. You guys deserve alot of credit. It is definetly appreciated.

--

Michael Mathewson CCNA,MCSE
Owner/Consultant
Northeast CT IT Solutions



SkykingOH
Posts: 9541
Member Since:
2007-12-17
Great job on the new

Great job on the new scripts. I can't wait for the 'executive' color/touch screen model to round out the line.

I just had to toss that in.

The Presence and Queue apps are awesome.

One small bug, if you log the phone out after you log back in "cannot display" flashes in the center portion of the screen. Taking the phone off hook and then on hook restores the display.

Not needing to reboot after changing the settings is very nice.

Keep up the great work.

--

Scott

aka "Skyking"



wrc1045
Posts: 199
Member Since:
2008-04-20
queues........

Can I ask how this is intended to work on the aastra phones? what is the functionality of this and how will it work? sorry I had to ask



mdiorio
Posts: 52
Member Since:
2009-03-24
First time upgrading the

First time upgrading the Aastra scripts. What files need to be backed up? Do the MAC.cfg's need to be backed up? I assume the demo-user.prf file as well. Anything else? Can I restore them after upgrading the package, or does the upgrade add features to these files that wouldn't be available if I restored?

Also, is there a way to test the new script without having to roll it out to the entire company? If something happens, I don't want it to affect every phone.

Thanks.



aastra1
Posts: 287
Member Since:
2006-11-06
Backup before upgrade

Hi mdiorio,

Quote:
First time upgrading the Aastra scripts. What files need to be backed up? Do the MAC.cfg's need to be backed up? I assume the demo-user.prf file as well. Anything else? Can I restore them after upgrading the package, or does the upgrade add features to these files that wouldn't be available if I restored?

No need to backup the mac.cfg files, they are compatible. The files you need to backup are:

  1. the .prf files,
  2. the .conf files,

Once the upgrade is done, you can still use your .prf files as they are compatible but you may want to change them to access to the new applications/features. For the .conf files, if we added new parameters they have a default value you might also look at them.
Also, all the phones should login/logout to get the new features, you can also use the apply_prf tool provided to reapply the .prf files to all the configured phones and have them reboot automatically.

Quote:
Also, is there a way to test the new script without having to roll it out to the entire company? If something happens, I don't want it to affect every phone

Unfortunately no, there is a way but it is pretty complicated to setup, maybe one day we will publish the beta rpm as an add-on to an existing version for tests. The best way to test is either to find an 'old' pc and install Trixbox and the new scripts or use the vmware version of Trixbox running on your Windows PC, sound quality is bad but at least you can test the scripts on a small number of phones.

Hope this helps.

Regards

--

---
aastra1
Aastra XML scripts 2.3.0 now available



aastra1
Posts: 287
Member Since:
2006-11-06
Beta 2 of the XML scripts 2.2.1 now available

All,

I just published the new Beta 2 RPM for the XML scripts 2.2.1.

The install/upgrade process from Beta1 is almost the same as the one to install Beta 1.

cd /tmp
wget http://65.205.71.13/2.2.1/aastra-xml-scripts-2.2.1-1.noarch.rpm
rpm -e aastra-xml-scripts
rpm -i aastra-xml-scripts-2.2.1-1.noarch.rpm
setup-aastra-xml
reboot

The plan is to go GA by the end of this week.

Thanks again for all your feedback.

Regards

--

---
aastra1
Aastra XML scripts 2.3.0 now available



nhue
Posts: 31
Member Since:
2007-06-07
Localization doesnt work on

Localization doesnt work on 480i (if you put French as default language and boot your phone its still in english), Presence features don't work on them either, you can set yourself as away and other phones calling will react properly but when you dial a phone with a presence setting you don't get any message at all.

I understand series 4 (firmware 1.4.3) is a dieing brand but is there any plans on making the script working better with them? Aside from that the scripts are really great on 5xi series.



syadnom
Posts: 52
Member Since:
2009-03-21
auto config on seperate vlan

this drifts a little off topic but i think that the aastra-xml scripts are how to accomplish this.

aastra, do you have any advice on how to get aastra 5xi phones to auto config on a seperate vlan than pcs are on while using the same cable? I am using the onboard bridge to run a computer on each of the phones. I want to put the aastra's on a different vlan but use the same cable. I can do protocal based vlans on my switch.

My idea is to just do the dot interface on the eth0 (eth0.1) and turn on vlan tagging on that interface, then add a vlan1 to the switch and find some way to get the phones to auto configure on vlan1 instead of the standard lan vlan0. I have a cisco router as the dhcp server and would like to keep the dhcp for the pcs there.

any help would be very much appreciated. I have over 100 aastra phones right now and still have 80 locations and over 400 phones to go and would like to get this figured out before deploying more sites.

Thanks



syadnom
Posts: 52
Member Since:
2009-03-21
executive aastra phone

I just have to second the notion of an aastra 59i / 59i-CT with a color touchscreen. maybe even consider 59i-cam or something with a built in camera. grandstream is the only one with a vidphone priced reasonably and grandstream phones are not nearly as rugged as aastra phones.

Thanks



thx247
Posts: 53
Member Since:
2009-02-11
This is how you configure

This is how you configure the VLAN options in the phone config files. May help.

#VLAN taggin on
tagging enabled: 1

#VLAN Setting for LAN port
VLAN id: 30

#VLAN Setting for PC port
VLAN id port 1: 1



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.