Onvif Profile S conformance support for event test cases

[shivamverma-cmyk]

We are working on profile pass event related test cases using onvif tool version-25 but while running we are observing step-14 is getting failed

EVENT-2-1-17-v14.12 BASIC NOTIFICATION INTERFACE - NOTIFY

STEP 1 - Get Event service address
StepStart: 2025-10-06T08:50:24.1947535Z
Transmit done
Receive done
STEP PASSED

STEP 2 - Get Event Properties
StepStart: 2025-10-06T08:50:24.2628442Z
Transmit done
Receive done
STEP PASSED

Timeout of 60 seconds will be used

STEP 3 - Creating listening server
StepStart: 2025-10-06T08:50:24.3529832Z
STEP PASSED

STEP 4 - Send Subscribe request
StepStart: 2025-10-06T08:50:24.3725418Z
Transmit done
Receive done
STEP PASSED

STEP 5 - Check that the DUT returned Subscribe response
StepStart: 2025-10-06T08:50:28.3816764Z
STEP PASSED

STEP 6 - Check that CurrentTime is specified
StepStart: 2025-10-06T08:50:28.3853121Z
STEP PASSED

STEP 7 - Check that TerminationTime is specified
StepStart: 2025-10-06T08:50:28.3893387Z
STEP PASSED

STEP 8 - Check that TerminationTime and CurrentTime has reasonable values
StepStart: 2025-10-06T08:50:28.3932661Z
STEP PASSED

STEP 9 - Validate CurrentTime and TerminationTime
StepStart: 2025-10-06T08:50:28.3970537Z
STEP PASSED

STEP 10 - Check if the DUT returned SubscriptionReference
StepStart: 2025-10-06T08:50:28.3999823Z
STEP PASSED

STEP 11 - Check if SubscriptionReference contains address
StepStart: 2025-10-06T08:50:28.4101755Z
STEP PASSED

STEP 12 - Check that URL specified is valid
StepStart: 2025-10-06T08:50:28.4212346Z
STEP PASSED

STEP 13 - Set Synchronization Point
StepStart: 2025-10-06T08:50:28.4338223Z
Transmit done
Receive done
STEP PASSED

STEP 14 - Wait for notification
StepStart: 2025-10-06T08:50:28.518578Z
No notification received!
STEP FAILED

STEP 15 - Send Unsubscribe request
StepStart: 2025-10-06T08:50:48.5342679Z
Transmit done
Receive done
Failed to unsubscribe through request. Error received: A reply message was received for operation 'Unsubscribe' with action 'http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/UnsubscribeRequest'. However, your client code requires action 'http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/UnsubscribeResponse'.
STEP PASSED

STEP 16 - Wait until Subscription Manager is deleted by timeout
StepStart: 2025-10-06T08:50:48.6853557Z
STEP PASSED

TEST FAILED

We understand some notification we have to send from camera to test we tried sending notificaiton but still getting failure

oid send_notify(const char *consumer_url)
{
FILE *fp;
char curl_cmd[1024];
const char *xml_file = "/customer/cpcm/cpcm_bins/notify.xml";

snprintf(curl_cmd, sizeof(curl_cmd),
"/customer/cpcm/cpcm_bins/curl -X POST --connect-timeout 1 -m 2 "
"--limit-rate 100K %s "
"-H 'Content-Type: application/soap+xml; charset=utf-8; action="http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify\"' "
"-H 'User-Agent: gSOAP/2.8' "
"-d '@%s' &>/dev/null &",
consumer_url, xml_file);

fp = popen(curl_cmd, "r");
if (fp)
pclose(fp);
}
Notify.xml content
xml
Copy code

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa5="http://www.w3.org/2005/08/addressing"
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
xmlns:tt="http://www.onvif.org/ver10/schema">
SOAP-ENV:Header
wsa5:Tohttp://www.w3.org/2005/08/addressing/anonymous</wsa5:To>
wsa5:Actionhttp://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify</wsa5:Action>
wsa5:MessageIDuuid:12345678-1234-1234-1234-123456789abc</wsa5:MessageID>
</SOAP-ENV:Header>
SOAP-ENV:Body
wsnt:Notify
wsnt:NotificationMessage
<wsnt:Topic Dialect="http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet">
tns1:VideoSource/MotionAlarm
</wsnt:Topic>
wsnt:Message
<tt:Message UtcTime="2025-10-07T14:25:00Z" PropertyOperation="Changed">
tt:Source
<tt:SimpleItem Name="VideoSourceConfigurationToken" Value="VideoSource_1"/>
</tt:Source>
tt:Data
<tt:SimpleItem Name="State" Value="true"/>
</tt:Data>
</tt:Message>
</wsnt:Message>
</wsnt:NotificationMessage>
</wsnt:Notify>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

[madhurao68]

Duplicate of #107

[Sergey-Borodanov-GRSE]

Hi @shivamverma-cmyk,

We apologize for the delayed response, and thank you for your patience.

Thank you for the detailed report.

We have seen similar behavior before — a failure at Step 14 (Wait for notification) — when an incorrect network interface is selected in the Device Test Tool (DTT).

Suggested check

Please open DTT → first tab (Discovery) and verify that the active IPv4 interface (the one currently in use) is selected.

After selecting the correct IPv4 connection, the test normally proceeds without errors.

Note:
Please also make sure that your firewall settings do not block the required port.

If the issue persists

If selecting the correct interface does not resolve the problem, please provide:

• Full DTT logs
• A short video showing:
  • all tabs in DTT with all options
    (including Management, Conformance Test, Diagnostics)
  • current network interface configuration
  • steps performed during the test run

This will help us reproduce the issue and investigate it further.

Thanks again for reporting this — we’re looking forward to your feedback.

Best regards