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
--
_____________________________________________________________________
-- 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
