IvozProvider

https://irontec.github.io/ivozprovider/en/
Admin
IvozProvider is a multi-level, provider-oriented IP telephony platform designed for managing and...
Tokens:60,219
Snippets:1,151
Trust Score:8.3
Update:5 months ago
Show doc for...
Tokens:
Raw
### Install IvozProvider (StandAlone Install)

Source: https://irontec.github.io/ivozprovider/en/tempest/basic_concepts/installation/debian_install.html

Installs the main IvozProvider metapackage for a StandAlone installation after configuring the APT repository. This command updates the package list and then installs the 'ivozprovider' package.

```bash
apt-get update
apt-get install ivozprovider

```

--------------------------------

### Example Extension Import File

Source: https://irontec.github.io/ivozprovider/en/tempest/_sources/administration_portal/client/vpbx/extensions.txt

This is an example of the CSV file format required for importing extensions. Ensure the 'Extension', 'CountryPrefix', 'Number', and optionally 'CountryCode' columns are correctly formatted.

```none
Extension,CountryPrefix,Number,CountryCode
200,+34,944048184,ES
201,+34,944048185,ES
202,+34,944048186
203,+1,944048187
204,+1,944048188,US
```

--------------------------------

### Incorrect Request Example

Source: https://irontec.github.io/ivozprovider/en/tempest/_sources/administration_portal/platform/terminal_manufacturers.txt

Shows an example of a wrong request format for terminal configuration files. Case sensitivity in the manufacturer name might lead to incorrect requests.

```console
https://PROV_IP:PROV_PORT/provision/subpath1/YEA-aabbccdd:ee:ff.cfg
```

--------------------------------

### Example Cisco SPA504G Provisioning Flow

Source: https://irontec.github.io/ivozprovider/en/tempest/_sources/administration_portal/platform/terminal_manufacturers.txt

Illustrates the sequence of requests a Cisco SPA504G terminal makes during the provisioning process, starting from DHCP to requesting specific configuration files.

```text
- Cisco SPA504G is turned on and requests an IP address to DHCP
- Receives “http://provision.example.com/provision” as DHCP option 66
- Request HTTP configuration from http://provision.example.com/provision/spa504g.cfg
- All 504G request the same file (spa504.cfg), prefixed with the given URL
- This file only contain basic configuration settings for the model and the URL 
  for the next request (p.e. https://provision.example.com/provision/$MAC.cfg)
- This way, each terminal (MAC should be unique) request a specific file 
  (and different) after the generic one has been served.
- This file will contain the specific configuration for the terminal:
   - User
   - Password
   - SIP Domain
```

--------------------------------

### Install Standalone IvozProvider

Source: https://irontec.github.io/ivozprovider/en/tempest/_sources/basic_concepts/installation/debian_install.txt

Install the IvozProvider metapackage for a standalone installation. This command updates the package list and installs the core IvozProvider package.

```bash
apt-get update
apt-get install ivozprovider
```

--------------------------------

### View Live SIP Traffic (All)

Source: https://irontec.github.io/ivozprovider/en/tempest/security_and_maintenance/maintenance/sip_captures.html

Run this command to see all live SIP traffic. Ensure sngrep is installed and accessible in your PATH.

```bash
sngrep

```

--------------------------------

### Configure APT Repository

Source: https://irontec.github.io/ivozprovider/en/tempest/_sources/basic_concepts/installation/debian_install.txt

Add the Irontec Debian repository to your system's APT sources. This is a required step before installing IvozProvider packages.

```bash
cd /etc/apt/sources.list.d
echo deb http://packages.irontec.com/debian tempest main extra > ivozprovider.list
```

--------------------------------

### Example CSV file for importing holidays

Source: https://irontec.github.io/ivozprovider/en/tempest/_sources/administration_portal/client/vpbx/routing_tools/calendars.txt

This is an example of the CSV file format required for importing holiday dates. Ensure fields are separated by semicolons and strings are enclosed in double quotes, with backslashes as escape characters.

```none
"New Year's Eve","2024-12-31"
"New Year's Day","2025-01-01"
"Labor Day","2025-05-01"
"\"Special\" Holiday","2025-12-26"
```
Tokens:
Raw