Aastra XML scripts 2.3.0 Beta

[vcallaway]

Interesting.

I went in and added those lines in the section: from-internal-custom and the vmail extention started working.

Looking at that section it is where all the nerd vittles goodies are setup.

 

[edisoninfo]

Interesting.

I went in and added those lines in the section: from-internal-custom and the vmail extention started working.

Looking at that section it is where all the nerd vittles goodies are setup.

Ha! I have a habit of making things much harder than they need to be. I'll try that also. thanks!

 

[ErikU]

Is there any way to get these scripts to look at without installing?

 

[aastra1]

Open the RPM

Is there any way to get these scripts to look at without installing?

Hi there,

We provide both the .rpm and the .src.rpm at http://65.205.71.13/2.3.0 just extract the files using the rpm2cpio command.

Regards

aastra1

 

[edisoninfo]

Where are the 57i screen messages stored? The DND key does not work and now the phone shows 'DND Activated' and I can not get rid of it. I have rebooted the phone and still the message shows. Help!!

 

[briankelly63]

Have you tried *79 from that phone? Aastra should track that...

 

[edisoninfo]

Have you tried *79 from that phone? Aastra should track that...

Did not try that, but the calls are coming in fine. I think it is just an xml display issue. It thinks there should be the DND message on the screen when it should not.

 

[briankelly63]

aastra1...

As part of the scripts / phone firmware project I'd like to suggest a new soft-key definition... Blf/Intercom/xfer.

I would like a key that will function as a normal BLF/xfer but unlike that definition the new one would launch an Intercom call when pressed. There appears to be no way to do this right now without losing the BLF functionality. Speedial/xfer with a value of *80xxx works but no BLF.

Brian

 

[tradefair]

Hi Aastra,

When I logout of the 57i model phone and log back in, all LED do not work. Am using Beta 4. Using Asterisk 1.6.2.7

 

[kevinb]

DND Problem fixed for me at least

Hey all, I had the same issue where the DND button would not show anything changed on the display but DID toggle it in asterisk itself, as well as had it say DND activated on the screen with the LED on, but in reality was not activated. Very fristrating to say the least. Just installed beta5 of the scripts and that seems to have fixed that issue in case anyone wants to try it. I'm on asterisk 1.4.21 and the latest firmware on my 57i. HTH.

Kevin

 

[Socs28]

What would it take to get the Parking script to subscribe to specific parking lots? I am installing for my local city government and the departments don't want to see eachother's parked calls.

 

[edisoninfo]

I saw mention of a Beta 5 and sure enough it existed. But, it did not fix the DND issue for me on my 57i phones. The button still gets ignored. If I then reboot the phone, ding, is shows DND and you can not turn it off. Clients very upset with this not working....

 

[carlosmp]

Are you sure DND is off?

I had this situation with Beta 4, and database show did have DND on. Once it got turned on, it wouldn't toggle off. We issued a Database deltree DND and that took care of it... (usual cautions)

 

[totalimpact]

I too am having the LED issue, the leds for DND, CFWD, day / night and Agent login dont seem to update unless you reboot the phone.

The voicemail button works perfect, but a 2nd vmail button for a general mailbox does not light up at all (i am specifying the user=my-general-vmbox).

I am running it on 2 different systems, same behavior:

57i 2.6 firmware
xml-scripts 2.3 beta5
asterisk 1.4.32 and 1.4.33
freepbx 2.7
I tried both with and without devstate enabled.

I downgraded to beta4, and many leds starting working, only DND, CFWD, and Followme did not work.

Also what is the point of devstate on asterisk 1.4? It is not included in 1.4 , so if this is enabled in amportal.conf, does it affect anything? I have installed the 1.4 backports for funcdevstate, so in my case it would be accurate.

I loaded up a vanilla install (no nerd addons), just plain piaf 1.4 + asterisk 1.4.33 for testing this with funcdevstate and g722 compiled, so theres no custom contexts or other addons to confuse it.

 

[aastra1]

XML DND explained

Hi all,

It looks like there are a lot of issues regarding the DND (also CFWD/FMFM...) functions with the new XML 2.3.0 scripts so I wanted to take some times to explain how it used to work and how it works now with the 2.3.0 scripts as we introduced some significant changes.

Before 2.3.0
When a user was pressing the DND key, the XML script was toggling the DND value in Asterisk database and immediately "locally" updated the LED as well as the idle screen message (if DEVSTATE was configured, the script was also changing the Custom DND devstate in order to update the user BLF status). Also to make sure that the DND sate was somewhat synchronized, LED and idle screen were synchronized after a reboot and on a regular basis (every 30 minutes).
One of the problem with this method is that if the user was toggling DND using the feature code (*76) by default it would take up to 30 minutes to have the DND state synchronized.

With 2.3.0
We tried to improve this mechanism to provide a real time update of the DND status using the manager event generated when the CustomDND hint changes.

So

• If the phone supports SIP Notify (firmware 2.x and 3.x) and has DEVSTATE configured (and working).

When the user toggles DND with the XML scripts using the DND key on his phone, the script updates the asterisk database and sets the CustomDND DEVSTATE which triggers a manager event collected by aastra_daemon1, a SIP Notify event is then sent to the phone in order to update the DND, the local update mechanism is not used anymore.​

The benefit of doing it this way is that now the phone DND is updated each time it is changed within asterisk for instance when the user dials *76 or if an external application sets the DND status (as long as this application properly sets the Custom DND DEVSTATE).​

• If not the scripts act as in 2.2, local update with periodic synchronization.

How to troubleshoot
First of all you must make sure that if DEVSTATE is configured in freePBX it actually works properly (Asterisk 1.4). The script documentation explains how to check if Asterisk is compiled with DEVSTATE. Another way to check is to do a "core show hints" under the asterisk console to check if the CustomDND are there for each extension.
The other thing you need to check is that freePBX DND module is installed, also make sure that freePBX is at least 2.5, 2.6 being recommended.
What you can also do is dial "*76" from the phone and sees if the DND is toggled on the phone.
You must also make sure that aastra_daemon1 is running or the sync event will not be collected.
To debug you can also listen to manager event to see if an "extensionstatus" type event is generated with "ext-dnd-hints". I am not sure there are simple apps to do that, we will add a tiny tool to do it for you.

I hope this post will help you to understand better how DND works and where to look if it did not work. If DEVSTATE is not enabled in amportal.conf the LED state should be immediately updated. You must understand that we have a hard time to keep up with all the changes between all the products, we focused our tests with the latest stable versions: Asterisk 1.6 and freePBX 2.7 but just within Asterisk 1.6 there are some differences in the manager API commands and answers. We are trying to stay compatible with the maximum of versions but it is not easy.

Regards

aastra1

 

[edisoninfo]

FreePBX 2.7.x
Asterisk 1.4.30
Aastra 57i firmware 2.6.066


So far the only thing I can come up with is this error in the 'full' log file:

Function DEVSTATE not registered

in the 'full' logs. The 'core show hints' command shows:

                  *7641@ext-dnd-hints       : Custom:DEVDND41       State:Unavailable     Watchers  0
                 *76403@ext-dnd-hints       : Custom:DEVDND403      State:Unavailable     Watchers  0
                 *76402@ext-dnd-hints       : Custom:DEVDND402      State:Unavailable     Watchers  0
                 *76401@ext-dnd-hints       : Custom:DEVDND401      State:Unavailable     Watchers  0
                  *7640@ext-dnd-hints       : Custom:DEVDND40       State:Unavailable     Watchers  0
                  *7631@ext-dnd-hints       : Custom:DEVDND31       State:Unavailable     Watchers  0
                  *7630@ext-dnd-hints       : Custom:DEVDND30       State:Unavailable     Watchers  0
                  *7628@ext-dnd-hints       : Custom:DEVDND28       State:Unavailable     Watchers  0
                  *7627@ext-dnd-hints       : Custom:DEVDND27       State:Unavailable     Watchers  0
                  *7625@ext-dnd-hints       : Custom:DEVDND25       State:Unavailable     Watchers  0
                  *7624@ext-dnd-hints       : Custom:DEVDND24       State:Unavailable     Watchers  0
                  *7623@ext-dnd-hints       : Custom:DEVDND23       State:Unavailable     Watchers  0
                  *7622@ext-dnd-hints       : Custom:DEVDND22       State:Unavailable     Watchers  0
                  *7621@ext-dnd-hints       : Custom:DEVDND21       State:Unavailable     Watchers  0
                  *7620@ext-dnd-hints       : Custom:DEVDND20       State:Unavailable     Watchers  0

root@pbx:/etc/asterisk $ grep DEVSTATE *
extensions_additional.conf:CFDEVSTATE = TRUE
extensions_additional.conf:FMDEVSTATE = TRUE
extensions_additional.conf:DNDDEVSTATE = TRUE

I checked the amportal.conf file and the USEDEVSTATE=true command is there and uncommented.

From the CLI> core show function DEVSTATE says there is not function registered.

 

[aastra1]

RE: totalimpact

I too am having the LED issue, the leds for DND, CFWD, day / night and Agent login dont seem to update unless you reboot the phone.

Please have a look at the post I just made explaining how the DND works.

The voicemail button works perfect, but a 2nd vmail button for a general mailbox does not light up at all (i am specifying the user=my-general-vmbox).

How did you change the phone configuration to add the general vm box? If you used the Web UI to do it, it will not be taken into account by the scripts. As explained in the script documentation, you either need to change the profile used by the phone then logout/login, add an entry in custom-user.prf then logout/login or modify the phone MAC.cfg and reboot the phone.
To troubleshoot and check what the script is using.
300 is the phone extension and 999 is the general mailbox (the vmail keys are respectively softkey4 and softkey5), on the console logged as root

#/var/www/html/aastra/utilities/read_context 300 vmail
Application vmail
Array
(
    [300] => Array
        (
            [key] => softkey4
            [label] => Voice Mail
        )
    [999] => Array
        (
            [key] => softkey5
            [label] => General
        )
)
#/var/www/html/aastra/utilities/read_context vmail
Application user
Array
(
    [999] => Array
        (
            [status] => on
            [count] => 0
            [msg] => 0
            [user] => Array
                (
                    [0] => 300
                )
        )
    [300] => Array
        (
            [status] => off
            [count] => 0
            [msg] => 0
            [user] => Array
                (
                    [0] => 300
                )
        )
)

The second command indicates that the vmbox 999 is monitored by the phone with extension 300 which also monitors its own VM box (300).
If this is not what you get from the commands that means that the phone configuration has not been parsed properly by the scripts which happens if you don't update the configuration as described earlier.

I am running it on 2 different systems, same behavior:

57i 2.6 firmware
xml-scripts 2.3 beta5
asterisk 1.4.32 and 1.4.33
freepbx 2.7
I tried both with and without devstate enabled.

I downgraded to beta4, and many leds starting working, only DND, CFWD, and Followme did not work.[/quote]
That I cannot believe, as explained in my previous post, if you disable USEDEVSTATE the LED will work immediately as the event mechanism is not used anymore. Just make sure to properly restart freePBX and Asterisk (amportal start) between the changes as well as restarting aastra_daemon1 and 2 (/etc/rc.d/init.d/aastra-daemon1 restart and /etc/rc.d/init.d/aastra-daemon2 restart).

Also what is the point of devstate on asterisk 1.4? It is not included in 1.4 , so if this is enabled in amportal.conf, does it affect anything? I have installed the 1.4 backports for funcdevstate, so in my case it would be accurate.

Some distros are providing Asterisk 1.4 compiled with the DEVSTATE back port so it make sense. If DEVSTATE is activated in amportal.conf it definitely has an impact as the scripts will work differently. So you have to make sure that if USEDEVSTATE is enabled in amportal.conf it actually works or the scripts will not work.

Hope this helps.

Regards

aastra1

 

[aastra1]

Re: edisoninfo

So far the only thing I can come up with is this error in the 'full' log file:

Function DEVSTATE not registered

Obviously FUNC DEVSTATE has not been compiled with your Asterisk 1.4. As I explained in previous posts, having DEVSTATE enabled in /etc/amportal.conf has a major impact on how the script will behave (no real impact on the freePBX side though).

So either you recompile Asterisk backporting the devstate code or you

1. disable USEDEVSTATE in /etc/amportal.conf
2. restart Asterisk/freePBX using the "amportal restart" command
3. go to freePBX Web interface and reload the configuration to properly change the dialplan
4. restart aastra_daemon1 and 2
5. "/etc/rc.d/init.d/aastra-daemon1 restart" and "/etc/rc.d/init.d/aastra-daemon2 restart"

Every should work fine after that.

in the 'full' logs. The 'core show hints' command shows:

                 *76403@ext-dnd-hints       : Custom:DEVDND403      State:Unavailable     Watchers  0
...

If DEVSTATE was working you should have (example for extension 403)

 *76403@ext-dnd-hints       : Custom:DEVDND403      State:Idle            Watchers  0
403@ext-local           : SIP/300&Custom:DND40  State:Idle            Watchers  0

I will modify the check_install to check if DEVSTATE is actually implemented when activated at the freePBX level.

Anyway do what I described in the first part of this post and your phones should work properly.

Regards

aastra1

 

[edisoninfo]

Thanks aastra1 ! Sorry for the noise. I guess I "assumed" incorrectly since the vars in amportal.conf where there and set by default, that the function was there also. I am compiling 1.4.33.1 now 'with' the func_devstate.c in place!

 

[Socs28]

I have done the core show function DEVICE_STATE and it is showing correctly, however when I do a core show hints it doesn't show the *76... entries. Any ideas? I have restarted the aastra daemons and everything else seems to be working.