| Settings to send MMS by operator MMSC (3 - 3G) |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| erikku Unregistered guest |
Hi, We are in the progress of evaluating the software and trying to send a MMS by using our operator (3 - 3G)'s MMSC thru NEC e616 3G phone connected to the internet using "*99#". I know there are two server settings, which are, MMSC URL: http://mms.um.three.com.hk:10021/mmsc and MMS Proxy: mms.three.com.hk:8799 using TCP connection mode. However, I am not sure what to put for "server address" under "MMSC routing" tab and "HTTP Port" and "Local Host Name or IP Address" under "MMSC" tab in the SMS gateway. I tried to put MMSC URL above as the "server address" but it prompt out an alert stating it cannot connect to the server. I am forced to put "MMS Proxy" as the "server address", but after all, it doesn't work. It can submitted the MMS, just the other 3G terminal cannot recieve it. Any idea would help! I am suspecting I should put something for the WAP Gateway IP address under "MMSC Routing tab" which we don't need it for 3G? -THANKS! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3128 Registered: 10-2002 |
Hi, Unfortunately, we do not support TCP/HTTP mode for connecting to an operator proxy at present. We only support using a WAP proxy. Hopefully it will not be too much longer before we implement an HTTP proxy option. (There are some technical issues where when we use the WAP proxy, we are able to simultaneously send MMS messages over multiple modems to the same MMSC ... but this will not be possible via the HTTP proxy.) Regarding "Local Host Name or IP Address", this setting is only important when you are using NowSMS as an MMSC, performing direct delivery of MMS messages. More information on this can be found at the following links: http://support.nowsms.com/discus/messages/1/589.html http://support.nowsms.com/discus/messages/485/1958.html But, this value is not important if you are routing all of your messages via an operator MMSC. Info on connecting to an operator MMSC in the manner that you describe can be found at the following link: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Connecting_to_operator_MMSC.htm However, as I mentioned, we only support connecting to a WAP proxy here ... and so far it appears that none of the 3 networks have a WAP proxy ... but only HTTP based proxies. So you might not get anywhere until we add an HTTP proxy option. -bn | |||
| erikku Unregistered guest |
Hi, Thanks for your fast reply. Actually, I just want to send out MMS messages using NowsSMS. I guess the Proxy is required only if I want to recieve MMS from MMSC as well. In this case, is there any way I can use NowSMS to send MMS to a 3G mobile? However I do have one question: Usually for a 2G operator, there will be a WAP gateway in between the MS and MMSC in order to translate the WSP to HTTP. However, as far as I know, there is no such setting for 3. I guess we use HTTP all the way so we can connect to the MMSC directly. In this case, would it be a problem when using MMSCOMMP to encode a customized MMS and use NowSMS to send the MMS meesage? -THANKS! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3242 Registered: 10-2002 |
It has taken me a little while to get back to you on this one. Basically, in NowSMS we have not previously implemented an option for submitting MM1 through an HTTP proxy. (We can do HTTP direct, but not with us dynamically initiating the GPRS or 3G connection.) The v5.51 release should be out by the beginning of next week. In v5.51, you can specify "http://ip.address:port" in the "WAP Gateway" field. This tells us to use an HTTP proxy instead of a WAP gateway for sending or receiving MMS messages through an operator MMSC. Unfortunately, v5.51 is not out yet, but it should be by the start of next week, and this is one of the features planned. -bn | |||
