Anyone know what this means? ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420

TravisWhidden
Posts: 95
Member Since:
2007-12-14

Apr 20 13:22:56 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:22:56 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
Apr 20 13:23:01 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:23:01 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
Apr 20 13:23:06 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:23:06 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
Apr 20 13:23:11 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:23:11 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
Apr 20 13:23:16 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:23:16 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
Apr 20 13:23:21 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:23:21 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
Apr 20 13:23:26 ERROR[17585] chan_woomera.c: cannot connect to {default} localhost/42420
Apr 20 13:23:26 NOTICE[17585] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...

I never saw this before.. just happened to log in to check our the server. I have not restarted it... just was kind of strange to see that notice over and over and over.

Any input would be apprecaited.

Trixbox Pro CCE -- Ill give you the ID via PM if needed.

--

Travis Whidden



Schwood
Posts: 478
Member Since:
2006-06-23
Is this a VoIP only system?

Is this a VoIP only system? As in, is there no Sangoma card installed?

If that is the case and you simply want the errors to stop, you should be able to do:

asterisk -r
unload chan_woomera.so

Alternatively, you can try restarting Asterisk (when no one is on the phone) with a 'service asterisk restart' or simply type 'reboot' and reboot the box.

All of these commands are done as root from SSH.

--

Chris Sherwood
FtOCC Admin and Tech Certified
Fonality Sales Engineer



TravisWhidden
Posts: 95
Member Since:
2007-12-14
Yea, I tried that -- and

Yea, I tried that -- and also restarted the whole server and it didnt help.

that module isnt used by the TrixBox right? I have no addin cards.. its all SIP trunks.

Travis Whidden

--

Travis Whidden



Schwood
Posts: 478
Member Since:
2006-06-23
Correct...that module is not

Correct...that module is not in use by trixbox Pro in a VoIP only system.

--

Chris Sherwood
FtOCC Admin and Tech Certified
Fonality Sales Engineer



TravisWhidden
Posts: 95
Member Since:
2007-12-14
Ok, I gave this a try, but

Ok, I gave this a try, but it did not seem to help.

asterisk -r -x unload chan_woomera.so

Still shows that notice in the log

If you let it run for a long time, you see this error message in the /var/log/asterisk/messages file

Apr 21 16:23:10 VERBOSE[3311] logger.c: **[WOOMERA]** Receive Message: {default} [localhost/42420]
--------------------------------------------------------------------------------

Apr 21 16:23:10 VERBOSE[3311] logger.c: **[WOOMERA]** Receive Message: {default} [localhost/42420]
--------------------------------------------------------------------------------

Restarting asterisk put is back to the original message I posted in post 1.

Any other ideas? our system seems to be running fine, I just dont like errors flooding my logs -- so it makes it harder to debug other problems.

--

Travis Whidden



Schwood
Posts: 478
Member Since:
2006-06-23
Hi Travis, Check out this

Hi Travis,

Check out this thread: http://www.trixbox.org/forums/vendor-forums-certified/sangoma/uni...

Add the 'noload' line to your /etc/asterisk/modules.conf file and then do 'service asterisk restart' and let me know if that works.

--

Chris Sherwood
FtOCC Admin and Tech Certified
Fonality Sales Engineer



TravisWhidden
Posts: 95
Member Since:
2007-12-14
Tried this.. and it still

Tried this.. and it still doesnt work.

At the bottom of the config:

[global]
chan_modem.so=yes
noload => chan_woomera.so

Still throw this 5 second retry over and over.

--

Travis Whidden



TravisWhidden
Posts: 95
Member Since:
2007-12-14
Ok.. I renamed

Ok.. I renamed chan_woomera.so to chan_woomera.so-old in the modules directory -- so far, that looks like it fixed it. dont know why the noload didnt work. Maybe it was being loaded in a different location???

--

Travis Whidden



repask
Posts: 2
Member Since:
2009-11-04
logs getting full

Hi,
I know it been a while from last reply in this thread but I got the same problem with system currently running.
My /var/log/asterisk/full is getting full of
[Nov 4 18:48:25] NOTICE[25198] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
[Nov 4 18:48:30] VERBOSE[26445] logger.c: == Connect attempt from '127.0.0.1' unable to authenticate
[Nov 4 18:48:30] ERROR[25198] chan_woomera.c: cannot connect to {default} localhost/42420
[Nov 4 18:48:30] NOTICE[25198] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
[Nov 4 18:48:35] VERBOSE[26446] logger.c: == Connect attempt from '127.0.0.1' unable to authenticate
[Nov 4 18:48:35] ERROR[25198] chan_woomera.c: cannot connect to {default} localhost/42420
[Nov 4 18:48:35] NOTICE[25198] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
[Nov 4 18:48:40] VERBOSE[26447] logger.c: == Connect attempt from '127.0.0.1' unable to authenticate
[Nov 4 18:48:40] ERROR[25198] chan_woomera.c: cannot connect to {default} localhost/42420
[Nov 4 18:48:40] NOTICE[25198] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...
[Nov 4 18:48:45] VERBOSE[26449] logger.c: == Connect attempt from '127.0.0.1' unable to authenticate
[Nov 4 18:48:45] ERROR[25198] chan_woomera.c: cannot connect to {default} localhost/42420
[Nov 4 18:48:45] NOTICE[25198] chan_woomera.c: Woomera {default} Cannot Reconnect! retry in 5 seconds...

Our system has Trixbox 2.6.2.3 ISO installed and using SIP service for inbound calls and PRI ISDN30 with AFT A101 Single port E1 Card without echo cancellation.
This system is running already for 2 months and didnt have this problem until last 2 weeks. We didnt change anything on it from the initial setup and it just started to happen.
As its mentioned here the workaround would be to disable the woomera channel but as we are using Sangoma T1 card I'm not sure if I can disable it without breaking up the outbound calls. Before we had it setup with inbound and outbound going through A101 card but when the first 5 second reconnection started to happen we changed over at least Inbound to SIP (before was our fail over destination).
I guess that woomera is used only by BRI card (examle A500) but would be nice to know why its actually happening and why it started after couple of weeks. Also if its the problem with disabling the woomera channel do I have to disable it with every future installation of Trixbox ISO which will be using Sangoma E1 card and not BRI? I just want to avoid making the same mistake in future installations.

Best regards,

Patrik Resetka



Schwood
Posts: 478
Member Since:
2006-06-23
Hi Patrik, Your best bet is

Hi Patrik,

Your best bet is to call into Support and open up a ticket. If you don't have a Support contract, you should wait until after hours and try disabling the module and then test functionality. If it works, then you're all set. If it breaks your A101, then re-enable the module.

Thanks,

--

Chris Sherwood
FtOCC Admin and Tech Certified
Fonality Sales Engineer



andrewvanh
Posts: 16
Member Since:
2009-01-21
Modules not Global

noload => chan_woomera.so

That command goes under the modules section and not global.



Comment viewing options

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