| 1 | initial version |
I assume you are using SIP.
The communication server on which you are running Wireshark will only be aware of the signalling (SIP/SDP). When phone A contacts phone B, the signalling (SIP/SDP) would go through your communication server, however when the two phones "know" each other the RTP stream will flow directly between the two phones (not though the Communication server), which I think is where your problem is. You are sitting in the signalling path and to get the RTP packets you should tap into the path between the two phones using a port span/port mirror,
There is however settings on most of the communication servers to keep the connection between the two phones pinned up through the server ( called hair pinning). This however put a lot of strain on your communication server. Then only the RTP packet would traverse the communication server
I hope this helps
| 2 | No.2 Revision |
I assume you are using SIP.
The communication server on which you are running Wireshark will only be aware of the signalling (SIP/SDP). When phone A contacts phone B, the signalling (SIP/SDP) would go through your communication server, however when the two phones "know" each other the RTP stream will flow directly between the two phones (not though the Communication server), which I think is where your problem is. You are sitting in the signalling path and to get the RTP packets you should tap into the path between the two phones using a port span/port mirror,
There is however settings on most of the communication servers to keep the connection between the two phones pinned up through the server ( called hair pinning). This however put a lot of strain on your communication server. Then only only, the RTP packet would traverse the communication server
I hope this helps