Hello, if the remote side (the public IP side) is capable to do something like asterisk's nat=yes (in sip.conf), than a mascerading router (like every cheap DSL router) would do enough NAT do let SIP work.
If the remote side does not support that nat-hack (which is not SIP standard), than you will need a NATing router also doing a lot of SIP header rewriting. Maybe the most easy thing will be to install asterisk on the NATing machine and operating regular SIP links on both sides. Roger. Nivin Kumar schrieb: > Hello, > > I'm in a bit of a fix. We have a particular Windows based softswitch > which is has its SIP and H323 ports hardcoded to listen on a particular > IP address. The problem is that the ISP is having major issues and we > can no longer depend on them for service. The softswitch will not listen > on any other IP address and this can not be fixed. I was thinking of > creating a NAT network wherein we will forward all traffic from another > public ip address to this server, however I'm not sure how this will > work. Do I need to modify the sip headers? Any thoughts or suggestions? > > Thanks, > Nivin > > -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
