Koozali.org: home of the SME Server

sip_reg_timeout

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #15 on: January 29, 2008, 09:27:34 PM »
Have you changed your router or router settings lately?
When you say Router, do you refer to the cable modem?
The answer is still No,  But..
we did have a suburb blackout a couple of weeks ago, and it took the ISP many hours to get back on the air.
So perhaps there is something at their end,  but I still don't understand why I get the same time out to my
internal network SPA-3102 trunk, and to the extensions.
I did also replace the wireless router, I'll swap the old one back today just to rul it out also.

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #16 on: January 29, 2008, 10:21:22 PM »
Well its not caused by my new wireless router,  which is only setup as an internal network Access point.
I am running on my old wireless router now, which is on the same subnet (no Nat involved)
and right now I am seeing..
Code: [Select]
[Jan 30 08:18:29] NOTICE[4671]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951901@sip.freshtel.net' timed out, trying again (Attempt #9)
[Jan 30 08:18:44] NOTICE[4671]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '61386835551@sip.pennytel.com' timed out, trying again (Attempt #8)
[Jan 30 08:18:59] NOTICE[4671]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87952609@sip.freshtel.net' timed out, trying again (Attempt #6)
l1nuxsvr*CLI> sip show peers
Name/username              Host            Dyn Nat ACL Port     Status
97951738/97951738          (Unspecified)    D          0        UNKNOWN
ft1738/87951738            202.86.50.100               5060     UNREACHABLE
pt5551/61386835551         203.166.6.160               5060     UNREACHABLE
09109431/09109431          125.213.160.81              5060     UNREACHABLE
5010/Study                 (Unspecified)    D          0        UNKNOWN
5009/Glen                  (Unspecified)    D   N      0        UNKNOWN
5008/HomePC                (Unspecified)    D          0        UNKNOWN
5007/Jo                    (Unspecified)    D   N      0        UNKNOWN
5005/Dani                  (Unspecified)    D          0        UNKNOWN
5004/Matt                  (Unspecified)    D          0        UNKNOWN
5000/homephone             (Unspecified)    D          0        UNKNOWN
11 sip peers [Monitored: 0 online, 11 offline Unmonitored: 0 online, 0 offline]
[Jan 30 08:19:14] NOTICE[4671]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951738@sip.freshtel.net' timed out, trying again (Attempt #9)

I might shut everything down, powered off, and bring all up clean again.
now my Internal DNS w2k3svr  and my sme server are both low on memory,  this couldnt be due to a lack of resource could it ?

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #17 on: January 30, 2008, 09:48:47 AM »
A complete shutdown / power off of all equipment, including Cable modem and did not help.

This leaves me with changes to sme  or a left over issue with the ISP.
I find the ISP hard to blame considering Asterisk is complaining about my internal extensions as well.
And I have no other issues (email,FTP,Web) with the ISP.

according to my yum.log ....
Code: [Select]
Jan 22 08:36:59 Updated: e2fsprogs.i386 1.35-12.11.el4_6.1
Jan 22 08:37:01 Updated: net-snmp-libs.i386 5.1.2-11.el4_6.11.2
Jan 22 08:37:04 Updated: perl-Net-DNS.i386 0.62-1.el4.rf
Jan 22 08:37:05 Updated: libxml2.i386 2.6.16-10.1
Jan 22 08:37:06 Updated: atrpms.noarch 71-1
Jan 22 08:37:09 Updated: net-snmp.i386 5.1.2-11.el4_6.11.2
Jan 22 08:37:10 Updated: rkhunter.noarch 1.3.0-4.el4.sme
Jan 22 08:37:12 Updated: smeserver-locale-it.noarch 1.2.0-33.el4.sme
Jan 22 08:37:16 Updated: e-smith-samba.noarch 1.14.1-3.el4.sme
Jan 22 08:37:17 Updated: smeserver-locale-es.noarch 1.2.0-33.el4.sme
Jan 22 08:37:17 Updated: perl-IO-Zlib.noarch 1.09-1.el4.rf
Jan 22 08:37:19 Updated: smolt.noarch 0.9.8.1-7.el4.sme
Jan 22 08:37:20 Updated: smeserver-locale-de.noarch 1.2.0-33.el4.sme
Jan 22 08:37:22 Installed: smeserver-yum.noarch 1.2.0-48.el4.sme
Jan 22 08:37:22 Updated: smeserver-locale-fr.noarch 1.2.0-33.el4.sme
Jan 22 08:37:23 Updated: smeserver-locale-sv.noarch 1.2.0-33.el4.sme
Jan 22 08:37:25 Updated: e-smith-nutUPS.noarch 1.2.0-17.el4.sme
Jan 22 08:37:25 Updated: smeserver-audittools.noarch 0.0.2-6.el4.sme
Jan 22 08:37:38 Updated: spamassassin.i386 3.2.4-46.el4
Jan 22 08:37:39 Updated: postgresql-libs.i386 7.4.19-1.el4_6.1
Jan 22 08:37:40 Updated: smeserver-support.noarch 1.6.0-43.el4.sme
Jan 22 08:37:41 Updated: net-snmp-utils.i386 5.1.2-11.el4_6.11.2
Jan 22 08:37:42 Updated: libxml2-python.i386 2.6.16-10.1
Jan 22 08:37:43 Updated: e-smith-viewlogfiles.noarch 1.8.0-7.el4.sme
Jan 22 08:37:49 Updated: tzdata.noarch 2007k-1.el4
Jan 22 08:37:50 Updated: e-smith-openssh.noarch 1.12.0-13.el4.sme
Jan 22 08:37:50 Updated: httpd-suexec.i386 2.0.52-38.ent.centos4.2
Jan 22 08:37:56 Updated: httpd.i386 2.0.52-38.ent.centos4.2
Jan 22 08:37:57 Updated: mod_ssl.i386 1:2.0.52-38.ent.centos4.2
Jan 22 08:38:04 Erased: check4updates
The date of Jan 22 would be roughly when I started having problems ..
(does asterisk keep a historic log somewhere so I can find problem start date ?)

Could any of the above updates have an affect on theses asterisk timeouts ?

Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: sip_reg_timeout
« Reply #18 on: January 30, 2008, 11:03:12 PM »
can you send a copy of sip.conf to us admin@selintra.com
are you running server-only or server-gateway

have you had any further local sip drop outs?

Best

S

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #19 on: January 30, 2008, 11:21:15 PM »
Thanks Jeff,
  sent... 
I run Server-gateway mode.

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #20 on: January 30, 2008, 11:48:23 PM »
sigh,
  yes  another hit  just now...
Code: [Select]
[Jan 31 09:44:51] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951901@sip.freshtel.net' timed out, trying again (Attempt #3)
[Jan 31 09:45:06] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951708@sip.freshtel.net' timed out, trying again (Attempt #3)
[Jan 31 09:45:21] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '61386835551@sip.pennytel.com' timed out, trying again (Attempt #2)
[Jan 31 09:45:36] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951738@sip.freshtel.net' timed out, trying again (Attempt #3)
[Jan 31 09:45:51] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '09109431@sip00.mynetfone.com.au' timed out, trying again (Attempt #4)
[Jan 31 09:46:06] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87950112@sip.freshtel.net' timed out, trying again (Attempt #4)
[Jan 31 09:46:21] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87952609@sip.freshtel.net' timed out, trying again (Attempt #4)
[Jan 31 09:46:36] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951901@sip.freshtel.net' timed out, trying again (Attempt #4)
[Jan 31 09:46:51] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '87951708@sip.freshtel.net' timed out, trying again (Attempt #4)
[Jan 31 09:47:06] NOTICE[4683]: chan_sip.c:7422 sip_reg_timeout:    -- Registration for '61386835551@sip.pennytel.com' timed out, trying again (Attempt #3)
l1nuxsvr*CLI> sip show peers
Name/username              Host            Dyn Nat ACL Port     Status
97951738/97951738          (Unspecified)    D          0        UNKNOWN
ft2609/87952609            202.86.50.100               5060     UNREACHABLE
ftel1901/87951901          202.86.50.100               5060     UNREACHABLE
ft1738/87951738            202.86.50.100               5060     UNREACHABLE
ft1708/87951708            202.86.50.100               5060     UNREACHABLE
ft0112/87950112            202.86.50.100               5060     UNREACHABLE
pt5551/61386835551         203.166.6.160               5060     UNREACHABLE
09109431/09109431          125.213.160.81              5060     UNREACHABLE
5010/Study                 (Unspecified)    D          0        UNKNOWN
5009/Glen                  (Unspecified)    D   N      0        UNKNOWN
5008/HomePC                (Unspecified)    D          0        UNKNOWN
5007/Jo                    (Unspecified)    D   N      0        UNKNOWN
5005/Dani                  (Unspecified)    D          0        UNKNOWN
5004/Matt                  (Unspecified)    D          0        UNKNOWN
5000/homephone             (Unspecified)    D          0        UNKNOWN
15 sip peers [Monitored: 0 online, 15 offline Unmonitored: 0 online, 0 offline]

I am getting no where with this

Offline william_syd

  • ****
  • 1,608
  • +0/-0
  • Nothing to see here.
    • http://www.magicwilly.info
Re: sip_reg_timeout
« Reply #21 on: January 31, 2008, 06:57:55 AM »
But since approx Mid January I have got this constantly,  and it does affect the Trunks.
I have had calls just stop,  mid call,  and my wife has now tried to make a call and got dead silence.

cat /var/log/yum/yum.log | grep Jan

Edit:

Opps.. didn't see a second page.
Regards,
William

IF I give advise.. It's only if it was me....

Offline arne

  • ****
  • 1,116
  • +0/-4
Re: sip_reg_timeout
« Reply #22 on: January 31, 2008, 10:31:08 PM »
db configuration show asterisk ?

When the sound stops at the start or in the middle of a speak this is typically traced down to be a firewall or a router problem.

Some routers do not have good properties for maintaining a datastream from a iptelephony call.

In question about firewalls and network technology there is normally answers like "will work" or "will not work". Ip telephony is actually the only firewalling/routing area I have looked into, where the anwer might be: "Might propably work most of the time, but not more than ten minutes." (Because it is a stream of udp packets.)

I think that this tread should contain a more detailed description of the network and which componenets that are used.
« Last Edit: January 31, 2008, 10:50:00 PM by arne »
......

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #23 on: January 31, 2008, 10:34:31 PM »
db configuration show asterisk ?
Quote
[root@l1nuxsvr /]# db configuration show asterisk
asterisk=service
    UDPPorts=4569,5060,10000:20000
    status=disabled
[root@l1nuxsvr /]#

Offline arne

  • ****
  • 1,116
  • +0/-4
Re: sip_reg_timeout
« Reply #24 on: February 02, 2008, 03:39:01 AM »
But this, is I believe, completely incorrect. Disabled but still running should be imposible, but if this status still exist this might explain why the SME firewall is closed, and why nothing work. Status need to be "enabled" to open the SME firewall, I think. (But how to enable - I allways forget these db commands - will try to take alook in the wiki.)
......

Offline arne

  • ****
  • 1,116
  • +0/-4
Re: sip_reg_timeout
« Reply #25 on: February 02, 2008, 03:43:17 AM »
I hope this will work:

config setprop asterisk status enabled
signal-event post-upgrade
signal-event reboot
......

Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #26 on: February 02, 2008, 06:27:27 AM »
But this, is I believe, completely incorrect. Disabled but still running should be imposible, but if this status still exist this might explain why the SME firewall is closed, and why nothing work. Status need to be "enabled" to open the SME firewall, I think. (But how to enable - I allways forget these db commands - will try to take alook in the wiki.)
I am not sure about that..  see http://forums.contribs.org/index.php?topic=38930.msg178340#msg178340
I believe SAIL does something strange with the startup..
I'd like Selintra to agree with the your suggestion before I try it.

definitely something odd going on and I appreciate all suggestions.
I'd really like to resolve this,  I'm going have to go back to the straight SPA setup soon.

Offline SARK devs

  • ****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: sip_reg_timeout
« Reply #27 on: February 02, 2008, 07:50:42 AM »
Hi Guys,

Arne is incorrect in this instance.  In 2.2 we had to drop the asterisk daemon because we went over to the ATrpms asterisk (which has its own asterisk daemon).  The SAIL rpm disables the Asterisk startup, which is what you have seen above.  SAIL starts a daemon called sark instead.

I have looked all over the web regarding your problem and I can find almost no references to local phones going unreachable from asterisk.  This suggests that your problem is probably unique to your setup.  I really don't think that this is an asterisk problem per se but maybe some kind of hardware problem (perhaps your  ethernet controllers?) or other subtle software issue.   Whatever it is, it isn't giving us any obvious clues as to what it is.

I would suggest you back your SAIL ID up to USB using the USB offload feature.  Run up a completely separate box (with a full .iso install) and restore from the USB stick.  If you don't have a separate box then I think you should cut your losses and regress to the .iso because I don't think this is going to be easily solved.

Best


Offline groutley

  • ****
  • 213
  • +0/-0
    • http://www.routley.homeip.net
Re: sip_reg_timeout
« Reply #28 on: February 02, 2008, 09:44:46 AM »
Thanks Jeff,
 appeciate the thoughts there.
I was starting to think that myself,  if only I had a spare box to run up !
I am not aware of this USB offload function, I'll have to RTFM ;-)

Thanks to you all for your thoughts..