Hi, When using STUN, the RTP address (including port) published in the SDP is the public address mapped by the NAT. So it is normal that SDP is not using the same port number as specified in media config (e.g: port 4000), since it is using the mapped port (which seems to be random, the port mapping is done by your NAT). The no audio problem may be caused by making call in LAN while STUN is used and your NAT doesn't support for hairpinning. Perhaps enabling ICE along with STUN can solve the problem. The log shows different problem though. It's about RTCP mapped port is not adjacent of RTP mapped port. Regards, nanang 2009/3/30 Eric Chamberlain <eric at rf.com>: > 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? > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >
