| That bloody Iphone... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2014 ⬆ |
◄ ► |
| Author | Message | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 13 Registered: 10-2003 |
Anyone got an overview over which message-types actually works with the Iphones? Wap-Push = not Web Linked Multimedia = not Vcard = not and so on... Perhaps someone made a good overview in here, or tweaks to make it work;) | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4851 Registered: 08-2008 |
Hi Lars, In general, WAP Push (Service Indication or Service Load) is a problem for many environments...but the two largest problems are iPhone and North America. Web Linked Multimedia should be fine on an iPhone ... but the link is sent visible in an SMS text message. In fact, I just tried it with a vCard and was able to download it on to an iPhone. The UI could be a little cleaner as our template displays this: Download File Contact Name.vcf (text/x-vCard) When you click on the link, the iPhone asks if you want to Open in "Contacts". It is a little cleaner if you can send the contact via MMS. -- Des NowSMS Support | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 14 Registered: 10-2003 |
Hi Des. Actually. I have Iphone2, Iphone 4 and Iphone 5. I have simcards for all danish telcos. Using latest nowsms demo, and using its web-interface. On the Iphones i cannot: receive WapPush *Receive MMS Message receive Web Linked Multimedia receive WAP vCard Regarding MMS Messages. I think the problem is not the Iphone. MY Android does receive MMS, but they are faulty, and the sender is wrong. The messa itself is from the phone, while the content is from the "sender"-parameter. And the content cannot be downloaded. I am running tests on all of this right now since i want to start using nowsms again. So i will be working on this the next couple of weeks. Generally i only want to use message-types that i can use on all handsets. From experience i have never successfully downloaded vCard's on Iphone's via HTTP download or other protocols. The only thing i ever made it work with was if the vCard physically was attached into a MMS message. ;)Lars | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 15 Registered: 10-2003 |
Sorry!!! I did receive Web Linked MMS. When opening the link in Safari, Safari does nothing but showing a white page. No content. No error messages or anything. My domain for this is on port 8080. But that should not be a problem. | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 16 Registered: 10-2003 |
Web Linked MMS = Web Linked Multimedia. For you newbies(like me) its just a webpage showing the content. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4852 Registered: 08-2008 |
I definitely was able to download a vCard via the iPhone web browser, so it is possible. All I did was attach one with a .vcf extension and included it as an attachment on the "Web Linked Multimedia" page. It sounds like most of your issues are port connectivity issues as the MMS and web linked content seem to be encountering similar issues. Since you are an advanced user (even if it has been awhile), here is how I'd start the troubleshooting: Locate the MMSCDATA directory under NowSMS. Create a simple text file, let's call it test.txt. From a device, try to access the MMSC host and port and request test.txt. For example, http://ip:port/test/txt. If you see the text file, then the server accessibility is ok. If you don't see it, then there is a connectivity issue (port forwarding or firewall or "MMSC Host Name" does not resolve externally). You can also look at MMSCDEBUG.LOG to see if HTTP requests from the device are showing up when there is an attempt to access the URL. This connectivity is required for the web linked content. This connectivity is required for MMS messages only if the MMSC is configured for "direct delivery MMS", which is blocked by many operators. There is an old article here that describes the issues from a technical perspective: http://www.nowsms.com/howmmsworks.htm Alternatively, with a modem, you can send MMS messages through the operator MMSC. In this case, the recipient does not connect back to your NowSMS to retrieve the content. Instead the content is transferred to the operator MMSC over the modem, and the operator MMSC delivers it. Configuring a modem this way is confusing, but there is a good guide here: http://www.nowsms.com/documentation/quickstartguide/NowSMSQuickStart3.pdf -- Des NowSMS Support | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 17 Registered: 10-2003 |
BUG REPORT: When generating a URL(folder) for WEb Linked Multimedia, please use only chars. The url that did not work on my iphones had a "." in the end. Iphone converts this as not being a part of the url. So if the URL is: "http://mmsc.com/MT/MgvtY4.", Ios converts it to: "http://mmsc.com/MT/MgvtY4". When i added the "." to the URL, it worked. Also, you should consider returning a 404 in the output when url does not exist. Aaand finally. topbar.gif is missing. Can we edit the .HTML and .CSS file? ;)Lars | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 18 Registered: 10-2003 |
Hi Des. Did you have Wifi on when you downloaded the .vcf file? I allways test without wifi since i need to guarantee that things are working on telco-net. I will give it a shot more though. | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 19 Registered: 10-2003 |
Des, regarding the whole MMS issue. I think sometimes we just need to keep it as simple as possible... I did read up on your current setup etc.. The .pdf you refer to. I assume you're talking about the last 2 pages. Since the first pages are all about MMS-MO and not MMS-MT. (MO = inbound, MT = outbound ;) ). I have absolutely no problems with MO MMS messages. I do have problems with MT. Just doesn't seem to work. And i am assuming it's because i am running things like i am with my old version of nowSMS. So i will spend the rest of this night reading and testing... | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 20 Registered: 10-2003 |
Des, I did create a MMS-route via MM1 on the modem. That actually works. However... 1. I do not recieve messages if a file is more than 159Kb. But maybe that is a telco-limit. But i doubt it. 2. Please tell me where do i connect/route nowsms so that i can bind together a modem/simcard with the MMS-ROUTE that i created??? I dont undestand how to. For MT traffic. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4853 Registered: 08-2008 |
Hi Lars,
Good catch. We will avoid this character in the future. That is fast tracked for a fix, but might only be fixed in the upcoming beta.
The IP in the MMSCDEBUG.LOG was telco. But I tried again without WiFi to confirm and still OK.
I'll be the first to agree that the setup process, for supporting MMS on modems in particular, is convoluted and confusing. Come back in about 2 weeks and the beta release ... well ... not to say too much again, but it will greatly simplify the modem setup process, increase the number of compatible modems, and take much better advantage of higher speed networks for sending/receiving speed.
1. Make sure the MMS Proxy Address for your operator is a version that includes ":" and a port number. The old proxies frequently fall over at around 300KB or sometimes smaller. What is the operator and what settings are you using? 2. I'm not sure what you mean by bind together? Do you mean for particular message routing? | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 21 Registered: 10-2003 |
>> Des: 2. I'm not sure what you mean by bind together? Do you mean for particular message routing? What i am trying to figure out is: 1. I have a modem. It has a MSISDN. Let's say +00122222222. 2. I want to be able to send MMS OUT from this modem. I set up a route and i call this route "+00122222222" 3. I have set up email2sms and email2mms. 4. I have set up Authorized user so that des@des.com is authorized to do email2sms/mms via +00122222222. 5. Now imagine i have 5 of these modems on my server. 6. nowSMS knows that if des@des.com sends an email2mms, it should be routed through +00122222222 7. But how does nowSMS know that this mms from des@des.com should be routed out through the mmsc-route i created??? It is easy if this route is set as default. But that cannot be done in a multiple-modem enviroment. So i guess what i am looking for is to tell nowSMS that every time i want to send MMS through +00122222222, it should use the mms-route i created. Can you undestand my point Des? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4854 Registered: 08-2008 |
Hi Lars, OK ... sorry for the delay in response. If e-mail is a primary application, I would recommend waiting for the new beta. The current e-mail to MMS implementation is designed primarily for customers using an MMSC configuration. There is some flexibility, but there are also some limitations. Most of these limitations will be removed in the upcoming beta, or at least that is the intent. In one of our other recent discussions, you asked about the ability to dynamically select SMS or MMS based upon the presence of an attachment. That is core to these changes. The current e-mail to MMS implementation needs to stay as it is. The e-mail to SMS implementation is being enhanced to include support for both SMS and MMS, for more general messaging configurations. I don't want to keep telling you to wait for the beta, but my instinct is that it would better fit your needs. Anyway, I'll try to explain what you can do now, and explain a little about how it will change. For both SMS and MMS, NowSMS can perform routing based upon sender, recipient, or accounting callbacks. Sender based routing works for the scenario that you describe. When you add an email address to the authorized list, you can define a sender address associated with that account. This is done by adding a comma and number to the email address in the authorized list, such as: des@des.com,+00122222222 (Alternatively, if you want to use quotas, you can define the email account as an "SMS User", enable SMTP login and apply a "forced sender address". However, in current releases, this only works for e-mail to SMS.) So far so good, you've probably already figured it out this far. For sender based routing in SMS, the "Phone Number" setting is used. For sender based routing in MMS, the "Sender Address" setting is used. However, for modem connections we tell you to leave this blank, and we actually use this setting when generating an MMS message. Some operators will allow you to configure the actual phone number here, and everything works. But it causes problems for some operators and does create a limitation. That is being addressed in the new beta by more tightly linking the SMS and MMS settings for a modem, and not requiring the separate MMS sender address setting. The next issue is ... what if you want SMS or MMS replies routed back to the e-mail sender? You can define a one to one e-mail to SMS and MMS mapping today, but it requires dedicating one e-mail address to receive all SMS or MMS from a modem. (SMS handled via a 2-way mailto: command, and MMS handled by a forward to e-mail address setting.) For e-mail to SMS there is also an option to dynamically track SMS replies and route them back to the e-mail sender. This setting allows a pool of modems (or other SMSC) to be used. For each e-mail to SMS, NowSMS looks to see if any other e-mail user has previously sent to this phone number. It then dynamically allocates a sender address from the pool. If an SMS reply is received, NowSMS knows which email address sent the message and routes the reply back via e-mail. As the new beta adds optional MMS support to the e-mail to SMS functionality, this dynamic tracking gets extended to MMS, and there iix no distinction as to whether the message is SMS or MMS. (Of course you can still assign a one to one e-mail user to modem mapping in future releases as well. The dynamic tracking just makes it easier.) Overall, this is a complicated issue, but hopefully my explanation makes sense. -- Des NowSMS Support | |||
| Lars Nielsen, MobileNation ApS - Denmark New member Username: Larsmservice Post Number: 23 Registered: 10-2003 |
Hi Des. Thank you for your replies and help. The way you describe it is very much how i run things and how i am running it on a very old version of nowSMS. You got to imagine that you are a radiostation. You have one MSISDN where your listeners can send sms/MMS til. You, the radio-host has an email inbox where all the messages comes in. And you can reply directly back to the listeners. 2 way communication, with MMS, for radio stations. Great product to have;). So, in my setup i have one modem dedicated to one radiostation. It's their simcard. All i do id forward the messages to their email-address. It's as simple as that. For 2 way support nad mms support, and to make things run as smoothly as possible i have to do the following: 1. Setup one modem in nowSMS with Radiostation MSISDN. 2. Forward MMS to studio@radiostation.com 3. Set up 2-way SMS support and do a mailto: studio@radiostation.com Now we have one way support. All sms/mms traffic get's sent to the email-address: studio@radiostation.com. Anyone can do that. Nothing special and nothing that stands out compared to my competitors. So I want to do 2 way giving the radiostation a way of communicating with their listeners by replying back to incoming SMS/MMS. That is also faily easy to setup in nowSMS. Only problem i have here is the 2 domains for sms and mms. It get's confusing in the radiostations studio. The DJ's don't get why they have to change the domain if they want to send MMS to someone who sent an sms to the studio. Problem 2 is that i have to create a mms-routing in order for the content to be hosted at the telco and not by nowSMS-server. It's not a problem when only running one modem on nowSMS. I becomes a problem when having multiple modems on nowSMS. The problem that pops up here is that i cannot tell nowSMS that this modem MMS-OUT capabilities should be done by using MMS-Route "some-route-name". But, as i read you Des, it actually is possible. That is if i do a http-post to nowSMS or sometihng else. Problem here is that i am doing it via email. Can i solve this in any way Des??? ;)Lars | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4908 Registered: 08-2008 |
Hi Lars, Very late follow-up ... but the beta version of NowSMS (the version with Android modem support) handles all of this transparently. If you haven't seen it, this version is available after the standard download form. For outbound email, there is an option to use MMS instead of SMS if the message exceeds max length or includes an image attachment. For inbound MMS, if it came from a modem, it uses the SMS e-mail settings, so it shares the same domain. All this is described in more detail here: http://www.nowsms.com/email-to-sms-mms-gateway-with-nowsms I see, however, we neglected to mention how to address problem #2 in that document. But I did just test to confirm it is working like Des described, where you add a phone number to associate with the email address in the authorized list. If an MMSC route is defined as using a modem listed in the SMSC list, both SMS and MMS get routed to the same modem based upon sender address. Setup is a little easier if using an Android device as a modem because we automatically create and link the MMSC route with the SMSC definition. But for conventional GSM modems, as long as "Modem Used" is set in the route, NowSMS will know to use the same sender address for both MMS and SMS. -bn Bryce Norwood Now SMS/MMS Support | |||
