Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cf-dev] Response unknown Token: Rejecting CON-2.03 // cf-dev Digest, Vol 4, Issue 7

Matthias,
Thanks for your feedback, which makes sense Apparently, the Token is automatically set by the Library API, but for some reason, when it is received by the device, it has a length of zero!
Puzzling!!!

In a related issue, when sending a server command/query to the device, we cannot send it with a COAP code GET But somehow it goes through correctly as a PUT

Any reason, Californium would only support PUT but not GET for a device Query?
In the Query message, we set options URI-PATH, URI-PORT, ETAG, and TEXT PLAIN format

Kind regards,
Jamal Mouline

-----Original Message-----
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On Behalf Of cf-dev-request@xxxxxxxxxxx
Sent: Tuesday, November 11, 2014 12:00 PM
To: cf-dev@xxxxxxxxxxx
Subject: cf-dev Digest, Vol 4, Issue 7

Send cf-dev mailing list submissions to
	cf-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	https://dev.eclipse.org/mailman/listinfo/cf-dev
or, via email, send a message with subject or body 'help' to
	cf-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
	cf-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than "Re: Contents of cf-dev digest..."


Today's Topics:

   1. Re: Response unknown Token: Rejecting CON-2.03
      (Kovatsch  Matthias)


----------------------------------------------------------------------

Message: 1
Date: Mon, 10 Nov 2014 18:56:56 +0000
From: "Kovatsch  Matthias" <kovatsch@xxxxxxxxxxx>
To: "Californium (Cf) developer discussions" <cf-dev@xxxxxxxxxxx>
Subject: Re: [cf-dev] Response unknown Token: Rejecting CON-2.03
Message-ID:
	<55877B3AFB359744BA0F2140E36F52B52A40D564@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Looks like the token does not match the one used in the request. Best use Wireshark to confirm this.
Then check your CoAP implementation on the device, why does not mirror the token correctly.
If it does mirror it correctly, maybe something is wrong with your request. Always use the CoapClient to issue request. Only use the raw (advanced) Requests when you know what you are doing (they are not reusable for instance and you need a new instance for every request you issue).

Ciao
Matthias


From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On Behalf Of Jamal Mouline
Sent: Montag, 10. November 2014 06:02
To: cf-dev@xxxxxxxxxxx
Subject: [cf-dev] Response unknown Token: Rejecting CON-2.03

Hi there,
We are using CoAP Califormium library for a server implementation communicating with an IoT device The server sends a command/query to the device and receives a Valid acknowledgment from the device

However we are seeing an error message from the library: Response unknown Token: Rejecting CON-2.03 and would appreciate some "user guide" to interpret/take action of reported errors

best regards,
Jamal Mouline
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/cf-dev/attachments/20141110/1ef36249/attachment.html>

------------------------------

_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev

End of cf-dev Digest, Vol 4, Issue 7
************************************


Back to the top