On 10-09-16 09:43 AM, Dan Journo wrote: >> That's not a bug. Only when the phone registers or performs some sort of >> action >> (such as placing a call, etc...) does Asterisk query the database. If your >> phones have a short re-registration time this becomes less of a problem. > > How do you explain that as soon as I issue a "reload" command, the realtime > phones stop receiving calls? > To test your theory, I rebooted the phone so that it had a fresh > registration, I made and receives calls successfully, then issued a 'reload', > then trying to dial in again, and the phone didnt ring. > > After a few seconds, the CLI says:- > [2010-09-16 14:39:29] NOTICE[24611]: chan_sip.c:17200 sip_poke_noanswer: Peer > 'kesher_201' is now UNREACHABLE! Last qualify: 58 > > How can this not be a bug? The phone works fine for hours, and then as soon > as I issue a reload command, its UNREACHABLE. > ps. The phone can still make calls after the "reload". It just stops > receiving calls after a "reload".
That sounds like a qualify issue in that the phone does not respond to a NOTIFY message. Check the SIP debug and see what is going on. Alternatively you could turn off the qualify option with qualify=no. Leif. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
