| 1 | = Checking if RTP Packets are Received = |
| 2 | |
| 3 | Use pjsua's '''{{{dq}}}''' (dump quality of current call) command from pjsua's menu to check that RTP packets are indeed received by pjsua. Use this command after the media is established, of course. |
| 4 | |
| 5 | Also make sure that current call selected is the call that you want. You can change current call with ''']''' and '''[''' command. |
| 6 | |
| 7 | Once correct call is selected and media is established, you can invoke '''{{{dq}}}''' command like below: |
| 8 | |
| 9 | {{{ |
| 10 | >>> dq |
| 11 | 14:54:37.008 pjsua.c |
| 12 | [CONFIRMED ] To: sip:user@localhost;tag=1857bde149264e2986c4aac1a26f5866 |
| 13 | Call time: 00h:00m:53s, 1st res in 1071 ms, conn in 1191ms |
| 14 | #0 speex @16KHz, sendrecv, peer=192.168.0.66:4000 |
| 15 | RX pt=103, stat last update: 00h:00m:01.753s ago |
| 16 | total 1.7Kpkt 72.2KB (127.2KB +IP hdr) @avg=10.6Kbps |
| 17 | pkt loss=0 (0.0%), dup=0 (0.0%), reorder=0 (0.0%) |
| 18 | (msec) min avg max last |
| 19 | loss period: 0.000 0.000 0.000 0.000 |
| 20 | jitter : 0.000 5.506 227.000 9.812 |
| 21 | TX pt=103, ptime=20ms, stat last update: 00h:00m:07.871s ago |
| 22 | total 0pkt 0B (0B +IP hdr) @avg 0bps |
| 23 | pkt loss=0 (-1.$%), dup=0 (-1.$%), reorder=0 (-1.$%) |
| 24 | (msec) min avg max last |
| 25 | loss period: 0.000 0.000 0.000 0.000 |
| 26 | jitter : 0.000 0.000 0.000 0.000 |
| 27 | RTT msec : 0.274 0.616 1.233 1.233 |
| 28 | }}} |
| 29 | |
| 30 | Pay attention to this part of the report: |
| 31 | |
| 32 | {{{ |
| 33 | RX pt=103, stat last update: 00h:00m:01.753s ago |
| 34 | total 1.7Kpkt 72.2KB (127.2KB +IP hdr) @avg=10.6Kbps |
| 35 | }}} |
| 36 | |
| 37 | as it shows the number of RTP packets received since the media is established. |
| 38 | |
| 39 | Make sure that the number makes sense for the duration of the call (without VAD, normally we'll have about 50 packets received per second). |
| 40 | |
| 41 | If the number is zero, then we're not receiving any RTP packets. There could be problems with the network, or NAT, or firewall, or something else, which is not related to the sound device. |
| 42 | |
| 43 | If the number is too low, it's possible that remote is transmitting silence frames, which of course will be rendered as silence in the speaker. |
| 44 | |