Brett Nemeroff wrote: > Nice addresses!! (rolling eyes) I guess they just thought they'd start > re-numbering the internet starting at 1.0.0.0. Brilliant! > > Well if it's routable it shouldn't matter. I thought you were going to > say that you had conflicting addresses in the RFC1918 space (ie: a > customer with a 192.168.15.20 address and a media gateway also on the > same address on the other side of the network). Other than that, even > if they are goofy addresses, it shouldn't matter as long as it's > properly routable. It is not routable unless you are in the MAN.
> > As for RTP and SIP.. You'll be telling the carriers to send RTP to > your external IP and signal to your external IP.. So I don't think > you'll have a problem. I'm curious why you say mediaproxy can't do it. I'm sorry, i was misunderstanding. I'm sorry, i was thinking that the relay server have 2 interfaces, one with public address and one from 1.0.0.0/8, so i was looking if media relay can listen on this two interfaces and "bridge" traffics. But i was misunderstanding. Both UAC and relay are on this MAN, so there is a route between UAC and relay. What are missing is a route between the carriers and the relay (that is natted). Its a simple problem of natting. So i have to look something like stun for translating the ip:port selected by the relay to the related external ip:port (i know that is a full cone). Sorry again for the misunderstanding. > > -Brett > > > > On Thu, Dec 11, 2008 at 4:44 AM, Giuseppe Roberti <[email protected]> wrote: >> My problem is that we have a lot of customer using provider called >> fastweb, on italy, that is the biggest nat i have ever seen :) >> This provider use optical fiber on internal MAN, at least in Milan, so >> that everybody in this MAN is a natted client. >> Because of fast internal network my customer tell me to put a media >> relay server that "bridge" the rtp traffic from the MAN to the carriers >> but i have problem on doing it with mediaproxy. >> I know that rtpproxy can do it, so i'm looking why mediaproxy seems not. >> >> I hope i am explained me clean. >> >> P.S. Note that the ip address of the clients on MAN are not from RFC1918 >> private address; it look like 1.0.0.0/9 for Milan Optical Fiber, >> 2.0.0.0/8 for Milan Hinterland, etc.. >> >> Brett Nemeroff wrote: >>> For what it's worth, I've had problems doing this with some [broken] >>> carriers. Namely they see a private address in one of the Vias and >>> they assume it's NAT.. Pretty messy. If you look through the archive >>> you'll see what happened to me. >>> >>> That being said, I think it's pretty unusual that this happens. >>> -Brett >>> >>> >>> On Wed, Dec 10, 2008 at 8:14 AM, Giuseppe Roberti <[email protected]> wrote: >>>> Hi. >>>> >>>> I have an opensips server running "between" a man local area and >>>> internet. This mean that UAC comes from local area and gateways are on >>>> internet. >>>> The local interface (eth0) ip is not reachable from internet. >>>> Opensips server can traverse the nat using add_local_rport(), can >>>> mediaproxy do the same ? >>>> >>>> Regards. >>>> >>>> -- >>>> Giuseppe Roberti >>>> <[email protected]> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >> >> -- >> Giuseppe Roberti >> <[email protected]> >> -- Giuseppe Roberti <[email protected]> _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
