| M-notifyresp-ind and m-acknowledge-ind to the VASP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Avigdor Ne'eman New member Username: Aneeman Post Number: 1 Registered: 03-2006 |
Hello, We are using a VASP to initiate an MMS to a mobile. Our 2006 NowSMS gateway is configured as an Internal MMSC. The mobile receives the MMS and the user is able to read the message. At the gateway we receive the following mobile indications: m-notifyresp-ind m-acknowledge-ind However, we do not get those indications back to the VASP. So, from the viewpoint of the VASP it is not aware of the delivery to the mobile, and the read of the message by the user. How should we configure the gateway in order to get those indications on the VASP? Thank you, Avi | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5633 Registered: 10-2002 |
Hi Avi, How does your VASP submit the message? Are you using MM7? Do you have <DeliveryReport>True</DeliveryReport> set in the MM7 message submission? There is also one other consideration. The delivery report is going to be sent back to the sender address of the original message. So you need to have an "MMSC Routing" definition going back to your VASP to allow the delivery report to be routed back to it. (The same would be required to allow the phone to reply back to the message.) -bn | ||||
| Avigdor Ne'eman New member Username: Aneeman Post Number: 2 Registered: 03-2006 |
Hello Bryce, We are using MM7. We have <DeliveryReport>True</DeliveryReport> set in the MM7 message submission. In the MMSC outbound routing, we have the VASP URL as the server address and the MSISDN Of the mobile as the default sender address. The server address is internal. The MMSC gateway has an external IP. I am attaching the MM7 message from the VASP. Thank you, Avi
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5634 Registered: 10-2002 |
Avi, I think the problem is that the sender address for the message is an e-mail address. The delivery notification would be routed to the e-mail address. Although we have made some concessions in the past to allow an e-mail address to be routed via a VASP ... I don't think that a delivery report will be delivered to a VASP if the recipient is an e-mail address. Instead, what would happen is that the delivery report would be sent as an e-mail to the original sender. My initial suggestion would be to change the sender address in the original message to use a short code number instead of an e-mail address. Then, define an "MMSC Routing" to your VASP with that short code defined in the "Route messages to this account for recipient phone number(s) field". Then, any time the MMSC has a message for that short code (be it a delivery report, or a reply from the mobile phone), it is going to get routed to this "MMSC Routing". -bn | ||||
| Avigdor Ne'eman New member Username: Aneeman Post Number: 3 Registered: 03-2006 |
Hello Bryce, It worked. Thank you so much for the very fast response and resolution of this issue! Regards, Avi | ||||
VASP mm7 message
