[Users] force_rtp_proxy() problem.
Ray Van Dolson
rayvd at digitalpath.net
Wed Aug 3 01:20:49 CEST 2005
On Wed, Aug 03, 2005 at 12:15:24AM +0200, Klaus Darilion wrote:
> Hi Ray!
> On which interface is rtpproxy listening? Try starting rtpproxy with
> command line options to bind on 18.104.22.168.
> This way, force_rtp_proxy should insert the 208... IP address into the SDP.
Thanks Klaus... getting closer--I think. I wonder if there is any way to run
two instances of rtpproxy? Voice packets are halfway flowing correctly, but
Outbound call from SIP ATA is established.
Asterisk shows RTP data going from 22.214.171.124 -> 126.96.36.199
However a tcpdump on OpenSER eth1 shows RTP data with source IP 188.8.131.52
-> 10.0.201.196. The source IP should be being rewritten as 10.0.201.5, but
it is not. In addition I don't get any voice data back from the SIP ATA
leading me to believe the force_rtp_proxy is somehow passing the public IP
address back to my SIP ATA device (which is unroutable).
Must be a way to handle this both ways. My config file is getting pretty
crazy so I may wipe everything out and start from scratch and try to keep it
> Ray Van Dolson wrote:
> >Thanks for the help earlier Bogdan.
> >I've gotten things working for the most part, but am having a problem with
> >force_rtp_proxy function.
> >Once again, here is my setup:
> >SIP ATA
> > - 10.0.201.196
> > - eth0: 184.108.40.206/24
> > - eth1: 10.0.201.5/24
> > - eth0: 220.127.116.11/24
> > - eth1: 10.0.201.6/24
More information about the sr-users