Trouble with Aastra XML scripts for Trixbox CE 2.6

gardnersmith
Posts: 9
Member Since:
2007-11-24

I am running TB 2.6 CE in my lab. I followied the installation procedures for installing the new Aastra XML scripts and auto-discovery process. All appeared to install correctly with no issues or errors. When I connect an Aastra 480iCT to the network, I get a startup button on the screen, and then when pressed it takes me to the "Initial Startup" screen. After entering the extension, and vm password, entering the timezone, the phone stays in "Loading Page..." for about a minute or 2 and then goes back to the "startup" mode. It did not create a .cnf file in the tftp directory, as I understand the next process to be.

Anyone else seen this issue?

--

Gardner Smith



gardnersmith
Posts: 9
Member Since:
2007-11-24
Guess nobody else has seen

Guess nobody else has seen this. Is there an Aastra rep monitoring this forum?

Gardner Smith

--

Gardner Smith



igorek600
Posts: 63
Member Since:
2007-07-21
same here

I have the same issue, did you fined a way to fix it?



gardnersmith
Posts: 9
Member Since:
2007-11-24
Not yet. I did go from a

Not yet. I did go from a 2.4 installation to 2.6 via upgrade. I have decided to try and do a clean install of 2.6 and retry the process. I am wondering if the TB included aastra xml scripts are conflicting with the new Aastra provided xml scripts.

Gardner Smith

--

Gardner Smith



skykingoh
Posts: 1012
Member Since:
2007-12-17
Completely remove the Aastra

Completely remove the Aastra software and the Aastra XML scriptes with yum. Then reinstall the software and scripts. Run the setup script and you should be good.

Scott



igorek600
Posts: 63
Member Since:
2007-07-21
I did this and no go, still

I did this and no go, still the same problem, anything else could be done? Oh yeh it looks like xml scripts 1.1 could not be removed is there any other option to remove everything? like with use of samba and manually deleting folders?
Loading "installonlyn" plugin
Setting up Remove Process
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package aastra-ipphone.noarch 0:2.2.0-1 set to be erased
---> Package aastra-xml-scripts.noarch 0:1.1.0-1 set to be erased
---> Package aastra-xml-scripts.noarch 0:2.0.0-1 set to be erased
--> Running transaction check

Dependencies Resolved

Package Arch Version Repository Size

Removing:
aastra-ipphone noarch 2.2.0-1 installed 18 M
aastra-xml-scripts noarch 1.1.0-1 installed 292 k
aastra-xml-scripts noarch 2.0.0-1 installed 2.6 M

Transaction Summary

Install 0 Package(s)
Update 0 Package(s)
Remove 3 Package(s)

Downloading Packages:
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
rmdir: invalid option -- R
Try `rmdir --help' for more information.
error: %postun(aastra-xml-scripts-1.1.0-1.noarch) scriptlet failed, exit status 1

Removed: aastra-ipphone.noarch 0:2.2.0-1 aastra-xml-scripts.noarch 0:1.1.0-1 aastra-xml-scripts.noarch 0:2.0.0-1
Complete!



aastra2
Posts: 245
Member Since:
2006-10-05
If the xml package isn't

If the xml package isn't being removed correctly, you should be able to get round this problem by using rpm directly.

WARNING: the following is untested

As root type the following command:

rpm -e --noscripts aastra-xml-scripts-1.1.0-1

I'm not sure if that's the correct package name, but you can find that by running "rpm -qa" and greping for the the xml packages.

This will remove the 1.1.0 script package without running the post uninstall script, which is causing the problem. The uninstall script is just trying to remove the cache file, here is a corrected command (if you want to run it).

rm -rf /var/cache/aastra

--

----
Gareth

Firmware 1.4.2 and 2.2.1 Released - download from http://www.aastratelecom.com/



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.