Home » Forums » Vendor Forums - Certified » Aastra endpoints

Solved:Problem with 6739i, aastra scripts and 2.8.0.4

dudu_georgescu
Posts: 44
 Member Since:
2010-01-30
Submitted by dudu_georgescu on Sat, 05/14/2011 - 7:33am.

I have two trixbox systems (2.8.0.3 and 2.8.0.4) and two Aastra 6739i phones. I have paired them up in a one to one relationship (one aastra phone paired with one trixbox system). The 2.8.0.3 system works just fine, the 2.8.0.4 system does not.

1) I have enabled debugging and tracing on both systems in the server.conf file. On both trixboxes I am getting the following error in the *.debug file (/var/cache/aastra) each time I restart the systems:

08:04:39 AM /var/www/html/aastra/asterisk/aastra_daemon2 Unable to connect to manager localhost:5038 (111): Connection refused

This looks like somebody tries to establish a TCP socket, however the server is not listening on port 5038, so the connection is refused (TCP socket level api connect and accept). I have no clue how to address this though.

2) There is no tracing file on the 2.8.0.4 system.

On the 2.8.0.3 system I get a *.log file in /var/cache/aastra:

[trixbox1.localdomain aastra]# cat 05142011.log
09:43:09 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=notify
09:43:09 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=notify
09:56:40 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=register
09:56:40 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=register
09:56:40 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=register
09:56:41 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP cfwd_asterisk user=200, action=register, value=, type=, selection=
09:56:41 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP dnd_asterisk user=200, action=register, status=
09:56:41 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP follow_asterisk user=200, action=register, value=, selection=
09:56:41 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP away_asterisk user=200, action=register, state=, value1=
09:56:41 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP agent_asterisk agent=200, action=register, queue=, page=1
09:57:55 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=register
09:57:55 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=register
09:57:55 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP sync_asterisk user=200, action=register
09:57:55 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP cfwd_asterisk user=200, action=register, value=, type=, selection=
09:57:55 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP dnd_asterisk user=200, action=register, status=
09:57:56 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP away_asterisk user=200, action=register, state=, value1=
09:57:56 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP logout_asterisk user=200, password=, action=register
09:57:56 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP follow_asterisk user=200, action=register, value=, selection=
09:57:56 AM 192.168.1.112 Aastra6739i MAC:00-08-5D-13-D4-97 V:3.0.1.2015-SIP agent_asterisk agent=200, action=register, queue=, page=1

As I stated already, no tracing on the other box (2.8.0.4)

3) The check_install script produces identical results on both boxes:

----------------------- Package installation -----------------------
Package php-gd ............................................ Passed
Package php-ldap .......................................... Passed
Package avahi ............................................. Passed
No Package mDNSResponder .................................. Passed
No Package mDNSResponder-util ............................. Passed
Phone firmware package (2.6.0) ............................ Passed
Package aastra-xml-scripts ................................ Passed
Cache Directory (/var/cache/aastra/) ...................... Passed
TFTP Directory (/tftpboot) ................................ Passed
/tftpboot/aastra.cfg ...................................... Passed
php-agi connection ........................................ Passed
freePBX database connection ............................... Passed
------------------ Asterisk/freePBX Configuration ------------------
Asterisk version (1.6) .................................... Passed
Asterisk location set to /etc/asterisk/ ................... Passed
Asterisk spooler set to /var/spool/asterisk/ .............. Passed
Voicemail configuration ................................... Passed
USEDEVSTATE set to True ................................... Passed
Wideband Codec (g722) configuration ....................... WARNING
-> You may want to activate g722 in /etc/asterisk/sip_general_custom.conf or via the freePBX module
freePBX mode set to extensions ............................ Passed
3 extension(s) configured ................................. Passed
No meet-me room configured ................................ WARNING
-> Please configure meet-me rooms using freePBX
Parking extension configured (70) ......................... Passed
No Intercom prefix configured ............................. WARNING
-> Please configure Intercom prefix using freePBX
No day/night index configured ............................. WARNING
-> Please configure day/night index using freePBX if you plan to use this function
No ACD queue configured ................................... WARNING
-> Configure queues using freePBX interface
----------------- Aastra XML scripts Configuration -----------------
Debug mode activated ...................................... Passed
Trace mode activated ...................................... Passed
Language not forced ....................................... Passed
Asterisk SIP proxy forced to AA_PROXY_SERVER .............. Passed
Asterisk SIP registrar forced to AA_REGISTRAR_SERVER ...... Passed
Phone Signature check is enabled .......................... Passed
Self-configuration admin password not configured .......... WARNING
-> You may want to configure it in config/asterisk.conf
Self-configuration user password not configured ........... WARNING
-> You may want to configure it in config/asterisk.conf for users without VM
Logout password check is enabled .......................... Passed
Auto-Logout feature is enabled ............................ Passed
Auto-Logout idle screen message is enabled ................ Passed
DND pauses all ACD queues disabled ........................ Passed
Speed dial application configured ......................... Passed
Outgoing state display application configured ............. Passed
Outgoing external lookup application not configured ....... Passed
Date/Time format (US) ..................................... Passed
User asked for timezone (no) .............................. Passed
No hidden directory extension ............................. Passed
Local dial plan ........................................... Passed
Country code: 1
Long distance prefix: 1
International prefix: 011
No outbound prefix
No local prefix
Local extension length not set

Please help

‹ Echo with aastra phones 57i XML menus: "All Page" works but goes into Meet-me conference room menu? ›


dudu_georgescu
Posts: 44
 Member Since:
2010-01-30
Yep, as defined in
Sat, 05/14/2011 - 1:51pm

Yep, as defined in asm-generic/errno.h, 111 is

#define ECONNREFUSED 111 /* Connection refused */

So the manager is not listening on port 111 when the daemon tries to connect to it.

Investigating further.



dudu_georgescu
Posts: 44
 Member Since:
2010-01-30
Wow, just wow. Apparently
Sat, 05/14/2011 - 3:34pm

Wow, just wow. Apparently the phone, when initially booted the very first time, tries to discover an tftp server on the network. It assumes that the first one it sees is the right one for downloading everything (firmware, config files, etc.). Subsequent reboots won't try to rediscover the tftp server, you are stuck with the one from the initial reboot.

If it cannot download anything, the phone fails silently --> no debug options which you set (either on the phone, or on the trixbox server) will EVER tell you important stuff like "well, I cannot find config files, even though I tried, and by the way, the address at which I tried was this: 192.blah.blah.blah". In my opinion, that would be very valuable information for debugging, worth its weight in gold.

Long story short, I had one extra TFTP server turned on on the network (left over from server network provisioning), and guess what, the phone was discovering that one before the trix tftp server. Just lovely! And subsequently at each reboot, it was trying to download everything from the wrong TFTP server, download which, of course, was failing.

Solution: either disable the extra TFTP server(s) available on the network - temporarily - and thus allow the AastraIP phone to discover the "proper" TFTP server upon initial power-on, or select "use alternate tftp server" in the aastra phone web interface (configuration server tab), and set the proper coordinates to your trixbox machine.

This took me a day to figure this out because of the lack of debug information/documentation :(



SkykingOH
Posts: 9682
 Member Since:
2007-12-17
Wow just wow, you don't have a clue
Sat, 05/14/2011 - 8:45pm

The phone does not find tftp servers, this information is communicated to the phone via option 66 in the DHCP message. The phone does not in any way remember the setting.

If you browse to the "configuration server" page of the telephone you will see the IP address of the tftp server as configured from DHCP.

Please explain to me how the information presented is deficient. The administrators guide explains all of the boot server options in detail.

You can have 100 tftp servers on the network and the phone would not know about them.

Don't blame the product for your lack of understanding.

--

Scott

aka "Skyking"



dudu_georgescu
Posts: 44
 Member Since:
2010-01-30
Yep, you're right, of course
Sun, 05/15/2011 - 7:17am

Yep, you're right, of course I do not have a clue, I do not install phones for a living and I am learning as I go :) I was extremely furious yesterday, hence the message (for sure a bit harsh).

Nevertheless, imho, the information is deficient from the point of view of the tracing/debug log info. I am not seeing any debug/trace messages to help me debug situations such as the one described above, neither from the phone side, nor from the server side. And while on the server side I was able to code php myself (and thus modify the scripts), there was nothing I could do on the phone side ...

And yep, you are right in respect of the DNS passing over the TFTP server name. The old system was provisioned before I started using bootp (network install) for my network. The new system is (of course) provisioned after. The most important difference is the passing of the TFTP server name through DNS to the provisioning system, so that it knows from where to load the OS installer. As I can clearly see now, that does not bode at all well with trix and aastra phones :(



SkykingOH
Posts: 9682
 Member Since:
2007-12-17
Not a problem, none of this
Sun, 05/15/2011 - 8:24am

Not a problem, none of this personal for me.

SO what debug information do you think is deficient? The phone shows the boot server. The admin guide has booting flow charts.

You installed on a foreign network (phones should sit on their own VLAN) that was not configured for VoIP.

The Aastra scripts are plug and play, it's the easiest phone to configure. In the XML manual it clearly states that option 66 has to be passed to the phone.

Just pointing out the other side of the coin.

--

Scott

aka "Skyking"



Comment viewing options

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