Port unreachables are expected during the teardown phase of a SIP dialog, have a look at http://lists.rtpproxy.org/pipermail/users/2008-June/000044.html for more information This is probably why you are seeing the ICMP unreachables, otherwise the problem is most likely in the last mile (either the subscriber UAC or the terminating gateway). Most commonly its due to bandwidth exhaustion but you'll have to evaluate the issue on a case by case basis
To date i've not had a single call quality issue that has been attributed to RTPProxy Ronald Voermans wrote: > Hello RTPProxy users, > > I'm still experiencing some quality issues with Openser and RTPProxy. Calls > sound very choppy sometimes (not always, around 10% of the calls). So, it > seems packets are lost, or jitter is pretty high sometimes. I've been running > a monitor between our RTPProxy and our ITSP for some weeks now, and I find > the following pretty interesting: > > I'm seeing a lot of 'ICMP Destination Unreachable (Port Unreachable)', being > generated by the OpenSer/RTPProxy. This means, I think, a RTP packet is > received by the RTPProxy server but it doesn't 'listen' to the port. This > results in a lost packets and thus choppy sound. > > The server is dimensioned enough i guess (xeon processor, 4GB memory for > around 30 calls concurrent). > > What could be the cause of this Port Unreachable message? > > Thanks in advance, > > Regards, > > Ronald > > _______________________________________________ > Users mailing list > Users@rtpproxy.org > http://lists.rtpproxy.org/mailman/listinfo/users > > _______________________________________________ Users mailing list Users@rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users
