Testing MMS Client on two emulators with NowSMS MMSC

Testing MMS Client on two emulators with NowSMS MMSC SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Testing MMS Client on two emulators with NowSMS MMSC « Previous || Next »
Author Message
emulatormms
Unregistered guest
Posted on Thursday, May 06, 2004 - 06:50 am:   

Hi,
I have MMS Clients running on two Win CE emulators on two different PCs. I have installed NowSMS software on the third PC. I have MMS client developed which uses WAP stack. I want to test sending and receiving of MMS messages from one emulator to the other using NowSMS MMSC. Can anybody help me in achieving this?
Regards,
Khan
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2526
Registered: 10-2002
Posted on Thursday, May 06, 2004 - 06:36 pm:   

Hi Khan,

Sending should not be a problem ... but receiving MMS messages in an emulator is not always possible. (The MMS notification that starts the MMS receiving process is sent in a WAP push message, and this WAP push message is usually sent over SMS ... but the emulator has no standard hook for how to receive this SMS.)

So let's take sending first.

The MMSC accepts HTTP connections. So if you're using a WAP stack, you're going to need a WAP proxy/gateway between the emulator and the MMSC. (You can download an eval of our WAP proxy at http://www.nowwap.com.)

An account for each of the emulators should be defined on the MMSC. This is done in the MMSC under the "MMSC Users" dialog.

On each emulator, you will be configuring the MMS Server URL as http://server:port/username=password, where username corresponds to the phone number or alias defined in the "MMSC Users" dialog, and password is the password associated with the account. (The MMSC will use this information in the URL to identify the device.)

At this point, you should be able to submit messages into the MMSC.

However, the MMSC doesn't have any outbound link for SMS (and NowSMS will complain about this fact when you configure it).

So the question is how to get the MMS notification into your emulator.

If the emulator will accept a WAP push over IP, then you can configure the MMSC so that it sends the push over IP instead of SMS.

You can determine if the emulator has any support for accepting WAP push over IP by running "NETSTAT -a" on the PC that is running the emulator. If this shows that an application is listening for UDP on port 2948, then there is an application listening for WAP push over IP.

If not, then there is no application listening for WAP push over IP, and what I'm about to suggest will not work.

In NowSMS v5.50, you can configure NowSMS to route MMS notifications for specific phone numbers to IP addresses. In the MMSC.INI file, it is possible to create an [IPNotify] section. Under this section header, specify PhoneNumber=IP.Address (e.g., +9999999=192.168.1.200), to have MMS notifications for the specified phone number get routed to the specified IP address. (This feature is intended primarily for testing environments.)

If your emulator does not support WAP push over IP ... then you need to figure out if it is possible to somehow push an SMS into the emulator.

NowSMS can be configured to submit SMS messages through an HTTP interface ... so you could write a script to act as glue between NowSMS and the emulator. This is a more difficult process, information on the parameters that NowSMS passes to an HTTP interface for sending SMS can be found at the following link:

http://www.nowsms.com/documentation/ProductDocumentation/configuring_smsc_connec tions/HTTP_SMSC.htm

-bn
emulatormms
Unregistered guest
Posted on Wednesday, May 12, 2004 - 03:58 am:   

Hi BN,
Thanks for your reply. I sent MMS message from my MMS emulator client via Now.WAP gateway. The Now.WAP gateway logs "POST http://server:port/sender_username=password" 200 50 "" "", where server:port is the ip address and port of MMSC. How does MMSC indicate that it has received an MMS message?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2556
Registered: 10-2002
Posted on Wednesday, May 12, 2004 - 02:21 pm:   

There should be an entry in the MMSC-yyyymmdd.LOG file.

NowSMS will then queue the notification to go out via SMS (SMS messages queued in Q subdirectory).

Or, if you're using that IP notification feature, the message will be queued in the IPNotify subdirectory.
emulatormms
Unregistered guest
Posted on Thursday, May 13, 2004 - 04:20 am:   

Hi BN,
Thanks for the information. Trying to send MMS message to MMS enabled phone is giving Invalid Recipient format TO: 09886027713 error. I tried with 00919886027713 and +919886027713 formats too, but the error is the same. How do I resolve this?
Regards,
Khan
emulatormms
Unregistered guest
Posted on Thursday, May 13, 2004 - 07:15 am:   

Hi BN,
I was able to resolve the Invalid Recipient problem. The MMSC Debug is not reporting any error during the send process. But I am not receiving the MMS message on the phone. What could be the problem?
Regards,
Khan
emulatormms
Unregistered guest
Posted on Thursday, May 13, 2004 - 11:29 am:   

Hi BN,
In the log file I am getting 2004-05-13 17:40:42,MMSIN,10.1.1.23,,,User Not Defined,FAILED error. I believe this error occurs when I use a non-existing username/phone number while configuring MMS Server URL. I am using the phone number of existing MMSC user, I am wondering why this problem is occurring!!:-(
Regards,
Khan
rdlg
Unregistered guest
Posted on Thursday, May 13, 2004 - 01:29 pm:   

Hi. I'm triying to send an MMS message (which has an WML file with an anchor element) to a Nokia 7210 emulator, but it doesn't work. The 'phone' doesn't receive nothing.
Can anybody help me?

Thanks.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2592
Registered: 10-2002
Posted on Friday, May 14, 2004 - 01:47 am:   

Nokia 7210 question duplicated at the link below:

http://support.nowsms.com/discus/messages/485/4360.html

Login Login / Register Logout Logout Search Last 30 Days Topics Topics