| MMS delivery notifications and read receipts |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| sam New member Username: Samdsouza Post Number: 6 Registered: 08-2006 |
Hi Wanted to know if its possible to disable/deactivate MMS delivery notifications and read receipts via some kind of MMSC.ini settings? Kindly let me know Thanks Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2194 Registered: 08-2008 |
Hi Sam, You can disable delivery reports and read reports from being sent out via one or more of your external MMSC connections ("MMSC Routing" definitions). This is done by manually editing VASPOUT\accountname\VASP.INI, and under the [VASP] header, adding DisableDeliveryReport=Yes There are also two global settings ... but they work a little differently. On the "MMSC" page of the configuration, there is a configuration option "Enable MMS Delivery Receipts". When this setting is UNchecked, the MMSC will not generate any delivery receipts. If a client requests a delivery receipt, and the message is routed to an external MMSC connection, and that MMSC returns a delivery receipt, it will be processed. So this setting does not disable all delivery receipts, just ones that would be generated by this MMSC. There is an additional setting available in the [MMSC] section of MMSC.INI ... EnableReadReceipt=No. This setting suppresses the read receipt messages on all messages processed by the MMSC so that receiving entities will not attempt to send a read receipt. -- Des NowSMS Support | |||
| sam New member Username: Samdsouza Post Number: 7 Registered: 08-2006 |
Hi Des Thanks for your inputs. There is one more query i had regarding the following parameters: LocalNumberPrefix=xxxxx LocalNumberMaxLength=# These settings are used in situations where a provider serves a particular city code within a country code, which sometimes happens with island operators. If the MMSC receives a message addressed to a recipient whose phone number length is less than or equal to LocalNumberMaxLength, it automatically prepends LocalNumberPrefix to the number, before applying standard local number to international number conversion. Lets say the country code is 365. A user can send a MMS in the following 3 recipient mobile number formats: MobileNumber (only the mobile number) 365MobileNumber (mobile number with country code) 0MobileNumber (suffix 0 before the mobile number) Using the above 2 parameters it works fine for the first 2 options. But when the user submits with 0MobileNumber (suffix 0 before the mobile number) it prefixes the country code and the recepient number becomes 3650MobileNumber which doesnt deliver to the mobile handset as the mobile number format should be 365MobileNumber and Not 3650MobileNumber on the SMS connection. Is there a way to resolve the above issue? I mean is it possible to replace and not preappend the "0" with "365". Kindly let me know Thanks Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2197 Registered: 08-2008 |
Hi Sam, It would help to know more specific details. What if you set LocalNumberPrefix=0 so that it prepends "0" to the number if the number is of a particular length? Also use MSISDNHeaderDefaultCountryCode=365 With these settings, someone sending from a "+365" number to MobileNumber will get converted to 0MobileNumber and then to +365MobileNumber. If you're still stuck, there are MSISDNHeaderPrefixConvert and MSISDNRecipientPrefixConvert settings. MSISDNHeaderPrefixConvert applies conversions from the MSISDN header to the sender address, and probably do not apply to your situation. MSISDNRecipientPrefixConvert applies conversions to problem recipient addresses after they go through the normalization process. The following setting in MMSC.INI under the [MMSC] header would make the conversions you need: MSISDNRecipientPrefixConvert=+3650:+365,3650:365 If after conversion, you have 3650MobileNumber, it would convert "3650" to "365", leaving you with 365MobileNumber. If possible, it is better to avoid these confusing conversion scenarios ... however, there are definitely situations where they are necessary. If this doesn't resolve your issue, give me some more details with actual values. -- Des NowSMS Support | |||
| sam New member Username: Samdsouza Post Number: 8 Registered: 08-2006 |
Hi Des Thanks for your inputs. Highly appreciate. Am testing NowMMSC outside the operators networks. The only settings working for me are: LocalNumberPrefix=xxxxx LocalNumberMaxLength=# I tried all the things you suggested. MSISDNRecipientPrefixConvert=+3650:+365,3650:365 doesnt do the required conversions. Still when the sms is submitted to the SMPP connections its 0MobileNumber. The lenght of the mobile number is 10 without the country code. Following examples: Submited MMS to 08521475756. Conversions happned like 0008521475756, 008521475756 and 36508521475756. Am not able to get this converted to 3658521475756 Would you like to see any specific logs? Kindly let me know Thanks Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2211 Registered: 08-2008 |
MMS.INI and MMSCDEBUG.LOG would be helpful. Also version number, as the MSISDNRecipientPrefixConvert setting does not exist in older versions. -- Des NowSMS Support | |||
| sam New member Username: Samdsouza Post Number: 9 Registered: 08-2006 |
Hi Des, That was it. Downloaded the latest version and it works great. Thanks a lot for your time on this. Sam | |||
