| Sending out MMS with a router involved |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| David Klugmann Unregistered guest |
Hi I have an issue when I try to send out an MMS notification or an MMS Message via the web interface. In both cases I refer to the external IP address of my machine to be sent to the phone as the location for retrieving the MMS message. Unfortunately my setup involves a router that forwards http requests on to the PC running the MMSC. The PC has it's own internal IP address and cannot see the external IP address given by the ISP (typing this just maps to the router config page). Netgear have said my PC will not be able to refer to this external IP address. The external address (and the mms file) is however visible from another PC and via WAP on the phone. The NowSMS software does a check that the mms file exists and has the correct mime type at the time of sending out the message or notification. In both cases (Notification and full message) I can't send out the MMS because the software cannot see the file referenced by the external IP. If I switch to the internal IP address it can see the file and send it out fine but then the phone at the other end has a communication error when trying to pick up the message because the notification is referring to the internal ip address and not the external one. Is there any way to turn of the validation check on sending out the notification or mms ? Alternatively can you suggest any other ways around the problem. Many thanks David | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 969 Registered: 10-2002 |
David, The easiest way to get around this check is with a HOSTS file entry. You'll find a HOSTS file in your \WINNT\SYSTEM32\DRIVERS\ETC directory. For example, let's say that your public IP address is 212.100.225.164, and that you have the firewall configured to map the HTTP port for the MMSC on that address back to 10.10.0.2. With many firewall configurations, the PC itself on 10.10.0.2 cannot make a connection to 212.100.225.164 that gets routed back through the firewall to the local PC. The only solution to deal with this is to assign a DNS host name to the public IP address (e.g., mms.domain.com). Then in the HOSTS file (in the \winnt\system32\drivers\etc directory) on the NowSMS PC, point that same DNS host name back to the private IP address. That way, when the gateway itself tries to connect to mms.domain.com, it gets the local address. When the phone connects to mms.domain.com, it goes through the public address exposed by the firewall. The only catch is that the HTTP port number that you are using for the MMSC must be mapped through the firewall as the same port number (you can't remap the port number so that it is one value outside the firewall and another value on the PC running the gateway). Whatever name you put into your local HOSTS file, this should be a DNS name that is valid for the outside world. Putting the entry into the HOSTS file only gets around the validation check. -bn | |||
| David Klugmann Unregistered guest |
Bryce Thanks again for the support. I will go ahead and implement that solution. David | |||
