| All MMS to mms-in |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Jake Archibald Unregistered guest |
I'm wanting to set up the MMSC so all messages go into the mms-in folder. I created a vasp which receives to the MMS-IN directory, then I created an MMSC Routing rule which routes all messages to the vasp (http://127.0.0.1:8002/mm7). However, when I send an MMS to the gateway it arrives but just sits in the MMSCDATA directory. Why isn't it moving to MMS-IN? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5259 Registered: 10-2002 |
Hi Jake, If the message sits in the MMSCDATA directory, then the routing is not being picked up. If the routing were being picked up, but there was a problem with its definition, messages would go to the VASPQ directory. Assuming that you have your route defined as the "Default Route", but messages are not routed as you expect, then the likely culprit is that you are sending messages to users that are in the "MMSC Users" list. The normal intent is that any users in this list should always receive their MMS messages via direct delivery. But if there is a reason to want to disable this behaviour, you can edit MMSC.INI, and under the [MMSC] header add: DisableMMSDirectDelivery=Yes -bn | |||
| Jake Archibald Unregistered guest |
This solves my problem, thanks muchly! | |||
| hay shteinboim New member Username: Hays Post Number: 1 Registered: 02-2006 |
what does the VASP need to implement in order to recieve the messages? I got the messages in VASPQ folder in .mms file, how can I get the parsed? do I need an external parser? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5540 Registered: 10-2002 |
You need to define an "MMSC Routing" defintion to route to your VASP. When NowSMS has a message to route to your VASP, it will use whichever protocol you defined in the "MMSC Routing". Basically, the main choices are: - MM7 - SOAP/XML based with MIME encoding for the message content over HTTP POST - MM4 - SMTP based with MIME encoding for the message content - MM1 - binary MMS encoding over HTTP POST MM7 is the most standardised protocol, and that is what I would recommend. An example of what an MM7 POST looks like can be found here: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Submitting_MMS_Messages_MM7.htm | |||
