| VASP Account |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Michael New member Username: Michael123 Post Number: 11 Registered: 02-2007 |
Hi, We are connected to few operators using one MMS hub (MM4 connection). For each operator we have configured one routing account with same server IP address and different e-mail domain and phone numbers. We also has one routing account with MMS hub e-mail domain and same IP. For all operators we are using only one VASP account, where we set IP restriction and MM4 ack is routing using MMS hub routing account. Here we meet a problem: we are receiving message from 1234@operator.domain and sending delivery report to 1234@HUB.domain. I think we need to configure own vasp account for each operators, but not sure how to do it. Do I need to add e-mail domain in VASP sender address or put there phone number range with wildcard (something like +995*)? Waiting for your suggestion, Thanks, Michael | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 967 Registered: 08-2008 |
Hi Michael, Is this causing a problem? The hub should rewrite this header when it processes the message. I realise that you're talking specifically about delivery reports ... However, the delivery reports really shouldn't be processed by the hub all that different from the sending of a regular message. When you send a regular message out via the hub, it gets addressed to the hub domain ... and the hub then takes care of routing the message so that when it arrives at the destination operator the recipient domain has been changed as needed by the hub. I can't see why the hub wouldn't be doing the same thing with delivery reports. -- Des NowSMS Support | |||
| Michael New member Username: Michael123 Post Number: 12 Registered: 02-2007 |
Hi Des, Thanks for your quick reply. Problem is only with few operators and it's related to their CDR/billing. We have own routing for each operator with their domain, so when we are sending regular message it's sending directly to operators domain. We have only one VASP account and their we have defined that MM4 ack is routed to hub domain. So we need own VASP account for each operator. Can we put domain name (operator.domain.com) or address range (+995*) in sender address or somewhere else in VASP? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 978 Registered: 08-2008 |
Hi Michael, The MM4 ACKs are different from delivery reports. However, I see what you mean ... delivery reports and read reports follow the same routing logic, as we want to make sure that the report goes back out via the same connection as which the message was received. (And in the case of MM4, we follow the ACK route that is normally used for ".RES" messages.) I guess the best solution would be to somehow treat different domains as separate VASP accounts. Or ... are you using routing callbacks to decide the outbound route for regular messages? Would it make more sense for us to allow the routing callback to override the routing. Right now, the routing callback is being bypassed for delivery reports and read reports, and maybe it should not be. What do you think? -- Des NowSMS Support | |||
| Michael New member Username: Michael123 Post Number: 13 Registered: 02-2007 |
Hi Des, Currently we aren't using routing callback. I agree that the best solution would be to somehow treat different domains as separate VASP accounts. Or it will be better for us to use routing callback? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 985 Registered: 08-2008 |
Hi Michael, You don't really need to use routing callbacks unless you have mobile number portability issues. The quickest solution that I can see would be to give you an update where delivery and read reports were not forced to follow the "MM4 ACK Route". I believe we could disable this very easily with a configuration switch. Then the standard outbound routing logic would apply for these messages, whether that was a routing callback or static routing based upon recipient prefix. Unfortunately, we're frozen changes at the moment, trying to finalize the current interim release as the new formal release. So it may be a week or two before we can make any changes. -- Des NowSMS Support | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7827 Registered: 10-2002 |
Michael, It's not a perfect solution, but we made a minor change to the MMSC to add a configuration to disable it from automatically routing receipts back to the connection from which the message was received. This way, the receipt messages will be routed via whatever routing is defined for normal MMS messages. This setting is available in the 2009.07.04 version at http://www.nowsms.com/download/nowsms2009rc.zip: * MMSC: Add configuration setting to disable the automatic routing of delivery receipts and read receipts back over the same connection that the original message was received from. To disable this automatic routing, edit MMSC.INI, and under the [MMSC] header, add AutoRouteReceipts=No. -bn | |||
| Michael New member Username: Michael123 Post Number: 14 Registered: 02-2007 |
Des, Bryce, Everything works fine. Thanks a lot, Michael | |||
