New Aastra XML scripts 2.2.0 for PIAF

[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...

@aastra: it may be a good idea to add a softkey for 'logout' on (at least) the 9143i's display in startup.php .. even if I hadn't removed the 'logout' from the config I still wouldn't have even rembered the (un-labled) bttn was mapped due to this new feature set.

I also see an 'override' directive (case) in startup.php.. is this called via browser for dev? i don't see a keymapping for it, or understand it's actual usage.

 

[Speedy2k]

I would like to know what i have to do to make the phone load it's own .prf file each time i log in? like
when 221 log in it will use 221-user.prf as base
and when 222 log in it will use 222-user.prf.

i know in the file asterisk.conf there is the profile option, but i would like to know what to put as the profile to make it variable depending on the phone that is login in? thanx!

 

[tel0p]

@speedy. the prf file's are template's for the config files located in /tftpboot. you can edit the template to set specific settings for the TYPE of phone but not for the individual extension (FWICT).

to edit the specific extension go into /tftpboot and edit the [MAC].cfg for the specific phone AFTER the initial startup config.

 

[Speedy2k]

if you go see in the /var/www/html/aastra/config/asterisk.conf
you see this line:

[Startup]
# Phone profile to use for self-configuration
profile=demo

so it will use demo-user.prf, but what i want is to put in this profile something like this:

[Startup]
# Phone profile to use for self-configuration
profile=$user

to make it load the $user-user.prf file so i can create the 221-user.prf file and put it in the /var/www/html/aastra/asterisk/ directories so i will be able to logout and log back in on another phone and get the same setting. but what is the variable format i must use in this file to make it use the extension #?? I'm sure it is doable.

 

[tel0p]

Here's what I did..
cp demo-user.prf MYCUSTOMER-user.prf
go into /var/www/html/aastra/config/asterisk.conf and change profile=MYCUSTOMER.



Again, I think you're missing the point of the PRF. The PRF is a TEMPLATE for ALL the Aastra phones on your system NOT individual extensions (221). AFTER you plug in your phones and have the template run you can edit the INDIVIDUAL phone config file's in /tftpboot/[MAC].cfg wher MAC is the MAC address of the INDIVIDUAL phone.

Making a specific extension (221-user.prf) defeats the entire purpouse of this 'general' template for phones.

I understand you want to have a user 'login' and see all their appropriate keys and config, specific to the user but the functionality just isn't implemented, from what I can tell. It would take a lot more code to store each config per user. Maybe in a future release?

Have a look at chapter 3 of the manual...

 

[aastra1]

Extra explanations

I have seen a couple of posts asking about the prf files and what they are.

The scripts are using 3 prf files:

• XXXX-user.prf which is the profile used in 'extensions' mode, this profile is applied each time a user logs in.
• XXXX-device-nouser.prf which is the profile used in 'deviceanduser' mode when you use the self-configuration for a device configured as ad-hoc. This is a very basic profile which allows to login/logout a user.
• XXXX-device-user.prf which is the profile used in 'deviceanduser' mode when you login a user on a ad-hoc device.

I have also seen a post (speedy2k) who wanted to have individual profile for each user, some where it defeats the purpose of defining a profile... But that could make sense if you have special users with a custom configuration or some BLF in deviceanduser mode.

This could be doable via a simple change in startup.php and sync.php, the script could check the existence of a XXX.prf (XXX being the user extension) and apply it instead of the configured profile. Based on your feedback on this one, I can do the changes, it is pretty simple.

Ideally what I would like to implement is the capability of defining multiple profiles (regular, agent, executive...) and you would assign a profile when you create the extension via freePBX but that means some changes in freePBX. Maybeone day.

Another question was about where the login parameters are stored, it is in /var/cache/aastra/startup_asterik.cfg, we store the MAC address, IP address and extension. This is used in extensions to check if a user is not already logged in somewhere else as Asterisk does not supprt multiple registrations. If it happens, the user is prompted with a message and the capability to 'override' which means logout the other phone and login on this one. This explains that if you delete the MAC.cfg of a user and go over the self-configuration again, the scripts will tell you taht you can't as you are already logged in on tis phone, you will need to edit startup_asterisk and delete the entry for this user. anyway the best way is to logout and login again.

Also we are working on a XML application which will allow the user to customize his phone defining all the keys himselh including BLF and speeddial. That will come...

Thanks again for all the great feedback you provide, we are happy to see that the XML scripts are widely used and appreciated as it represents a lot of work for us... Remember that they are free.

aastra1

 

[Phone_User]

Aastra XML patch for 2.2.0 scripts

FYI I was scanning forums and came across this post about a patch for 2.2.0 scripts. It has to do with the phones registering every 1 minute.

http://www.trixbox.org/forums/vendo...ml-scripts-220-couple-bug-fixes-patch-1-relea

 

[Phone_User]

Echo with updated firmware.

After installing the 2.2.0 scripts and new firmware I have noticed and echo in my phone.

Has anyone else had this problem. Is there a way to get rid of it. I have only installed it on one phone and am now concerned as some users will notice this and really start to ... You know what I mean.

 

[aastra1]

Be patient, the patch for the scripts is being tested on PIAF. It will be available shortly.

aastra1

 

[aastra1]

XML Scripts 2.2.0, patch 1 released

All,

Thanks to your feedback, a couple of bugs/enhancements have been identified in the aastra-xml-scripts 2.2.0, there are probably more but one of the bug is significant enough to need this post, it cannnot wait for the next release of the scripts.
As patching source code can be tricky for some, we provide an official patch script which does the job for you.

Daemon is sending a SIP Notify to every phone every minute
Because of a mistake handling the socket timeout with the Asterisk Manager, the scripts consider that Asterisk is restarted every minute and therefore sends a sync SIP Notify to every phone which has a park.php key. This implementation just adds some useless load on your server as well as on the phones, I would advise to install if you have more than 10 phones.
The changes are in /var/www/html/aastra/include/AastraAsterisk.class.php and /var/www/html/aastra/asterisk/daemon.php


Pickup a parked call by going off-hook
This used to work in the previous release of the scripts, when you were using tyhe Visual parking you could pickup the selected parking slot by going off-hook.
Changes are in var/www/html/aastra/asterisk/park.php


Patch script
The patch script is available from the PBX in a Flash repository used for the XML scripts.
Installation

# cd /tmp
# wget http://pbxinaflash.net/source/aastra-xml-2.2.0/aastra-xml-scripts-2.2.0-patch-1.x.gz
# gunzip aastra-xml-scripts-2.2.0-patch-1.x.gz
# chmod +x aastra-xml-scripts-2.2.0-patch-1.x
# ./aastra-xml-scripts-2.2.0-patch-1.x

Results

aastra-xml-scripts 2.2.0 PATCH 1
================================
Checking aastra-xml-scripts package...Done
Checking patch package...Done
Patching /var/www/html/aastra/include/AastraAsterisk.class.php...Done
Patching /var/www/html/aastra/asterisk/daemon.php...Done
Patching /var/www/html/aastra/asterisk/park.php...Done
Script completed.

Don't forget to reboot once the patch is installed.

These patches are not mandatory but recommended.

Again, any feedback welcome.

Regards

aastra1

 

[TheShniz]

I've got some brand spanking new 9480iCT's w/ new label'ing as 35iCT's.

When I add them to the system (entering extension/password), they reset as normal and come back w/ the relative extension information... however, they only have a single button programmed: "StartUp".

In fact, they are all identified in /var/cache/aastra/startup_asterisk.cfg as 35iCT's... not 9480iCT's. As it stands right now, I'm assuming the XML scripts are unaware of the 35iCT model and are not properly creating the configuration files.

Can I fool the script into thinking they are in fact 9480iCT's, or can I add the 35iCT model to the /var/www/html/aastra/demo-user.prf ?

Updated:
I should mention that I have 5i-series telephones working just fine on the same system w/ the XML.

 

[aastra1]

33i/9143i, 35i/9480i and 35iCT/9480iCT Important message

The earliest hardware versions of the 9143i, 9480i and 9480iCT were called/labeled respectively 33i, 35i and 35iCT and some of them were shipped with an obsolete firmware 2.0.5 which will not upgrade directly to the latest firmware 2.4.1 and therefore will not be supported by the XML scripts. During the boot sequence, the phones are looking for 33i.st, 35i.st and 35iCT.st not 9143i.st, 9480i.st or 9480iCT.st.

Sure we could add the phone models in the .prf files to be supported by the scripts but most (if not all of them) would not work with the scripts, the scripts are designed for 2.4.1 (or at least 2.3.1).

So what you have to do on your PIAF server as the aastra-ipphone 2.4.1 package is installed:

[FONT=Arial]cd /tftpboot[/FONT]
[FONT=Arial]cp 9143i.st 33i.st[/FONT]
[FONT=Arial]cp 9480i.st 35i.st[/FONT]
[FONT=Arial]cp 9480iCT.st 35iCT.st[/FONT]

Then REBOOT the phones.

After reboot the 2.4.1 firmware is installed and the phone will now look for the right firmware in the future (9143i.st...). So this is the one ond only time you have to do it.
All the scripts should work smoothly with the new firmware. If you already tried to self-configure the phones you may have to edit /var/cache/aastra/starup_asterisk.cfg to avoid the error message "You are already using the extension on this phone".

This information regarding the firmware upgrade of the early 3i was sent to our distributors and resellers, unfortunately it looks like it did not make it to you so I guess that this reminder is useful.

Let us know if you still have issues and sorry for the inconvenience.

Regards

aastra1

 

[wardmundy]

Gosh. 16 minutes for a response. Aastra is obviously falling apart.

 

[TheShniz]

Interesting... no, it never did make it down to me, HMmmmmmmmmm... it happens. We've got a fairly long history w/ our sales rep, as he was also our rep w/ Active Voice before joining Aastra, great guy.

We sell predominantly 5i-series of Aastra phones, w/ a few 480i CT's here & there... so this is my first batch of updated 9480i's. The black plastic looked a little odd at first, but quickly got used to it. I am glad you mentioned the 9143's in your post, cuz I've got 2x boxes waiting to be programmed next.

...thanx for the quick response

 

[webcoaster]

First thanks for the code and the patch things are looking good so far on our end.

Using 6-57i, 1-480i CT and two Polycom 601, like Polycoms but they might end up on ebay or for sale here.

Question on the reboot in the patch post, when you reference a reboot in your instructions are you speaking of the entire box, a program or just the phone?

I'm new to PBX systems so that's where the question comes from.

I also have a request that the aastra/readme.txt be updated to reflect PIAF and not Trixbox for us that are noobs.

Thanks in advance, this community rocks.

-Cheers

 

[foneman]

Vmail

has anyone had an issue with recording greetings on their vmail with these scripts? It seems that as soon as a user presses one to record the unavailable scripts, it immedidately asks to press 1 to accept.
I am looking at the timing to see. TIA

 

[aastra1]

Reboot in that case means reboot the server.

aastra1

 

[aastra1]

has anyone had an issue with recording greetings on their vmail with these scripts? It seems that as soon as a user presses one to record the unavailable scripts, it immedidately asks to press 1 to accept.
I am looking at the timing to see. TIA

What you describe happens when the voice mail box has never been initialized. The user probably never received a message or recorded his signature).
It works fine when the VM box is initialized.

aastra1

 

[Speedy2k]

aastra1:

I would like to know if you can point me in the right direction to make your script use the <userid>-user.prf file instead of the demo-user.prf file, and if it is possible to create one <userid>-user.prf file if it not exist already based on the demo-user.prf file.

And i have a little request for you just let me know if it is doable. Is it possible to create a little php script that will go into the system and create a local directories with the extension and name as it is in the system of all the extension on the system and put them into the top 6 buttons with the BLF light working for it so we can see if they are online or not ?? thanx a lot!

 

[Phone_User]

Minor error

Found a small error in one of the macros

[Feb 24 06:58:26] WARNING[6803] pbx_config.c: No closing parenthesis found? 'Set(_REALCALLERIDNUM=${REALCALLERIDNUM}'

Its in the macro-presence-playnotification macro