| MMS options |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through June 02, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Paul Bryson New member Username: Pbryson Post Number: 5 Registered: 01-2010 |
Des, 1) What is difference from normal MMS compared to with param mms.addparameter ("SMSWAPPush", "Yes") (IE: Multimedia Content Push)? 2) You say nowSMS uses MM7 by default, is this true if my MMSC routing is set to MM1? 3) your answer to question 2 might answer this, but if I have to change the MMSC routing setting from MM1 to MM7 does the same java sendMMS stuff work or is there another example to point me to? 4) I assume then one cant send to multiple recipients if using MM1, or is it just cheaper using MM7 for multiple recipients? Paul | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1750 Registered: 08-2008 |
Hi Paul, 1.) That parameter should be "MMSSMSPush" instead of "SMSWAPPush". That is an old typo that I'm glad you reminded me needs to be fixed. If either "MMSWAPPush" or "MMSSMSPush" is specified, then it is not a real MMS message. The content of the message is converted to a static HTML and WML page, and a URL link is sent to the recipient via SMS to allow them to view the content in a browser. 2.) I must have confused my words. MM7 is the most common protocol that is used when you are connecting to a mobile operator as a "Value Added Service Provider". It is not employed as a default protocol. 3.) Whatever outbound routing type you use, the application interface stays the same. 4.) You can send to multiple recipients via MM1. However, you are likely to be charged for multiple messages. You transmit the message to the operator as a single message, but the mobile operator delivers it separately to each of the recipients. When sending to multiple recipients, there are a few things to keep in mind. First, if you submit an MMS message with multiple recipients to NowSMS, NowSMS might decide to break the message into multiple submissions. This is because mobile operator systems often have per message recipient limits. These limits are not standardised, and NowSMS has default limits depending on the protocol type. MM1=5 EAIF=10 MM7=100 MM4=1 (Side note for future searches ... it is best to keep MM4 at 1, even though this may be considered inefficient. Experience has taught us that many systems can get confused about delivery receipt and non-delivery receipt generation when there are multiple recipients via MM4.) So, using MM1 as an example, if you submit a message to 12 recipients, NowSMS is going to send to a group of 5, another group of 5, then a group of 2. You can edit VASP\outboundaccountname\VASP.INI and set MaxRecips=## under the [VASP] header to change this default, but you should test to see what the practical limit is for your mobile operator when making any changes. A related note ... if you are sending bulk messages, you may want to edit VASP\outboundaccountname\VASP.INI and set ForceBCC=Yes under the [VASP] header. This forces all recipient information to be submitted to the MMSC as BCC instead of TO. -- Des NowSMS Support | |||
| Paul Bryson New member Username: Pbryson Post Number: 6 Registered: 01-2010 |
Thanks Des, I looks like using either "MMSWAPPush" or "MMSSMSPush" , the default behaviour is that the nowSMS is the MMSC, is this correct and can that be changed? I am in test phase so my nowSMS is not exposed to the internet, but I dont even get a sms on phone when using "MMSWAPPush" or "MMSSMSPush", is this becuse the phone tries automatically to download the URL? Paul | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1757 Registered: 08-2008 |
Hi Paul,
No. In these configurations, the content has to be stored somewhere that it can be served up via a web server. We don't have any options to FTP it to another web server, only to use the built in web server of the MMSC. You should at least get an SMS though. Are you able to send simple text messages from the NowSMS web interface? Maybe something is wrong with the SMS side of the configuration. The most common issue is the "SMS Access" setting under the "Properties" for the modem in the "SMSC" list. Setting it to "GSM" is required for some mobile operators. If that doesn't resolve the problem, are there errors being reported in the SMSOUT-yyyymmdd.LOG file? -- Des NowSMS Support | |||
| Paul Bryson New member Username: Pbryson Post Number: 7 Registered: 01-2010 |
Sorry for delay, it was a sms config issue, thanks | |||
