IP address is used instead of phone number

IP address is used instead of phone number SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » IP address is used instead of phone number « Previous || Next »
Author Message
Anonymous
 
Posted on Tuesday, June 15, 2004 - 01:05 am:   

I've created a phone simulator and using NowSMS/MMSC Gateway and NowSMS Web Interface I was able to send a MMS message to my phone simulator (IP address was used as a phone number). But when I tried to use a cell-phone to send the MMS message, I got an indication saying that the message was corrupted. The IP address is not local. Any idea??
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2845
Registered: 10-2002
Posted on Tuesday, June 15, 2004 - 08:36 pm:   

There's a trick where you can define that particular phone numbers should receive notifications to a TCP/IP address.

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.)
Anonymous
 
Posted on Tuesday, June 15, 2004 - 11:46 pm:   

Hi Bryce, thank you for your response. I've followed what you suggest, however the simulator still not showing any sign of receiving the MMS message. I was able to look inside the incoming message and was getting "application/vnd.wap.sic" MIME content-type (with no X-WAP-APPLICATION-ID) instead of "application/vnd.wap.mms-message". When sending from NowSMS Web Interface the "application/vnd.wap.sic" was never there. Is this normal? And what is this "application/vnd.wap.sic" anyway? Kinda new in the wireless world. Thank you.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2858
Registered: 10-2002
Posted on Wednesday, June 16, 2004 - 06:09 pm:   

No, that is not normal.

Go to the "MMSC Routing" page of the NowSMS configuration.

Make sure the "Default Route" is set to "Direct Delivery (internal MMSC)".

It sounds like it is configured as "Convert MMS To Multimedia WAP Push" on this page. That means that instead of delivering the MMS as a true MMS message, we convert it to a WML page, and send a "Service Indication" WAP push linking to the page. "application/vnd.wap.sic" is the MIME type for a WAP Push "Service Indication" message.

-bn
Anonymous
 
Posted on Monday, June 21, 2004 - 09:36 pm:   

Once again, thank you for your great support. Right now MMS sending/receiving is working between 2 simulators. Still, there are couple things I found during testing that I need to understand. First, why is it NowSMS Web Interface doesn't generate SMIL message when sending MMS? Second, when Enable Dynamic Image + Audio Conversion is checked, somehow if there were 2 attachments in the MMS message (1st is Image type, 2nd is Text type), the Text type attachment was eliminated from the message and so I only see the image, but not the text when I viewed the incoming message. But if Enable Dynamic Image + Audio Conversion is not checked, I could see both attachments. Haven't tried if I reversed the order of attachment. Thank you.
Anonymous
 
Posted on Tuesday, June 22, 2004 - 12:38 am:   

Oh, one more thing. If I ran NowSMS/MMSC, NowWAP and simulator (Rx) on the same machine (same local IP address) and another simulator (Tx) on different machine, MMS receiving was not working at all. I captured all incoming packets using Ethereal and looks to me all packets actually arrived. Is there any differences between NowWAP and Kannel WAP (this one was used on my first experiment)? Thank you.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2961
Registered: 10-2002
Posted on Wednesday, June 30, 2004 - 05:26 pm:   


quote:

First, why is it NowSMS Web Interface doesn't generate SMIL message when sending MMS?




SMIL is not technically required for an MMS message (although the presentation can suffer). We do allow you to include a SMIL file as one of the file objects that is included in a message ... but we don't automatically generate any SMIL.


quote:

Second, when Enable Dynamic Image + Audio Conversion is checked, somehow if there were 2 attachments in the MMS message (1st is Image type, 2nd is Text type), the Text type attachment was eliminated from the message and so I only see the image, but not the text when I viewed the incoming message. But if Enable Dynamic Image + Audio Conversion is not checked, I could see both attachments.




Does your device have a user agent profile? ("Profile:" header)

It sounds like possibly "text/plain" is not referenced as a valid content type for MMS within the user agent profile.

Can you post this profile?

Note ... if you update that profile, you need to delete the cached copy of the profile in the UAProf subdirectory of NowSMS.


quote:

Oh, one more thing. If I ran NowSMS/MMSC, NowWAP and simulator (Rx) on the same machine (same local IP address) and another simulator (Tx) on different machine, MMS receiving was not working at all. I captured all incoming packets using Ethereal and looks to me all packets actually arrived. Is there any differences between NowWAP and Kannel WAP (this one was used on my first experiment)?




Running all that on the same PC should not be an issue. The WAP gateway should not even be a factor in this, as it is not used in the push part of the transaction. (It is only used when the client pulls the MMS content after receiving the push.)

In this configuration, NowSMS will periodically retry the push. Perhaps something is wrong with the emulator binding to port 2948 to receive the push over UDP?

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