New Aastra XML scripts for Trixbox CE

☺ ♪ ♫ ♫

WOOOOHOOOO!!!

♪ ♫ ♫ ☺

Just like Christmas.

not (yet) avalible for trixbox 2.2?

http://www.nsd.dk/?Support:Trixbox:Queuetoggle

this would be a nice app to add, although i cant get it to work anymore for some reason, has anyone used this on recent versions?

right - i have used it before, but on a new 2.6 system it dont work, just gives soemthing like page error on the phone.

i also wanted to do it like this:
http://xx.xx.xx.xx/queuetoggleaastra.php?agent=$$SIPUSERNAME$$&queue=xx

but neither way seem to work on this new system, are there any specific phpagi settings that requires? thanks Peter.

Working on resolving the dependencies for 2.2. none of them are in the repo.

libc.so.6
rtld
mpg123

(mDNS was in the repo)

so, where are these button templates coming from now? I see nothing is in aastra.cfg anymore, except the startup script.

I just set this up at home, and here's a couple of things I've noticed:

First, I can't say for sure if it was these scripts, but somehow the sticky bit got set on the voicemail extension directory and the INBOX for that extension, and group perms were removed. This make it impossible to retrieve messages from anywhere.

I'm pretty sure it's these scripts that caused the sticky bit issue, because I made another extension without hooking up a phone and I was able to leave and retrieve messages all I wanted.

Second, even after I fixed the permissions issue I can't use the voice mail xml button on my 480i I've got at home. I can see the message, but when I select "play" it just says "Loading Page..." for a minute or so, then times out. The only thing in the console when this happens are some login and log out messages for the management port.

I get this in /var/log/httpd/error_log:

[Fri Apr 11 21:15:56 2008] [error] [client 192.168.0.120] PHP Warning:  Invalid argument supplied for foreach() in /var/www/html/admin/functions.inc.php on line 83, referer: <a href="http://mediasrv/recordings/index.php" title="http://mediasrv/recordings/index.php">http://mediasrv/recordings/index.php</a>
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - Got event.. newchannel
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - No event handler for event 'newchannel'
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - Got event.. newcallerid
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - No event handler for event 'newcallerid'
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - Got event.. extensionstatus
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - No event handler for event 'extensionstatus'
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - Got event.. extensionstatus
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - No event handler for event 'extensionstatus'
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - Got event.. hangup
[Fri Apr 11 21:16:17 2008] [error] [client 192.168.0.108] Fri, 11 Apr 2008 21:16:17 -0500 - No event handler for event 'hangup'

And here's the access log:

192.168.0.108 - - [11/Apr/2008:21:29:10 -0500] "GET /aastra/asterisk/vmail.php?ext=501 HTTP/1.0" 200 322 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"
192.168.0.108 - - [11/Apr/2008:21:29:15 -0500] "GET /aastra/asterisk/vmail.php?ext=501&user=501 HTTP/1.0" 200 340 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"
192.168.0.108 - - [11/Apr/2008:21:29:20 -0500] "GET /aastra/asterisk/vmail.php?user=501&ext=501&pin=501 HTTP/1.0" 200 922 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"
192.168.0.108 - - [11/Apr/2008:21:29:25 -0500] "GET /aastra/asterisk/vmail.php?user=501&pin=501&ext=501&folder=INBOX&action=zoom&msg=0000-INBOX HTTP/1.0" 200 872 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"
192.168.0.108 - - [11/Apr/2008:21:29:28 -0500] "GET /aastra/asterisk/vmail.php?user=501&pin=501&ext=501&folder=INBOX&action=play&msg=0000-INBOX HTTP/1.0" 200 113 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"
192.168.0.108 - - [11/Apr/2008:21:29:59 -0500] "GET /aastra/asterisk/incoming.php?number=0000&name=VoiceMail&user=501 HTTP/1.0" 200 250 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"
192.168.0.108 - - [11/Apr/2008:21:29:59 -0500] "GET /aastra/asterisk//vmail.php?action=display&msg=0000-INBOX&user=501&pin=501&ext=501&folder=INBOX HTTP/1.0" 200 481 "-" "Aastra480i Cordless MAC:00-08-5D-18-46-42 V:1.4.2.3000-SIP"

Any ideas?

I auto provisioned the phone using the provided scripts. I'll double check them, though, I brought this phone from work, so there might be some left over local junk configs. Thanks for the tip.

The "park" button doesn't seem to work either.

I can park by transferring by hand, but not the park button. I can still retrieve the parked call with the xml parking app, but not actually park the call.

Update: I installed from a 2.6.0.7 CD and the xml voicemail issue is resolved. However, the park issue on the 57i still exists. Pressing the "park" key does nothing. Further, it's now happening on the 480i as well.

Edit: Sigh. My fault.

If you don't have a parking lot configured before you generate the configs using the Aastra scripts, then they don't know where to send the calls.

The park directive in the config was just set to "asterisk;" instead of, say, "asterisk;70" so it couldn't park the calls. Changing that in the configs fixed the issue.

Also, re-generating the configs after creating a parking lot works too.

You'll have to regenerate the configs. Once they're created the template (prf) file isn't read any more.

At the very least, you'll have to delete the MAC.cfg in /tftpboot, but you might also have to edit out the entry in /var/cache/aastra/startup_asterisk.cfg and maybe the extension.* files in /var/cache/aastra. I haven't (obviously) figured out what all is going on in these scripts yet.

There might be a "right" way to do this too that I don't know about.

I was wondering about the public button myself. I'll have to see if I can figure it out.

For the record, on my home machine I ended up wiping it out and installing 2.6.0.7 on it and the xml voice mail issue is gone. That was a huge pain in the ass, because I also use that box as my media server, and I have over a TB of movies and music and junk on it that all had to be moved around. Fun evening.

OK. Sounds like the Public button is a function built into the 480i CT. I don't normally use one (480i on my desk), but the desk I was sitting at has one. I just never noticed...

I have the .cfg files back to a manageable state at this point. Thanks again!

Anyone?

I have 57i's and have been using ethan's daynight XML script, but the problem is it does not update the other phones when the mode is changed, does the Aastra day night mode script address this? The whole reason for a script like this for me is to change my IVR when we close shop for the day/week. Does no good if it can only be seen on one phone, I need the mode to be visible within a few seconds/minutes on a dozen phones.

Cheers, Nathan

make sure debug and trace are off - turning them on screws up the auto setup

Did you really just use an archaic misogynistic term to describe a voice prompt, or am I misunderstanding this phrase?

Anyway, you haven't given enough information for anyone to help you. Here's a checklist, though:

1) are your phones set up to allow auto-answer?

2) is the paging module installed?

3) is the paging feature code enabled in general settings?

4) can you use the paging feature code to page (*80EXTNUM)?

5) what do your logs say when it fails?

I'm not sure where it is in the web interface, but the config file options are:

sip intercom line: 1
sip allow auto answer: 1

If you've set up a paging group you don't need the *80, you just dial the paging group number. If your phone responds to *80303 then dialing the paging group number should work.

As for the missed call thing, you've got two choices:

1) configure a button on the main page for "Callers List" if you haven't already. You can do something like:

topsoftkey6 type: callers
topsoftkey6 label: "Callers List"

Of course, you can use any button number you'd like, and label it however you'd like.

2) just turn off missed calls:

missed calls indicator disabled: 1

1) Delete or rename MAC.cfg
2) go to /var/cache/aastra
3) edit /var/cache/aastra/startup_asterisk.cfg and delete the section for that extension
4) delete any .context .key or .session files for that MAC and extension
5) re-provision the phone.

HTH.

Thanks Kodak :) Fixed

I want to explicitly thank you for not only following through on your promise of documentation, but on following through in a very professional manner.

A lot of companies would throw together some half-assed docs for a FOSS application, but you guys went above and beyond on this. Thanks a bunch.

I have the 9133i and once autodiscovery is complete and I have entered the extension and password, I get "NO SERVICE" on the phones. Any suggestions?

Just had a chance to set up a system with the new xml scripts...Amazing! Great work guys! After getting stuck in config file hell with both Cisco and Polycom, I can't imagine using any other device.

Thank you!

-THX2000

Looks like the aastra-xml-scripts version yum is handing out at the moment is the old 1.1.0-1 version. Is this since I am running 2.2.4 of trixbox?

Hay all

When I run setup-aastra-xml I get
-bash: setup-aastra-xml: command not found

Any ideas?

I was installing the package on a vmware 2.6 a couple of weeks ago and the install failed. This was becasue of a dependency on mpg123. The dependencies for that package weren't correct.

try installing esound...
yum install esound

and see if that works.

Cheers

Kieran

I installed script on 2.6.7 and have a problem. Phone starts, gives me an option to choose ext, time zone but never goes past it, it just will not reboot or create mac.cfg. What could be the problem....? where should I look for it?

Any chance yall are going to get these to work with trixbox Pro? The day/night button in general would be very cool for my Pro users.

check the following thread for a possible solution
http://trixbox.org/forums/vendor-moderated-forums/aastra-endpoint...

You should double check the permissions of the /tftpboot directory on Asterisk, at a guess the config script is failing to write the new .cfg file into the directory.

1) the owner of all the files in /tftpboot should all be asterisk.asterisk. Do:

chown asterisk.asterisk /tftpboot/*

2) the files in /var/cache/aastra won't be created until you successfully register a phone, then some stuff will show up in there. You haven't successfully registered a phone yet, I don't think.

I think you'll be OK after you change the permissions in /tftpboot.

Oh, also, if you already have a MAC.cfg corresponding to the Aastra phones you are trying to configure in /tftpboot, then make sure you move them or delete them.

Checked the owner and permissions to the \tftpboot directory. It is correct as Asterisk the owner and rwx on everything.

Also removed aastra rpm's as per next post and then rebooted and reinstalled.
I also reset to factory defaults.
Its worse now, it never reboots after entering the timezone info.
The fact that it loads the startup xml script and verifies extension and password correctly means there is dialogue between Trixbox and the phone and also the extension number and password are correct etc.

Niot sure what to do next except try and copy a working system

I have this working on a from scratch FreePBX system so you don't need Trixbox to install this. Should work on any distribution.

http://www.powerpbx.org/content/aastra-xml-scripts-part-ii-autopr...

I installed the AASTRA XML Scripts via the package manager and it installed perfectly. However now when I go to the console and type setup-aastra-xml I get the message 'command not found'. What did I do wrong???

Thanks!

Dean
Anaheim, CA

I am using the Aasta 57i's - brilliant phone with the Asstra scripts.

I now am tring to get the paging feature working- intercom works well.

I assume paging is a one to many one way intercom - and have a page group setup with the extensions setup.

This deos not work ( Alison tells me that the feature is not setup) Dialling *80202 (where 202 is the paging group number) also does not work.

Can someone tell please - how to do a page? It could easily be me not understand how it s supposed to work.