26 Sep
2005
26 Sep
'05
3:58 p.m.
We would like to use STUN as preferred NAT traversal method but for
those situations where STUN does not work we would offer an outbound
proxy (configured in user agent). We would like to keep the NAT
traversal proxy completely separate from SER. I wonder has anybody
implemented this ? how ? and any other suggestions/feedback.
Br /Kevin Brennan.
26 Sep
26 Sep
5:31 p.m.
The basic problem you run into is when you separate the registrar function
from the far-end NAT traversal function.
I decided not to pursue the for now but was looking at using the Path header
as one possible solution. I guess there are other, simpler solutions,
depending on your SER configuration and network architecture.
As far as I can tell, most commercial SBCs are also B2BUAs so they solve the
problem in a completely different way.
Mark
On 9/26/05, Kevin Brennan <kevin.brennan(a)redsquared.com> wrote:
We would like to use STUN as preferred NAT traversal method but for
those situations where STUN does not work we would offer an outbound
proxy (configured in user agent). We would like to keep the NAT
traversal proxy completely separate from SER. I wonder has anybody
implemented this ? how ? and any other suggestions/feedback.
Br /Kevin Brennan.
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
27 Sep
27 Sep
2:25 p.m.
Kevin Brennan wrote:
We would like to use STUN as preferred NAT traversal
method but for
those situations where STUN does not work we would offer an outbound
proxy (configured in user agent). We would like to keep the NAT
traversal proxy completely separate from SER. I wonder has anybody
implemented this ? how ? and any other suggestions/feedback.
I did this once. The idea was to changes the aor (user@domain) to
user@domain@outboundproxyIP.
Thus, when forwarding the request to the main proxy, the contact header
was replaced with user@domain@outboundproxyIP and the the OBP stores
user@domain@outboundproxyIP instead of user@domain in the location table.
It was a really bad hacked done by modifying the save() function and
using replace() in ser.cfg heavilly.
I guess it might be easier to implement, maybe without coding by using
avpops.
regards
klaus
7002
days inactive
7003
days old
2 comments
3 participants
participants (3)
-
Kevin Brennan -
Klaus Darilion -
Mark Aiken