| Routing of inbound VASP messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Wolfgang Röckelein |
Hi, I want to route messages coming from an inbound VASP connection (EAIF) per certain phone numbers to convert them to WAP push (since the P800 does not understand application/java-archive in MMS, only per WAP). However, the routing entries seem to be ignored for messages coming from a VASP connection. How can I work around that? | |||
| Bryce Norwood - NowSMS Support |
Hi Wolfgang, I'm not certain that I understand the message flow completely. I assume you have an account defined in the "MMSC VASP" list. In the "MMSC Routing for Received Messages" option, you would have it set for "Standard MMS Delivery". This means that when an MMS message is received in from this account, it gets routed the same as a message that is submitted via the web interface or from a phone ... and the routing rules defined on the "MMSC Routing" page would apply. If you have a routing that routes some recipient phone numbers to a WAP push, then it should work properly. If that is how you have things configured, and it is not working properly, then please put the gateway into debug mode: Edit SMSGW.INI, and add Debug=Yes under the [SMSGW] section header. Also edit MMSC.INI, and add Debug=Yes under the [MMSC] section header. Then restart the gateway services. Repeat your message sending attempt, and then e-mail me (nowsms@now.co.uk) the SMSDEBUG.LOG, MMSCDEBUG.LOG, SMSGW.INI and MMSC.INI files. -bn | |||
