[asterisk-users] Realtime Context
Zeeshan Zakaria
zishanov at gmail.com
Wed Aug 18 07:50:19 CDT 2010
Thanks for the details. I Agreed you know what you are doing. As for doing
it more elegantly, it is not possible to do a fruitful discussion without
knowing all the details of how your dialplan works, neither is this the goal
here. But I offer similar hosted PBX service, just use one context for all
the companies, use various logics in the dialplan to differentiate between
the tenants, their updates, new inserts etc., and never needed to do any
reload. I identify tenant by their account ids and one context works for
all. CDRs are perfectly fine, billing is even great and automated. If fact I
have developed/programmed three multi-tenant solutions for far, including
one for a busy client, and used the same logic. They all work perfectly
fine. That was why I wondered why you needed reloads. But you must be doing
something which genuinely requires a reload, not saying that you are not
doing it right.
Zeeshan A Zakaria
--
www.ilovetovoip.com
On 2010-08-18 6:49 AM, "Ishfaq Malik" <ish at pack-net.co.uk> wrote:
Hi
I'll give you an example process flow
Our customer logs onto our VoIP Portal and orders a SIP Geographic number
Geo number is successfully ordered which inserts an entry into our
extensions table in MySQL DB in the default context which has a goto command
to a newly created specific context for handling the incoming on that
number.
The customer goes to the dial plan managing section of the portal and sets
the number to ring an extension of his followed by going to voicemail. In
the back end 2 new inserts are made into the extensions table for the newly
created context.
Also, an insert is made into a table to say that the extensions table has
been updated.
A cron runs and sees that the extensions table has been updated.
this gets a distinct list of contexts from the extensions table and writes
each one to a new extensions.con putting in the realtime switch for each
context.
The cron then executes a dialplan reload
If you can see a more elegant way of doing the above so that no intervention
is required by anyone other that the customer, please let me know as I'm
always willing to learn better ways of doing things.
Also, please bear in mind that we offer a hosted service for customers so we
have lots of different companies all working off the same server(s)
Ish
On 18/08/10 10:37, Zeeshan Zakaria wrote:
>
> So why you need a reload when you are using the real...
--
_____________________________________________________________________
-- 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100818/0bdf4da1/attachment.htm
More information about the asterisk-users
mailing list