<p>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.<br>
</p>
<p>Zeeshan A Zakaria</p>
<p>--<br>
<a href="http://www.ilovetovoip.com">www.ilovetovoip.com</a></p>
<p><blockquote type="cite">On 2010-08-18 6:49 AM, "Ishfaq Malik" <<a href="mailto:ish@pack-net.co.uk">ish@pack-net.co.uk</a>> wrote:<br><br>
<div bgcolor="#ffffff" text="#000000">
Hi<br>
<br>
I'll give you an example process flow<br>
<br>
Our customer logs onto our VoIP Portal and orders a SIP Geographic
number<br>
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.<br>
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.<br>
Also, an insert is made into a table to say that the extensions table
has been updated.<br>
<br>
A cron runs and sees that the extensions table has been updated.<br>
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.<br>
The cron then executes a dialplan reload <br>
<br>
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.<br>
<br>
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)<br>
<br>
Ish<p><font color="#500050"><br><br>On 18/08/10 10:37, Zeeshan Zakaria wrote:<br>><br>> So why you need a reload when you are using the real...</font></p></div>
<br>--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></p>