{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.KmUTj2y2/b1/asterisk_22.1.0~dfsg+~cs6.14.60671435-1_amd64.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.KmUTj2y2/b2/asterisk_22.1.0~dfsg+~cs6.14.60671435-1_amd64.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -13,8 +13,8 @@\n f5f36f50a4521a71e79985da0bdce6eb 78168 comm optional asterisk-mp3_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n 83c6deafbcc677d1c86e2ca915bc913b 69592 debug optional asterisk-mysql-dbgsym_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n 015c41b80293786f3a070ae269a6c838 74352 comm optional asterisk-mysql_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n 0c44b67b9e81a74eab9f91a826c94e96 1070564 debug optional asterisk-ooh323-dbgsym_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n 51ff47ab88bfe1d584a4e8b348234a33 386988 comm optional asterisk-ooh323_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n db9ecbc61b32216da50e1603bf9efa5a 1376404 debug optional asterisk-tests-dbgsym_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n 11e5ca7facf7cf8b4cb370bd57929968 581000 comm optional asterisk-tests_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n- bf59b10bb89a135e39412be2bcd10f05 2404832 comm optional asterisk_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n+ 2e5ab335c317f24db9018922317055b9 2404800 comm optional asterisk_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb\n"}, {"source1": "asterisk_22.1.0~dfsg+~cs6.14.60671435-1_amd64.deb", "source2": "asterisk_22.1.0~dfsg+~cs6.14.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 2024-11-27 11:37:42.000000 debian-binary\n -rw-r--r-- 0 0 0 8292 2024-11-27 11:37:42.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2396348 2024-11-27 11:37:42.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 2396316 2024-11-27 11:37:42.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": "@@ -25458,40 +25458,14 @@\n \n \n core\n \n \n core\n \n- \n- Set the channel group name for log filtering on this channel\n- \n- \n- Channel log group name. Leave empty to remove any existing group membership.\n- You can use any arbitrary alphanumeric name that can then be used by the\n-\t\t\t\t"logger filter changroup" CLI command to filter dialplan output by group name.\n- \n- \n- \n- Assign a channel to a group for log filtering.\n- Because this application can result in dialplan execution logs\n-\t\t\tbeing suppressed (or unsuppressed) from the CLI if filtering is active,\n-\t\t\tit is recommended to call this as soon as possible when dialplan execution begins.\n- Calling this multiple times will replace any previous group assignment.\n- exten => s,1,Set(LOG_GROUP()=test)\n-\t\t\t\tsame => n,NoOp() ; if a logging call ID group filter name is enabled but test is not included, you will not see this\n- exten => s,1,Set(LOG_GROUP()=important)\n-\t\t\t\tsame => n,Set(foo=bar) ; do some important things to show on the CLI (assuming it is filtered with important enabled)\n-\t\t\t\tsame => n,Set(LOG_GROUP()=) ; remove from group important to stop showing execution on the CLI\n-\t\t\t\tsame => n,Wait(5) ; do some unimportant stuff\n- \n- \n- Log\n- \n- \n \n Keepalive command.\n \n \n \n \n A 'Ping' action will elicit a 'Pong' response. Used to keep the\n@@ -27147,14 +27121,40 @@\n \n \n \n PresenceState\n \n \n \n+ \n+ Set the channel group name for log filtering on this channel\n+ \n+ \n+ Channel log group name. Leave empty to remove any existing group membership.\n+ You can use any arbitrary alphanumeric name that can then be used by the\n+\t\t\t\t"logger filter changroup" CLI command to filter dialplan output by group name.\n+ \n+ \n+ \n+ Assign a channel to a group for log filtering.\n+ Because this application can result in dialplan execution logs\n+\t\t\tbeing suppressed (or unsuppressed) from the CLI if filtering is active,\n+\t\t\tit is recommended to call this as soon as possible when dialplan execution begins.\n+ Calling this multiple times will replace any previous group assignment.\n+ exten => s,1,Set(LOG_GROUP()=test)\n+\t\t\t\tsame => n,NoOp() ; if a logging call ID group filter name is enabled but test is not included, you will not see this\n+ exten => s,1,Set(LOG_GROUP()=important)\n+\t\t\t\tsame => n,Set(foo=bar) ; do some important things to show on the CLI (assuming it is filtered with important enabled)\n+\t\t\t\tsame => n,Set(LOG_GROUP()=) ; remove from group important to stop showing execution on the CLI\n+\t\t\t\tsame => n,Wait(5) ; do some unimportant stuff\n+ \n+ \n+ Log\n+ \n+ \n \n extended\n \n \n core\n \n \n@@ -34017,1840 +34017,14 @@\n \n \n \n \n \n extended\n \n- \n- Core Geolocation Support\n- \n- \n- Location\n- \n- Parameters for defining a Location object\n- \n- \n- Must be of type 'location'.\n- \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- 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- 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- 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- 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- Profile\n- \n- Parameters for defining a Profile object\n- \n- \n- Must be of type 'profile'.\n- \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- Reference to a location object\n- \n- \n- Reference to a location object\n- \n- \n- Reference to a location object\n- \n- \n- location specification type\n- \n- xxxx\n- \n- \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- Sets the value of the Geolocation-Routing header.\n- \n- \n- Sets if empty Civic Address elements should be suppressed\n-\t\t\t\t\tfrom the PIDF-LO document.\n- \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- 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- STIR/SHAKEN module for Asterisk\n- \n- \n- STIR/SHAKEN attestation options\n- \n- Globally disable verification\n- \n- \n- File path to a certificate\n- \n- \n- URL to the public certificate\n- \n- Must be a valid http, or https, URL.\n- \n- \n- \n- Attestation level\n- \n- \n- On load, Retrieve all TN's certificates and validate their dates\n- \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- STIR/SHAKEN TN options\n- \n- Must be of type 'tn'.\n- \n- \n- File path to a certificate\n- \n- \n- URL to the public certificate\n- \n- Must be a valid http, or https, URL.\n- \n- \n- \n- Attestation level\n- \n- \n- On load, Retrieve all TN's certificates and validate their dates\n- \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- STIR/SHAKEN verification options\n- \n- Globally disable verification\n- \n- \n- A boolean indicating whether trusted CA certificates should be loaded from the system\n- \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- 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- 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- 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- 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- 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- Directory to cache retrieved verification certs\n- \n- \n- Maximum time to wait to CURL certificates\n- \n- \n- Number of seconds a cache entry may be behind current time\n- \n- \n- Maximum size to use for caching public keys\n- \n- \n- Number of seconds an iat grant may be behind current time\n- \n- \n- Number of seconds a SIP Date header may be behind current time\n- \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- RFC9410 uses the STIR protocol on Reason headers\n-\t\t\t\t\tinstead of the SIP protocol\n- \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- Relaxes check for query parameters, user/password, etc.\n-\t\t\t\t\tin incoming Identity header x5u URLs.\n- \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- An IP or subnet to permit when checking\n-\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n- \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- STIR/SHAKEN profile configuration options\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- 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- 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- Qualify a chan_pjsip endpoint.\n- \n- \n- \n- The endpoint you want to qualify.\n- \n- \n- \n- Qualify a chan_pjsip endpoint.\n- \n- \n- \n- \n- Provide details about an identify section.\n- \n- \n- The object's type. This will always be 'identify'.\n- \n- \n- The name of this object.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- The name of the endpoint associated with this information.\n- \n- \n- \n- \n- \n- \n- Provide details about an Address of Record (AoR) section.\n- \n- \n- The object's type. This will always be 'aor'.\n- \n- \n- The name of this object.\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- \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- The total number of contacts associated with this AoR.\n- \n- \n- The number of non-permanent contacts associated with this AoR.\n- \n- \n- The name of the endpoint associated with this information.\n- \n- \n- \n- \n- \n- \n- Provide details about an authentication section.\n- \n- \n- The object's type. This will always be 'auth'.\n- \n- \n- The name of this object.\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- \n- \n- The name of the endpoint associated with this information.\n- \n- \n- \n- \n- \n- \n- Provide details about an authentication section.\n- \n- \n- The object's type. This will always be 'transport'.\n- \n- \n- The name of this object.\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- \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- \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- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- The name of the endpoint associated with this information.\n- \n- \n- \n- \n- \n- \n- Provide details about an endpoint section.\n- \n- \n- The object's type. This will always be 'endpoint'.\n- \n- \n- The name of this object.\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- \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- \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- \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- \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- \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- \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- \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- \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- \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- \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- \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- \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- \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- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- The aggregate device state for this endpoint.\n- \n- \n- The number of active channels associated with this endpoint.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Provide details about an Address of Record (AoR) section.\n- \n- \n- The object's type. This will always be 'aor'.\n- \n- \n- The name of this object.\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- \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- Provide details about an Address of Record (Auth) section.\n- \n- \n- The object's type. This will always be 'auth'.\n- \n- \n- The name of this object.\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- \n- \n- \n- \n- \n- \n- Provide details about a contact section.\n- \n- \n- The object's type. This will always be 'contact'.\n- \n- \n- The name of this object.\n- \n- \n- IP address of the last Via header in REGISTER request.\n-\t\t\t\t\tWill only appear in the event if available.\n- \n- \n- Port number of the last Via header in REGISTER request.\n-\t\t\t\t\tWill only appear in the event if available.\n- \n- \n- The elapsed time in decimal seconds after which an OPTIONS\n-\t\t\t\t\tmessage is sent before the contact is considered unavailable.\n- \n- \n- Content of the Call-ID header in REGISTER request.\n-\t\t\t\t\tWill only appear in the event if available.\n- \n- \n- Asterisk Server name.\n- \n- \n- If true delete the contact on Asterisk restart/boot.\n- \n- \n- The Path header received on the REGISTER.\n- \n- \n- The name of the endpoint associated with this information.\n- \n- \n- A boolean indicating whether a qualify should be authenticated.\n- \n- \n- This contact's URI.\n- \n- \n- The interval in seconds at which the contact will be qualified.\n- \n- \n- Content of the User-Agent header in REGISTER request\n- \n- \n- Absolute time that this contact is no longer valid after\n- \n- \n- The contact's outbound proxy.\n- \n- \n- This contact's status.\n- \n- \n- \n- \n- \n- \n- \n- \n- The round trip time in microseconds.\n- \n- \n- \n- \n- \n- \n- Provide details about a contact's status.\n- \n- \n- The AoR that owns this contact.\n- \n- \n- This contact's URI.\n- \n- \n- This contact's status.\n- \n- \n- \n- \n- \n- \n- \n- \n- The round trip time in microseconds.\n- \n- \n- The name of the endpoint associated with this information.\n- \n- \n- Content of the User-Agent header in REGISTER request\n- \n- \n- Absolute time that this contact is no longer valid after\n- \n- \n- IP address:port of the last Via header in REGISTER request.\n-\t\t\t\t\tWill only appear in the event if available.\n- \n- \n- Content of the Call-ID header in REGISTER request.\n-\t\t\t\t\tWill only appear in the event if available.\n- \n- \n- The sorcery ID of the contact.\n- \n- \n- A boolean indicating whether a qualify should be authenticated.\n- \n- \n- The contact's outbound proxy.\n- \n- \n- The Path header received on the REGISTER.\n- \n- \n- The interval in seconds at which the contact will be qualified.\n- \n- \n- The elapsed time in decimal seconds after which an OPTIONS\n-\t\t\t\t\tmessage is sent before the contact is considered unavailable.\n- \n- \n- \n- \n- \n- \n- Provide details about a contact's status.\n- \n- \n- The object's type. This will always be 'endpoint'.\n- \n- \n- The name of this object.\n- \n- \n- The transport configurations associated with this endpoint.\n- \n- \n- The aor configurations associated with this endpoint.\n- \n- \n- The inbound authentication configurations associated with this endpoint.\n- \n- \n- The outbound authentication configurations associated with this endpoint.\n- \n- \n- The aggregate device state for this endpoint.\n- \n- \n- The number of active channels associated with this endpoint.\n- \n- \n- \n- \n- \n- Lists PJSIP endpoints.\n- \n- \n- \n- Provides a listing of all endpoints. For each endpoint an\n- EndpointList\n- event\n-\t\t\tis raised that contains relevant attributes and status information. Once all\n-\t\t\tendpoints have been listed an\n- EndpointListComplete\n- event is issued.\n- \n- \n- \n- \n- \n- \n- \n- \n- Provide final information about an endpoint list.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Detail listing of an endpoint and its objects.\n- \n- \n- \n- The endpoint to list.\n- \n- \n- \n- \n- Provides a detailed listing of options for a given endpoint. Events are issued\n-\t\t\tshowing the configuration and status of the endpoint and associated objects. These\n-\t\t\tevents include\n- EndpointDetail\n- ,\n- AorDetail\n- ,\n- AuthDetail\n- ,\n- TransportDetail\n- , and\n- IdentifyDetail\n- . Some events may be listed multiple times if multiple objects are\n-\t\t\tassociated (for instance AoRs). Once all detail events have been raised a final\n- EndpointDetailComplete\n- event is issued.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Provide final information about endpoint details.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Lists PJSIP AORs.\n- \n- \n- \n- Provides a listing of all AORs. For each AOR an\n- AorList\n- event\n-\t\t\tis raised that contains relevant attributes and status information. Once all\n-\t\t\taors have been listed an\n- AorListComplete\n- event is issued.\n- \n- \n- \n- \n- \n- \n- \n- \n- Provide final information about an aor list.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Lists PJSIP Auths.\n- \n- \n- \n- Provides a listing of all Auths. For each Auth an\n- AuthList\n- event\n-\t\t\tis raised that contains relevant attributes and status information. Once all\n-\t\t\tauths have been listed an\n- AuthListComplete\n- event is issued.\n- \n- \n- \n- \n- \n- \n- \n- \n- Provide final information about an auth list.\n- \n- \n- \n- \n- \n- \n- \n- \n- \n- Lists PJSIP Contacts.\n- \n- \n- \n- Provides a listing of all Contacts. For each Contact a\n- ContactList\n- event is raised that contains relevant attributes and status information.\n-\t\t\tOnce all contacts have been listed a\n- ContactListComplete\n- event\n-\t\t\tis issued.\n- \n- \n- \n- \n- \n- \n- \n- \n- Provide final information about a contact list.\n- \n- \n- \n- \n- \n- \n- \n- \n \n SIP Resource using PJProject\n \n \n Endpoint\n \n \n@@ -38802,14 +36976,1840 @@\n \t\t\t\t\t\tendpoint, instead of simply those that have already been negotiated.\n \t\t\t\t\t\tRFC 3261 specifies this as a SHOULD requirement.\n \n \n \n \n \n+ \n+ Qualify a chan_pjsip endpoint.\n+ \n+ \n+ \n+ The endpoint you want to qualify.\n+ \n+ \n+ \n+ Qualify a chan_pjsip endpoint.\n+ \n+ \n+ \n+ \n+ Provide details about an identify section.\n+ \n+ \n+ The object's type. This will always be 'identify'.\n+ \n+ \n+ The name of this object.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ The name of the endpoint associated with this information.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about an Address of Record (AoR) section.\n+ \n+ \n+ The object's type. This will always be 'aor'.\n+ \n+ \n+ The name of this object.\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+ \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+ The total number of contacts associated with this AoR.\n+ \n+ \n+ The number of non-permanent contacts associated with this AoR.\n+ \n+ \n+ The name of the endpoint associated with this information.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about an authentication section.\n+ \n+ \n+ The object's type. This will always be 'auth'.\n+ \n+ \n+ The name of this object.\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+ \n+ \n+ The name of the endpoint associated with this information.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about an authentication section.\n+ \n+ \n+ The object's type. This will always be 'transport'.\n+ \n+ \n+ The name of this object.\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+ \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+ \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+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ The name of the endpoint associated with this information.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about an endpoint section.\n+ \n+ \n+ The object's type. This will always be 'endpoint'.\n+ \n+ \n+ The name of this object.\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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \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+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ The aggregate device state for this endpoint.\n+ \n+ \n+ The number of active channels associated with this endpoint.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about an Address of Record (AoR) section.\n+ \n+ \n+ The object's type. This will always be 'aor'.\n+ \n+ \n+ The name of this object.\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+ \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+ Provide details about an Address of Record (Auth) section.\n+ \n+ \n+ The object's type. This will always be 'auth'.\n+ \n+ \n+ The name of this object.\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+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about a contact section.\n+ \n+ \n+ The object's type. This will always be 'contact'.\n+ \n+ \n+ The name of this object.\n+ \n+ \n+ IP address of the last Via header in REGISTER request.\n+\t\t\t\t\tWill only appear in the event if available.\n+ \n+ \n+ Port number of the last Via header in REGISTER request.\n+\t\t\t\t\tWill only appear in the event if available.\n+ \n+ \n+ The elapsed time in decimal seconds after which an OPTIONS\n+\t\t\t\t\tmessage is sent before the contact is considered unavailable.\n+ \n+ \n+ Content of the Call-ID header in REGISTER request.\n+\t\t\t\t\tWill only appear in the event if available.\n+ \n+ \n+ Asterisk Server name.\n+ \n+ \n+ If true delete the contact on Asterisk restart/boot.\n+ \n+ \n+ The Path header received on the REGISTER.\n+ \n+ \n+ The name of the endpoint associated with this information.\n+ \n+ \n+ A boolean indicating whether a qualify should be authenticated.\n+ \n+ \n+ This contact's URI.\n+ \n+ \n+ The interval in seconds at which the contact will be qualified.\n+ \n+ \n+ Content of the User-Agent header in REGISTER request\n+ \n+ \n+ Absolute time that this contact is no longer valid after\n+ \n+ \n+ The contact's outbound proxy.\n+ \n+ \n+ This contact's status.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ The round trip time in microseconds.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about a contact's status.\n+ \n+ \n+ The AoR that owns this contact.\n+ \n+ \n+ This contact's URI.\n+ \n+ \n+ This contact's status.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ The round trip time in microseconds.\n+ \n+ \n+ The name of the endpoint associated with this information.\n+ \n+ \n+ Content of the User-Agent header in REGISTER request\n+ \n+ \n+ Absolute time that this contact is no longer valid after\n+ \n+ \n+ IP address:port of the last Via header in REGISTER request.\n+\t\t\t\t\tWill only appear in the event if available.\n+ \n+ \n+ Content of the Call-ID header in REGISTER request.\n+\t\t\t\t\tWill only appear in the event if available.\n+ \n+ \n+ The sorcery ID of the contact.\n+ \n+ \n+ A boolean indicating whether a qualify should be authenticated.\n+ \n+ \n+ The contact's outbound proxy.\n+ \n+ \n+ The Path header received on the REGISTER.\n+ \n+ \n+ The interval in seconds at which the contact will be qualified.\n+ \n+ \n+ The elapsed time in decimal seconds after which an OPTIONS\n+\t\t\t\t\tmessage is sent before the contact is considered unavailable.\n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide details about a contact's status.\n+ \n+ \n+ The object's type. This will always be 'endpoint'.\n+ \n+ \n+ The name of this object.\n+ \n+ \n+ The transport configurations associated with this endpoint.\n+ \n+ \n+ The aor configurations associated with this endpoint.\n+ \n+ \n+ The inbound authentication configurations associated with this endpoint.\n+ \n+ \n+ The outbound authentication configurations associated with this endpoint.\n+ \n+ \n+ The aggregate device state for this endpoint.\n+ \n+ \n+ The number of active channels associated with this endpoint.\n+ \n+ \n+ \n+ \n+ \n+ Lists PJSIP endpoints.\n+ \n+ \n+ \n+ Provides a listing of all endpoints. For each endpoint an\n+ EndpointList\n+ event\n+\t\t\tis raised that contains relevant attributes and status information. Once all\n+\t\t\tendpoints have been listed an\n+ EndpointListComplete\n+ event is issued.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide final information about an endpoint list.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Detail listing of an endpoint and its objects.\n+ \n+ \n+ \n+ The endpoint to list.\n+ \n+ \n+ \n+ \n+ Provides a detailed listing of options for a given endpoint. Events are issued\n+\t\t\tshowing the configuration and status of the endpoint and associated objects. These\n+\t\t\tevents include\n+ EndpointDetail\n+ ,\n+ AorDetail\n+ ,\n+ AuthDetail\n+ ,\n+ TransportDetail\n+ , and\n+ IdentifyDetail\n+ . Some events may be listed multiple times if multiple objects are\n+\t\t\tassociated (for instance AoRs). Once all detail events have been raised a final\n+ EndpointDetailComplete\n+ event is issued.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide final information about endpoint details.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Lists PJSIP AORs.\n+ \n+ \n+ \n+ Provides a listing of all AORs. For each AOR an\n+ AorList\n+ event\n+\t\t\tis raised that contains relevant attributes and status information. Once all\n+\t\t\taors have been listed an\n+ AorListComplete\n+ event is issued.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide final information about an aor list.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Lists PJSIP Auths.\n+ \n+ \n+ \n+ Provides a listing of all Auths. For each Auth an\n+ AuthList\n+ event\n+\t\t\tis raised that contains relevant attributes and status information. Once all\n+\t\t\tauths have been listed an\n+ AuthListComplete\n+ event is issued.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide final information about an auth list.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Lists PJSIP Contacts.\n+ \n+ \n+ \n+ Provides a listing of all Contacts. For each Contact a\n+ ContactList\n+ event is raised that contains relevant attributes and status information.\n+\t\t\tOnce all contacts have been listed a\n+ ContactListComplete\n+ event\n+\t\t\tis issued.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ Provide final information about a contact list.\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ STIR/SHAKEN module for Asterisk\n+ \n+ \n+ STIR/SHAKEN attestation options\n+ \n+ Globally disable verification\n+ \n+ \n+ File path to a certificate\n+ \n+ \n+ URL to the public certificate\n+ \n+ Must be a valid http, or https, URL.\n+ \n+ \n+ \n+ Attestation level\n+ \n+ \n+ On load, Retrieve all TN's certificates and validate their dates\n+ \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+ STIR/SHAKEN TN options\n+ \n+ Must be of type 'tn'.\n+ \n+ \n+ File path to a certificate\n+ \n+ \n+ URL to the public certificate\n+ \n+ Must be a valid http, or https, URL.\n+ \n+ \n+ \n+ Attestation level\n+ \n+ \n+ On load, Retrieve all TN's certificates and validate their dates\n+ \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+ STIR/SHAKEN verification options\n+ \n+ Globally disable verification\n+ \n+ \n+ A boolean indicating whether trusted CA certificates should be loaded from the system\n+ \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+ 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+ 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+ 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+ 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+ 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+ Directory to cache retrieved verification certs\n+ \n+ \n+ Maximum time to wait to CURL certificates\n+ \n+ \n+ Number of seconds a cache entry may be behind current time\n+ \n+ \n+ Maximum size to use for caching public keys\n+ \n+ \n+ Number of seconds an iat grant may be behind current time\n+ \n+ \n+ Number of seconds a SIP Date header may be behind current time\n+ \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+ RFC9410 uses the STIR protocol on Reason headers\n+\t\t\t\t\tinstead of the SIP protocol\n+ \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+ Relaxes check for query parameters, user/password, etc.\n+\t\t\t\t\tin incoming Identity header x5u URLs.\n+ \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+ An IP or subnet to permit when checking\n+\t\t\t\t\thostnames in incoming Identity header x5u URLs.\n+ \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+ STIR/SHAKEN profile configuration options\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+ 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+ 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+ Core Geolocation Support\n+ \n+ \n+ Location\n+ \n+ Parameters for defining a Location object\n+ \n+ \n+ Must be of type 'location'.\n+ \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+ 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+ 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+ 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+ 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+ Profile\n+ \n+ Parameters for defining a Profile object\n+ \n+ \n+ Must be of type 'profile'.\n+ \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+ Reference to a location object\n+ \n+ \n+ Reference to a location object\n+ \n+ \n+ Reference to a location object\n+ \n+ \n+ location specification type\n+ \n+ xxxx\n+ \n+ \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+ Sets the value of the Geolocation-Routing header.\n+ \n+ \n+ Sets if empty Civic Address elements should be suppressed\n+\t\t\t\t\tfrom the PIDF-LO document.\n+ \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+ 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 bluetooth\n no\n extended\n \n \n no\n"}]}]}]}]}]}