List Info

Thread: one design suggestion!




one design suggestion!
user name
2006-04-12 05:54:03

Hi all,

         I have a suggestion to support NAT.

         As I have read source code of gnugk. (www.gnugk.org), it’s open design of h323 gatekeeper., in which gatekeeper contains an embedded proxy, if gatekeeper find the client is behind NAT( which is found by comparing receive addr and client register addr), gatekeeper will proxy rtp data for client when these natted client make call.

         So my advice is we can do same work as gnugk, just replace ip and port in SDP with proxy’s addr and port. And don’t like gnugk, we can dispart proxy from repro, and one repro can control multiple proxy, and can do load balance between these proxy.

         I found openser(www.openser.org) also adopt this design, but their proxy is implemented in python. I think this will reduce performance of proxy. Maybe we use same design but do it in c++!

 

 

Routing scenario
user name
2006-04-13 06:11:17
Hi

I have next scenario:

1. INVITE sip:user1mycompany.com arrives to SIP proxy
2. Proxy decides to fork this request to two destinations:
sip:user2mycompany.com sip:user3external.com 3. Because of
local policy my
proxy MUST send all requests with external domains in
target's Request-URI
to preconfigured next hop proxy.

I may use URI with maddr for external URI, but rfc3261 says:
==8<=====================================================
=====
The maddr field has been used as a simple form of loose
source routing. It
allows a URI to specify a proxy that must be traversed
en-route to the
destination. Continuing to use the maddr parameter this way
is strongly
discouraged (the mechanisms that enable it are deprecated).
Implementations
should instead use the Route mechanism described in this
document,
establishing a pre-existing route set if necessary (see
Section 8.1.1.1).
This provides a full URI to describe the node to be
traversed.
==8<=====================================================
=====

I cannot find the way to specify
"Route-per-target".

What is the right way to implement such behaviour using new
nice design of
Capuchin? Is it possible to write monkey (baboon?) for that?

Thanks
Alex




_______________________________________________
repro-devel mailing list
repro-devellist.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/repro-devel

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )