New Aastra XML scripts 2.2.0 for PIAF

[yesmat]

Sorry ignore my question. I downloaded the pdf and have all the info.
Thanks

 

[n9yty]

Greetings!

I am new to Asterisk and PBX In A Flash.

Are these scripts preferred over the ones linked to and gone over in the two posts on this site about setting up the AAstra 57i phones?

I have set these new scripts up, but just wanted to be sure they weren't going to cause problems by being used in lieu of the ones written up about.

Also, even though I had selected (I thought) "extension" mode, the phone asked me to log in the first time, which it had not done with the previous version of the scripts. However, after several power-cycles I have not been asked to log in again.

Also, when I select "Services" and then "WebApps", I get a message that the myAastra service is no longer available. I did visit the web site and see that. Will a future version of these scripts remove that or update it to point to somewhere else?

Thanks for all the great work, and for sharing it with us!

 

[aastra1]

Two different things

Hi n9yty,

I understand that you are confused between the XML scripts for PBX in a Flash and the hosted XML scripts a.k.a myAastra.com.
These are 2 complete different things.

XML Scripts for PBX in a Flash
These are XML scripts designed for Aastra SIP phones connected to a PBX in a Flash server bringing new phone features such as self-configuration, DND, Call Forward, Visual voice mail... These scripts are installed on the PBX in a Flash Server. When installed, if you plug an Aastra SIP phone on your network, the phone will automatically 'discover' the server and you will be prompted for a username and password. You must have configured an extension using freePBX with a voicemail (the password is the VM password). After reboot, the phone is fully configured with all the features, check out the documentation for more details.

MyAastra.com
This was an experimentation from Aastra to provide hosted XML services to unify the desktop and the SIP phones connected to any platform. You needed to register your phones with an account to share features such as RSS feeds and contacts.
Aastra has decided to stop this experimentation. Currently the phones are still pointing to the service (Webapps key) but this has been removed in the latest firmware 2.5.0.

We are preparing the next version of the XML scripts for PIAF (2.2.1) bringing more features.

Stay tuned.

Regards

Aastra1

 

[rushter]

I am glad that n9tyt asked the question that he did but I am not sure that it was completely answered. I am getting ready to take the plunge for the 4 aastra's that we have here and need a little more info about these scripts. Everything that I have read so fair makes me want to install these right away but I have my aastras running with the buttons configured the way we want etc. But since my last re-install of the whole PiAF system two weeks ago I think that one of my aastra's is actually causing a bunch of problems. (see my 'Weird Happenings' post) The question is this - after installing these scripts and updating the firmware, etc - what effects will it have on the phones already installed? Will it basically wipe what is on them now? Will I have to 're-register' them with PiAF? I do not need logins and all of our phones are just extensions - which way should this be installed? Sorry for what some may consider silly questions I am still a noob on this and love this forum and the whole pbx idea - just need a bit of guidance every now and then.

 

[foneman]

Great Scripts

These scripts are AWESOME and if you take the time and realy read into the nut and bolts, they are invaluable. Especially the demo-user.prf files. I use them exclusively now for deployment of our systems and have sample .prf files for different applications. FIRST THING TO DO IS FIND OUT WHAT BUTTONS YOU WANT. Then, change the .prf file accordingly and all your Aastra phones will come up.
It is a handy tool especially for larger deployments. That being said, if you have someone that needs a different button, you can still change the MAC.cfg file for that particular phone.
Great job on Aastra1's part for these.

 

[BigSeph]

Great job on the scripts, I have a question though:

I'll be looking through the logs on my end, but after upgrading the aastra scripts to this version I can no longer make local phone calls. I require users to enter 1-25x-xxx-xxxx (area code starts with 25) to make local calls. Is there something hardcoded in these scripts that's catching the phone after dialing the 125?

Thanks and I have to say that for a call center these scripts simplify things a ton for agents.

 

[BigSeph]

So I can call numbers that are in my area code that don't involve a "995"

996, 986, etc. work fine, but "995" is hanging. If I could call those numbers before the script upgrade, and can't since, I have no clue what could be causing it. Logs look normal. Sorry to hijack the thread, just trying to get this figured out. ^_^

**EDIT** I can call out to those numbers just fine using a SIP softphone (3CX/xLite) but not using an Aastra 57i with the latest firmware.

Also I don't see an "outgoing.php" in my var/www/html/aastra/ folder, I see an "incoming.php"

 

[rushter]

I hope someone can help on this one. Installed the scripts, was following all of the instructions and started with just one of my Aastra 57i's. Got the phone to where it says to login - logged in using the extension and the vm pw and it comes up and says unable to connect to Asterisk Manager and I cannot get any further. I looked thru this whole thread and did all of the steps that others were considering - set the phone to factory defaults, made sure nothing was in the cache, I am pretty sure that it must be something else.

Any ideas?

 

[foneman]

Problems Continue

Well, I have been experiencing the same stuff that Rushter has and is keeps getting worse.
We have 6 55i phones with the 2.5 firmware and now, the phones go to NO SERVICE, then, they ring like crazy, lights light up and the only way to stop is to unplug the phones.
Do we have buggy 2.5 firmware?
Aastra1 please help.

 

[aastra1]

Manager connection problems

Hi Rushter,

I hope someone can help on this one. Installed the scripts, was following all of the instructions and started with just one of my Aastra 57i's. Got the phone to where it says to login - logged in using the extension and the vm pw and it comes up and says unable to connect to Asterisk Manager and I cannot get any further.

There are a couple of things you can do regarding the script connection.

In /etc/asterisk/manager.conf you should have something like this

[admin]
secret=amp111
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,command,agent,
userwrite = system,call,log,verbose,command,agent,user

And in /etc/amportal.conf something like this at the beginning of the file

# AMPMGRUSER: the user to access the Asterisk manager interface
AMPMGRUSER=admin
 
# AMPMGRPASS: the password for AMPMGRUSER
AMPMGRPASS=amp111

Both files must match.

The scripts are using 'localhost' for the server name and port 5038 to connect to the Asterisk Manager. Make sure that 'localhost' is a valid entry in the host files.

Another thing you can do is activate the debug mode to get some traces why the connection fails.
in /var/www/html/aastra/config/server.conf set DEBUG=1
Then generate a connection error. The traces should tell you what happened.

Hope this helps.

Regards

aastra1

 

[rushter]

Everything was as you said it was but I noticed one small thing and, being a newbie, did not know how to change it. I had two amportal.conf files one was amportal.conf and the other amportal.conf.org the difference being ownership the org one has asterisk:asterisk and the newer one is root:root - could this be the issue?

 

[aastra1]

Did you activate the debug traces as I explained in my previous answer? What do they say? The log file is located in /var/cache/aastra.

aastra1

 

[fishfilet]

I have just finished playing around with a Polycom 601 it was a great phone. Awesome qualitly in build, tactile feel and just about everything. That being said I purchased three 57i's and the work that Aastra has done here is simply amazing! I will be purchasing 30 more 57i's within the month!

I had a quick question, will the Meet-me function of the phone with these scripts work with the new Web Meet me? I think it is 3.0 or something. I just have the initial Meet-Me from the install but would like to upgrade. However I do not want to mess anything up!

 

[fishfilet]

Hello SShrivastava,

Here are some answers to your questions.

Some explanations about the variables used by the scripts

• ext is the phone extension used to play the message
• user is user voice mail username
• pin is the user voice mail password

This was designed to allow access to your VM from any phone.
So you must add
?ext=$$SIPUSERNAME$$&user=$$SIPUSERNAME$$&pin=XXXX
in the profile file.

I suppose that the error message is displayed when you delete a long message while playing. I added this 'delete' key while playing because some users were asking for it...
Anyway there is a way to have delete stop the playback and delete the message, I will do it for the next version of the scripts but it will be available only on the phones running 2.x firmware (so not for 480i).

Hope this helps

Regards

aastra1

I am trying to get this to work as well. My line looks like this.

softkey3 value: http://192.168.0.100:80/aastra/asterisk/vmail.php?ext=$$SIPUSERNAME$$&user=$$SIPUSERNAME$$&pin=12345678

Note this is in my mac.cfg or should this go into the template. I assume the mac.cfg because this extension was already created and also if it is in the template then all users would need the same password and if they change it it would also break this feature.

When i hit the voice mail softkey i get "Authentication failed Wrong user and/or password. I have to set user=105 or whatever the extension is and then it works. I can do this I am just wondering why the directions above are not working for me. I assume I am doing something wrong.

 

[fishfilet]

So far I am very impressed with this but I have a couple of questions.

First our current phones show a directory of company extensions. This is similar to the pre configured directory. Then we each user may want to add phone numbers to a personal directory and this is also there under services. But we also have a directory that shows a list of common numbers like vendors, support agents and such that are set by an admin and show up on every phone. This was easy to do with the polycom each user had directory-xml and you could just put company contacts in the default 0000-directory.xml. How can I get this functionality on the 57i?

Second the preconfigured buttons are almost perfect for our aplication but the intercom seems lacking for instance when you hit intercom you then enter the extention and away you go. But what if you dont know the extention? When you use the directory and you get a list of extentions the bottom pane changes to show dial. It seems like it should also have an intercom button if you want to intercom the person instead of calling. Can anyone help me with setting this up?

 

[bbqsauce86]

So far I am very impressed with this Second the preconfigured buttons are almost perfect for our aplication but the intercom seems lacking for instance when you hit intercom you then enter the extention and away you go.

Are you talking about the Icom key? It's my understanding that it only works on the 57i as an intercom key between the base and cordless sets. If I'm wrong, I'd love someone to correct me.

I hate making misstatements.

 

[fishfilet]

Yes that is the key I am talking about. I am using two 57i's without the cordless sets. If you press icom you get a dial tone then you enter an extension and it intercoms that extension. In other words that extension auto answers the call on speaker phone so it is an intercom system. same as hitting *80 and the ext. example *80105 intercoms extention 105.

 

[solutions4smb]

Remote Handsets don't Startup

I forgot I had one remote (home office) handset and when it rebooted, it loaded new firmware, new config, just won't let me Startup.

What do I need to do to handle provisioning through NAT and a firewall (what ports)?

Is it possible?

Do I need to provision locally, then move to remote location?

Thanks. Love the Aastras, mainly because of the scripts.

 

[SShrivastava]

I get the same error when I make the recommended change, so for now I'm stuck with entering the VM password with each login.

I am trying to get this to work as well. My line looks like this.

softkey3 value: http://192.168.0.100:80/aastra/asterisk/vmail.php?ext=$$SIPUSERNAME$$&user=$$SIPUSERNAME$$&pin=12345678

Note this is in my mac.cfg or should this go into the template. I assume the mac.cfg because this extension was already created and also if it is in the template then all users would need the same password and if they change it it would also break this feature.

When i hit the voice mail softkey i get "Authentication failed Wrong user and/or password. I have to set user=105 or whatever the extension is and then it works. I can do this I am just wondering why the directions above are not working for me. I assume I am doing something wrong.

 

[tel0p]

softkey3 value: http://192.168.0.100:80/aastra/asterisk/vmail.php?ext=$$SIPUSERNAME$$&user=$$SIPUSERNAME$$ &pin=12345678

@Fishfilet: Why is there a space between $$SIPUSERNAME$$ and the &pin=12345678 ? Was this copy and pasted or maybe the forum?