hellkvist.org

[eyt]

Great program! it's let me get around AT&T not supporting my phone yet... I am running into one problem. Someone posted a similar question on the Peffisaur forum, but it seems to have magically resolved for them.

Basically the message gets delivered and stored, but the phone is unhappy with the response string and wants to resend.

I've tried tweaking a few things, but without much luck. Any ideas?

[Peffis]

Have you made sure that the server doesn't put put any sort of error message in the return message? You could either try the "poster"-script that I posted in some other thread to check that the output from your server is ok (it's bloody hard to debug by using the phone alone).

You could also try and post against my installation and see if you experience the same problem. It's at "http://hellkvist.org/diary/(send.php or view.php)".

What phone is it? Someone mentioned that Siemens for instance can be extra picky with the return message. They need a message id as well it seems (and not only the fields in writeBackSendConf. Unfortunately when I tried adding it it broke it for SonyEricsson phones. It did make it work for Siemens though. If you do have a Siemens phone I could perhaps try and find that piece of code for you. It's just a matter of adding one or two lines in writeBackSendConf if I remember correctly.

If it's some Nokia or SonyEricsson or any of the others then I think it might be a problem with either your setup or your wap gw. Are you running your own gw in that case? A kannel one perhaps? Or are you relying on your operator's gw?

Sorry for not being able to be more specific. The error causes in these matters are SEVERAL as there are so many free degrees.

[Eyt]

I've been using your script to debug... Responses look something like:

[Peffis]

Yes, that's what the response should look like so it seems to be installed properly. So what can then be the problem...the 6600 should be happy with what the script return because I know of at least on person who has sent a message ok with that phone (and most vendors seem to have the same implementation roughly in the phones).

So my guess would be that the gw/proxy does not really properly relay the data back to your phone. It is probably very standards compliant - it can just be configured to not relay certain content types so that people will be forced to use their own servers where they can charge you for it.

Are you using the same proxy as you do when sending normal MMS:es? If AT&T has another Proxy for other type of wap traffic -like browsing - then you can try and use that one instead (check your wap profiles). That's a trick that has helped many as those gw's are often configured to be more open.

Apart from that, well, there are so many points of failure so without studying the noop of the network it's very hard to know what's going on. And your operator won't help you much I'm afraid

[Peffis]

...or another guess would be that your server is very slow to respond so that the phone times out and does a resend before it receives the reply.

[Eyt]

I don't think it's the delay... you're probably right about the proxy/gateway blocking stuff. AT&T most likely doesn't want people to run use someone else's mmsc.

I'll need to think about it, but maybe it's a lost cause...

[Eyt]

when I just post a text or audio message through MMS (no image), it goes through...

So on a whim I commented out the apply_hooks call and things magically started to work...

odd, but I'll have to dig deeper to figure out exactly what the problem was.

[Eyt]

I'm just dumb, forgot to compile in GD support, it was dying on imagecreatefromjpeg, and test script doesn't submit an image, so...

[Peffis]

Hehe, you are not the first Many people say "It's not working" and it's often GD's fault - or missing GD rather.

Good to see it's working for you now!

Have fun!
Cheers
Stefan