Twilio → Vobiz: Phone Numbers & DID

​

Twilio → Vobiz mapping

​

Before / after: search inventory and buy

from twilio.rest import Client

client = Client(ACCOUNT_SID, AUTH_TOKEN)

# 1. Search the catalog for a local number
available = client.available_phone_numbers('US').local.list(
    area_code=415,
    sms_enabled=True,
    voice_enabled=True,
    limit=20,
)
number = available[0].phone_number   # e.g. '+14155551234'

# 2. Provision it onto your account
incoming = client.incoming_phone_numbers.create(phone_number=number)
print(incoming.sid, incoming.phone_number)

​

Before / after: route inbound calls

# Point the number's voice webhook at your TwiML endpoint
client.incoming_phone_numbers(NUMBER_SID).update(
    voice_url='https://example.com/answer',
    voice_method='POST',
)

# ...or hand inbound calls to an Elastic SIP Trunk
client.incoming_phone_numbers(NUMBER_SID).update(
    trunk_sid='TKxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
)

from flask import Flask, Response
from vobiz import vobizxml

app = Flask(__name__)

@app.post('/answer')
def answer():
    resp = vobizxml.ResponseElement()
    menu = resp.add_gather(action='https://example.com/menu', method='POST',
                           input_type='dtmf', num_digits=1)
    menu.add_speak('Press 1 for sales, 2 for support.')
    return Response(resp.to_string(), mimetype='application/xml')

​

Before / after: list, then release

# List owned numbers (optionally filtered)
for n in client.incoming_phone_numbers.list(limit=50):
    print(n.sid, n.phone_number, n.voice_url)

# Filter to one number
matches = client.incoming_phone_numbers.list(phone_number='+14155551234')

# Release it back to Twilio
client.incoming_phone_numbers(NUMBER_SID).delete()

​

Key differences

• The E.164 number is the key. Twilio identifies a provisioned number by an opaque PNxxxx… SID; Vobiz uses the phone number itself (+14155551234). Store the E.164 and you can search, buy, route, and release without a lookup round-trip.
• Inventory instead of a live catalog search. list_inventory_numbers returns Vobiz’s ready-to-buy stock, so search results are exactly what you can purchase_from_inventory in the next call — a deterministic two-step buy.
• Routing lives on the trunk/app. Where Twilio sets voice_url per number, Vobiz assigns the DID to a trunk_group_id and the trunk carries the answer_url. Many numbers can share one flow, and re-pointing a whole product is a single trunk edit rather than an update per number. Twilio’s trunk_sid/voice_application_sid patterns map cleanly onto this model.
• Same webhook contract. Vobiz fetches your answer_url and expects XML back — identical to Twilio’s voice_url request/response cycle. Swap the TwiML builder for vobizxml and the handler is a near tab-swap. Inbound requests carry an X-Vobiz-Signature you validate the same way you validated X-Twilio-Signature.
• E.164 formatting is endpoint-specific. purchase_from_inventory takes the number with the leading + in the body; unrent_number takes it without the + in the path; assignment endpoints take it URL-encoded (%2B14155551234). The SDK handles this for you.
• Sub-account DID assignment is first-class. assign_did_to_subaccount(auth_id, e164=, sub_account_id=) moves a DID to a child account in one call — handy for reseller and multi-tenant setups, alongside Vobiz’s India KYC tooling.