| Nokia 6100: Spinning envelope but no MMS Message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
We had tested on SMS function and it worked very well, but MMS did not work. We tried to send a few MMS to a MMS ready phone (Nokia 6100 with GPRS subscription) and we saw a spinned envelope (that should indicate a MMS coming), but at end there is nothing received. We also tried to trace at MMS Gateway Service machine and found there is totally no traffic coming to retrieve the MMS message. Do you know what could be the reason? Does your gateway also need MMS capable GSM modem/phone for MMS function to work? For the testing, we just used a normal GSM phone (Siemens S35i) to connect to the gateway. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi. A normal GSM modem is fine. To help troubleshoot your problem, allow me to explain some background information for how MMS works. The process of delivering an MMS message to a handset works like this: 1.) You start with a content file that contains the content of an MMS message. This message may have been created by an application, or it may have been created by a user sending the message from a mobile phone. (When the message is sent from a mobile phone, a mobile phone connects to an MMSC via WAP and transmits the MMS message content to an MMSC and the MMSC then takes responsibility for further delivery.) It could also be created by using the web menu interface of the Now SMS/MMS Gateway. 2.) The MMS message content is published (usually by an MMSC) so that it is accessible via a URL. 3.) An MMS notification message is sent to the recipient mobile phone using binary SMS. This MMS notification message contains header information about the MMS message, and a URL pointer that tells the mobile phone how to retrieve the MMS message content. 4.) The recipient mobile phone opens a WAP session, and retrieves the MMS message content from the URL contained in the MMS notification message. It happens this way whether it is an operator MMSC that is delivering the message, or another MMSC, such as the MMSC built into our Now SMS/MMS Gateway. After the handset receives the MMS notification message, In order to actually receive the MMS message content, it must open up a WAP session and retrieve the MMS message content from an MMSC. There are settings configured on a mobile phone to specify how the mobile phone makes a data connection to open a WAP session to send and receive MMS messages. These settings are similar to the settings used for the WAP browser in the mobile phone, however, they are logically separate from the WAP browser settings. These settings include a GPRS Access Point Name (APN) to which the phone connects to make a GPRS data connection (MMS can be transmitted over dial-up WAP in many phones as well, but GPRS is more common), and the IP address of a WAP gateway. From your description, it sounds like the phone is receiving the MMS notification that is transmitted over SMS, but it is not able to retrieve the MMS message content over WAP. This could be the result of either a configuration issue related to the MMSC, or a configuration issue related to the MMS settings on the mobile phone. Here are some suggestions of things to check: 1.) First, verify that your MMSC is accessible over the open internet, and that it is not blocked by a firewall. The receiving phone needs to connect back into the MMSC to retrieve the message. If you connect to the HTTP port of the MMSC with a web browser, you'll just get a "page not found" error ... but you would see a log entry on the MMSC indicating that there had been a request received. 2.) Make sure that that the "Local Host Name or IP Address" configured on the MMSC page of the Now SMS/MMS Gateway configuration dialog is accurate. The MMS URL that is sent out to the mobile phone contains a reference to this host name. 3.) Re-configure your MMSC to use HTTP port 80. Some operator WAP gateways have firewalls that prevent access to any content that is on a port other than port 80. If you are sending an MMS notification message where the content server resides on a port other than 80, change the content server to use HTTP port 80. Repeat your attempt to send an MMS message. Note that changing these settings will only affect messages that are sent after the change is made, they will not change attributes of messages that were already sent. 4.) Check the WAP profile that is associated with the MMS setup in your phone, and verify that this is the same WAP profile that you use for regular WAP browsing activities. It has been noticed that some operators are setting up restrictive MMS profiles, where the MMS profile connects to a separate GPRS APN, and a separate WAP gateway, which only allow access to the operator MMSC. After changing the MMS setup to use the WAP profile that you use for regular WAP browsing activities, repeat your test. 5.) It is possible that your operator has constructed a "walled garden" in attempts to lock users to their content services. To leave the walled garden, check with your operator to determine what GPRS APN (access point name) should be used for PDA/PC type connections, and if a username or password is required, what those values should be. Create a WAP profile on your phone that connects to that GPRS APN. Specify an IP address for the WAP gateway of 213.48.20.10 (this is a gateway at the Now Wireless offices, if you have your own WAP gateway, substitute that gateway IP address). Try using that WAP profile to browse to a site, such as http://mms.now.co.uk/index.wml. Switch back to your normal WAP settings for browsing, but configure the MMS services on your phone to use the WAP profile that you just created. 6.) Are you using your own WAP gateway instead of the operator WAP gateway, or does your operator not yet support MMS? MMS requires that WAP gateways support "SAR" (segmentation and re-assembly). Some early WAP gateways did not provide this support. If you are unsure about your WAP gateway, you may want to try using the public WAP gateway referenced in the previous item. Hopefully there is an answer or explanation for your specific problem in here somewhere! -bn | |||
| Anonymous |
Hi, I've had my Nokia 6100 for about a month now and I can't get online, it keeps asking for an IP address. What is this and how do I find one for my phone. My network is O2. Thanks} | |||
| Bryce Norwood - NowSMS Support |
Have you tried the O2 web site? Assuming that it is O2 in the UK, try http://ota.o2.co.uk/O2UK/index.jsp. | |||
