GetPhysicalDeviceName error

[avc859587618170]

Hey gang.. I get a weird error when callling the "GetPhysicalDeviceName" endpoint. I'm passing it this payload:

{
      "device": "3136622132:rcd2cm2act81t:0.0.0.0:1"
}

And it returns this error: 500: checkserversidelogs

In the dmcc-error.log logs, I actually see the payload it wants to return, but it doesn't return it and there's an error above the payload. It looks like this:

<131>Oct 4 15:15:39 rcd1aesrel10t DmccMain[12441] -04:00 2024 152 1 com.avaya.aes | :ClearableQueuedExecutor-1: com.avaya.telrestsvc.telephony.service.callback.ha ndler.FunctionalEptGenericCBRH[38] ERROR - Response =<?xml version="1.0" encoding="UTF-8"?>
<GetPhysicalDeviceNameResponse xmlns="http://www.avaya.com/csta"><deviceType>station</deviceType><device>3136622132</device><name>Dave Test</name></GetPhysicalDeviceNameResponse>

Any insight would be appreciated!

Have a good day!

Dave

[flynn1]

There seems to be a bug on AES. I will open an MR when I regain access to the ticketing system.

[avc859587618170]

Thanks as always and have a good day!!

Dave

[avc878962129396]

Hi Dave,

It looks like you're encountering a server-side error when calling the GetPhysicalDeviceName endpoint, indicated by the 500: checkserversidelogs response. Since the error message suggests checking the server-side logs, look for any additional details in the dmcc-error.log file that might provide more context on the error. The specific error message just before your payload may contain clues about what's going wrong. Confirm that the device identifier (3136622132:rcd2cm2act81t:0.0.0.0:1) is valid and corresponds to an existing physical device in your system. An invalid or unrecognized device could lead to errors. These steps should help you diagnose and hopefully resolve the 500 error you're experiencing. If you discover any specific error messages in the logs, feel free to share them for more targeted assistance.

[avc859587618170]

Hi Dave,

It looks like you're encountering a server-side error when calling the GetPhysicalDeviceName endpoint, indicated by the 500: checkserversidelogs response. Since the error message suggests checking the server-side logs, look for any additional details in the dmcc-error.log file that might provide more context on the error. The specific error message just before your payload may contain clues about what's going wrong. Confirm that the device identifier (3136622132:rcd2cm2act81t:0.0.0.0:1) is valid and corresponds to an existing physical device in your system. An invalid or unrecognized device could lead to errors. These steps should help you diagnose and hopefully resolve the 500 error you're experiencing. If you discover any specific error messages in the logs, feel free to share them for more targeted assistance.

There's actually no error above the error that I posted above. That error I posted above is from the dmcc-error.log, and it's the only log entry for that time. The next line above it is from almost 5 hours earlier. It's just really weird that I can see the payload it built to return, it actually found the station and it was going to return the name, but then there's no other entries below that line. It never delivered the payload and it gave me that weird 500 error..

Thanks for the reply!

Dave

[flynn1]

Opened AES-34392 for this.

[avc859587618170]

Opened AES-34392 for this.

Thanks Martin!

Have a great weekend!

Dave