Using Appro 3.0 for ONVIF

Mohammad Alam

Hi,

I am running Appro 3.0 on my target machine. I am not able to run ONVIF functionality present in Appro 3.0. While running boa server I am getting errors like

SOAP 1.2 fault: SOAP-ENV:Sender [no subcode]
"End of file or no input: Network is unreachable"
Detail: [no detail]

This message is coming while sending Hello message.

Am I missing something for running ONVIF?

Thanks

Alam

over 13 years ago

0 Mayank Agarwal over 13 years ago

Expert 2600 points

Hi,

I have sent a mail to Appro for version 3.0 of DM368IPNC software but i haven't heard from them so far.

From where did you get the updated version 3.0 of DM368IPNC software.

Thanks and Regards,

Mayank

0 Raghu Kudva over 13 years ago in reply to Mayank Agarwal

TI__Genius 11000 points

Mayank,

Can you check with your local FAE to get details of v3.0?

Regards,

Raghu

0 Barath Silvanlabs over 13 years ago

Prodigy 140 points

Hi Alam,

Can you please let us know the network setup of the camera and client machine. We would also like to know if the Hello functionality works if you connect the camera locally to a PC/Laptop (static IP).

0 Mohammad Alam over 13 years ago in reply to Barath Silvanlabs

Prodigy 100 points

Hi Barath,

Camera is running locally in static ip mode with dhcp disabled. Hello functionality is not working. soap_end_send() function present in soap_send___ns1__sendHello() returns with -1.

Here are the console logs. (It contains my debug prints also)

queue id:131076
queue id:0
queue id:32769
HASH_TABLE_SIZE = 254
server_port=80
[01/Jan/2000:06:53:25 +0000] boa: server version Boa/0.94.13
[01/Jan/2000:06:53:25 +0000] boa: server built Apr 17 2012 at 12:07:58.
[01/Jan/2000:06:53:25 +0000] boa: starting server pid=710, port 80
Starting ONVIF 
probe_thread created
hello_thr DISCOVERABLE
sending Hello *****
ip =10.100.207.206
IPAddr =http://10.100.207.206/onvif/services http://10.100.207.206/onvif/services
HwId=urn:uuid:1419d68a-1dd2-11b2-a105-00E00ADD0000
probe_thr DISCOVERABLE Mode 
Connect/reconnect to host='239.255.255.250' path='/' port=3702
ERROR soap_connect 
sending Hello failed *****
SOAP 1.2 fault: SOAP-ENV:Sender [no subcode]
"End of file or no input: Network is unreachable"
Detail: [no detail]
sending Hello *****
ip =10.100.207.206
IPAddr =http://10.100.207.206/onvif/services http://10.100.207.206/onvif/services
HwId=urn:uuid:1419d68a-1dd2-11b2-a105-00E00ADD0000
Connect/reconnect to host='239.255.255.250' path='/' port=3702
ERROR soap_connect 
sending Hello failed *****
SOAP 1.2 fault: SOAP-ENV:Sender [no subcode]
"End of file or no input: Network is unreachable"
Detail: [no detail]
sending Hello *****
ip =10.100.207.206
IPAddr =http://10.100.207.206/onvif/services http://10.100.207.206/onvif/services
HwId=urn:uuid:1419d68a-1dd2-11b2-a105-00E00ADD0000
Connect/reconnect to host='239.255.255.250' path='/' port=3702
ERROR soap_connect 
sending Hello failed *****
SOAP 1.2 fault: SOAP-ENV:Sender [no subcode]
"End of file or no input: Network is unreachable"
Detail: [no detail]
sending Hello *****
ip =10.100.207.206
IPAddr =http://10.100.207.206/onvif/services http://10.100.207.206/onvif/services
HwId=urn:uuid:1419d68a-1dd2-11b2-a105-00E00ADD0000
Connect/reconnect to host='239.255.255.250' path='/' port=3702
ERROR soap_connect 
sending Hello failed *****
SOAP 1.2 fault: SOAP-ENV:Sender [no subcode]
"End of file or no input: Network is unreachable"
Detail: [no detail]

Regards

Alam

0 Barath Silvanlabs over 13 years ago in reply to Mohammad Alam

Prodigy 140 points

Alam,

Can you please provide us the following details

- IP details of the IPNC camera using 'ifconfig -a' command

- routing information of the IPNC camera using 'route -n' command

- log of the full boot process till run level 5

- IP details of the client machine using ifconfig -a (Linux system) or ipconfig /all (Windows) commands

0 Mohammad Alam over 13 years ago in reply to Barath Silvanlabs

Prodigy 100 points

Hi Bharath,

I have connected my device directly with my Linux host machine. Device has proper IP and mac settings. Both can ping each other.

Where do you think the actual problem is?

Regards

Alam

0 Barath Silvanlabs over 13 years ago in reply to Mohammad Alam

Prodigy 140 points

Alam,

This problem will occur only when the network interface, to which Boa webserver is bound, is not configured before the boa webserver actually starts. In your case, since this network interface will ultimately come up, you will be able to ping the device.

We would also like you to kill Boa webserver once and start it manually and see if this error comes. Please send us the boot log of the camera after performing this operation.

0 Mohammad Alam over 13 years ago in reply to Barath Silvanlabs

Prodigy 100 points

Thanks Barath, I was missing Gateway settings. I set the gateway through console and restarted boa, it worked.

0 stevenyin over 13 years ago in reply to Barath Silvanlabs

Intellectual 440 points

hi Barath:

I use IPNC V3.0 REF, now open the onvif test tools 1.02, if I press "Discover Devices", it can get nothing. it can not discover my IPC, my IPC uses static IP(192.168.1.168), but if I fill "192.168.1.168" in "Device IP", and press "Probe", then can get response from my IPC, and display regarding infomations on the "Discovery" page, such as "IP, UUID", BRAND, and so on.

Could you give me some suggestions please ? Thanks

REGARDS

Steven

0 Barath Silvanlabs over 13 years ago in reply to stevenyin

Prodigy 140 points

Hi Stevenyin,

We are unable to reproduce the error. Some of the Device Discovery troubleshooting steps that you can follow are listed below:

1. There have been reported problems with discovery on computers with multiple network interface cards. Therefore it is recommended installing the test tool on computers with only one network interface card.

2. If you are using Windows Vista or higher, you need to stop Function Discovery Resource Publication windows service to make device discovery work properly. You can do this by executing following command: “net stop FDResPub”, or using Services console. (refer ONVIF Test Tool Installation Guide).

3. If all the above steps are taken care of and Discovery is still failing; ping the IPC from the system on which the ONVIF Test Tool is running, and check if "Discover Devices" is working now.

Processors

Processors forum

Using Appro 3.0 for ONVIF