I dunno what you are trying to explain but a simple scenario for topology hiding would look something liek this:
UA OSIPs/RTPP * CARRIER <--------------<>--------------<>----------> <########<>########<>######> In the above scenario your OpenSIPs and RTPProxy are both running on the same server so both your SIP signaling and RTP stream will be relayed to OpenSIPs/RTP box. Now your OSIPs will relay these requests to your * server and similarly RTPProxy will relay your RTP stream to the * box. Now if you look on UA(User Agent's) side only one node will be visible to it. To furthur secure your * box you can remove it from public domain and assign it a local IP. Possibilities are endless :). Lastly i am sure i explained every thing right. Please correct me if i am wrong anywhere. Regards, Qasim On Fri, Aug 31, 2012 at 6:20 PM, Nick Khamis <[email protected]> wrote: > >> RTP is used for many purposes most commonly to hide your internal > network topology i.e. in your case your * server also it helps in NAT > traversal. > > That is exactly what we are trying to accomplish. Would like all SIP > traffic to go through the OpenSIPS server, > > > Could someone kindly illustrate graphically how the flow of traffic is > suppose to look in a topology hidden network using NAT traversal > please? Should there be port forwarding > of RTP traffic to the Proxy? Meaning, should the incoming ITSP traffic > be directed at OpenSIPS: > > > ----->: Initial Stream > *****> Asterisk Stream > > What I think we have now, and why we don't need RTP NAT traversal yet: > > Scenario 1 > > UC > Proxy > Asterisk > ITSP > * Router 192.168.2.1 * > Back to > Asterisk > Back to Proxy > Back to UC (Final) > > Proxy------->Asterisk--------> ITSP > UC -------> * * * * > <****** ***************** ****** Router*** > > > What we should have and need eventually (Topology Hiding using NAT > traversal): > > Scenario 2 > > UC > Proxy > Asterisk > ITSP > *Router 192.168.2.1 * > Back to > OpenSIPS > Back to UC (Final) > > > Proxy------->Asterisk-------->ITSP > UC -------> * * > <****** * * > *****Router 192.168.2.1**** > > > > i.e., there has to be no direct connection between the UCs or ITSP and > asterisk. I think we have accomplished this without using RTP proxy > since everything is on the same subnet, > or am I incorrect? And as you mentioned, the RTP stream is now being > directed at the Asterisk server? Will get a NGREP trace posted when I > get to work. Please remember > that this is done using virtual machines as a test bed for now... > > > > Thank you Kindly for your Help, > > Nick. > > > On Fri, Aug 31, 2012 at 12:11 AM, [email protected] > <[email protected]> wrote: > > Most probably your RTP stream is directly bein connected to * server. > RTP is > > used for many purposes most commonly to hide your internal network > topology > > i.e. in your case your * server also it helps in NAT traversal. > > > > Regards, > > Qasim > > > > On Fri, Aug 31, 2012 at 8:05 AM, Nick Khamis <[email protected]> wrote: > >> > >> Thank you guys for your response. It's the strangest thing. I removed > >> all the rtpproxy and nathelper stuff, and it works perfectly? > >> Everything is on the same subnet, i.e.: > >> > >> Router > >> | > >> ------------- MySQL 192.168.2.105 (Virtual Box) > >> | > >> ------------- OpenSIPS 192.168.2.102 (Virtual Box) > >> | > >> -------------Asterisk 192.168.2.110 (Virtual Box) > >> | > >> ------------- Polycom 192.168.2.102 (Virtual Box) > >> > >> > >> The flow of transmition is: > >> > >> UC------->Proxy------->Asterisk > >> > >> > >> And I have two way audio without rtp proxy or port forwarding. I'm now > >> scared and confused. Can someone please > >> explain to me how this is? > >> > >> Thanks in Advnace, > >> > >> Nick. > >> > >> _______________________________________________ > >> Users mailing list > >> [email protected] > >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
