New Aastra XML scripts 2.3.0 GA

Aastra -

Fantastic job.....Will be using three sites for beta testing next week.

Will provide feedback.

For all the forum members, Aastra's integration with Asterisk/FreePBX is worlds ahead of any other vendor.

Ok, I had to rebuild my primary trixbox (thank goodnews for backups!)

Installed the new scripts. They work well, but.... When I park a call (6755i), I don't get the LED on the Park key. (LED works as it should on the VM) This new update did fix the day/night led not working however.

This may very well have something to do with the rebuild trix, not the scripts... Anyone have any ideas?

Scott

Hi Scott,

To understand what's going on I need to know more details of your configuration as explaied in the initial post.

1. Asterisk version
2. freePBX version
3. freePBX mode (extensions or devicesanduusers)
4. USEDEVSTATE in /etc/amportal.conf
   The parking application is tricky because there have been some changes in the manager API between Asterisk 1.4 and 1.6 (even within 1.6). That's why I need to know more details...

   Regards

Extensions mode (stated above)
Not sure what framework tb 2.8.0.4 is using. I'll look when I get home.
Yes, DND does activate/deactivate when I press the DND button. (stated above)
USEDEVSTATE=TRUE in amportal.conf

Going to table this for now...

The system wasn't a pristine install, and may have other issues. Right now I'm back to my original server (trix 2.6.3, ext mode, and 2.2.1 Aastra XML scripts) and the parking working there.

If I have the problem on the new production server I'm installing I'll repost.

BTW - Aastra, thank you! Your work has made the trixbox platform greater than the sum of its parts. Appreciate you help

Scott

I installed these scripts today and have foud some wonderful improvements from the previous version (along with a few issues). Night mode, visual voicemail, parking, and the directory have immediately noticable improvments. Great job!

My platform details....
Aastra 57i phones
Asterisk 1.6.2.6
FreePBX 2.7.0.2
AMPEXTENSIONS=deviceanduser
USEDEVSTATE=true
Using AsteriskNOW distro (not trixbox)

Issues and/or feature requests noticed so far are...

1. I am having the same issue with LED synchronization on my 57i phones as previously reported by others here as well as on the PIAF forum. This includes presence, DND, and Call Fwd (not sure of Follow-me) applications. The buttons handle their specfic functions, however the LED simply does not update. I have also confirmed that toggling functions such as DND from feature codes does *not* toggle the LED on the phone. Voicemail and night mode LED's seem to function fine, however.

2. For some reason I was unable to playback voicemails using visual voicemail until I made a slight change to aastra-vm.php. I had to change the call to the ControlPlayback command to force it to follow the format $agi->exec('ControlPlayback',$sound_file.'|2000|6|4|0|5|1'). As written, it wanted to use pipe delimiters for 1.4 and commas for 1.6. After my change, I forced it to use pipes all the time and the vm application works fine.

3. If I have an adhoc device without a default user, I can successfully login and logout of the device with the scripts. Upon login, it correctly syncronizes all LED's (see issue #1 above) and screen information for the logged-in user. HOWEVER, if I have a device WITH a default user, then NONE of a new user's information will synchronize if a new user tries to login to the phone (still shows the default user even though the new user is logged-in). I presume this is because the only way that I am able to login another user to a device with a default user is with the *11 feature code (see below), and perhaps the proper update event is not being sent/caught to update the phone.

4. When an adhoc device is assigned with a default user, I believe the issue of not having a "login" button when the default user is logged-in existed in the previous version of the scripts as well. Because of this, the "logout" button really only adds value when the phone has no default user. As a feature requested, I think one of two options would be great: 1) if it's an adhoc device and only the default user is logged-in, change the logout button to a login button (so someone can login as another user), or 2) on the logout screen along with the logut and cancel choices, have a choice to "login as another user". This would allow me to set some of my 57i's with default users, but also give people the ability to login to them without using *11 (and have it update the screen too!).

Thanks again for the great work!!

I have experienced a problem where my BLFs were not working properly and although it took asking someone else for help we discovered that the following line is needed in the CFG files for the BLFs to work correctly for some button types such as the pickup button.

sip xml notify event: 1

I also figured out that certain buttons such as day/night need to be configured in the MAC.cfg and not the aastra.cfg file for the corrisponding blf to work correctly.

I don't know if these are still true with these new scripts as I have not had a chance to test them but this might be worth trying to see if it helps.

Hello there,

When you say
My platform details....
Aastra 57i phones
Asterisk 1.6.2.6
FreePBX 2.7.0.2
AMPEXTENSIONS=deviceanduser
USEDEVSTATE=true
Using AsteriskNOW distro (not trixbox)

That is where lies the problem, even if we try to make the scripts very flexible, we cannot test every possible environment. There are major differences between Asterisk 1.4, 1.6.0, 1.6.1 and 1.6.2, we have done our tests using packaged solutions like Trixbox because it is a stable environment, it is impossible for us to test every flavor of every product...

So

1. I am having the same issue with LED synchronization on my 57i phones as previously reported by others here as well as on the PIAF forum. This includes presence, DND, and Call Fwd (not sure of Follow-me) applications. The buttons handle their specfic functions, however the LED simply does not update. I have also confirmed that toggling functions such as DND from feature codes does *not* toggle the LED on the phone. Voicemail and night mode LED's seem to function fine, however.
LED status is done by listening manager events, these are not consistent between Asterisk versions... so have a look at the code in the daemons and tell us what's different.

2. For some reason I was unable to playback voicemails using visual voicemail until I made a slight change to aastra-vm.php. I had to change the call to the ControlPlayback command to force it to follow the format $agi->exec('ControlPlayback',$sound_file.'|2000|6|4|0|5|1'). As written, it wanted to use pipe delimiters for 1.4 and commas for 1.6. After my change, I forced it to use pipes all the time and the vm application works fine.
Kind of the same answer, differences between asterisk implementations, the Asterisk version for Trixbox 2.8.0.3 needs ',' for separators not '|' so in Beta 2 we try both because there would be too many combination to test. Try beta 2.

3. If I have an adhoc device without a default user, I can successfully login and logout of the device with the scripts. Upon login, it correctly syncronizes all LED's (see issue #1 above) and screen information for the logged-in user. HOWEVER, if I have a device WITH a default user, then NONE of a new user's information will synchronize if a new user tries to login to the phone (still shows the default user even though the new user is logged-in). I presume this is because the only way that I am able to login another user to a device with a default user is with the *11 feature code (see below), and perhaps the proper update event is not being sent/caught to update the phone.
We have identified some MAJOR problems with the deviceanduser mode which has never been updated since DEVSTATE has been introduced so all the user hints are wrong, we are looking for a fix in beta3 we already did some fixes in Beta2 but I would advise not to login/logout with the keys but with *11 and *12 until we fix everything. The fix may even be to actually call *11 and *12 as the AGI behind it is very complex and changes everytime freePBX updates it.

4. When an adhoc device is assigned with a default user, I believe the issue of not having a "login" button when the default user is logged-in existed in the previous version of the scripts as well. Because of this, the "logout" button really only adds value when the phone has no default user. As a feature requested, I think one of two options would be great: 1) if it's an adhoc device and only the default user is logged-in, change the logout button to a login button (so someone can login as another user), or 2) on the logout screen along with the logut and cancel choices, have a choice to "login as another user". This would allow me to set some of my 57i's with default users, but also give people the ability to login to them without using *11 (and have it update the screen too!).
Again we will have a look in Beta3.

Thanks for your feedback even if I would have preferred a pure Trixbox installation...

Regards

Does anyone have any tips on php code debugging in these scripts? Syslog from the phone doesn't help me very much, nor does the log generated by trace/debug options built into the xml-scripts. I'm used to throwing echo's at each function to see which function the script is dieing at. I'd like to take the DND script and see where it's dieing, and try to come up with a fix. I make so many modifications to the initial install, and I don't want to part with any of them. I'm on the same boat as bclarkindy. I press the DND button, it activates, but the phone doesn't update. If I activate DND by the feature code, it does update the phones screen and blf. I'd like to find a way to trigger the update in the same manner it is triggered by dialing the feature code. It looks like it's with sync.php.

The syntax of the command used in the scripts to update the state of custom devices used to track LED status needed to be changed (at least on my Asterisk 1.6.2 install). Once I replaced all instances of "core set global DEVICE_STATE()" with the command "devstate change" within AastraAsterisk.php, the LEDs started updating properly (for the most part, see below).

While I now get LED feedback in realtime, LED's do NOT seem to syncrhonize reliably when changing users (using *11/*12). The only testing I've done with this so far is if the device has a default user (it might work better without a default user, I will test tomorrow). Voicemail and presence LEDs never seem to sync on login, and it also looks as though the others (DND, call fwd, follow-me LEDs, etc.) "hiccup" every once in awhile and don't sync properly. Logging in again typically fixes the latter.

I'm not sure if this is a firmware issue or a script issue, however I have had a couple test phones completely lock up a couple times over the last couple days of testing. I had to restart the phones to get them to respond. I am only mentioning this because I've not had this problem before. I will keep my eyes open to determine what I'm doing with the phone when this occurs.

Voicemail playback now works fine for me in beta 2.

Thanks again fo the great work!
-Brian

If you use the aastra_debug to print an array make sure that you do
aastra_debug(print_r($array,True));
The True will make it a string and not dump it to stdout.

Also thanks to your input, we fixed the DND/daynight... LED problem with Asterisk 1.6.2 the command used to change the devstate device is now obsolete. Fixed in Beta 3.

We will try to fix the issues in deviceanduser mode with beta3 if we can, if not we will not support this mode anymore as it becomes too complex to manage in sync with freePBX.

Regards

If you don't have Day Night Mode installed, the 2.3.0 scripts go
nuts with:

[Fri May 14 08:24:14 2010] [error] [client 10.1.250.91] PHP Fatal error:
Cannot use object of type DB_Error as array in
/var/www/html/aastra/include/AastraAsterisk.php on line 1069
[Fri May 14 08:24:14 2010] [error] [client 10.1.250.105] PHP Fatal error:
Cannot use object of type DB_Error as array in
/var/www/html/aastra/include/AastraAsterisk.php on line 1069

I have the exact problem as Atcom Alberta. When Accessing voicemail you can not take the phone off speaker.

Phone Model 35i firmware 2.6.0.66
Trixbox Version: 2.6.2.3
FreePBX Version: 2.5.1.5
FreePBX Mode: deviceanduser
USEDEVSTATE: true

startup.php does the right but apply_prf has a problem with some special characters.

the sip secret is: aSking?28 but app_prf wrote out: aSking\?28

Have you tried the scripts with trixbox 2.8.0.4 yet?

Yes we succesfully tested Beta 4 with Trixbox CE 2.8.0.4.
Stay tuned Beta 4 is on its way.

Regards

1. 9143i, 57i, 6739i (tested on these, maybe others)
2. N/A (asterisk 1.6.2.7)
3. 2.7
4. deviceanduser
5. USEDEVSTATE activated

I think the logic got flipped around between the !'s and the or. With the change below dnd.php actually works(*). The display will show "DND activated" and the status is updated in astdb. Without the change below the script is ineffectual.

--- dnd.php.orig	2010-05-26 23:09:53.000000000 -0500
+++ dnd.php	2010-05-31 17:22:55.000000000 -0500
@@ -80,7 +80,7 @@ switch($action)
 		$object = new AastraIPPhoneExecute();
 
 		# No external sync
-		if((!$AA_FREEPBX_USEDEVSTATE) or (!Aastra_is_sip_notify_supported()))
+		if(($AA_FREEPBX_USEDEVSTATE) or (Aastra_is_sip_notify_supported()))
 			{
 			# Update via the "check" mechanism
 			$object->addEntry($XML_SERVER.'&action=check');

Also, as we have lots of queue users and for those others, would a default behavior of this be welcome?

--- dnd.php.orig	2010-05-31 17:19:32.000000000 -0500
+++ dndqueue.php	2010-05-24 09:38:36.000000000 -0500
@@ -75,18 +75,24 @@ switch($action)
 		# Change DND status
 		$dnd=Aastra_manage_dnd_Asterisk($user,'change');
 
+		if ($dnd) Aastra_queue_pause_Asterisk($user,'','true');
+		else Aastra_queue_pause_Asterisk($user,'','false');
+
 		# Prepare display update
 		require_once('AastraIPPhoneExecute.class.php');
 		$object = new AastraIPPhoneExecute();

This works well in our environment.

* - With either change, the light never lights though. The dnd key isn't stored in the cache and the logic to light $key around line 130 always fails as $key is ''. It appears that dnd.php is never called during sync.php or stored during startup.php. (Of the phones I have available, only the 6731i lights the LED.)

The MAC .cfg is built with (on the 43i and 57i/39i phones respectively):

prgkey2 type: xml
prgkey2 value: http://$$AA_XML_SERVER_AA$$/$$AA_XMLDIRECTORY_AA$$/asterisk/dnd.php?user=$$SIPUSERNAME$$

softkey1 type: xml
softkey1 label:DND
softkey1 value: http://$$AA_XML_SERVER_AA$$/$$AA_XMLDIRECTORY_AA$$/asterisk/dnd.php?user=$$SIPUSERNAME$$
softkey1 line: 1

I think I solved my voicemail audio problem from a post in another forum. I upgraded the 57i firmware to 2.6 and the visual voicemail app seems to work better. I can now pickup the handset during playback and the audio redirects from the speaker to the handset (as it should).

In apply_prf there's this line:

if($fmode=='1') $array_profile=Aastra_readCFGfile('../asterisk/'.$profile.'-user.prf', '#', ':');
else $array_profile=Aastra_readCFGfile('../asterisk/'.$profile.'-device-nouser.prf', '#', ':');

Why if I'm in deviceanduser mode will it always only use the 'nouser' profile? Shouldn't that really be -device-user.prf instead? If this were the case, it would miss the Core values from the device-nouser.prf file where I have things like the vlan configuration.

What am I missing?

Shouldn't the processing be something like:
device-nouser.prf Core
device-user.prf Common (unless key is defined in nouser Core)
device-user.prf Model/Template (unless key is defined in nouser Core)

It seems that startup.php and sync.php does this differently. Neither agrees with how apply_prf does it. Maybe all the create_mac should be abstracted out each of those files and and put in a single include. That single implementation could then ensure consistent processing.

NB: I haven't followed the flow if FPBX is in 'extensions' mode.

Hi Peter,

What you need to understand about the 2.3.0 version of the scripts is that we made a major change in the way we synchronize the LED for DND, CFWD... Now the update is made with the aastra-daemon1 daemon which listens to Asterisk manager events when the DND is toggled which allows us to have synchronization when a user toggles DND by dialing *76. This is why in the code we check if the feature is supported (USEDEVSTATE and custom SIP notify supported), if supported changing the DND will generate a manager event which will update the DND so no need to do a local LED/idlescreen message update, we kept the local mechanism for "old" phones or if USEDEVSTATE is not enabled.
So in one word, the logic is not reversed, it should work perfectly... Maybe you should look if your aastra-daemon1 is running, also make sure that you use the user_login_out.agi we make available to login/out the users. Maybe you should also look if the DND event is properly generated by Asterisk and handled by aastra-daemon1.

When you say that the DND key is not stored in the cache make sure that you are looking at the DEVICE.context file not the one for the user.

We liked the idea of pausing/unpausing the ACD queues when toggling the DND, that makes a lot of sense, so we have added it in Beta5 with a configuration parameter to enable/disable it, that is definitely a great feature.

Also I was curious, why are you using the deviceanduser mode, now the login/logout does not need a reboot anymore a lot of users have switched back to extensions as the other mode has some serious issues when used for call center agents. We also know that this mode might not be supported any longer by freePBX.

We just tested a configuration like yours and everything works fine, so please check the various things we pointed.

Regards

Peter,

What you are missing is that in "deviceanduser" mode apply_prf and startup.php are only taking care of the device configuration not the user because the user configuration is updated when the user logs in.

This is why we only need xxx-nouser.prf, only the device configuration is updated. The "true" user login is done in sync.php when the phone registers or when it receives a SIP Notify.

Hope this helps.

Regards

I think I may have sifted through the DND light issue. Rather than change the dnd.php script to add the pause hooks for the queue members I copied it to dndqueue.php and used that script. The sync.php:425 (and key.php:210) app no longer matches. The value gets set in ASTDB, but the phone doesn't reflect the change. I should have used queuednd.php and it would have been fine. By not having this match, the key was never noted as being the DND key.

We use the deviceanduser as most our users have their desk phone but also have a softphones installed as part of our DR (Disaster Recovery) plan. In extensions mode we'd have to have not only the extra extensions but a follow-me configuration for each user that they could mess up via the recordings GUI. Having the devices (softphones, SIP clients on mobile phones and web apps) just seems more elegant.

Thanks!

Beta 4
◦6757i firmware 2.5.2.2002
◦Trixbox 2.8.0.3
◦USEDEVSTATE is activated

Hi

Issue related to presence status

When I switch the status to away the phone hang for 20 sec

Question related to directory app

I would like to know if the status (like idle,ringing and busy) is refreshed automatically because the only way to update the status is to press any button in the directory app

otherwise beta4 seem very stable

thank you

I am now using 2.8.4 and xml-scripts beta 4. I also upgraded to the newest firmware avail from aastra for a 57iCT. Myself and 3 55i's are having the same issue with the follow-me led. When activated the light will not turn on immediately, if I let it sit for 10 minutes or so it will light up. When I deactivate it, it will stay on even though its deactivated and will sometimes turn off after 10 - 20 min or usually we have to do a phone reboot in order for the light to sync back up. DND seems to be working.

Thanks for all your hard work aastra1!

Beta 4
◦6757i firmware 2.5.2.2002
◦Trixbox 2.6.2.3
◦USEDEVSTATE is activated

When changing status in Presence application, after choosing the new status and pressing Select the sreen displays "Please Wait" for about 30 seconds followed by "Data Timeout". Despite the error Presence still seems to be fully operational, just a long delay and error msg when setting. If I press the "Presence" softkey while its displaying "Please Wait", the presence menu is displayed immediately and the change takes effect.

Any idea what the timeout issue is? Sounds like the same issue as maclord1.

I don't understand we cannot reproduce when we try, it works fine, anyway it seems to work. The phone will only reboot if applying the profile actually changes MAC.cfg, it MAC.cfg is the same there is no reboot.

Regards

Hello Plahpoy,

We perfectly reproduced your issues which comes from a typo in /var/www/html/aastra/include/AastraAsterisk.php in line 2553 (NOY_INUSE instead of NOT_INUSE)

foreach($devices as $device) Aastra_set_devstate_asterisk('Custom:FOLLOWME'.$device,'NOY_INUSE',$as);

must be replaced by

foreach($devices as $device) Aastra_set_devstate_asterisk('Custom:FOLLOWME'.$device,'NOT_INUSE',$as);

Just to be on the safe side, make sure that the FMFM state change works when you dial *21+Extension and also make sure that freePBX has properly setup the custom hints, on the asterisk console (example for extension 400)

*CLI>core show hints
     *21400@ext-findmefollow           : Custom:FOLLOWME400    State:InUse

Good catch!

Thanks for your help.

Regards

Aastra1:

# Update LED and idle screen
if($is_sip_notify and $AA_ISYMPHONY)

doesn't seem to work for the presence issue in trixbox 2.6.2.3. The modification to /var/www/html/aastra/asterisk/away.php seems to break the function altogether...

Aastra1 was missing the closing tag so the red highlight command was not working. I fixed this in the post.

Glad to hear that the workaround worked for you. There is no direct downside for this workaround in the short term, we have implemented an update based on user events in order to support iSymphony presence module that we developped with Schmooze because we needed to support an external update of the presence status so right now as the iSymphony module is not there is no need to have this mechanism in place, the LED/screen update can be performed locally.

So you are good but if one day you plan to implement iSymphony presence synchronization will definitely fail. This problem is common to both Trixbox 2.6 and 2.8 even worse with 2.8.

Regards

So I compiled on the devstate backport for asterisk 1.4, but it doent seem to change anything.
This is a different system:
trix 2.6
asterisk 1.4.32
freepbx 2.7
devstate enabled in amportal and backport installed
57i aastra firmware 2.6
xml beta5

Right now the following LED keys do light up and turn off when appropriate
Voicemail
Presence

But all the other keys do not turn on or off when pressing those buttons:
DND
CallFWD
FollowMe
Agent Login
Day/Night

If I press a button, then reboot the phone, then the led comes on, and if I disable the feature, the led will stay lit until another reboot.

Is there a recommendation as far as using trix 2.6 or 2.8 as to which version of asterisk works best with these scripts, I am hoping to do a full deployment with it this next week, but not if the leds dont work.

Hello jayhide,

With the XML scripts 2.3 this cannot work, either backport devstate (and make sure that it is loaded and working) or disable the function in amportal.conf (don't forget to restart asterisk and freePBX). As many people seem to have this kind of issue, we are working in beta6 to have an hybrid solution between a "local" update and an event based update for the LED/idle screen message.

Please read the documentation...

Here is what you have to do.
in the phone MAC.cfg located at /tftpbootassuming that 500 is the general mailbox

softkey1 type: xml
softkey1 label: "Genrl VM"
softkey1 value: http://192.168.200.18:80/aastra/asterisk/vmail.php?ext=$$SIPUSERNAME$$&user=500

then reboot the phone

When the phone registers, the MAC.cfg is parsed and the key is stored for the daemon. Just tried it it works like a charm. You can also modify the ".prf" template and perform an apply_prf to all the phones it would work too. What will not work is to do this update using the Web UI. Again this is detailed in the documentation.

Hope this helps.

aastra1

Hi jahyde,

I'm running Beta 5 on 1.6.2.x, FPBX 2.7 and devstate. The DND, CFWD and Follow-me work as expected on both 57i and 43i phones. Maybe it's something with devstate? Can you see if it sets the values with a 'database show' after hitting the buttons?

Hi jahyde,

If the LED update is not performed with USEDEVSTATE it is because for some reason aastra_daemon1 is not receiving the manager event it is expecting when a feature is activated either is not generated or it has a wrong format. If you want I can send you something that traces manager events and see what is generated when you press the DND key or press "*76".
Anyway Beta6 has a workaround for you. Will publish it today.

Regards

aastra1

I'm having the same issue as jahyde on trixbox 2.6.2.3 with 9480i phones and tried the:

if($AA_ASTERISK_VERSION=='1.6') $res=$as->Command('devstate change '.$device.' '.$state);
else
{
$res = $as->Command('core set global DEVSTATE('.$device.') '.$state);
$res = $as->Command('core set global DEVICE_STATE('.$device.') '.$state);
}

which didn't make any difference. I reverted /var/www/html/aastra/include/AastraAsterisk.php and changed USEDEVSTATE=no in amportal.conf and indications seem to be working correctly now.