15:08:48 <mc_> mentax: we typically create "aggregate" databases, like 'sip_auth' or 'accounts', when we need to search for docs across accounts
15:09:02 <mc_> but there isn't multi-db querying in stock couch
15:09:19 <mc_> i've heard there are add-ons to allow it, haven't tried, can't vouch, buyer beware, etc
15:54:58 <Serge> Good morning! What will be the best way to have ability to call extensions between accounts? I have a customer who have 2 locations with 2 different names and IVRs so, before they use nextiva and they was able to specify 2 locations 
16:07:32 <hmmhesays> Serge create a classifier with an account prefix. Add those numbers to number manager and handle it that way.
16:46:05 <Serge> hmmhesays: hmm can you explain little bit more?
16:47:02 <Serge> some examples would be great
16:54:32 <hmmhesays> Serge, The idea is you create system wide routeable numbers using globally non routable prefixes. Just like adding DID's to each account
17:38:26 <Serge> mc_: Does "knm_voip_innovations" support provisioning off E911?
18:14:37 <mc_> no, check number_manager/src/providers for e911 modules
18:14:46 <mc_> dash, telnyx, vitelity i think
19:07:28 <fink> if you're really bored, just change emergency_provisioning_url in the couch doc and point it to your own api that translates your provider's e911 api responses into dash-compatiable xml :|
22:59:37 <hmmhesays> Nothing wrong with going that route
23:04:22 <hmmhesays> fink, you ever use the eavesdrop api in acdc?
23:05:10 <fink> hmmhesays: no, sir... only implemented a very small subset of acdc's api, mainly just getting queues set up and torn down with agents
23:23:55 <hmmhesays> fink, yeah that's what we're using it for as well after building a UI for it. It looks like it *should* work though it seems like something isn't getting started because the request times out. 
23:33:38 <fink> never really looked into it, but it looks like eavesdropping from the acdc api is handled through spyvsspy?
23:33:50 <fink> publish_eavesdrop_req / handle_eavesdrop_req ?