{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.qYt5seKS/b1/asterisk_22.5.1~dfsg+~cs6.15.60671435-1_amd64.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.qYt5seKS/b2/asterisk_22.5.1~dfsg+~cs6.15.60671435-1_amd64.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -13,8 +13,8 @@\n 8530e1d22ae2b725a6c508d3000dc3b0 59312 comm optional asterisk-mp3_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n bc8abbd28741217ef19a3120d3337f43 69708 debug optional asterisk-mysql-dbgsym_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n 7b0df558d835a2656f0ec9603847e50b 55552 comm optional asterisk-mysql_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n 87e11c084004fd7cb2f0a9cc3c297cf1 1070524 debug optional asterisk-ooh323-dbgsym_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n f6a10f8ddc9b8e3864d6f402992713f6 368820 comm optional asterisk-ooh323_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n 31455bbaf85f23bf26504ca7e3753551 1378464 debug optional asterisk-tests-dbgsym_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n d7ee9b707acea0f2a3e3ac4f62a0a81d 562788 comm optional asterisk-tests_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n- 8178e2daf95dd7f0b8e5c3885cc8232b 2504528 comm optional asterisk_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n+ caaf916aaf438db2d28aa9ee52579da4 2504488 comm optional asterisk_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb\n"}, {"source1": "asterisk_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb", "source2": "asterisk_22.5.1~dfsg+~cs6.15.60671435-1_amd64.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2025-08-03 09:18:38.000000 debian-binary\n -rw-r--r-- 0 0 0 8328 2025-08-03 09:18:38.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2496008 2025-08-03 09:18:38.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 2495968 2025-08-03 09:18:38.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "./usr/share/asterisk/documentation/core-en_US.xml", "source2": "./usr/share/asterisk/documentation/core-en_US.xml", "unified_diff": null, "details": [{"source1": "./usr/share/asterisk/documentation/core-en_US.xml", "source2": "./usr/share/asterisk/documentation/core-en_US.xml", "comments": ["Ordering differences only"], "unified_diff": "@@ -38295,1104 +38295,14 @@\n \n \n \n \n \n extended\n \n- \n- STIR/SHAKEN module for Asterisk\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- STIR/SHAKEN attestation options\n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Globally disable verification\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- File path to a certificate\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- URL to the public certificate\n- \n- Must be a valid http, or https, URL.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Attestation level\n- \n- \n- \n- 20.12.0\n- 21.7.0\n- 22.2.0\n- \n- Attestation level to use for unknown TNs\n- \n- Normally if a callerid TN isn't configured in stir_shaken.conf\n-\t\t\t\t\tno Identity header will be created. If this option is set,\n-\t\t\t\t\thowever, an Identity header will be sent using this\n-\t\t\t\t\tattestation level. Since there's no TN object, you must\n-\t\t\t\t\tensure that a private_key_file and public_cert_url are\n-\t\t\t\t\tconfigured in the attestation or profile objects for\n-\t\t\t\t\tthis to work.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- On load, Retrieve all TN's certificates and validate their dates\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Send a media key (mky) grant in the attestation for DTLS calls.\n-\t\t\t\t\t(not common)\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- STIR/SHAKEN TN options\n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Must be of type 'tn'.\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- File path to a certificate\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- URL to the public certificate\n- \n- Must be a valid http, or https, URL.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Attestation level\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- On load, Retrieve all TN's certificates and validate their dates\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Send a media key (mky) grant in the attestation for DTLS calls.\n-\t\t\t\t\t(not common)\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- STIR/SHAKEN verification options\n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Globally disable verification\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- A boolean indicating whether trusted CA certificates should be loaded from the system\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Path to a file containing one or more CA certs in PEM format\n- \n- These certs are used to verify the chain of trust for the\n-\t\t\t\t\t\tcertificate retrieved from the X5U Identity header parameter. This\n-\t\t\t\t\t\tfile must have the root CA certificate, the certificate of the\n-\t\t\t\t\t\tissuer of the X5U certificate, and any intermediate certificates\n-\t\t\t\t\t\tbetween them.\n- See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Path to a directory containing one or more hashed CA certs\n- \n- \n- \n- For this option, the individual certificates must be placed in\n-\t\t\t\t\t\tthe directory specified and hashed using the\n- openssl rehash\n- command.\n- \n- See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Path to a file containing one or more CRLs in PEM format\n- \n- If you with to check if the certificate in the X5U Identity header\n-\t\t\t\t\t\tparameter has been revoked, you'll need the certificate revocation\n-\t\t\t\t\t\tlist generated by the issuer.\n- See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Path to a directory containing one or more hashed CRLs\n- \n- \n- \n- For this option, the individual CRLs must be placed in\n-\t\t\t\t\t\tthe directory specified and hashed using the\n- openssl rehash\n- command.\n- \n- See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Path to a file containing one or more untrusted cert in PEM format used to verify CRLs\n- \n- If you with to check if the certificate in the X5U Identity header\n-\t\t\t\t\tparameter has been revoked, you'll need the certificate revocation\n-\t\t\t\t\tlist generated by the issuer. Unfortunately, sometimes the CRLs are signed by a\n-\t\t\t\t\tdifferent CA than the certificate being verified. In this case, you\n-\t\t\t\t\tmay need to provide the untrusted certificate to verify the CRL.\n- See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Path to a directory containing one or more hashed untrusted certs used to verify CRLs\n- \n- \n- \n- For this option, the individual certificates must be placed in\n-\t\t\t\t\t\tthe directory specified and hashed using the\n- openssl rehash\n- command.\n- \n- See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Directory to cache retrieved verification certs\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Maximum time to wait to CURL certificates\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Number of seconds a cache entry may be behind current time\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Maximum size to use for caching public keys\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Number of seconds an iat grant may be behind current time\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Number of seconds a SIP Date header may be behind current time\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- The default failure action when not set on a profile\n- \n- \n- \n- \n- If set to\n- continue\n- , continue and let\n-\t\t\t\t\t\t\tthe dialplan decide what action to take.\n- \n- \n- \n- \n- If set to\n- reject_request\n- , reject the incoming\n-\t\t\t\t\t\t\trequest with response codes defined in RFC8224.\n- \n- \n- \n- \n- If set to\n- return_reason\n- , continue to the\n-\t\t\t\t\t\t\tdialplan but add a\n- Reason\n- header to the sender in\n-\t\t\t\t\t\t\tthe next provisional response.\n- \n- \n- \n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- RFC9410 uses the STIR protocol on Reason headers\n-\t\t\t\t\tinstead of the SIP protocol\n- \n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- When set to true, will cause the verification process to not consider a\n-\t\t\t\t\t\tmissing or invalid SIP \"Date\" header to be a failure. This will make the\n-\t\t\t\t\t\tIAT the sole \"truth\" for Date in the verification process.\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Relaxes check for \"https\" and port 443 or 8443\n-\t\t\t\t\tin incoming Identity header x5u URLs.\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Relaxes check for query parameters, user/password, etc.\n-\t\t\t\t\tin incoming Identity header x5u URLs.\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- An existing ACL from acl.conf to use when checking\n-\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- An IP or subnet to permit when checking\n-\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- An IP or subnet to deny checking\n-\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- STIR/SHAKEN profile configuration options\n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Must be of type 'profile'.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- 18.22.0\n- 20.7.0\n- 21.2.0\n- \n- Actions performed when an endpoint references this profile\n- \n- \n- \n- Don't do any STIR/SHAKEN processing.\n- \n- \n- Attest on outgoing calls.\n- \n- \n- Verify incoming calls.\n- \n- \n- Attest outgoing calls and verify incoming calls.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- 16.15.0\n- \n- Gets the number of STIR/SHAKEN results or a specific STIR/SHAKEN value from a result on the channel.\n- \n- \n- The index of the STIR/SHAKEN result to get. If only 'count' is passed in, gets the number of STIR/SHAKEN results instead.\n- \n- \n- The value to get from the STIR/SHAKEN result. Only used when an index is passed in (instead of 'count'). Allowable values:\n- \n- \n- \n- \n- \n- \n- \n- \n- This function will either return the number of STIR/SHAKEN identities, or return information on the specified identity.\n-\t\t\tTo get the number of identities, just pass 'count' as the only parameter to the function. If you want to get information on a\n-\t\t\tspecific STIR/SHAKEN identity, you can get the number of identities and then pass an index as the first parameter and one of\n-\t\t\tthe values you would like to retrieve as the second parameter.\n- same => n,NoOp(Number of STIR/SHAKEN identities: ${STIR_SHAKEN(count)})\n-\t\t\tsame => n,NoOp(Identity ${STIR_SHAKEN(0, identity)} has attestation level ${STIR_SHAKEN(0, attestation)})\n- \n- \n- \n- HTTP binding for the Stasis API\n- \n- \n- \n- 12.0.0\n- \n- General configuration settings\n- \n- \n- 12.0.0\n- \n- Enable/disable the ARI module\n- \n- This option enables or disables the ARI module.\n- \n- \n- ARI uses Asterisk's HTTP server, which must also be enabled in\n- http.conf\n- .\n- \n- \n- \n- \n- http.conf\n- https://docs.asterisk.org/Configuration/Core-Configuration/Asterisk-Builtin-mini-HTTP-Server/\n- \n- \n- \n- \n- 11.11.0\n- 12.4.0\n- \n- The timeout (in milliseconds) to set on WebSocket connections.\n- \n- If a websocket connection accepts input slowly, the timeout\n-\t\t\t\t\t\tfor writes to it can be increased to keep it from being disconnected.\n-\t\t\t\t\t\tValue is in milliseconds.\n- \n- \n- \n- \n- 12.0.0\n- \n- Responses from ARI are formatted to be human readable\n- \n- \n- \n- 12.0.0\n- \n- Realm to use for authentication. Defaults to Asterisk REST Interface.\n- \n- \n- \n- 12.0.0\n- \n- Comma separated list of allowed origins, for Cross-Origin Resource Sharing. May be set to * to allow all origins.\n- \n- \n- \n- 14.2.0\n- \n- Comma separated list of channel variables to display in channel json.\n- \n- \n- \n- \n- 12.0.0\n- \n- Per-user configuration settings\n- \n- \n- 13.30.0\n- 16.7.0\n- 17.1.0\n- \n- Define this configuration section as a user.\n- \n- \n- \n- \n- Configure this section as a\n- user\n- \n- \n- \n- \n- \n- \n- \n- 13.30.0\n- 16.7.0\n- 17.1.0\n- \n- When set to yes, user is only authorized for read-only requests\n- \n- \n- \n- 13.30.0\n- 16.7.0\n- 17.1.0\n- \n- Crypted or plaintext password (see password_format)\n- \n- \n- \n- 12.0.0\n- \n- password_format may be set to plain (the default) or crypt. When set to crypt, crypt(3) is used to validate the password. A crypted password can be generated using mkpasswd -m sha-512. When set to plain, the password is in plaintext\n- \n- \n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- Outbound websocket configuration\n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- Must be \"outbound_websocket\".\n- \n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- The ID of a connection defined in websocket_client.conf.\n- \n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- Comma separated list of stasis applications that will use this websocket.\n- \n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- The local ARI user to act as.\n- \n- \n- \n- 20.15.0\n- 21.10.0\n- 22.5.0\n- \n- Subscribe applications to all event\n- \n- \n- \n- \n- \n- Core Geolocation Support\n- \n- \n- \n- 16.29.0\n- 18.15.0\n- 19.7.0\n- \n- Location\n- \n- Parameters for defining a Location object\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Must be of type 'location'.\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Location specification type\n- \n- \n- \n- \n- The\n- location_info\n- parameter must contain a comma separated list of IANA codes\n-\t\t\t\t\t\t\t\t\tor synonyms describing the civicAddress of this location.\n-\t\t\t\t\t\t\t\t\tThe IANA codes and synonyms can be obtained by executing\n-\t\t\t\t\t\t\t\t\tthe CLI command\n- geoloc show civicAddr_mapping\n- .\n- \n- \n- \n- \n- The\n- location_info\n- parameter must contain a comma\n-\t\t\t\t\t\t\t\t\tseparated list valid GML elements describing this location.\n- \n- \n- \n- \n- The\n- location_info\n- parameter must contain a single\n-\t\t\t\t\t\t\t\t\tURI parameter which contains an external URI describing this location.\n- \n- \n- \n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Location information\n- \n- \n- The contents of this parameter are specific to the\n-\t\t\t\t\t\t\tlocation\n- format\n- .\n- \n- \n- \n- location_info = country=US,A1=\"New York\",city_district=Manhattan,\n-\t\t\t\t\t\tA3=\"New York\", house_number=1633, street=46th, street_suffix = Street,\n-\t\t\t\t\t\tpostal_code=10222,floor=20,room=20A2\n- \n- \n- location_info = Shape=Sphere, pos3d=\"39.12345 -105.98766 1920\", radius=200\n- \n- \n- location_info = URI=https:/something.com?exten=${EXTEN}\n- \n- \n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Fully qualified host name\n- \n- \n- This parameter isn't required but if provided, RFC8787 says it MUST be a fully\n-\t\t\t\t\t\tqualified host name. IP addresses are specifically NOT allowed. The value will be placed\n-\t\t\t\t\t\tin a\n- loc-src\n- parameter appended to the URI in the\n- Geolocation\n- header.\n- \n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Location determination method\n- \n- This is a rarely used field in the specification that would\n-\t\t\t\t\t\tindicate the method used to determine the location. Its usage and values should be\n-\t\t\t\t\t\tpre-negotiated with any recipients.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Level of confidence\n- \n- This is a rarely used field in the specification that would\n-\t\t\t\t\t\tindicate the confidence in the location specified. See RFC7459\n-\t\t\t\t\t\tfor exact details.\n- Sub-parameters:\n- \n- \n- One of:\n- \n- \n- \n- \n- \n- \n- \n- A percentage indicating the confidence.\n- \n- \n- \n- \n- https://www.rfc-editor.org/rfc/rfc7459\n- \n- \n- \n- \n- \n- 16.29.0\n- 18.15.0\n- 19.7.0\n- \n- Profile\n- \n- Parameters for defining a Profile object\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Must be of type 'profile'.\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- PIDF-LO element to place this profile in\n- \n- \n- \n- \n- \n- \n- \n- Based on RFC5491 (see below) the recommended and default element\n-\t\t\t\t\t\t\tis\n- device\n- .\n- \n- \n- \n- https://www.rfc-editor.org/rfc/rfc5491.html#section-3.4\n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Reference to a location object\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Reference to a location object\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Reference to a location object\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- location specification type\n- \n- xxxx\n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Notes to be added to the outgoing PIDF-LO document\n- \n- \n- The specification of this parameter will cause a\n- <note-well>\n- element to be added to the\n-\t\t\t\t\t\toutgoing PIDF-LO document. Its usage should be pre-negotiated with\n-\t\t\t\t\t\tany recipients.\n- \n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Sets the value of the Geolocation-Routing header.\n- \n- \n- \n- 16.29.0\n- 18.15.0\n- 19.7.0\n- \n- Sets if empty Civic Address elements should be suppressed\n-\t\t\t\t\tfrom the PIDF-LO document.\n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Determine which profile on a channel should be used\n- \n- \n- \n- Use the incoming profile if it exists and has location information, otherwise use the\n-\t\t\t\t\t\t\tconfigured profile if it exists and has location information. If neither profile has location\n-\t\t\t\t\t\t\tinformation, nothing is sent.\n- \n- \n- Use the configured profile if it exists and has location information, otherwise use the\n-\t\t\t\t\t\t\tincoming profile if it exists and has location information. If neither profile has location\n-\t\t\t\t\t\t\tinformation, nothing is sent.\n- \n- \n- Discard any incoming profile and use the configured profile if it exists and\n-\t\t\t\t\t\t\tit has location information. If the configured profile doesn't exist or has no\n-\t\t\t\t\t\t\tlocation information, nothing is sent.\n- \n- \n- Discard any configured profile and use the incoming profile if it exists and\n-\t\t\t\t\t\t\tit has location information. If the incoming profile doesn't exist or has no\n-\t\t\t\t\t\t\tlocation information, nothing is sent.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- 16.28.0\n- 18.14.0\n- 19.6.0\n- \n- Get or Set a field in a geolocation profile\n- \n- \n- The profile parameter to operate on. The following fields from the\n-\t\t\t\tLocation and Profile objects are supported.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Additionally, the\n- inheritable\n- field may be\n-\t\t\t\tset to\n- true\n- or\n- false\n- to control\n-\t\t\t\twhether the profile will be passed to the outgoing channel.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- When used to set a parameter on a profile, if the profile doesn't already exist, a new\n-\t\tone will be created automatically.\n- \n- The\n- ${GEOLOCPROFILESTATUS}\n- channel variable will be set with\n-\t\ta return code indicating the result of the operation. Possible values are:\n- \n- \n- \n- Success\n- \n- \n- No or not enough parameters were supplied\n- \n- \n- There was an internal error finding or creating a profile\n- \n- \n- There was an issue specific to the parameter specified\n-\t\t\t(value not valid or parameter name not found, etc.)\n- \n- \n- \n- \n \n \n 12.0.0\n \n Qualify a chan_pjsip endpoint.\n \n \n@@ -44995,14 +43905,1104 @@\n only.\n \n \n \n \n \n \n+ \n+ Core Geolocation Support\n+ \n+ \n+ \n+ 16.29.0\n+ 18.15.0\n+ 19.7.0\n+ \n+ Location\n+ \n+ Parameters for defining a Location object\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Must be of type 'location'.\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Location specification type\n+ \n+ \n+ \n+ \n+ The\n+ location_info\n+ parameter must contain a comma separated list of IANA codes\n+\t\t\t\t\t\t\t\t\tor synonyms describing the civicAddress of this location.\n+\t\t\t\t\t\t\t\t\tThe IANA codes and synonyms can be obtained by executing\n+\t\t\t\t\t\t\t\t\tthe CLI command\n+ geoloc show civicAddr_mapping\n+ .\n+ \n+ \n+ \n+ \n+ The\n+ location_info\n+ parameter must contain a comma\n+\t\t\t\t\t\t\t\t\tseparated list valid GML elements describing this location.\n+ \n+ \n+ \n+ \n+ The\n+ location_info\n+ parameter must contain a single\n+\t\t\t\t\t\t\t\t\tURI parameter which contains an external URI describing this location.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Location information\n+ \n+ \n+ The contents of this parameter are specific to the\n+\t\t\t\t\t\t\tlocation\n+ format\n+ .\n+ \n+ \n+ \n+ location_info = country=US,A1=\"New York\",city_district=Manhattan,\n+\t\t\t\t\t\tA3=\"New York\", house_number=1633, street=46th, street_suffix = Street,\n+\t\t\t\t\t\tpostal_code=10222,floor=20,room=20A2\n+ \n+ \n+ location_info = Shape=Sphere, pos3d=\"39.12345 -105.98766 1920\", radius=200\n+ \n+ \n+ location_info = URI=https:/something.com?exten=${EXTEN}\n+ \n+ \n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Fully qualified host name\n+ \n+ \n+ This parameter isn't required but if provided, RFC8787 says it MUST be a fully\n+\t\t\t\t\t\tqualified host name. IP addresses are specifically NOT allowed. The value will be placed\n+\t\t\t\t\t\tin a\n+ loc-src\n+ parameter appended to the URI in the\n+ Geolocation\n+ header.\n+ \n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Location determination method\n+ \n+ This is a rarely used field in the specification that would\n+\t\t\t\t\t\tindicate the method used to determine the location. Its usage and values should be\n+\t\t\t\t\t\tpre-negotiated with any recipients.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Level of confidence\n+ \n+ This is a rarely used field in the specification that would\n+\t\t\t\t\t\tindicate the confidence in the location specified. See RFC7459\n+\t\t\t\t\t\tfor exact details.\n+ Sub-parameters:\n+ \n+ \n+ One of:\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ A percentage indicating the confidence.\n+ \n+ \n+ \n+ \n+ https://www.rfc-editor.org/rfc/rfc7459\n+ \n+ \n+ \n+ \n+ \n+ 16.29.0\n+ 18.15.0\n+ 19.7.0\n+ \n+ Profile\n+ \n+ Parameters for defining a Profile object\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Must be of type 'profile'.\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ PIDF-LO element to place this profile in\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Based on RFC5491 (see below) the recommended and default element\n+\t\t\t\t\t\t\tis\n+ device\n+ .\n+ \n+ \n+ \n+ https://www.rfc-editor.org/rfc/rfc5491.html#section-3.4\n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Reference to a location object\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Reference to a location object\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Reference to a location object\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ location specification type\n+ \n+ xxxx\n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Notes to be added to the outgoing PIDF-LO document\n+ \n+ \n+ The specification of this parameter will cause a\n+ <note-well>\n+ element to be added to the\n+\t\t\t\t\t\toutgoing PIDF-LO document. Its usage should be pre-negotiated with\n+\t\t\t\t\t\tany recipients.\n+ \n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Sets the value of the Geolocation-Routing header.\n+ \n+ \n+ \n+ 16.29.0\n+ 18.15.0\n+ 19.7.0\n+ \n+ Sets if empty Civic Address elements should be suppressed\n+\t\t\t\t\tfrom the PIDF-LO document.\n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Determine which profile on a channel should be used\n+ \n+ \n+ \n+ Use the incoming profile if it exists and has location information, otherwise use the\n+\t\t\t\t\t\t\tconfigured profile if it exists and has location information. If neither profile has location\n+\t\t\t\t\t\t\tinformation, nothing is sent.\n+ \n+ \n+ Use the configured profile if it exists and has location information, otherwise use the\n+\t\t\t\t\t\t\tincoming profile if it exists and has location information. If neither profile has location\n+\t\t\t\t\t\t\tinformation, nothing is sent.\n+ \n+ \n+ Discard any incoming profile and use the configured profile if it exists and\n+\t\t\t\t\t\t\tit has location information. If the configured profile doesn't exist or has no\n+\t\t\t\t\t\t\tlocation information, nothing is sent.\n+ \n+ \n+ Discard any configured profile and use the incoming profile if it exists and\n+\t\t\t\t\t\t\tit has location information. If the incoming profile doesn't exist or has no\n+\t\t\t\t\t\t\tlocation information, nothing is sent.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 16.28.0\n+ 18.14.0\n+ 19.6.0\n+ \n+ Get or Set a field in a geolocation profile\n+ \n+ \n+ The profile parameter to operate on. The following fields from the\n+\t\t\t\tLocation and Profile objects are supported.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Additionally, the\n+ inheritable\n+ field may be\n+\t\t\t\tset to\n+ true\n+ or\n+ false\n+ to control\n+\t\t\t\twhether the profile will be passed to the outgoing channel.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ When used to set a parameter on a profile, if the profile doesn't already exist, a new\n+\t\tone will be created automatically.\n+ \n+ The\n+ ${GEOLOCPROFILESTATUS}\n+ channel variable will be set with\n+\t\ta return code indicating the result of the operation. Possible values are:\n+ \n+ \n+ \n+ Success\n+ \n+ \n+ No or not enough parameters were supplied\n+ \n+ \n+ There was an internal error finding or creating a profile\n+ \n+ \n+ There was an issue specific to the parameter specified\n+\t\t\t(value not valid or parameter name not found, etc.)\n+ \n+ \n+ \n+ \n+ \n+ HTTP binding for the Stasis API\n+ \n+ \n+ \n+ 12.0.0\n+ \n+ General configuration settings\n+ \n+ \n+ 12.0.0\n+ \n+ Enable/disable the ARI module\n+ \n+ This option enables or disables the ARI module.\n+ \n+ \n+ ARI uses Asterisk's HTTP server, which must also be enabled in\n+ http.conf\n+ .\n+ \n+ \n+ \n+ \n+ http.conf\n+ https://docs.asterisk.org/Configuration/Core-Configuration/Asterisk-Builtin-mini-HTTP-Server/\n+ \n+ \n+ \n+ \n+ 11.11.0\n+ 12.4.0\n+ \n+ The timeout (in milliseconds) to set on WebSocket connections.\n+ \n+ If a websocket connection accepts input slowly, the timeout\n+\t\t\t\t\t\tfor writes to it can be increased to keep it from being disconnected.\n+\t\t\t\t\t\tValue is in milliseconds.\n+ \n+ \n+ \n+ \n+ 12.0.0\n+ \n+ Responses from ARI are formatted to be human readable\n+ \n+ \n+ \n+ 12.0.0\n+ \n+ Realm to use for authentication. Defaults to Asterisk REST Interface.\n+ \n+ \n+ \n+ 12.0.0\n+ \n+ Comma separated list of allowed origins, for Cross-Origin Resource Sharing. May be set to * to allow all origins.\n+ \n+ \n+ \n+ 14.2.0\n+ \n+ Comma separated list of channel variables to display in channel json.\n+ \n+ \n+ \n+ \n+ 12.0.0\n+ \n+ Per-user configuration settings\n+ \n+ \n+ 13.30.0\n+ 16.7.0\n+ 17.1.0\n+ \n+ Define this configuration section as a user.\n+ \n+ \n+ \n+ \n+ Configure this section as a\n+ user\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 13.30.0\n+ 16.7.0\n+ 17.1.0\n+ \n+ When set to yes, user is only authorized for read-only requests\n+ \n+ \n+ \n+ 13.30.0\n+ 16.7.0\n+ 17.1.0\n+ \n+ Crypted or plaintext password (see password_format)\n+ \n+ \n+ \n+ 12.0.0\n+ \n+ password_format may be set to plain (the default) or crypt. When set to crypt, crypt(3) is used to validate the password. A crypted password can be generated using mkpasswd -m sha-512. When set to plain, the password is in plaintext\n+ \n+ \n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ Outbound websocket configuration\n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ Must be \"outbound_websocket\".\n+ \n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ The ID of a connection defined in websocket_client.conf.\n+ \n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ Comma separated list of stasis applications that will use this websocket.\n+ \n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ The local ARI user to act as.\n+ \n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ Subscribe applications to all event\n+ \n+ \n+ \n+ \n+ \n+ STIR/SHAKEN module for Asterisk\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ STIR/SHAKEN attestation options\n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Globally disable verification\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ File path to a certificate\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ URL to the public certificate\n+ \n+ Must be a valid http, or https, URL.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Attestation level\n+ \n+ \n+ \n+ 20.12.0\n+ 21.7.0\n+ 22.2.0\n+ \n+ Attestation level to use for unknown TNs\n+ \n+ Normally if a callerid TN isn't configured in stir_shaken.conf\n+\t\t\t\t\tno Identity header will be created. If this option is set,\n+\t\t\t\t\thowever, an Identity header will be sent using this\n+\t\t\t\t\tattestation level. Since there's no TN object, you must\n+\t\t\t\t\tensure that a private_key_file and public_cert_url are\n+\t\t\t\t\tconfigured in the attestation or profile objects for\n+\t\t\t\t\tthis to work.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ On load, Retrieve all TN's certificates and validate their dates\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Send a media key (mky) grant in the attestation for DTLS calls.\n+\t\t\t\t\t(not common)\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ STIR/SHAKEN TN options\n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Must be of type 'tn'.\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ File path to a certificate\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ URL to the public certificate\n+ \n+ Must be a valid http, or https, URL.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Attestation level\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ On load, Retrieve all TN's certificates and validate their dates\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Send a media key (mky) grant in the attestation for DTLS calls.\n+\t\t\t\t\t(not common)\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ STIR/SHAKEN verification options\n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Globally disable verification\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ A boolean indicating whether trusted CA certificates should be loaded from the system\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Path to a file containing one or more CA certs in PEM format\n+ \n+ These certs are used to verify the chain of trust for the\n+\t\t\t\t\t\tcertificate retrieved from the X5U Identity header parameter. This\n+\t\t\t\t\t\tfile must have the root CA certificate, the certificate of the\n+\t\t\t\t\t\tissuer of the X5U certificate, and any intermediate certificates\n+\t\t\t\t\t\tbetween them.\n+ See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Path to a directory containing one or more hashed CA certs\n+ \n+ \n+ \n+ For this option, the individual certificates must be placed in\n+\t\t\t\t\t\tthe directory specified and hashed using the\n+ openssl rehash\n+ command.\n+ \n+ See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Path to a file containing one or more CRLs in PEM format\n+ \n+ If you with to check if the certificate in the X5U Identity header\n+\t\t\t\t\t\tparameter has been revoked, you'll need the certificate revocation\n+\t\t\t\t\t\tlist generated by the issuer.\n+ See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Path to a directory containing one or more hashed CRLs\n+ \n+ \n+ \n+ For this option, the individual CRLs must be placed in\n+\t\t\t\t\t\tthe directory specified and hashed using the\n+ openssl rehash\n+ command.\n+ \n+ See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Path to a file containing one or more untrusted cert in PEM format used to verify CRLs\n+ \n+ If you with to check if the certificate in the X5U Identity header\n+\t\t\t\t\tparameter has been revoked, you'll need the certificate revocation\n+\t\t\t\t\tlist generated by the issuer. Unfortunately, sometimes the CRLs are signed by a\n+\t\t\t\t\tdifferent CA than the certificate being verified. In this case, you\n+\t\t\t\t\tmay need to provide the untrusted certificate to verify the CRL.\n+ See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Path to a directory containing one or more hashed untrusted certs used to verify CRLs\n+ \n+ \n+ \n+ For this option, the individual certificates must be placed in\n+\t\t\t\t\t\tthe directory specified and hashed using the\n+ openssl rehash\n+ command.\n+ \n+ See https://docs.asterisk.org/Deployment/STIR-SHAKEN/ for more information.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Directory to cache retrieved verification certs\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Maximum time to wait to CURL certificates\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Number of seconds a cache entry may be behind current time\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Maximum size to use for caching public keys\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Number of seconds an iat grant may be behind current time\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Number of seconds a SIP Date header may be behind current time\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ The default failure action when not set on a profile\n+ \n+ \n+ \n+ \n+ If set to\n+ continue\n+ , continue and let\n+\t\t\t\t\t\t\tthe dialplan decide what action to take.\n+ \n+ \n+ \n+ \n+ If set to\n+ reject_request\n+ , reject the incoming\n+\t\t\t\t\t\t\trequest with response codes defined in RFC8224.\n+ \n+ \n+ \n+ \n+ If set to\n+ return_reason\n+ , continue to the\n+\t\t\t\t\t\t\tdialplan but add a\n+ Reason\n+ header to the sender in\n+\t\t\t\t\t\t\tthe next provisional response.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ RFC9410 uses the STIR protocol on Reason headers\n+\t\t\t\t\tinstead of the SIP protocol\n+ \n+ \n+ \n+ 20.15.0\n+ 21.10.0\n+ 22.5.0\n+ \n+ When set to true, will cause the verification process to not consider a\n+\t\t\t\t\t\tmissing or invalid SIP \"Date\" header to be a failure. This will make the\n+\t\t\t\t\t\tIAT the sole \"truth\" for Date in the verification process.\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Relaxes check for \"https\" and port 443 or 8443\n+\t\t\t\t\tin incoming Identity header x5u URLs.\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Relaxes check for query parameters, user/password, etc.\n+\t\t\t\t\tin incoming Identity header x5u URLs.\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ An existing ACL from acl.conf to use when checking\n+\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ An IP or subnet to permit when checking\n+\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ An IP or subnet to deny checking\n+\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ STIR/SHAKEN profile configuration options\n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Must be of type 'profile'.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 18.22.0\n+ 20.7.0\n+ 21.2.0\n+ \n+ Actions performed when an endpoint references this profile\n+ \n+ \n+ \n+ Don't do any STIR/SHAKEN processing.\n+ \n+ \n+ Attest on outgoing calls.\n+ \n+ \n+ Verify incoming calls.\n+ \n+ \n+ Attest outgoing calls and verify incoming calls.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ 16.15.0\n+ \n+ Gets the number of STIR/SHAKEN results or a specific STIR/SHAKEN value from a result on the channel.\n+ \n+ \n+ The index of the STIR/SHAKEN result to get. If only 'count' is passed in, gets the number of STIR/SHAKEN results instead.\n+ \n+ \n+ The value to get from the STIR/SHAKEN result. Only used when an index is passed in (instead of 'count'). Allowable values:\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ This function will either return the number of STIR/SHAKEN identities, or return information on the specified identity.\n+\t\t\tTo get the number of identities, just pass 'count' as the only parameter to the function. If you want to get information on a\n+\t\t\tspecific STIR/SHAKEN identity, you can get the number of identities and then pass an index as the first parameter and one of\n+\t\t\tthe values you would like to retrieve as the second parameter.\n+ same => n,NoOp(Number of STIR/SHAKEN identities: ${STIR_SHAKEN(count)})\n+\t\t\tsame => n,NoOp(Identity ${STIR_SHAKEN(0, identity)} has attestation level ${STIR_SHAKEN(0, attestation)})\n+ \n+ \n \n bluetooth\n no\n extended\n \n \n no\n"}]}]}]}]}]}