Hello, We are running into a strange problem, hopefully someone has seen it before. If we configure pjsip to use STUN, our pjsip RTP packets do not come from the RTP port specified in the SDP, resulting in outbound audio or no audio. The RTP port advertised in the SDP and used for outbound RTP appear to be random and don't match the RTP port specified as the starting port when we call media config. RTP is set to start using port 4000 but the logs will look like: ... 10:55:41.068 pjsua_media.c Note: STUN mapped RTCP port 35043 is not adjacent to RTP port 41060 ... 10:55:41.181 pjsua_media.c Note: STUN mapped RTCP port 42720 is not adjacent to RTP port 41939 ... 10:55:41.286 pjsua_media.c Note: STUN mapped RTCP port 33482 is not adjacent to RTP port 34305 ... 10:55:41.389 pjsua_media.c Note: STUN mapped RTCP port 43696 is not adjacent to RTP port 41815 ... If we disable STUN, then the logs look like: ... 11:05:29.785 pjsua_core.c SIP UDP socket reachable at 10.0.2.2:55060 11:05:29.786 udp0x86ea00 SIP UDP transport started, published address is 10.0.2.2:55060 11:05:29.794 pjsua_media.c RTP socket reachable at 10.0.2.2:4000 11:05:29.794 pjsua_media.c RTCP socket reachable at 10.0.2.2:4001 11:05:29.802 pjsua_media.c RTP socket reachable at 10.0.2.2:4002 11:05:29.802 pjsua_media.c RTCP socket reachable at 10.0.2.2:4003 11:05:29.809 pjsua_media.c RTP socket reachable at 10.0.2.2:4004 11:05:29.810 pjsua_media.c RTCP socket reachable at 10.0.2.2:4005 11:05:29.815 pjsua_media.c RTP socket reachable at 10.0.2.2:4006 11:05:29.815 pjsua_media.c RTCP socket reachable at 10.0.2.2:4007 ... Has anyone encountered this issue before or know why these port numbers are all over the place? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090329/d62abeea/attachment.html>
