Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

/api/v2/telephony/providers/edges Inconsistent Data Returned

  • 1.  /api/v2/telephony/providers/edges Inconsistent Data Returned

    Posted 06-05-2025 18:15

    Lloyd | 2019-09-29 19:35:01 UTC | #1

    We have multiple customers using the same type of edge devices and have been using /api/v2/telephony/providers/edges to query the devices to monitor health status as well as keep track of asset data, etc.

    This has been working fine for a year or so, however recently the API call has stopped returning model and sometimes stagedVersion.

    It will stop being returned for a week or two and then mysteriously/randomly start being returned again for the same devices without those devices rebooting/restarting/etc.

    Is there a reason for this?

    Here's some examples from today:

    Returning 'model':

    { "EdgeMetrics-callDrainingState": "NONE", "EdgeMetrics-conversationCount": "0", "EdgeMetrics-currentVersion": "1.0.0.17100300", "EdgeMetrics-dateCreated": "2019-02-13T04:52:40.484Z", "EdgeMetrics-dateModified": "2019-09-28T18:42:45.928Z", "EdgeMetrics-deviceId": "4b2e20d6-b640-4002-bcab-86f8743cdb74", "EdgeMetrics-deviceName": "***", "EdgeMetrics-deviceStatusCode": "ACTIVE", "EdgeMetrics-edgeDeploymentType": "HARDWARE", "EdgeMetrics-fullSoftwareVersion": "edgebin-1.0.0.8470.1909091804-w64r", "EdgeMetrics-healthStatus": "HEALTHY", "EdgeMetrics-model": "SlimJim-0X", "EdgeMetrics-onlineStatus": "ONLINE", "EdgeMetrics-osName": "Microsoft Windows Embedded 8 Standard", "EdgeMetrics-pairingId": "CVTH8-F43WC-RFRRG-9DCVC-7J9QT", "EdgeMetrics-physicalEdge": "True", "EdgeMetrics-serialNumber": "KSA3163547", "EdgeMetrics-siteName": "******", "EdgeMetrics-siteState": "active", "EdgeMetrics-softwareFullVersion": "edgebin-1.0.0.8470.1909091804-w64r", "EdgeMetrics-softwareStatusCurrent": "False", "EdgeMetrics-softwareStatusVersionCurrent": "True", "EdgeMetrics-softwareStatusVersionLatestRelease": "True", "EdgeMetrics-softwareVersion": "1.0.0.8470", "EdgeMetrics-softwareVersionConfiguration": "release", "EdgeMetrics-softwareVersionPlatform": "w64", "EdgeMetrics-softwareVersionTimestamp": "1909091804", "EdgeMetrics-stagedVersion": "1.0.0.17100300", "EdgeMetrics-version": "177" },

    Not returning' model':

    { "EdgeMetrics-callDrainingState": "NONE", "EdgeMetrics-conversationCount": "0", "EdgeMetrics-currentVersion": "1.0.0.16121500", "EdgeMetrics-dateCreated": "2017-10-09T00:26:27.870Z", "EdgeMetrics-dateModified": "2019-09-29T13:10:43.666Z", "EdgeMetrics-deviceId": "bd5ab880-3a66-43c1-91ef-cc113bcdecff", "EdgeMetrics-deviceName": "********", "EdgeMetrics-deviceStatusCode": "ACTIVE", "EdgeMetrics-edgeDeploymentType": "HARDWARE", "EdgeMetrics-fullSoftwareVersion": "edgebin-1.0.0.8470.1909091804-w64r", "EdgeMetrics-healthStatus": "HEALTHY", "EdgeMetrics-onlineStatus": "ONLINE", "EdgeMetrics-osName": "Microsoft Windows Embedded 8 Standard", "EdgeMetrics-pairingId": "9HYRC-7T9CH-K39NH-4CYTW-3DDHN", "EdgeMetrics-physicalEdge": "True", "EdgeMetrics-serialNumber": "2M27320070", "EdgeMetrics-siteName": "**********", "EdgeMetrics-siteState": "active", "EdgeMetrics-softwareFullVersion": "edgebin-1.0.0.8470.1909091804-w64r", "EdgeMetrics-softwareStatusCurrent": "False", "EdgeMetrics-softwareStatusVersionCurrent": "True", "EdgeMetrics-softwareStatusVersionLatestRelease": "True", "EdgeMetrics-softwareVersion": "1.0.0.8470", "EdgeMetrics-softwareVersionConfiguration": "release", "EdgeMetrics-softwareVersionPlatform": "w64", "EdgeMetrics-softwareVersionTimestamp": "1909091804", "EdgeMetrics-stagedVersion": "1.0.0.16121500", "EdgeMetrics-version": "2650" },

    Thanks Lloyd

    Lloyd | 2019-09-29 19:56:16 UTC | #2

    Just a note - JSON examples above are from my code; So they are the root nodes of the JSONreturned with EdgeMetrics- prefixed. But I've verified in the RAW JSON response from the API that the keys are missing.

    Also SerialNumber and ParingId have now missing for these edges as well; While other edges of the same type and software version are still reporting them

    tim.smith | 2019-09-30 15:17:57 UTC | #3

    Please open a case with PureCloud Care to investigate the missing data. Customer-specific data cannot be investigated via the forum.

    FWIW, the response contract for GET /api/v2/telephony/providers/edges doesn't actually document those properties as required, so it's possible that the answer may be that those properties aren't guaranteed to be included in the response. However, the behavior you're describing sounds more like a bug to me.

    Lloyd | 2019-10-01 21:28:47 UTC | #4

    Tim,

    Understood - Thanks for your guidance.

    Cheers Lloyd

    system | 2019-11-01 21:28:51 UTC | #5

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 6134



Related Content