{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.xQCyThMO/b1/asterisk_20.6.0~dfsg+~cs6.13.40431414-2_amd64.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.xQCyThMO/b2/asterisk_20.6.0~dfsg+~cs6.13.40431414-2_amd64.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -13,8 +13,8 @@\n 20ea9ddc27a7492a041ec89242f6ed7c 95548 comm optional asterisk-mp3_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n 2704a21a9682c758b3e4f209d031c859 67900 debug optional asterisk-mysql-dbgsym_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n c8c1b86c901afa9a46c42fdac90e0b59 91488 comm optional asterisk-mysql_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n 7d432198347c9f166942dbaec3041f63 1059048 debug optional asterisk-ooh323-dbgsym_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n 0600b1bdf46471b0bd8a9979065d74a2 403948 comm optional asterisk-ooh323_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n e5343c3af464953404843053f64df083 1375608 debug optional asterisk-tests-dbgsym_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n a6940c535420ef52bdfd4bc74d9832cc 590976 comm optional asterisk-tests_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n- 5d1639b663576e5d82365e0ef39be8aa 2417540 comm optional asterisk_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n+ 8742f2361ff7e132e43f4ca28eb468f4 2417596 comm optional asterisk_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb\n"}, {"source1": "asterisk_20.6.0~dfsg+~cs6.13.40431414-2_amd64.deb", "source2": "asterisk_20.6.0~dfsg+~cs6.13.40431414-2_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-01-30 10:42:08.000000 debian-binary\n -rw-r--r-- 0 0 0 8436 2024-01-30 10:42:08.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2408912 2024-01-30 10:42:08.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 2408968 2024-01-30 10:42:08.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": "@@ -35410,337 +35410,1233 @@\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+ Qualify a chan_pjsip endpoint.\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+ The endpoint you want to qualify.\n \n- \n- \n- \n- \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- 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+ 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- 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+ \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@@ -38643,1233 +39539,337 @@\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+ 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- \n- The endpoint you want to qualify.\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- 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+ \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- 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+ 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- \n- \n- \n- Provide final information about a contact list.\n- \n- \n- \n- \n- \n- \n- \n- \n+ \n \n bluetooth\n no\n extended\n \n \n no\n"}]}]}]}]}]}