| URGENT! [ShortCode] directive problems |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| David Chkhartishvili New member Username: Datoch Post Number: 27 Registered: 06-2004 |
Hi Bryce, here is my scenario: I have set up shortcode directive and accounting url like this: MMSAccountingURL=http://myhost/myscript [ShortCode] 1234=some@email.com For each sent MMS we got two accounting callbacks: MMSSend PreAuth Callback and MMSSend Accounting Callback. In the PreAuth callback 'To' field is 1234 but in the MMSend callback 'To' field is some@email.com. Thus I cannot identify messages sent to number 1234. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4335 Registered: 10-2002 |
Hi David, I'm afraid there's not any way around that. It has to do with how (and when) the translation takes place. It would be relatively easy (famous last words) for us to change the PreAuth callback so that the short code was translated before the callback. But it sounds like you would like the short code to be preserved through the final accounting callback. And I can't see a good way of doing that. I'll ask another engineer to take a look and see if they have any other ideas. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 28 Registered: 06-2004 |
Bryce, What I'm trying to do is to charge MMSs sent to 1234 differently. If I understood you correclty, currently it's not possible, but I think operators should be able to charge per destionation address. P.S. could you include both numbers in fianl callback? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4348 Registered: 10-2002 |
David, I understand. In this case, I think you're going to have to charge based upon the e-mail address that appears in the callback. Talking to one of my colleagues, he had an idea of how we could handle this. He suggested that rather than handling this through the somewhat hidden short code table, we could implement this through the outbound VASP routing. The outbound routing allows you to define that specific numbers get routed through the connection, and one of the routing options is SMTP. The only problem is that we expect to send to phonenumber@domain. But he was suggesting that we could very easily modify this handler so that if the specified domain contained an "@", we would simply rewrite the recipient address to the address specified in the domain parameter. This would give you the desired effect in the callbacks. But it would also have a side effect that this could be enabled without enabling full outbound SMTP sending, because you can specify the address of an SMTP server in this configuration, and you could connect directly to the content provider's e-mail server. He's running some tests to make sure this is feasible, and to ensure that there aren't any unwanted side effects. But I'm more comfortable with this approach than I am with trying to make callback changes via the shortcode table in the INI file. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 29 Registered: 06-2004 |
Bryce, 1. If I charge based on email, than directly sent messages to that email will be charged as in shortcode case. 2. I didn't mean only shortode->email scenario, I also meant shortcode -> MSISDN or shortcode -> MM7. P.S. I will be out of office for one week. I will try to keep in touch with you. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4410 Registered: 10-2002 |
David, 1. I understand. But I would also think that they probably should be charged the same, so that someone didn't circumvent your short code. 2. The VASP approach that I outlined above (which has now been implemented, but not yet released) will handle everything except shortcode->MSISDN. (It will handle shortcode->email and shortcode->any VASP including MM7.) Basically, the way that the shortcode translation is implemented is just as a translation table. By the time the send callback is issued, we no longer have access to the non-translated entry. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 30 Registered: 06-2004 |
Hi Bryce, Finally I'm back. Does 5.51b contains modifications mentioned here? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4468 Registered: 10-2002 |
Hi David, Yes, v5.51b includes the VASP approach. The description is a bit vague: MMSC: When defining an MM4/SMTP external connection, if the "E-Mail Domain" field contains a "@", then any messages for this route are routed to the e-mail address specified in this field. This is a simple way to redirect a specific phone number or short code to an e-mail address. But the idea is that instead of using that short code table, you define an "MMSC Routing" for each of these providers. And you put a full "e-mail address" in the "E-Mail Domain" field. Any message that matches the routing criteria for the route get redirected as e-mail to the specified e-mail address. This setting does require that you specify an SMTP server to which you connect. If you want to keep it simple, you could just specify your standard SMTP relay server here, but you might want to go direct to the content provider. -bn | |||
