Unified Networks IP Stimulus (UNIStim)
Unistim is a Nortel proprietary VOIP protocol. It is a lower level protocol than ["SIP"] or most other VOIP protocols. It's important to always think of the phone as a very dumb terminal. Whereas with ["SIP"], the phone has a basic understanding of a phone call,in Unistim the phone knows how to send key press events, display text, flash light, and stream audio. All intelligence is at the switch layer. Like ["SIP"] Unistim does use ["RTP"] as its audio transport. Unistim has a couple layers to it. Unistim
- |_sequence number |_packet-type (ack,nak,or payload)
- |_terminal id (if phone is originator) |_command array
- |_supporting data as required
It is my understanding that Unistim is basically an ["IP"] adaptation of Nortel's DMS protocol.
- ["UDP"]: Typically, UNIStim uses ["UDP"] as its transport protocol. The well known UDP port for UNISTIM traffic is 5000.
Example of multiple commands comming from the switch: attachment:cmd_array_from_switch.gif Example of phone sending key press event showing terminal id:
The PROTO dissector is (fully functional, partially functional, not existing, ... whatever the current state is). Also add info of additional Wireshark features where appropriate, like special statistics of this protocol.
(XXX add links to preference settings affecting how PROTO is dissected).
Example capture file
XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.
A complete list of PROTO display filter fields can be found in the [http://www.wireshark.org/docs/dfref/protofirstletter/proto.html display filter reference]
Show only the PROTO based traffic:
You cannot directly filter PROTO protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.
Capture only the PROTO traffic over the default port (80):
tcp port 80
- add link to PROTO specification and where to find additional info on the web about it, e.g.:
[http://www.ietf.org/rfc/rfc123.txt RFC 123] The RFC title - explanation of the RFC content.