| Preventing SMS web link notification per VASP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 8 Registered: 06-2010 |
Hi, In our deployment of NowSMS we're notifying clients by SMS web link (with code) to retrieve messages from the web after some timeout without being retrieved directly. The problem is that we're charging MMS MT (mobile terminated) coming form a certain VASP, so people who wait enough should be able to retrieve this messages for free !! Is it possible to inhibit sms web link for certain VASP traffic? This is *important* for this stop happening!! Thank you in advance. Best regards, Gonzalo | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2259 Registered: 08-2008 |
Hi Gonzalo, At first I thought that this was a follow-on to this discussion: http://support.nowsms.com/discus/messages/485/59875.html However, I see that it is not. Are you using the "MMSRetrieve" callback? I see that we are generating an "MMSRetrieve" callback when a user retrieves a message via the web link. However, the message ID in this callback is different, and nowhere is there any record of how the ID was converted. Yet, if a delivery report was requested, a delivery report goes back for the original message ID. So we do still know what the original message ID was. Would your problem be resolved if we returned the original message ID in the "MMSRetrieve" callback when a message is retrieved via the web link? I want to make sure that I understand correctly before we try to engineer any solutions. -- Des NowSMS Support | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 9 Registered: 06-2010 |
Hi Des, thank you for your prompt reply. We're not using MMSRetrive callback, yet intended to be implemented soon. But I think it would be better not to notify users about messages we don't want to be retrieved by web. Meanwhile, if there's no other solution (ie. blocking SMS weblink notification for the traffic coming from a certain VASP), we could try to run periodically a script that changes "UndeliveredScan" key inside of .INI file of the messages from this VASP (stopping notification for them). The general idea is that we don't want users to download by the web messages coming from a VASP. Please let me know if I have settled up the problem correctly. Thank you again. Best regards, Gonzalo | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2261 Registered: 08-2008 |
Hi Gonzalo, This is very good detective work that you have done. Setting the following in the message INI file will indeed stop the MMS to SMS with web link timeout conversion: [UndeliveredScan] Scanned=Yes I hope to have update information on the other issues that you raised toward the end of this week. -- Des NowSMS Support | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 10 Registered: 06-2010 |
Thank's Des ;-) I'll be waiting your advances on these subjects. Perhaps it'd be possible to include on the next release a checkbox in VASP configuration, selecting wether to notify by SMS web link this traffic or not. Best regards, Gonzalo | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 14 Registered: 06-2010 |
Hi Des, do you have any scheduled update for a patch regarding this issue? I've been asked to solve this problem *this* week, so if you won't have a patch after this period I'll have to implement another solution.. What they require is to avoid MMS to SMS web link timeout conversion for a traffic coming for a certain VASP. Thank you in advance. Regards, Gonzalo | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2308 Registered: 08-2008 |
Hi Gonzalo, The previous update has a setting that has not been fully tested. We could not easily implement a way to block this by VASP. However, what we did implement was a "blocked sender list", so that certain MMS message senders could be blocked from having messages converted to SMS with web link. The configuration setting is in the [MMSC] section of MMSC.INI. UndeliverableRouteToSMSBlockSender=xxxx,yyyy,zzzz If there are multiple entries, the list is comma delimited. Wildcard characters * and ? can be used in an address entry, similar to the way they are used in routing entries. This setting has not been fully tested, which is why I did not mention it previously. Due to my schedule this week, I am unable to test it, so I would suggest that you try it. It should not be necessary to restart the MMSC service to apply or update this setting. The MMSC should pick up the setting dynamically if you add it. -- Des NowSMS Support | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 15 Registered: 06-2010 |
Hi Des, Thank's a lot!. I'll test it ;-) Just one question, does it work for senders with format user@domain? This VASP is actually using sender with email format just to receive delivery notifications when recipient gets his mms (and also because our charging gateway detects this sender format to charge MMS when user retrieves it). Thank you again! Best regards, Gonzalo | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 16 Registered: 06-2010 |
Hi Des, after *lots* of tests, I've got some good news and bad news for you: The good one is that this *is* the feature I needed, and I managed to make it work properly ;-) The "bad" one is that you've to add an ending "," as the last delimiter of the UndeliverableRouteToSMSBlockSender list. For example, in order to catch the last blocked sender (zzzz) the correct line would be: UndeliverableRouteToSMSBlockSender=xxxx,yyyy,zzzz, (with a "," at the end) Another thing is that if MMS to SMS web link conversion takes place with senders with email format (user@domain), the SMS appears truncated after the "@" (maybe because "@" is a character with special meaning in the sms -that ecloses key words like @@code@@, for example), and should be "escaped" somehow. I'm *really* happy with the results and the feature you've added, which lets me put into production this service next week without having to do cryptic scripts.. Thank you again. Best regards, Gonzalo | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2323 Registered: 08-2008 |
Hi Gonzalo, Try sending messages that contain @ from the NowSMS web interface. If it als o causes truncation here, this means your SMSC is expecting a different char acter set. In GSM, @ is encoded as a null character. To fix this go into advanced settings for the properties of the SMPP connect ion and set the SMSC character set to iso-8859-1. -- Des | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 20 Registered: 06-2010 |
Hi Des, SMSs sent from web interface have same problem, effectively. But it wasn't solved changing character set.. strange.. I'll ask SMSC people about this setting. Regards, Gonzalo | |||
