|Is the CoAP binding protocol not fully supported in OM2M? [message #1741763]
||Mon, 29 August 2016 11:00
| yoshida takuma
Registered: August 2016
I tried to create resources in OM2M using both HTTP and CoAP requests. For me HTTP worked fine, no Problem, but I am still confused about the CoAP protocol. And I have three questions, related to CoAP:
1) When I tried to send request directly to the address of mn-cse: coap://127.0.0.1:5684/......, I got an request failed, and I found that in mn-cse there is no server running coap port 5684. Is that the coap not fully supported in mn-cse?
2) My in-cse running coap port 5683 and mn-cse running coap port 5684 (based on the config file). I tried to send the coap request to create the contentInstance under DATA container: coap://127.0.0.1:5683/~/mn-cse/mn-name/APP/DATA. What I figured out is: The request first will come to in-cse because request send to port 5683, then the in-cse will process the request using CoAP Server class and Forward this request to mn-cse. At this Point, the poa address of mn-cse which using HTTP will be used as the Redirect URL for the retarget request to mn-cse, then the request will be sent to http://127.0.0.1:8282/~/mn-cse........ and when request comes to mn-cse, the process will be done using RestHttpServlet class, and resource will be created.
So what make me confused here is: I sent at the beginning coap request, but then the request was done using http because mn-cse is not able to receive coap request. Can anyone clarify me this point? If mn-cse not able to receive coap request, then I can not create the subscription under mn-cse using CoAP. Is it true?
3) Can I change the protocol using in poa address, default is http, and is it possible to change to coap?
Thank you in advanced!
[Updated on: Mon, 29 August 2016 11:00]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02490 seconds