Páginas relacionadas.
Friday, January 1, 2021
Friday, December 18, 2020
Video corto de demostracion TestYourCall
Wednesday, October 14, 2020
Bandwidth en completar adquisicion de VoxBone
- Leading North American and international cloud platforms come together to supercharge enterprise communications across 60+ countries representing 93% of global GDP
- Global enterprises will benefit from a unified software platform and network for the rapid launch and hyper-scale of communications applications and experiences
- Combination will accelerate and expand Bandwidth’s opportunity to serve $17.7 billion CPaaS market with a five-year CAGR of 33% (2019 to 2024)1
- Voxbone’s 2020 revenue is expected to be more than $85 million and up more than 25% year-over-year, and upon close will be accretive to Bandwidth’s non-GAAP gross margin and non-GAAP net income
RALEIGH, NC and LONDON, UK — Oct 12, 2020 — Bandwidth (NASDAQ: BAND), a leading enterprise cloud communications company announced it has signed a definitive agreement to acquire Voxbone, an international enterprise cloud communications leader, for an enterprise value of €446 million EUR, representing a multiple of approximately six times anticipated Voxbone 2020 revenue. Voxbone has been majority-owned by Vitruvian Partners, a leading growth- and technology-focused investment firm headquartered in London, UK, since 2015. Voxbone is a leading European-based communications platform and IP voice network. Since 2005, their mission has been to simplify global communications for businesses by providing compliant, quality coverage that can be integrated with any contact center, conferencing platform or voice application.
Wednesday, September 16, 2020
Friday, August 21, 2020
Imagenes nuevas (y corregidas) de Kazoo Embebido
Tenemos disponibles nuevas imagenes para instalar kazoo VoIP en servidores genericos y appliances de AMD 64 bits.
Las mismas incluyen tecnologias SquashFS y Overlays, con el proposito de proveer un sistema mucho mas compacto y de mas espacio a utilizar.
En menos de 5 minutos, usted obtiene una instalacion de Kazoo/2600hz (version 4.3 ) disponible, con solo algunos pasos de configuracion.
Enlace al Proyecto:
https://sourceforge.net/projects/kazoo-pbx-embedded/
International Phone Numbers / Numeros Telefonicos Internacionales
By default, Kazoo includes appropriate configurations for running the system in the United States. Nothing, however, stops folks from re-configuring the system to support other country's numbering system.
2600Hz encourages you to consider sticking with the E.164 format for globally rout-able numbers.
Determine if a number is "global"#
The first thing to configure is how to tell when a number is "globally rout able" versus an internal extension. This is managed in the system_config/number_manager configuration document, under the reconcile_regex key.
"reconcile_regex": "^\\+?1?\\d{10}$|^\\+[2-9]\\d{7,}$|^011\\d{5,}$|^00\\d{5,}$"
Here is the default, which if reading regexps isn't second nature, optionally matches a + and a 1 (the country code for the US), followed by any 10 digits, or matches 8-or-more digit numbers (prefixed by a +), or the international dialing codes for the US.
Resources / Llamadas salientes en Kazoo
Route the caller to external resources (typically upstream providers).
Schema#
Validator for the resources callflow data object
| Key | Description | Type | Default | Required | Support Level |
|---|---|---|---|---|---|
bypass_e164 | Use the original requested number instead of normalizing to E164 | boolean() | false | ||
caller_id_type | Which configured caller-id to use (key in the 'caller_id' object) | string() | external | false | |
custom_sip_headers.in | Custom SIP Headers to be applied to calls inbound to Kazoo from the endpoint | #/definitions/custom_sip_headers | false | ||
custom_sip_headers.out | Custom SIP Headers to be applied to calls outbound from Kazoo to the endpoint | #/definitions/custom_sip_headers | false | ||
custom_sip_headers.^[a-zA-z0-9_\-]+$ | The SIP header to add | string() | false | ||
custom_sip_headers | A property list of SIP headers | object() | false | ||
do_not_normalize | Use the original requested number instead of normalizing; otherwise try to apply the endpoint's dialplan to the requested number | boolean() | false | ||
dynamic_flags.[] | string() | false | |||
dynamic_flags | List of function names (or 'zone') that are called on the Call record to populate the 'flags' array sent to the resource(s) for matching | array(string()) | false | ||
emit_account_id | Toggles whether to put the account id in the SIP packets | boolean() | false | ||
format_from_uri | If true, puts the account realm in the From header | boolean() | false | ||
from_uri_realm | Override the From realm in the SIP packets | string() | false | ||
hunt_account_id | When using local resources, use this account instead of the account making the call (useful for resellers) | string() | false | ||
ignore_early_media | Toggle whether to ignore early media | boolean() | false | false | |
outbound_flags.[] | string() | false | |||
outbound_flags | List of flags to use when matching resources to route the call | array(string()) | [] | false | |
resource_type | sets a custom resource type for the published amqp message | string() | false | ||
ringback | Tone or file to play while waiting for the leg to be answered | string() | false | ||
skip_module | When set to true this callflow action is skipped, advancing to the wildcard branch (if any) | boolean() | false | ||
timeout | How long, in seconds, to wait for the call to be answered | integer() | false | ||
to_did | Statically set the DID to dial | string() | false | ||
use_local_resources | Toggle whether to use the account's (or hunt_account_id's) resources vs the system resources | boolean() | true | false |
