Merge branch 'reset-sip-v2' * reset-sip-v2: After SIP reset, offer to change inbound fwd Reset sip account using v2 API
Reset sip account using v2 API SipAccount now uses only v2 APIs for lookup, create, update, and delete
Merge branch 'sip-outbound' * sip-outbound: Support transcription disablement option Port in inbound calls + voicemail Allow fetching fwd timeout as well Get OGM for a customer Helper to fetch customer's vcard-temp Make Disposition more real Allow constructing CDR for an inbound or outbound event Outbound calls from v2 SIP endpoint work and save a CDR
Helper to fetch customer's vcard-temp
Remove BigDecimal.new It turns out in newer versions of Ruby this isn't cool anymore. The new way is BigDecimal(value), which is dumb, but whatever...
Customer always has a JID
Ask electrum to notify on new BTC addresses Otherwise we won't know when someone has paid...
Factor out CustomerRepo Using the Repository pattern to encapsulate the fetch and create operations on the persistence layer for a domain object. These were not really factories in the classic sense, but rather "fetch from persisitence layer" methods, and so they now have a home.
Merge branch 'btc_spop' * btc_spop: Get new Bitcoin address from Redis set
Get new Bitcoin address from Redis set This set is populated by a cron job to have only known-good available addresses in it.
Add btc_addresses to Customer And use that in registration instead of implementing it inline
Merge branch 'create-reset-sip-account' * create-reset-sip-account: Create or reset SIP account Factor out Catapult connection
Create or reset SIP account New command to create or reset SIP account. Always try create first because it's faster and more common, fall back to search the list for our account if that fails due to conflict. Password is always randomly generated from the mnemonicode word list.
Usage command Customer has a CustomerUsage which can fetch data to build a UsageReport which returns a jabber:x:data form "table" as per spec for per-day in the last month. Minutes come from cdr table in postgresql. Messages come from redis.
Merge branch 'pass-messages' * pass-messages: Pass messages to and from the SGX
Pass messages to and from the SGX Rewriting the from/to as appropriate.
Merge branch 'create_customer_id' * create_customer_id: Create customer_id if it does not exist before we start registration Break out CustomerPlan Inject BackendSgx per customer
Create customer_id if it does not exist before we start registration
Break out CustomerPlan We had Plan and Customer but the relationship between the two lived entirely in Customer, which was growing quite large. Break that relationship out into its own concept and give it a name.
Merge branch 'new-signup-add-credit-card' * new-signup-add-credit-card: Happy path for credit card signup Panic should work on any value for error Allow getting default payment method, not just index Object representing the backend SGX to use Stop polluting Object namespace with Blather DSL Work in the presence of em-synchrony Helper to allow ordering phone number from Bandwidth v2 Helper to get a promise that resolves after N seconds Every payment kind will need the plan, so put it at the top Use registration pattern for Payment kinds Method to bill the plan of a Customer Use Forwardable for simple delegations Helper to allow using sync-style code in a Promise context New signup: go to web to choose credit card OOB helper Reject promise on stanza error Fix typo