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

KeyDescriptionTypeDefaultRequiredSupport Level
bypass_e164Use the original requested number instead of normalizing to E164boolean()false
caller_id_typeWhich configured caller-id to use (key in the 'caller_id' object)string()externalfalse
custom_sip_headers.inCustom SIP Headers to be applied to calls inbound to Kazoo from the endpoint#/definitions/custom_sip_headersfalse
custom_sip_headers.outCustom SIP Headers to be applied to calls outbound from Kazoo to the endpoint#/definitions/custom_sip_headersfalse
custom_sip_headers.^[a-zA-z0-9_\-]+$The SIP header to addstring()false
custom_sip_headersA property list of SIP headersobject()false
do_not_normalizeUse the original requested number instead of normalizing; otherwise try to apply the endpoint's dialplan to the requested numberboolean()false
dynamic_flags.[]string()false
dynamic_flagsList of function names (or 'zone') that are called on the Call record to populate the 'flags' array sent to the resource(s) for matchingarray(string())false
emit_account_idToggles whether to put the account id in the SIP packetsboolean()false
format_from_uriIf true, puts the account realm in the From headerboolean()false
from_uri_realmOverride the From realm in the SIP packetsstring()false
hunt_account_idWhen using local resources, use this account instead of the account making the call (useful for resellers)string()false
ignore_early_mediaToggle whether to ignore early mediaboolean()falsefalse
outbound_flags.[]string()false
outbound_flagsList of flags to use when matching resources to route the callarray(string())[]false
resource_typesets a custom resource type for the published amqp messagestring()false
ringbackTone or file to play while waiting for the leg to be answeredstring()false
skip_moduleWhen set to true this callflow action is skipped, advancing to the wildcard branch (if any)boolean()false
timeoutHow long, in seconds, to wait for the call to be answeredinteger()false
to_didStatically set the DID to dialstring()false
use_local_resourcesToggle whether to use the account's (or hunt_account_id's) resources vs the system resourcesboolean()truefalse