[Serusers] Rtpproxy: media not forward

[Ladislav Andel]

Depending on how many users you have registering to your SER you can 
change the range of ports served by rtpproxy.
Default is 35000-65000 and this can be changed in rttp_defines.h and 
recompile
your rtpproxy. Then you can open just ports on your firewall as it is 
defined in.
rttp_defines.h.

Ladislav

PREVOT Paul wrote:
>
> I apologize for my former question. It was just a firewall issue on 
> the computer running rtpproxy. I didn’t open the right ports L
>
> But is it possible to configure rtpproxy to open ports automatically 
> on firewalls, instead of opening a huge number of ports manually?
>
> Regards,
>
> Paul
>
> ------------------------------------------------------------------------
>
> *De :* serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] 
> *De la part de* PREVOT Paul
> *Envoyé :* jeudi 6 avril 2006 13:42
> *À :* serusers at lists.iptel.org
> *Objet :* [Serusers] Rtpproxy: media not forward
>
> Dear all,
>
> I have installed rtpproxy from 
> http://www.openser.org/downloads/snapshots/rtpproxy/rtpproxy-cvs-latest.tgz 
> on the same computer as Openser.
>
> I started it without options. /var/run/rtpproxy.pid and .sock are created.
>
> I suppose a communication is established between OpenSer and Rtpproxy 
> as SDP messages are correctly replaced, it means “Connection 
> Information c” shows rtpproxy IP address and ports.
>
> Also both UAs sent RTP media to rtpproxyIP:port described in SDP body, 
> but rtpproxy doesn’t forward any RTP packets from one UA to the other.
>
> Tcpdump –n udp and host 213.48.xxx.yyy result:
>
> 11:48:49.191130 IP 213.48.xxx.yyy.2236 > 207.245.aaa.bbb.35000: UDP, 
> length 60
>
> 11:48:49.250183 IP 213.48.xxx.yyy.2236 > 207.245.aaa.bbb.35000: UDP, 
> length 60
>
> 11:48:49.255407 IP 213.48.xxx.yyy.2237 > 207.245.aaa.bbb.35004: UDP, 
> length 60
>
> 11:48:49.297050 IP 213.48.xxx.yyy.2236 > 207.245.aaa.bbb.35000: UDP, 
> length 60
>
> 11:48:49.297275 IP 213.48.xxx.yyy.2237 > 207.245.aaa.bbb.35004: UDP, 
> length 60
>
> 11:48:49.335890 IP 213.48.xxx.yyy.2237 > 207.245.aaa.bbb.35004: UDP, 
> length 60
>
> 11:48:49.339723 IP 213.48.xxx.yyy.2236 > 207.245.aaa.bbb.35000: UDP, 
> length 60
>
> 11:48:49.393997 IP 213.48.xxx.yyy.2237 > 207.245.aaa.bbb.35004: UDP, 
> length 60
>
> Have you ever come across that issue? How can I get 
> 207.245.aaa.bbb.35000 > 213.48.xxx.yyy.2237? Does this problem occur 
> because both UAs are in the same local network? (I don’t thing so)
>
> I would be very thankful if you could give me an idea about it.
>
> Thanks a lot
>
> Paul
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>