[Spce-user] Problems with NAT-Fukction and mediaproxy

Klaus Peter v. Friedeburg friedeburg at aco.de
Mon Oct 31 18:18:25 EDT 2011

> -----Ursprüngliche Nachricht-----
> Von: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
> Andreas Granig
> Gesendet: Montag, 31. Oktober 2011 22:55
> An: spce-user at lists.sipwise.com
> Betreff: Re: [Spce-user] Problems with NAT-Fukction and mediaproxy
> Hi,
> On 10/31/2011 09:17 PM, Klaus Peter v. Friedeburg wrote:
> > The PST-Gateway that we used also work with loadbalancer and inserted some contact-header. All of the
> items of the gateway platform are reacheable over public IP's but ce interpreted this a NAT-DEVICE! The
> consequence is, that all calls to PST are handled by mediaproxy.
> > How is the way to tell ce that the PST-Gateway is not a NAT-DEVICE?
> Basically it detects "NAT" (or better: uses mediaproxy) if the address
> in the SDP is different from the IP it received the SIP message from.

Yes you are right, the IP from SDP are different. For the first immediate step I have comment out all proxy_offer/answer lines in proxy-skipt-file and change the IP for asterisk (dispatcher entry in database) to the public IP becaue I don't know how is the way to formulate a working IF condition for the peer.

> In the upcoming release (later in November), there's already a peer
> preference to never use mediaproxy for that peer. If you can't wait that
> long, you need to change proxy.cfg.tt2 to not call rtpproxy_offer/answer
> for calls from/to this peer.

Klaus Peter

More information about the Spce-user mailing list