https://devzone.nordicsemi.com/f/nordic-q-a/25124/openthread-coap---communication-initiated-by-serverHi, I&#39;m developing multiprotocol applications based on examples from Thread SDK: Proximity/CoAP server and BLE UART/CoAP client. All CoAP communication in this examples is initiated from client by sending requests, but I&#39;d like to have a possibilityen-USTelligent Community 13Tue, 23 Apr 2019 20:46:43 GMThttps://devzone.nordicsemi.com/thread/183269?ContentTypeID=1Tue, 23 Apr 2019 20:46:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bbc0b3b2-fa4e-46a8-acb1-e1c32951940cAchim Kraus<p>With 2 years delay :-)</p> <p>CoAP defines the message in a way, that it is very easy to implement a client and a server even on the same socket! If the used library supports that, depend on the libraries developer. Standards as LWM2M from the OMA are using that feature.</p> <p>If it works in your network environment is a different question and it&#39;s mostly the one, which denies that approach. In many case &quot;some NATs&quot; are on the way, and they usually close the IP-route back after a few seconds without traffic. With that, you can usually reach your client only within a few seconds after the client reached your server.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/98959?ContentTypeID=1Wed, 13 Sep 2017 15:02:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b3daefb5-364d-4016-83f9-1dd73e66998bJ&#248;rgen Holmefjord<p>You can&#39;t really do that, as the server/client architecture of CoAP is based on request/response operations. If you setup CoAP resources on the client, you are basically making it a SoAP server. What is the problem you are facing when trying to do this?</p><div style="clear:both;"></div>