Pelco Developer Network (PDN)

GetProfiles ONVIF request

Pelco ONVIF PTZ Profile

We are trying to integrate the Pelco cameras in our third party software, we are getting video in our software but when we try to access the PTZ profile we are not getting anything. Attached file is the response from Pelco camera . can you validate this...?.

Attached is the response from the Pelco camera for GetProfiles ONVIF request.

There is no class/prefix defined for 'pa' in the xml. As a result, the LoadXML function fails. This is the same reason due to which it fails in ODM as well.
If there is a prefix defined for 'pa' which is referenced in the XML everywhere, such as:
xmlns:pa="" in the SOAP envelope, there won't be a problem.

Thanks in Advance,


Vinaya N

Edit by PelcoChris to display attachment: PelcoResponse.txt

Hello there, thank you for your post!

That's an interesting find there. I'm sorry that I couldn't determine what camera model you were using to test with from the the xml information.

What camera are you using? What is the environment like? What firmware is it using?

If it isn't using the most current and updated firmware, that would be my first suggestion is to update the camera. It could be an issue that has been resolved with an update. It sounds very familiar to me, I think we encountered something similar with an ONVIF driver in VideoXpert for another non-Pelco camera.

If you are still having problems after trying this suggestion, please let me know the answers to these questions and we can proceed with additional troubleshooting.

Firmware is latest one only, still we are unable to access the PTZ profiles

Firmware Version:

Hardware Version:

Model Number:

Serial Number:

Thank you for the additional information.

I have this camera as well and I'm running the same firmware version too. I see that when I try to use the 'Profiles' link in ONVIF Device Manager, it comes up with an error:


I did some additional research and discovered that this specific issue had been discovered by the camera team. There has been some work done to correct it though the release with the fix has not happened yet. I'm trying to find out additional information about when the fix may be available. I will let you know when I hear back.

camera now responds with a 417 (Expectation Failed) error

We found one more issue. After upgrading the firmware of the camera, the camera now responds with a 417 (Expectation Failed) error. Earlier( firmware), it used to respond with an invalid XML response for the GetProfiles request (the unidentified 'pa' class).
Any hints on how to solve this issue?

Please allow me to restart to ensure I understand what you tried:

You downgraded the firmware from to to give that a try. Now, instead of having an issue with the specific part of the XML, the camera now responds with 417 Expectation Failed error to the GetProfiles request -- right?

My suggestion is to keep using for now. I did trade emails with members of camera engineering, and the fix for the 'pa' string is scheduled for release in the next firmware version - which is scheduled for release near the end of Q1 2018 (March time frame).

Typically issues with the products should go directly to Product Support via phone call or email, by the way. I had access to this camera here to try it out so I wanted to verify the behavior for you too. It may be necessary to communicate with our Product Support teams if there are problems that need to be reported to the camera team (that's the proper route).