<html><body bgcolor="#ffffff"><DIV><FONT face=Verdana size=2>Hi Ashutosh,</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>Thanks for your response. </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>The readme file of mediaproxy talks about load balancing the RTP streams across multiple proxies. </FONT></DIV>
<DIV><FONT face=Verdana size=2>Does the signaling also follow the same path as the media (for the same call). </FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana size=2>Also, The readme file of the mediaproxy says that:</FONT></DIV>
<DIV>"Once it has determined which domain to use to obtain the list of available<BR>proxy servers, it will make a DNS lookup for the following SRV records:<BR>_mediaproxy._tcp.selected.domain.name"</DIV>
<DIV> </DIV>
<DIV>Does this mean that the DNS lookup serves as the routing mechanism for the call?</DIV>
<DIV> </DIV>
<DIV>Also, the document says:</DIV>
<DIV>"However it should be fairly easy to implement another dispatcher that uses a<BR>different mean to determine the proxy server (like using a database mapping),<BR>or even to distribute the traffic by other means than SIP domain name."</DIV>
<DIV> </DIV>
<DIV>I guess that this means that I could use a 3rd party routing engine to route the calls. </DIV>
<DIV>Is that correct? If so, is there an interface in the dispatcher that I could use to make the</DIV>
<DIV>dispatcher talk to my routing DB and not do a DNS lookup.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Vikrant</DIV>
<DIV> </DIV></body></html>