[asterisk-users] Bug with Realtime?

[Danny Nicholas]

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Dan Journo
Sent: Thursday, September 16, 2010 8:44 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Bug with Realtime?

>> 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".

>I want to move my clients over to realtime so they can manage their
accounts online, but I cant do that if they become UNREACHABLE when I do a
reload.

>Thanks
>Dan

I'm still going to defend that this is not a "bug".  It is up to you to
insure that your phones are in constant connectivity without burdening your
bandwith.  You could be aggressive and register your phone every 30 seconds;
a more realistic approach would be a register every 90-120 seconds (I have
Polycom 501's and they take at least 90 seconds to come back up on a
restart).  If your clients can't take 2 minutes of "downtime" on a phone,
they don't need to be on VOIP.