[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 10:43 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Bug with Realtime?

> Noted - but if OP does a "reload" once a day, 120 seconds (2 minutes) out
of
> 1 day (14400 seconds) is 99.17% uptime; "close enough" to 99.999 percent
in
> most folks books.  What percentage of businesses use their phones 24/7?

Even if its once a month, it's still too much in my book. No wonder people
have had "bad experiences" with voip.
If I'm going to run my service on a platform that will inevitably have some
downtime, I wouldn't be a very good business man!

Let's say I add a new provider to my service and therefore have to add
another "register=>" command into sip.conf, I'd have to issue a "sip reload"
which would kill off all the realtime sip phones.

> A reload flushes the SIP registration database, so once you do a 
> reload, that phones reg is gone.

Surely you could move the "flush" part of "sip reload" into a separate
command and therefore ensure the realtime phones stay connected properly.
Still doesnt explain why, when I do a "reload", only the realtime users are
affected, and not the hard coded ones.

Dan

Just a WAG, but I'm betting that the hard-coded users are loaded into a hash
that Asterisk handles and the real-time users are either in a different hash
or not at all.  Since real-time is an "add-on" vs a "built-in" feature, this
might indeed be a "bug" or shortcoming.  Have you checked the Issue Tracker
for this?