The question: what do you check first when a VoIP call connects but audio only goes one direction, and how much of the blame belongs to NAT and RTP port handling versus the phone itself? I have an order, but I would like to compare it with yours.
My lean is that it is the network about nine times in ten. A phone that registers and rings has already proven signaling works. SIP is the telephone call to set things up. RTP is the actual conversation, and it travels on separate UDP ports, usually a wide range. One-way audio means the setup got through but one of the two media streams did not. Think of a phone line where the ring got through and the voice only goes one way down the pipe.
My order of work:
- Check the physical layer first. A bad cable or a duplex problem rarely gives clean one-way audio, but it takes two minutes to rule out.
- Ask which direction is missing, and who is behind NAT. The side that cannot be heard is usually advertising a private address in its SDP, so the far end sends audio into a void.
- Capture on the firewall, not the phone. What does the capture say?
tcpdump -ni eth0 udp and portrange 10000-20000
Adjust the range to whatever your PBX uses. If you see RTP leaving but nothing coming back, look at the firewall state and port forwards. If RTP arrives and the phone stays silent, then the phone is worth a look. 4. Check for SIP ALG on the router. I have seen it rewrite headers in ways that help nobody. Turn it off and test again. 5. Only then look at codec mismatch, handset settings, or firmware.
I do not have much experience with hosted PBX services where the carrier controls the media path, so my method may not fit there.
Where do you start? And has anyone found a phone fault that really was the phone, after the network checked out clean?
Dwayne