[Asterisk-Users] Realtime SIP Registrations

[Aaron Daniel]

On Thu, 2006-06-29 at 10:04 +0100, Tim Panton wrote:
> Yes, except, if I understand you correctly, you would also
> need to write insert and update triggers on the view, so that
> when asterisk writes to the compiled config, the correct changes
> are applied to your separate tables.
> That might limit your choice of databases a bit.

The way I designed the second table, you wouldn't have to update any
other tables with information from the sipregs table.  The only
information in there is information that asterisk needs to contact
phones and such.  So, for example, unless you need the ip address listed
somewhere else in your database, you can leave it in sipregs.

> 
> The other thing to watch is that you have to ensure that
> the resulting view behaves exactly the way that asterisk
> expects it to, unless you get the join right, you can
> get duplicate (apparently identical) records back
> which would confuse asterisk.

That's something that you have to be careful about anyhow :)  The way
I'm looking at it, you can either use a view (we use 3 different tables
for actual phone configuration... so a view makes sense).  Or for
smaller systems, use an actual sippeers table and put the info in there.

-- 
Aaron Daniel
Computer Systems Technician
Sam Houston State University
amdtech at shsu.edu
(936) 294-4198