| Mms client emulator |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 22, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| vijay New member Username: Vijvij Post Number: 1 Registered: 11-2008 |
Hi, i am able to send mms from VASP to NowMMSC server. but i want to receive it in a mms client. can you suggest some emulator to use becuase my VASP server has to handle deliver reports and read reports. i tried with openwave sdk simulator phone but i was not able to do connect to NowMMSC. thanks, Vijay | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7685 Registered: 10-2002 |
Hi Vijay, No...sorry, I can't. Every MMS client emulator that we've seen has a proprietary interface for delivering a message to the client. From what I've seen, they either read MMS message files from a directory ... or you need to manually open a file that contains an MMS message. Overall, they are not good for interfacing with an actual MMSC. Here's an old link where I talk about sending an MMS message to an emulator by configuring NowSMS to send the WAP Push via IP instead of SMS: http://support.nowsms.com/discus/messages/485/4184.html If an emulator listens for WAP Push over UDP port 2948 (which an actual phone would do), then it is possible. But aside from MMS clients being developed in lab environments and tested with NowSMS, I'm not aware of any general purpose emulator downloads. Unfortunately, the best solution for most people is sending messages over a live network. -bn | |||
| vijay New member Username: Vijvij Post Number: 2 Registered: 11-2008 |
Hi, i tried to receive the message in an SMTP client and it is working fine. Instead of an MMS phone client i used an email account ( by giving the recepient address as an email address) . Please find the configurations i have done 1)under MMSC tab for "SMTP relay host" i gave my SMTP server address. 2) In my VASP account for "VASP sender address", i gave valid email address ( sender@mail.com) and also in the same page i selected the "forward to email address" option and there also i gave a valid email address( receiver@mail.com). So, when i send a mms from my VAS application it reaches NowMMSC and then NowMMSC forwards it as MM4 message to the receiver's account( i.e., receiver@mail.com) . when i access that account from an email client before opening that particular message it informed that the sender has requested for read receipt and asked me to say ok to send an read receipt. but that read receipt is not coming back to NowMMSC but it goes to sender@mail.com's inbox. but actually Now MMSC should receive that read report and pass it to my VAS application right ? please let me what is the config setting i have to do to receive the read reports in my VAS application. Thanks, Vijay | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7688 Registered: 10-2002 |
Hi Vijay, Any replies or reports are going to be routed back to the sender address. So if you are sending the message out of the MMS world to an e-mail address ... in order for any replies to make it back to you, your sender address would need to be a phone number or short code. When the MMSC routes the MMS message out to e-mail, it is going to convert the phone number or short code to an e-mail address by appending the "Domain Name for MMS E-Mail". In order for the e-mail reply to get routed back to the MMSC, there would need to be an e-mail path that gets this domain name routed back to the MMSC via SMTP. This would mean that either you need to have an MX record for that domain pointing back to the MMSC ... or another SMTP server needs to accept mail for this domain and relay it via SMTP to the MMSC. If you're not familiar with DNS, or don't have full control over your DNS ... this can be a difficult task. And, all that said, I'm not sure that this is a real good substitute for sending to real phones. There is no standard for "read report" or "read receipt" formats in the e-mail world. So a "read receipt" coming back from the e-mail client is going to look like any other e-mail, it's just going to have some text in it (that is e-mail client dependent) indicating that the message has been read. The MMSC will accept that and deliver it as the text of an MMS message. One other thing ... to route messages for a phone number or short code to your VASP, you need to have an "MMSC Routing" definition that defines the outbound connection to your VASP. In the "Route messages to this account for recipient phone number(s)" field, you would put in your short code or phone number, so that the MMSC knows that if it receives a message for this number, it needs to deliver it to your VASP. -bn | |||
