Webex Calling DECT Device Settings - Get the List of DECT Networks for an organization

Get the List of DECT Networks for an organization

Retrieves the list of DECT networks for an organization.

DECT Networks provide roaming voice services via base stations and wireless handsets. A DECT network can be provisioned up to 1000 lines across up to 254 base stations.

This API requires a full or read-only administrator auth token with a scope of spark-admin:telephony_config_read.

GET/v1/telephony/config/dectNetworks

Query Parameters

orgId

string

List of DECT networks in this organization.

name

string

List of DECT networks with this name.

locationId

string

List of DECT networks at this location.

Response Properties

dectNetworks

array[DECTNetworkDetail]

List of DECT networks in an organization.

string

Unique identifier for the DECT network.

name

string

Name of the DECT network. This should be unique across the location.

displayName

string

DECT network name displayed on the handset.

chainId

number

Chain ID of the DECT network.

model

BaseStationType

Base station model deployed in the DECT network.

DMS Cisco DBS210

string

Cisco DBS210 base station model.

DMS Cisco DBS110

string

Cisco DBS110 base station model.

defaultAccessCodeEnabled

boolean

Default access code is enabled. If true, the default access code is mandatory. If false, auto-generated access code is used.

defaultAccessCode

string

Default access code for the DECT network. The default access code should be unique within the same location to avoid the handset accidentally registering with base stations from different DECT networks in range. This is mandatory when defaultAccessCodeEnabled is true.

numberOfBaseStations

number

Number of base stations in the DECT network.

numberOfHandsetsAssigned

number

Number of handsets assigned to the DECT network.

numberOfLines

number

Number of lines in the DECT network.

location

Location of the DECT network.

string

Location identifier associated with the member.

name

string

Location name associated with the member.

Response Codes

The list below describes the common success and error responses you should expect from the API.

Code	Status	Description
200	OK	Successful request with body content.
201	Created	The request has succeeded and has led to the creation of a resource.
202	Accepted	The request has been accepted for processing.
204	No Content	Successful request without body content.
400	Bad Request	The request was invalid or cannot be otherwise served. An accompanying error message will explain further.
401	Unauthorized	Authentication credentials were missing or incorrect.
403	Forbidden	The request is understood, but it has been refused or access is not allowed.
404	Not Found	The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.
405	Method Not Allowed	The request was made to a resource using an HTTP request method that is not supported.
409	Conflict	The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.
410	Gone	The requested resource is no longer available.
415	Unsupported Media Type	The request was made to a resource without specifying a media type or used a media type that is not supported.
423	Locked	The requested resource is temporarily unavailable. A `Retry-After` header may be present that specifies how many seconds you need to wait before attempting the request again.
428	Precondition Required	File(s) cannot be scanned for malware and need to be force downloaded.
429	Too Many Requests	Too many requests have been sent in a given amount of time and the request has been rate limited. A `Retry-After` header should be present that specifies how many seconds you need to wait before a successful request can be made.
500	Internal Server Error	Something went wrong on the server. If the issue persists, feel free to contact the Webex Developer Support team.
502	Bad Gateway	The server received an invalid response from an upstream server while processing the request. Try again later.
503	Service Unavailable	Server is overloaded with requests. Try again later.
504	Gateway Timeout	An upstream server failed to respond on time. If your query uses `max` parameter, please try to reduce it.

GET

/v1/telephony/config/dectNetworks{?orgId,name,locationId}

Header

Authorization
Use personal access token
Bearer
This limited-duration personal access token is hidden for your security.

Query Parameters

orgId
string
List of DECT networks in this organization.
name
string
List of DECT networks with this name.
locationId
string
List of DECT networks at this location.

https://webexapis.com/v1/telephony/config/dectNetworks?orgId=Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE&name=Training-DectNetwork&locationId=Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OL2E4Mjg5NzIyLTFiODAtNDFiNy05Njc4LTBlNzdhZThjMTA5OA

200 / OK

            {
                "dectNetworks": [
                    {
                        "id": "Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE",
                        "name": "Demo-DectNetwork",
                        "displayName": "Demo-DectNetwork",
                        "chainId": 1224,
                        "model": "DMS Cisco DBS210",
                        "defaultAccessCodeEnabled": true,
                        "defaultAccessCode": "1234",
                        "numberOfBaseStations": 2,
                        "numberOfHandsetsAssigned": 5,
                        "numberOfLines": 2,
                        "location": {
                                    "id": "Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OL2E4Mjg5NzIyLTFiODAtNDFiNy05Njc4LTBlNzdhZThjMTA5OA",
                                    "name": "Cisco-HQ"
                        }
                    }
                ]
            }