I have a temperature, humidity and pressure sensor working over the LoRaWAN , I can get the read with the phone by NFC.
Also, I have some Arduino projects working with esp32 and RFM9X(Lora) boards to exchange data between the radio modules.
I want to sniff the LoraWAN packages that exchange between radio boards or between the sensor and another device
How I can do that by Wireshark??
I already have cc2531usb dongle I am using it for ZigBee packets , can i use it for Lora and how?
In order to capture LoRaWAN uplink messages, you need a LoRaWAN gateway. In order to capture downlink messages, you need an end device. The difference between UL and DL messages is that DL is sent with inverse polarization. This is why sniffing LoRaWAN messages is not so easy.
The easiest way to see what is going on between a LoRaWAN end device and a network is to use a packet logger that is usually provided by a network server.
One of the best packet logger is Actility's Wireless Logger, that you can try on the ThingPark Community portal.
Related
I am trying to build a LoRaWAN-based sensor network. These sensors communicate their data through the LoRaWAN protocol to the gateway which forwards these data to an application server through the MQTT protocol and in the other way around.
The communication has to be done from the sensors to the server and from the server to the sensors. However, things get tough at the gateway level since the message from the sensors to the server and the message from the server to the sensors can arrive at any time and my LoRaWAN module (the RN2483 from Microchip) cannot be on listening and sending mode at the same time. Hence, if I try to forward the message from the server to the sensors, the LoRaWAN packet sent by the sensors will be lost.
Do you have protocol ideas or literature suggestion for efficiently sharing the LoRaWAN module between listening and sending mode?
Thank you all and have a nice day.
I strongly recommend you to read LoRaWAN specification carefully. The LoRaWAN (not LoRa P2P model) has 3 types device, class A, B and C. RN2483 is one of class A devices, it will always have 2 receive windows (RX1, RX2) which last for 1 second long each after sending the message to gateway (uplink). You may use this feature to schedule your downlink messages. And the LoRaWAN server and LoRaWAN app server will handle the downlink issue (e.g., when to send downlink, immediately or one by one).
What is the difference between Jackdaw and KillerBee on ZigBee USB Stick, both seem to be sniffing packet, but Jackdaw can act as a network interface, and KillerBee is only used for pentest? As far as I understand it, you can't use either to connect to like a hub or Wireless router, but only to ZigBee based devices, which would be the IoT devices such as sensors or smart socket etc.
Thank you
How to connect VOIP to PSTN? I have read a lot about VOIP to VOIP. But how is it possible to connect VOIP to PSTN? I have tried to search after this information on Google without success.
It depends on type of your PSTN lines. In short, for T1/E1 you can use big carrier-grade gateways, Cisco for example, and for 2-wire POTS lines you can use small phone adapters with FXS/FXO ports, such as Audiocodes or Linksys. They are SIP-based, so you will need to register them as SIP endpoints.
The interworking that you mention is generally performed on a SoftSwitch. These are any to any Signaling protocol conversion. So a very common scenario is what you referred to as VoIP to PSTN or vice versa. I am using SIP to ISUP as a example here.
Usually the PSTN side can be broken to Signaling Gateways and Media Gateways. While the Signaling GW converts the SIP Request / Response to equivalent Signaling message, the SDP is used to control the Media Gateway based on MEGACO or MGCP. For a normal SIP Call these shall be the conversion for the signaling message. Similar rules apply for H323 to PSTN conversion.
INVITE + SDP -> IAM 180 / 183 -> ACM / CPG 200 -> ANM / CON BYE -> REL
You can check RFC 3398 to check some of these SIP to PSTN conversion rules.
There was another mechanism ITU-Q.1912.5 where the entire ASN encoded ISUP Message body is carried as part of the MIME attachment of the SIP Message and then the message is extracted and sent to the SS7 network. This was part of IPX / GSX [Global Switching Exchange] where the messages across long hops shall be carried over VoIP and on its last mile be converted to equivalent ISUP Signaling.
Now if you are only interested in knowing how a SIP UA can be terminated on a Mobile phone you need to have a partnership with one of the VoIP carriers that provide ISUP Termination capabilities. But somewhere in there switching equipment they will be having mechanisms similar to what is explained above.
There are ATA devices that have a VOIP as well as a POTS port and can connect calls between them. Linksys SPA3102 is one such device. These things are extremely configurable and you can have them automatically answer voip calls and provide a PSTN dial tone or automatically call preset phone numbers.
In general, two communicate between bluetooth devices, first we perform a bluetooth pairing between two devices and then starts further communication between them.
My problem scenario is simply to transfer a hello packet from one bluetooth device to another bluetooth device.
For this i am planning to use sockets programming technique i.e. RFCOMM sockets.
I got some help about this from http://people.csail.mit.edu/albert/bluez-intro/x502.html
So, my query is do we require bluetooth pairing between two devices before initiating communication with RFCOMM socket connection.
Or does 48 bits device address is only necessary to transfer some data packet from one bluetooth device to other and bluetooth pairing could be avoided.
No, it is not.
Bluetooth device can be in one of the four modes:
Broadcaster
Observer
Peripheral
Central
In broadcaster mode device can only send advertisement messages. This includes name and HwID.
In Observer mode device can only receive advertisement messages.
Peripheral = Broadcaster + can take in connect requests
Central = Observer + can send out connect requests.
If you have an application which does not want to connect use first two modes above.
Please let me know if this addresses your question.
Can anyone please tell me if it is possible to publish the voice from an IP based telephone to a RTP based media server - like a Wowza Media Server or Flash Media Server?
Thanks
You probably need to give more info if you want a more specific answer, but a quick response is that yes it is possible.
If the IP phones is something you are building or can modify then you can simply send any outgoing RTP packets both to the other end of the call and the media server, and forward any received RTP packets to the media server.
If you are not able to modify the phone, then you may still be able to achieve what you are looking for by 'mirroring' the RTP packets that are sent to and received from the IP phone, to the RTP media server (see http://en.wikipedia.org/wiki/Port_mirroring for an overview of port mirroring, and www.audiocodes.com/filehandler.ashx?fileid=43289 for some specific discussion on 'tapping' phone calls).
Note, that you need to be aware of the law if this is to record or 'tap' live calls. Even if they are your own calls on your own phone, different countries have different laws about what can and cannot be recorded and what notification you have to give the parties involved in the call (this is why calls to call centers etc often start with a message that the call may be recorded for training or other purposes).