Hi Andres,
You are right, this works now only if you assign different domains per
users and you know where they are. You could change the lookup logic
based on a different algorithm if you toy either with the DNS server or
the dispatcher. So the dispatcher does a lookup in a particular
database in place of DNS and there you can map geo-location to a media
proxy domain. You would still want to use the DNS lookups because it
provides the load balancing and fail-over for multiple IPs.
Alternatively, we can customize media proxy to handle particular
situations subject to a commercial contract.
Kind regards,
Adrian
On Oct 9, 2005, at 7:50 PM, Andres wrote:
Hi Adrian,
I assume the proxy dispatcher is the one who performs the DNS SRV
Lookup, not the client. How can the proxy dispatcher then decide
whats best for the client? Or are you also implying separate domains
for each geographical region? I do see your product states
"Distributed geographical location" as a feature, but greater detail
in how to accomplish this is needed. I still cannot see it clearly
(on the other hand Greger's suggestion about using different domains
is easy enough but not possible in our network).
Thanks,
Andres
Adrian Georgescu wrote:
Andres,
Mediaproxy does that, it does a DNS lookup to locate the server(s)
for each call. Use a dynamic DNS engine (like the geo module of Power
DNS) and you can distribute geographically the streams per user.
Adrian
Hi,
Can anybody think of a way to assign a subscriber's call to a specific
rtpproxy? The idea is to have one main SER server but multiple
rtpproxy
servers handling the media stream close to where the subs are. The
SER
server can be a continent away but the rtpproxy is in the same city as
the users. I was thinking of using ACL (groups) somehow but not sure
if
it is at all possible.
Any ideas?
Thanks,