Aastra XML scripts 2.3.0 Beta

[ghurty]

I updated to beta 6, but now the park button is missing from the bottom.

Any clue where it is?



Thanks

 

[aastra1]

Re: Cannot display

I was able to correct the display issue by reapplying the 2.6 firmware rpm and restarting my phones.

Hi there,

We have not been able to reproduce the issue in our lab. Usually a "Cannot display" indicates that the scripts are not properly answering to the HTTP GET performed by the phone, either invalid XML or script crash.

We have done some php fixes to remove some ogf the php warnings but again we could not reproduce. Also we don't understand why reinstalling 2.6.0 fixed the problem.

Mystery...

Regards
aastra1

 

[aastra1]

Re: Colman

Hi,

Bit of an Aastra XML noob, so apologies if the question is a bit obvious

I am planning to upgrade the XML scripts for a customer in the very near future. I'm comfortable with the process described above, but you don't say what the user will experience on the handset after the process is complete? Will the handset retain the existing login information or will they have to enter their ext & vmail pwd again? I'm presuming that the mac.cfg files will remain and that the phones will log in automatically, but I'd rather know for sure so that when I do the update remotely I can prepare the customer for any required actions on their part.

Thanks for your help,

Colman

If you upgrade from the previous script version, first make sure that the default profile we define fits your needs. Now when you will perform the "apply_prf -r ALL", all the (Aastra) phones MAC.cfg will be updated and a SIP Notify is sent to the phone to reboot it. On the user side there is nothing to do, that as long that the phone is registered at the time the SIP notify is sent.
You should try it on a VM if you are scared of the update, but again make sure that the .prf you are using is the one you want and if you have your own make sure that it has been updated with the latest changes, please refer to the documentation for all the changes.

Hope this helps.

Regards

aastra1

 

[aastra1]

Park Button

I updated to beta 6, but now the park button is missing from the bottom.

Any clue where it is?

Thanks

Hi there,

Since Beta4 (I think), we have made the Parking key being both the park and pickup key, this is why we implemented it on the top keys for the 55i and 57i. The other benefiot of doing this is that parking is now a blind transfer, no need to hang up once the key is pressed, the parking orbit is displayed on the phone.
You can come back to the previous configuration if you want to, again the default profile we provide is just an example of what you can do.

Regards

aastra1

 

[kevinb]

Script Issue

aastra1,
I upgraded to the latest firmware and b6 of the scripts. Completely uninstalled b5 like the instructions say. Under b5 the only problem I had was the DND problem like others, where the DND button and display state were never updated, however DND was toggled when you pressed the button. Well, b6 seems to have fixed that problem completely, at least for mo. However, now my call fwd does not function properly. After the upgrade my Call Fwd button on the phone (57i) came on and permanently stays lit and says CFWD activated on the screen. It is NOT actually activated and if I press the Call Fwd button it says on the Call forward for 701 then below it says Call Forward is currently deactivated and I have button options at the bottom for Acivate, My Numbers and Exit. Any idea why this is happening even thought it is telling me call fwd IS deactivated? I get inbound calls fine. Like I said, this is the first time I ever had this problem, after I installed b6. Thanks.

Kevin

 

[aastra1]

Re: Kevinb

aastra1,
I upgraded to the latest firmware and b6 of the scripts. Completely uninstalled b5 like the instructions say. Under b5 the only problem I had was the DND problem like others, where the DND button and display state were never updated, however DND was toggled when you pressed the button. Well, b6 seems to have fixed that problem completely, at least for mo. However, now my call fwd does not function properly. After the upgrade my Call Fwd button on the phone (57i) came on and permanently stays lit and says CFWD activated on the screen. It is NOT actually activated and if I press the Call Fwd button it says on the Call forward for 701 then below it says Call Forward is currently deactivated and I have button options at the bottom for Acivate, My Numbers and Exit. Any idea why this is happening even thought it is telling me call fwd IS deactivated? I get inbound calls fine. Like I said, this is the first time I ever had this problem, after I installed b6.

That is really weird indeed, have you tried to reboot the phone? Also I will need more details on your setup, which Asterisk version, which freePBX version, which freePBX mode, USEDEVSTATE enabled or not, phone firmware version... Anything will help us to reproduce and fix. Right now we have not been able to reproduce and the changes we have done for CFWD in Beta6 cannot explain this issue.

Regards

aastra1

 

[kevinb]

Update

aastra1,
Ok, here is the info you asked for.
Asterisk - 1.4.21
FreePBX - 2.8.0rc1.3
Firmware on 57i - 2.6.0.66

Now, I happened to find what's causing the problem by accident. I reset the phone to factory defaults to clear the config and restarted. It pulled the config from my pbx no problem, started up and the CFWD problem was gone! HOWEVER (always a damn gotcha), when I assigned a second line on the phone to register to my dev box (same asterisk and fpbx versions, but diff ext number) and restarted the phone the problem was back, exactly like I explained in my first post. To confirm I restarted the phone again, no change. Then I removed the reg to the dev box, restarted again, and voila, problem gone again. I tried this 3 times just to verify. Restarting the pbx makes no difference either. So it seems like the script is being weird when it is registered to more than one server. I don't remember this being a problem in the past and I normally have 2 lines registered to the different boxes. Any ideas? Has anyone else in the forum tried this, or can confirm I'm not the only one seeing this? Thanks.

Kevin

 

[aastra1]

Re: kevinb

aastra1,
Ok, here is the info you asked for.
Asterisk - 1.4.21
FreePBX - 2.8.0rc1.3
Firmware on 57i - 2.6.0.66

Now, I happened to find what's causing the problem by accident. I reset the phone to factory defaults to clear the config and restarted. It pulled the config from my pbx no problem, started up and the CFWD problem was gone! HOWEVER (always a damn gotcha), when I assigned a second line on the phone to register to my dev box (same asterisk and fpbx versions, but diff ext number) and restarted the phone the problem was back, exactly like I explained in my first post. To confirm I restarted the phone again, no change. Then I removed the reg to the dev box, restarted again, and voila, problem gone again. I tried this 3 times just to verify. Restarting the pbx makes no difference either. So it seems like the script is being weird when it is registered to more than one server. I don't remember this being a problem in the past and I normally have 2 lines registered to the different boxes. Any ideas? Has anyone else in the forum tried this, or can confirm I'm not the only one seeing this? Thanks.

Hello kevinb, you never mentioned that you had a second line configured on the phone and this is the origin of the problem. First of all the scripts have not been designed to handle multiple lines on the phone for many reasons. The main one is that the phone is parsing $$SIPUSERNAME$$ when the scripts are called which sends the focused line so if you are on line 2 and press the DND key, the scripts will try to set the DND on the second SIP line which might not even be on the same Asterisk server.

Anyway what is happening to you is that the scripts implement an action uri registered which is called the first time the SIP extension registers to the server. The script then synchronize the phone status (DND, CFWD, agent...). In your case it will be called twice, one for the regular extension and one for your second line. You are probably not lucky because your second extension even on another server matches an extension on your Asterisk server and this extension has probably the CFWD activated.

To confirm this, go to the second line (press the right arrow key), the phone should display L2 instead of L1. Then press the CFWD key, the script will probably say that it is activated...

So this is what you can do to solve your problem: in demo-user.prf change everywhere

# Action URI
action uri registered: http://$$AA_XML_SERVER_AA$$/$$AA_XMLDIRECTORY_AA$$/asterisk/sync.php?action=register&user=$$SIPUSERNAME$$

by

# Action URI
action uri registered: http://$$AA_XML_SERVER_AA$$/$$AA_XMLDIRECTORY_AA$$/asterisk/sync.php?action=register&user=[COLOR=red]$$AA_[/COLOR]SIPUSERNAME[COLOR=red]_AA[/COLOR]$$

and also

action uri poll:http://$$AA_XML_SERVER_AA$$/$$AA_XMLDIRECTORY_AA$$/asterisk/sync.php?action=check&user=$$SIPUSERNAME$$

by

action uri poll:http://$$AA_XML_SERVER_AA$$/$$AA_XMLDIRECTORY_AA$$/asterisk/sync.php?action=check&user=$$[COLOR=red]AA_[/COLOR]SIPUSERNAME[COLOR=red]_AA[/COLOR]$$

Doing this will replace the dynamic variable of the phone by the static value of the user extension. Then do an apply_prf -r ALL to update the phones.
One other way is to do the change in the phone MAC.cfg and replace $$SIPUSERNAME$$ by the regular extension number and reboot the phone.

Let us know if it works for you.

Regards

aastra1

 

[kevinb]

Thanks for the info aastra1. I understand the reasoning behind the scripts only working on one line. I wasn't looking to use them on the dev box, it was just a simple reg so I can do testing on it. If I recall correctly, in my old config I used the same ext. number on both pbx's so perhaps thats why I never say an error? Either way I'll try one of the changes you suggest. Like I said, I want the full functionality of the scripts on my prod box, so I don't want to hose that up. Worst case I can try digging out one of my old phones to use on the dev machine. Thanks for your help, and of course the great scripts. I love the 57i and these make it even better!

Kevin

 

[aastra1]

Re: kevinb

Thanks for the info aastra1. I understand the reasoning behind the scripts only working on one line. I wasn't looking to use them on the dev box, it was just a simple reg so I can do testing on it. If I recall correctly, in my old config I used the same ext. number on both pbx's so perhaps thats why I never say an error? Either way I'll try one of the changes you suggest. Like I said, I want the full functionality of the scripts on my prod box, so I don't want to hose that up. Worst case I can try digging out one of my old phones to use on the dev machine. Thanks for your help, and of course the great scripts. I love the 57i and these make it even better!

Exactly if the extension was the same on both server everything would work fine because in any case the scripts would use the same extension number.
The change in the config file will fix your problem, we will study a better solution in the next version of the scripts.

Thanks

aastra1

 

[kevinb]

I did it the easy way asstra1, just changed my ext to the same as on my prod box and it stopped. Thanks for all your help.

Kevin

 

[briankelly63]

aastra1,

Any chance these scripts could at some point include Aastra Mobile Client (AMC) functionality (like MX-One) so iphone's and or android phone could be used with Aastra's Mobile App and Asterisk-PIAF?

Brian

 

[aastra1]

Aastra Mobile Client

aastra1,
Any chance these scripts could at some point include Aastra Mobile Client (AMC) functionality (like MX-One) so iphone's and or android phone could be used with Aastra's Mobile App and Asterisk-PIAF?

Hi Brian,

Yes that would be a great add-on to the whole system but that would be some significant work for us. I have heard that this kind of feature is on its way... not from us but from a major player in the Asterisk/freePBX world. Not sure what is the exact game plan but I know it is coming.

Regards

aastra1

 

[donh]

mDNS to avahi?

Hi I have some 480i phones and am wondering what avahi is being used for. I guess from reading that it does not work on these older phones. Is it just the initial discovery? That works fine with dhcp option 66. Do mDNS and avahi provide other features?

The reason I ask is that the version of mDNSResonder in your ftp is causing dependency problems with the latest version of avahi from centos.

Thanks,
Don

PS: Are you still checking Elastix forums?

 

[aastra1]

Re: mDNSResponder vs avahi

Hi I have some 480i phones and am wondering what avahi is being used for. I guess from reading that it does not work on these older phones. Is it just the initial discovery? That works fine with dhcp option 66. Do mDNS and avahi provide other features?

The reason I ask is that the version of mDNSResonder in your ftp is causing dependency problems with the latest version of avahi from centos.

We now recommend avahi because avahi is a true standard CentOS package, the mDNSResponder packages have been customized... Avahi is solely used for the auto-discovery process using the very same Apple "Bonjour" protocol but unfortunately incompatible with the phones running 1.4.

So if you have DHCP 66 you don't need either of them (except we have made a dependency in the rpm), we added this auto-discovery mechanism because not everybody has a decent DHCP server and it does the job.

PS: Are you still checking Elastix forums?

Unfortunately the focus has been more on PIAF and another one starting with a T as we were in a beta phase for the scripts. It is a lot of work to monitor multple forums.

Regards

aastra1

 

[donh]

That's kind of what I thought. But you are right it will cause problems for old phones if you don't have a good dhcp server. Not sure if this would help make things more compatable for older phones or not. http://linux.die.net/man/8/avahi-dnsconfd my dhcp works fine. Maybe when things settle down you can look at it.

Thanks,
Don

 

[colman]

OK, carried out the upgrade and all the phones restarted correctly, and the CFWD & AWAY functionality has been restored.

Couple of issues:
1. Despite not being a device&user setup, the first soft key on the 6731i's is the login/logout function.
2. After a call finishes, the display reads 'Cannot display'. looking in the Apache error log I see "[Tue Jul 13 13:43:49 2010] [error] [client 192.168.0.63] PHP Fatal error: Call to a member function output() on a non-object in /var/www/html/aastra/asterisk/outgoing.php on line 301" Any ideas?

 

[aastra1]

Re: Colman

OK, carried out the upgrade and all the phones restarted correctly, and the CFWD & AWAY functionality has been restored.

Good

Couple of issues:
1. Despite not being a device&user setup, the first soft key on the 6731i's is the login/logout function.

This is not an issue, if you read the documentation you will understand that even in extensions mode the scripts provide a login/logout (hot desking) capability this is why you have a logout button in the profile. If you don;t want it just modify the default template (demo-user.prf) and replace the logout button with something else.

2. After a call finishes, the display reads 'Cannot display'. looking in the Apache error log I see "[Tue Jul 13 13:43:49 2010] [error] [client 192.168.0.63] PHP Fatal error: Call to a member function output() on a non-object in /var/www/html/aastra/asterisk/outgoing.php on line 301" Any ideas?

Feels like a bug but based on the trace involving outgoing.php the error should be when a phone dials out not when you hang up. Can you give us more details on your platform, Asterisk version, freePBX version... and also dos it happen for every call or just specific calls such as external calls, also have you enabled the external number lookup? Anything would help us to understand. Also we assume you are using Beta6 right?

Regards

aastra1

 

[aastra1]

Re: Don

That's kind of what I thought. But you are right it will cause problems for old phones if you don't have a good dhcp server. Not sure if this would help make things more compatable for older phones or not. http://linux.die.net/man/8/avahi-dnsconfd my dhcp works fine. Maybe when things settle down you can look at it.

We will have a look but as stated in the documentation the 2.3.0 scripts will be the last one to be compatible with the phones running 1.4.x, it is too much work for us to maintain the compatibility as we develop new features both in the scripts and in the phones.

aastra1

 

[colman]

Good


This is not an issue, if you read the documentation you will understand that even in extensions mode the scripts provide a login/logout (hot desking) capability this is why you have a logout button in the profile. If you don;t want it just modify the default template (demo-user.prf) and replace the logout button with something else.

Ah, OK. Was thrown by the change of button assignments.

Feels like a bug but based on the trace involving outgoing.php the error should be when a phone dials out not when you hang up. Can you give us more details on your platform, Asterisk version, freePBX version... and also dos it happen for every call or just specific calls such as external calls, also have you enabled the external number lookup? Anything would help us to understand. Also we assume you are using Beta6 right?

Definitely happens after every call hangup on every handset. All handsets are 6731i's with firmware 2.5.3.2002. The installation is Asterisk 1.4.31 with FreePBX Framework 2.5.1.1 Not touched external number lookup. And I am using Beta6, yes.

Thanks for your help.

Colman