| Delivery Callbacks in MMSC Routing(mm4) |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Victor J. Servin New member Username: Victorjs Post Number: 1 Registered: 01-2006 |
Bryce, We need to connect to another operator MMSC. The connection will be made using mm4 protocol. What we need to know if there will be a callback upon the other MMSC message accept confirmation so in that moment we can charge for the message. We are aware that there is a callback that confirm the mssg sent in the MMS p2p, but we are not shure if it does the same when connection to another mmsc. We will use the Routing callback wich we are already using for legacy support Thanks VJS | |||
| Adolfo Abegg New member Username: Adol Post Number: 1 Registered: 01-2006 |
Hi Bryce, any comments about this post? We need your assistance with this question. Thank you very much. | |||
| Adolfo Abegg New member Username: Adol Post Number: 2 Registered: 01-2006 |
Bryce, I read the "NowSMS v5.51 Release Available" announce: http://support.nowsms.com/discus/messages/53/5898.html where you say that "For delivery reports received over an MM4 or MM7 connection, these messages now generate "MMSDeliveryReport" callbacks instead of "MMSSend" callbacks." Does the v5.51c of the NOW GW work in the same way? Thanx! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5424 Registered: 10-2002 |
Hi, Yes, you do get a callback with MM4 connections. There is the pre-auth to determine whether or not to accept the message, and then there is the accounting callback after it is accepted. There are some slight differences in the callback, unfortunately, I can't find a reference to them at the moment. But you should be able to figure them out with a test connection. As I recall, there are "VASPIN=" and "VASPSender=" parameters that are used to identify when messages are coming in from one of these connections. And when a message is getting routed out externally, the callback will include a "VASP=" parameter to identify the external recipients. Regarding the "MMSDeliveryReport" callbacks, I don't see anything in the v5.51c release notes that would supercede the v5.51 release note in this respect, so that would still be valid. -bn | |||
