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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100526/7051d0d1/attachment.htm
Assume previous IP is LAN. Forwarding public IP ports to LAN is straighforward. However, with SIP headers you will (don't know H323) have to modify outgoing SIP headers: replace LAN ip with WAN ip. For callers you have to substitute RTP destination IP For callees you have to substitute RTP source IP. I`m afraid you will have to check more details here: http://www.ietf.org/rfc/rfc3261.txt Maybe client sends server it's own IP address? However, dumb header substitution + port range forwarding should work in all cases for SIP. On Wed, May 26, 2010 at 3:55 PM, Nivin Kumar <nivinkumar24 at yahoo.in> wrote:> > 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
----- "Nivin Kumar" <nivinkumar24 at yahoo.in> wrote:>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? --- And this is related to Asterisk...... how? If your 'particular Windows based softswitch' doesn't in fact allow you to change the listening interfaces then it sounds like one "great" piece of software. If you're going to post something completely OT to the list, at least have the courtesy of telling us what softswitch you're talking about? --Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100526/860fccac/attachment.htm
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 > >
Skip the whole NAT scenario. Put up an asterisk box with two network interfaces. One interface connects to the real world on your new IP address from your new ISP. The other interface can be on the same subnet as the windows box that you can't change. Set up a SIP trunk to your Windows box. Use packet 2 packet bridging in asterisk. Now that the emergency is over you can migrate off of your Windows thing at a more comfortable pace. You will be using someone else's public IP privately for awhile, but the main thing affected by that is your asterisk box won't be able to talk to anybody in that subnet in the outside world. You'll have to determine how bad of a thing that would be. BTW: What the heck is this software? Sounds like whoever wrote that wasn't thinking ahead.> 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 > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100526/ec98927d/attachment.htm