MMS Retreiving Problem

MMS Retreiving Problem SearchSearch
Author Message
Anonymous
 
Posted on Tuesday, January 25, 2005 - 07:33 am:   

Hello Bryce,

How are you.

In NowSMS everything is working very fine, except MMS. I can retrive messages via WAP. means http://xxx.xxx.xxx.xxx/xx/xx/xx.wml retreiving is fine. Sending WAP msg is fine.

But I tried to send MMS messeges using web interface. From web interface it is giving error

Error: Unable to fetch URL:
http://xxx.xxx.xxx.xxx:xxxx/xxxxx/xx/xxxxxx.MMS

I tried by typing above url in browser It's opening the file.

We have Firewall also.

I am attaching My MMSC Setting page.MMSC Detail
Anonymous
 
Posted on Tuesday, January 25, 2005 - 07:46 am:   

I want to tell you some more information about My MMSC settings.

I have SMPP connection. Receive MMS settings are checked and No proper configuration is done under MMS settings. I think it is not related to above probs.
MMSC routing is set at Direct Delivery (internal MMSC).

Thanks


Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3980
Registered: 10-2002
Posted on Wednesday, January 26, 2005 - 05:55 pm:   

Hi,

I assume that 212.143.10.1 is your external IP address, and 192.162.10.20 is your internal address.

If you can retrieve the multimedia WAP push files ok, then it sounds like the IP address assignments are ok.

What is likely the problem is that your NAT (network address translation) router does not allow you to connect from inside the firewall to the externally accessible IP address. This is a limitation of many NAT firewalls.

Basically, NowSMS is just doing a type of edit check to try to validate that the host name is correct. But some NAT firewalls get in the way.

In the past, I've usually recommended that the way to solve this problem is to assign a DNS name to your external IP address. Then in your local HOSTS file on the NowSMS PC (WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS), put in a HOSTS entry that points that same host name to your local address. (See http://support.nowsms.com/discus/messages/485/1350.html)

But, there might be a simpler way.

If you edit MMSC.INI, and under the [MMSC] header, add ExpireDynamicLinks=4320 ... then this setting will have a side effect of disabling the edit check on the URL. The setting deletes dynamically generated URLs (such as MMS messages or multimedia WAP Push content), x minutes after they have been initially retrieved. In this case, I'm just specifying an arbitrary value of 4320 minutes, which is 3 days.

-bn
Anonymous
 
Posted on Thursday, January 27, 2005 - 07:25 am:   

Thanks Bryce,

Using ExpireDynamicLinks=4320 MMS messages also going.

From Server Its going and in log also it is devivered. But in my 7610 Nokia mobile it is not in the Inbox. Left side on the screen it is showing G.

Thanks
Anonymous
 
Posted on Thursday, January 27, 2005 - 10:08 am:   

I also tried with 6100. In both cases, It is showing some icon like G... and after some time disappear.

I don't know if it is the problem of settings in Mobile or NowSMS.

Can you help me, what can be the problem.

Thanks

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4016
Registered: 10-2002
Posted on Thursday, February 03, 2005 - 09:37 pm:   

That's a different issue ...

See http://www.nowsms.com/howmmsworks.htm for an explanation.

If multimedia WAP Push is working, but MMS is not, then this suggests that everything is ok in your configuration, but that your operator's MMS settings block message delivery from external MMSCs.

More detail and info on options can be found at the above link. But if you have any questions, please let me know so I can clarify.

-bn