Determine the Phone MAC Address
To add phones to the Third-Party Call Control system, determine the MAC address of a Cisco IP Phone.
Procedure
Perform one of the following actions:
|
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
To add phones to the Third-Party Call Control system, determine the MAC address of a Cisco IP Phone.
Perform one of the following actions:
|
The Cisco IP Phone is used as a part of a SIP network, because the phone supports Session Initiation Protocol (SIP). The Cisco IP Phone is compatible with other SIP IP PBX call control systems, such as BroadSoft, MetaSwitch, and Asterisk.
Configuration of these systems is not described in this document. For more information, see the documentation for the SIP PBX system to which you are connecting the Cisco IP Phone.
This document describes some common network configurations; however, your configuration can vary, depending on the type of equipment that your service provider uses.
Phones can be provisioned to download configuration profiles or updated firmware from a remote server when they are connected to a network, when they are powered up, and at set intervals. Provisioning is typically part of high-volume, Voice-over-IP (VoIP) deployments and is limited to service providers. Configuration profiles or updated firmware are transferred to the device through use of TFTP, HTTP, or HTTPS.
You can configure the phone to report its full configuration, delta changes in the configuration, or the status data to the server. You can add up to two URLs in the Report Rule field to specify the destination for the report, and include an optional encryption key.
When requesting delta configuration and status reports at once, separate report rules with a space. Include a destination upload-URL in each of the report rules. You can optionally precede the report rule by one or more content arguments that are enclosed in square brackets [ ].
When a report upload is attempted, the HTTP Report Method field specifies whether the HTTP Request that the phone sends should be an HTTP PUT or an HTTP POST. Choose:
PUT Method–To create a new report or overwrite an existing report at a known location on the server. For example, you may want to keep overwriting each report that you send and only store the most current configuration on the server.
POST Method–To send the report data to the server for processing, such as, by a PHP script. This approach provides more flexibility for storing the configuration information. For example, you may want to send a series of phone status reports and store all the reports on the server.
Use the following content arguments in the Report Rule field to send specific configuration reports:
Content Argument |
Report Content |
||
---|---|---|---|
Default: Blank |
Full Configuration report |
||
[--delta] |
Configuration report contains only the latest changed fields For example,
|
||
[--status] |
Full Phone Status report |
||
|
When you specify the [--key <encryption key>] argument in the Report Rule, the phone applies AES-256-CBC encryption to the file (configuration, status, or delta), with the specified encryption key.
Note |
If you have provisioned the phone with Input Keying Material (IKM) and want the phone to apply RFC 8188-based encryption to the file, do not specify the --key argument. |
Access the phone administration web page. See Access the Phone Web Interface.
Step 1 |
Select . |
Step 2 |
Set the parameter for each of the five fields as described in Parameters for Reporting the Phone Configuration to the Server. |
Step 3 |
Click Submit All Changes. Example of user inputs and the resulting actions of the phone and provisioning server for the Report Rule:
|
Field | Description | ||||
---|---|---|---|---|---|
Report Rule |
Specifies how the phone reports its current internal configuration to the provisioning server. The URLs in this field specify the destination for a report and can include an encryption key. You can use the following keywords, encryption key, and file locations and names to control how you store the phone configuration information:
Perform one of the following:
|
||||
HTTP Report method: |
Specifies whether the HTTP Request that the phone sends should be an PUT or an POST.
Perform one of the following:
Allowed values: PUT|POST Default: POST |
||||
Report to Server: |
Defines when the phone reports its configuration to the provisioning servers.
Perform one of the following:
Allowed values: On Request|On Local Change|Periodically Default: On Request |
||||
Periodic Upload to Server: |
Defines the interval (in seconds) that the phone reports its configuration to the provisioning servers. This field is used only when Report to Server is set to Periodically. Perform one of the following:
Allowed values: An integer ranging between 600 and 259200 Default: 3600 |
||||
Upload Delay On Local Change: |
Defines the delay (in seconds) that the phone waits after a change is made, and then reports the configuration. This field is used only when Report to Server is set to On Local Change. Perform one of the following:
Allowed values: An integer ranging between 10 and 900 Default: 60 |