[Home]

Summary:ASTERISK-15207: [regression] After upgrading i see a lot more Notices peers status
Reporter:Lorenz Barth (bartpbx)Labels:
Date Opened:2009-11-24 04:17:31.000-0600Date Closed:2011-06-07 14:10:33
Priority:TrivialRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/DatabaseSupport
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hi, after upgrading the 1.4.27 from 1.4.24 i see a lot more messages about our realtime peers. These peers have qualify=yes but I don't think its ok to get this message for one peer again and again.

Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5
[Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5
[Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5
[Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5
[Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5
[Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5
[Nov 24 11:06:12] NOTICE[21546]: chan_sip.c:17050 sip_poke_noanswer: Peer 'xxx' is now UNREACHABLE!  Last qualify: 5


I think that this problem is related to random server "hangups" where the sip channel is no longer responding. I could not reproduce this crashes till today.

****** ADDITIONAL INFORMATION ******

Running 1.4.27 with res_odbc + realtime. Sip.conf rt settings are:
rtCacheFriends=yes    
rtnoupdate=no        
rtIgnoreRegExpire=yes
rtAutoClear=360
Comments:By: Lorenz Barth (bartpbx) 2009-11-26 01:34:54.000-0600

Hi, this Problem also exists in 1.4.26.3

By: Tilghman Lesher (tilghman) 2009-11-27 09:21:05.000-0600

> rtIgnoreRegExpire=yes

Try setting this option to "no" and see if the repeated notices disappear.

By: S├ębastien Couture (sysreq) 2009-12-03 01:37:40.000-0600

I am also experiencing this issue since I've upgraded from 1.4.26.3 to 1.4.27.1.

I use the ODBC backend, and my realtime SIP settings are as follows:

rtcachefriends=yes
rtsavesysname=yes
rtupdate=yes
rtautoclear=no
ignoreregexpire=yes

Even after using 'ignoreregexpire=no' as suggested by tilghman, I still get these multiplicated qualify notifications.

By: Tim King (timking) 2009-12-03 12:54:21.000-0600

Its rtignoreregexpire

By: S├ębastien Couture (sysreq) 2009-12-03 13:12:35.000-0600

The option is actually called 'ignoreregexpire' in sip.conf, and 'rtignoreregexpire' in iax.conf.

A 'sip show settings' confirms the change took effect:

Realtime SIP Settings:
----------------------
 Realtime Peers:         Yes
 Realtime Users:         Yes
 Cache Friends:          Yes
 Update:                 Yes
 Ignore Reg. Expire:     No

By: Lorenz Barth (bartpbx) 2009-12-03 14:48:23.000-0600

Hi, changing this opion has no effekt to the problem.

By: Leif Madsen (lmadsen) 2010-01-07 10:58:12.000-0600

This is still an issue on the latest 1.4 branch right?

By: Lorenz Barth (bartpbx) 2010-01-28 06:48:23.000-0600

We Switched to 1.6 so from our point of view this is not an issue anymore

By: Leif Madsen (lmadsen) 2010-02-16 13:45:34.000-0600

Suspending this issue for now as the reporter appears to have resolved this by moving up to 1.6, and Russell feels this may be resolved, so I'm suspending this issue for now. If someone has this issue again on the latest 1.4 releases, please open a new issue. Thanks!