| Route MMS to multiple server address |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
is it possible for me to route an inbound MMS to multiple Outbound? if it is possible, how can i do that? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3996 Registered: 10-2002 |
The only solution that I can think of would be to route the received e-mail to an e-mail address. Then have that e-mail address be a forward list on your mail server which forwards to multiple addresses ... where those e-mail addresses might get routed back to NowSMS for delivery via MMS. Maybe if you can give me more detail about what you're trying to accomplish, I could come up with some other suggestion. -bn | |||
| Anonymous |
when i receive a MMS i want to store the MMS in a folder at the same time i want to send a SMS back to the user. so im trying to use jsp to get the MMS and store it in a remote server then send a notification to the recipient to fetch it from the remote server. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4074 Registered: 10-2002 |
That would be (more than) a bit difficult. The only way that I could see doing it would be to define an "MMSC Routing" which routed the message to an MM7 connection. Where your application received the MM7 and parsed it for storage. And then you could forward the MM7 to another server for delivery. The specifics really depend on how users are submitting messages into the system. If there are a large number of users, then I would expect that they are defined as standard MMSC user accounts. If there are a small (or controlled) number of accounts, I would have them connect in as a VASP ... where there VASP is configured to forward all inbound requests to your application over MM7. Then you could MM7 back as another VASP account to submit the message back for final delivery through the NowSMS MMSC without requiring another server. -bn | |||
| weir Unregistered guest |
ive got a english saegem vodafone but i now live in spain i have a spanish sim card in my phone but unable to sent mms because of the server address is still english can any one help me to change this | |||
| Anonymous |
thanks for the answer bryce. another 2 questions i have in mind, first: on MMSC configuration window can i put the "Local host name or IP Address" as, example, "192.168.0.1:8080"? basically the question is, can i put a port number in that field? when i did it on the web interface it throw an exception "Error: Invalid Content Type for URL:" second: if, i fill the "Local host name or IP Address" field with "192.168.0.1". when a MMS received by NOWSMS, NOWSMS will send a notification message to the recipient. what will the URL be? will NOWSMS append additional URL? from what i observe NOWSMS will append "/yyyymmdd/hh/MMSFileName.MMS" after the server IP Address. m'I correct? thanks, -JT | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4106 Registered: 10-2002 |
Hi JT, 1.) NowSMS always applies the port number associated with "local host name or IP address" to be the "HTTP Port Number" configured on that same "MMSC" configuration page. Keep in mind that if you use a private IP address like 192.168.0.1, the MMS settings on the mobile phone need to be such that they make a data connection that connects in to your private network. (See http://www.nowsms.com/howmmsworks.htm for more background information.) 2.) Yes. It can vary somewhat, but that is the general format. -bn | |||
| Anonymous |
thanks for the answer Bryce! another question i want to ask. when sending MMS notification NOWSMS will 'always' check for the path whether the file is exist or not. if the file is not exist NOWSMS will not send the notification. m'I right to say that? is there any way i can disable this? i want to send a notification no matter the file is exist or not. is it possible? thanks, -JT | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4125 Registered: 10-2002 |
JT, If the system is configured to only perform direct delivery of MMS messages as an MMSC, then NowSMS will always attempt to validate the URL that it generates which contains the MMS message content. That is because it is essentially pushing that URL to the receiving device. So by validating the URL, we can solve some common configuration problems. Note that this particular check only applies when NowSMS is generating the URL dynamically. See the 3rd message in the following thread for an explanation of how problems related to this check can be avoided: http://support.nowsms.com/discus/messages/1/8204.html. If you are sending an notification for a URL that you generate, NowSMS also will attempt to validate that, but this check can be disabled in v5.51 and later by including "&MMSURLValidate=No" in the HTTP request. More info on that setting: * MMS Notification via Web Interface: Add support for parameter "MMSURLValidate=No". When submitting an MMS Notification (using the MMSURL parameter), this parameter can be added to the request to tell NowSMS not to pre-fetch (validate) the URL before sending the notification. Note that if NowSMS does not pre-fetch the URL, NowSMS cannot verify that the URL is of the correct MIME type or content format. Also, note that if NowSMS does not pre-fetch the URL, NowSMS cannot read the "From" and "Subject" headers from the MMS message, and the "MMSFROM=" and "MMSSUBJECT=" parameters should be used to supply these values. ("Subject" is optional, but a "From" header should be included, otherwise many MMS terminals will reject the message.) | |||
| Anonymous |
thanks bryce! thats the information im looking for. -JT | |||
| Anonymous |
what is the significance of notification reject of MMS . does it deletes the message from the MMSC | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4352 Registered: 10-2002 |
It tells the MMSC to stop trying to deliver it. Whether or not it gets deleted at that point may be implementation specific. | |||
