Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

You can test API methods on the interactive API browser page and without writing code
Some of the resources described on the page may not be available by default due to the type of application (see Creating and authorizing applications).

The resource allows you to use the API to link multiple extensions. The main extension number will be reflected in statistics and events, and only when the main extension is called, the associated extensions will be called. If the associated extension number is called, only it will be called. When making an outgoing call from the associated extension, the outgoing call from the main extension will be emulated.

Synchronization parameters of extensions in “bundle“

Synchronizing parameters of extensions in “bundle“

phone resource fields:
"record_transfer", "ringback_sound", "geo_list", "record_enabled", "hold_music", "announce_sound_upon_outgoing_call", "announce_sound_upon_incoming_call", "conference_pin", "conference_announce_caller_name", "conference_end_on_exit", "record_format", "record_stereo", ”incoming_limit”

extension resource fields:
"status", "dial_rule_id", "dial_rule_limit"

  1. When creating a "bundle", the parameters of the associated extension are overwritten according to the main

  2. When updating the parameters on any of the extensions in the “bundle”, the parameters of the other extensions in the “bundle” are also updated

  3. Nothing happens when extension in “bundle“ is removed

"Bundle" resources

 POST /client/{client_id}/extensions_bundle/{extension_id}

POST /client/{client_id}/extensions_bundle/{extension_id}

The POST resource allows you to set a list of related extensions for the main one specified in the extension_id. The extension_id specified in the path must be the ID of the internal number of the ‘phone' type.

URL Parameters

Name

Type

extension_id

string

Json parameters

Name

Type

Description

extension_id

array

Set a list of extension IDs to associate them with the main extension that was specified in the request path as extension_id.

The specified extensions must be of the phone type, must not be other main extensions, and must not be associated with any other extension.

Response fields

Name

Type

Description

bundle_list

array

List of related extension numbers

bundle_id

int

id of the main extension

 GET /client/{client_id}/extensions_bundle/{extension_id}

GET /client/{client_id}/extensions_bundle/{extension_id}

The GET resource allows you to get a list of related extensions. The extension_id specified in the path must be the ID of the internal number of the ‘phone' type.

URL Parameters

Name

Type

extension_id

string

Response fields

Name

Type

Description

bundle_list

array

List of related extension numbers

bundle_id

int

id of the main extension

 DELETE /client/{client_id}/extensions_bundle/{extension_id}

DELETE /client/{client_id}/extensions_bundle/{extension_id}

The DELETE resource allows you to untie the extensions from the main one. The extension_id specified in the path must be the ID of the internal number of the ‘phone' type.

URL Parameters

Name

Type

extension_id

string

Response fields

Name

Type

Description

bundle_list

array

List of related extension numbers

bundle_id

int

id of the main extension

Usage example

For example, client_id=801, where the main extension number is extension_id=31456 and the list of associated extensions contains the id: 32486, 32767

  • No labels