[Spce-user] force_outbound_proxy in ngcp.sbcprofile.conf

[Andreas Granig]

Hi Stefan,

On 05/19/2011 01:08 PM, Stefan Sayer wrote:
> as we figured out in recent discussion on sems list
> (http://lists.iptel.org/pipermail/sems/2011-May/003666.html),
> force_outbound_proxy may make SEMS not 3261-compliant, as it adds itself
> as first route. Probably next_hop_ip and next_hop_port should be used
> instead.

We use outbound_proxy, but not force_outbound_proxy, so this shouldn't
break 3261, as far as I understood it.

The convenient thing about outbound_proxy is that when we've multiple
load-balancers instead of just one (eg. if you scale out the community
edition), then the load-balancer puts itself into the Path during
subscriber registration, and the proxy can set the outbound proxy to
this load-balancer for calls back out to the subscriber. This way, a
subscriber can go via an arbitrary load-balancer (e.g. by using DNS SRV
or even RR) and the NGCP would still be able to traverse NAT.

Guess it would be possible with next_hop/port also by using my own
headers (?), but it'd still need to extract that from the Path URI in
the proxy, which I don't when I use outbound_proxy.



Andreas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20110519/80d3d933/attachment-0001.asc>