MMSc is getting weird! | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
Author | Message | |||
FRaveau Frequent Contributor Username: Fraveau Post Number: 51 Registered: 06-2012 |
Hi, I have a strange behaviour of the plateform with a partial service: Some MMS work but others don't. WAPGW error logs get show things like : "Error: Timeout waiting for response from content server" or "Winsock Error 11001 -- cannot resolve host name" and mmsc log: "User Not Defined,FAILED" despite the RADIUS log shows the IP. The platform was fully working two days ago. The only strange think is that i have a lot of HTTP trafic in the GW I shouldn't have; as it's supposed to be used only for MMS. I guess it's because customers have wrongly configured theirs handset usgin the GW for all trafic. (BTW is there a way to avoid this?). Is that a possible explanation? I sent you my log files to nowsms[at]nowsms.com with "to DES: FRAVEAU logs" as a title. Any help much appreciated! Thanks | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4442 Registered: 08-2008 |
Hi Franck, I'm working my way through it. But I think it is a handset settings issue. Let me explain what I see. Every MMSIN record that is ok has a source address of 127.0.0.1. Every MMSIN record that says "User Not Defined" has a source address in the 10.x.x.x range. This tells me the handsets with the problem are bypassing the proxy port. It looks like the MMSC and the WAPGW are on the same machine. Can you firewall off 8080 so that it is only accessible locally? This is not strictly necessary, but it will clear up the MMSC logs of a lot of errant connections. Actually, what might be the best idea ... if you wanted to work with the handsets that are configured with 8080 as the proxy port ... you could bind 2 IP addresses to the machine. 1 IP (the existing one configured as the proxy address) would be used by NowWAP, and NowWAP would listen to the originally configured proxy port plus 8080. The other IP would be used by MMSC. You would just need to update DNS for your mms and mmedia hosts to point to the new address. A HOSTS file entry on the PC would handle requests routed via the WAP gateway, but DNS would need to be updated for mmedia to resolve properly for the messages converted to SMS with web link. Before making any changes, I want to understand what settings are configured in the phones and how the convert to SMS with web link settings are configured. I will send you an e-mail to reply to so we can go over those settings. Does the 2 IP address solution sound like a possible way forward for you? I am concerned that if you have misconfigured phones already, it may be easier to try to work with them instead of updating their settings. -- Des NowSMS Support | |||
FRaveau Frequent Contributor Username: Fraveau Post Number: 52 Registered: 06-2012 |
You were right! Our OTA configuration provider made some changes a few days ago and an error went in (GW port to 8080). We won't change our network architecture to handle the bad configurations outhere but it's true something should be done to avoid all those wrong attempts. I can't completly firewall 8080 as it's also used for legacy experience (SMS + link). Do you think it's possible to deny proxy type of trafic only? I'll talk to our admin about that Thank you for your support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4443 Registered: 08-2008 |
Glad we were able to identify quickly. I think the two IP address solution is probably the only workable solution if you want to do anything at all. (You might be able to filter the other based upon Host: header, but it is not causing a problem other than lots of errors in the logs.) You'd just have to avoid using 127.0.0.1 in any HOSTS files because when either NowWAP or the MMSC is bound to a single IP it doesn't listen on the loopback address. If you can fix the phones configured incorrectly easily enough, it is probably best to leave well enough alone. -- Des NowSMS Support |