vB Easy Archive - 650p/700p/755p verizon text message errors

Pages: 1

650p/700p/755p verizon text message errors
(Click here to view the original thread with full colors/images)

Posted by: EvilSpork

I have been getting intermittent errors when sending SMS and MMS messages from my 700p. i also had these errors on my old 650p, and my friend with the same service has had the same errors on his old 650p, 2 refurb 650p's, and a brand new 755p.

The error pops up after sending an SMS or MMS. it will send like normal and then immediately kick the message back with an error. it feels a lot like a mailer daemon when sending an email to a bad address.

i have been through three trouble tickets with verizon, each is now closed as resolved. they have claim to have never seen these errors and have no idea why i get them. they insist it is a problem with my device, yet it has happened with FIVE different palm devices. after they tried to swap my new 700p for a refurb(i refused) they did more research and decided i was sending EMS. (enhanced messaging, aka 161 or more characters or special symbols, formatting, etc. click the link for more info)

they informed me that treo 650p/700p/755p are not EMS capable devices, and because i was sending EMS they were failing. that was a great idea except i can send the message "hi" and get errors. i tell them, and they just tell me to stop sending 161+ character messages.

it seems the verizon network thinks regular generic SMS are EMS for no reason. i have tried to push this point to the reps but they wont hear it.

this all started some time in roughly june/july2007.
all the errors are formatted as Code 2, Error Name (#)
the most common error is the Destination Resource Shortage (35), though i have gotten Network Failure (3) and No Acknowledgment (34).

has anyone seen this before? know a solution? anything?

pictures of the errors:

Posted by: etard

I have gotten these exact errors on my Verizon 650 maybe 10 times and always just assumed they were network errors at the moment. as I could always resend them soon after. I never attributed it to something specific about the message and never really thought to much about it.

I am looking at some right now that are all the same error

Message Failed Status Information:
(256) Unknown Cause Code

11/28/07
1/4/08
1/10/08
1/24/08
2/1/08
2/24/08
2/24/08
4/15/08
4/17/08

Posted by: Instantwill

Well, I think Verizon is telling you a fib. These codes all indicate an issue on the carrier side, not the phone side. I have gotten a couple of these codes in the couple of years I've used Treos(650,700p&700wx) with my Alltel service. You just need to get a hold of the right person in tech support to help you sort it out. I'm assuming by looking at the screen shots, that you have good signal and call quality is OK. The easy answer for any carrier is to always blame the equipment, not their network.

Posted by: etard

this is kind of interesting:

http://www.commzgate.com/2007/07/22...ith-gsm-modems/

Posted by: grivas3

Funny how you guys talk about this because it happens to me sometimes. Not lately though. What I do is just ignore it. And eventually it will resend. What I do tend to do every month is do a monthly update. *228 and dial 1. After that, do it again and dial 2 instead. Also I take the battery out of the PDA every morning. What this does it reboots the cell phone. And the reason for it is because. The phone can't work 24 hours straight 7 days a week without being turned off. Just doesn't make sense. You have to put it to rest. Like us. We get to sleep. So it's basically the same with the phone. Me I don't turn it off. Because I use the alarm on it. I just wait until I wake up and do the battery out then I will put it back in. I wait for about a minute before putting it back in. Just a suggestion, good luck.

Posted by: EvilSpork

Quote:

Originally Posted by etard

this is kind of interesting:

http://www.commzgate.com/2007/07/22...ith-gsm-modems/

Quote:

Originally Posted by Instantwill

Well, I think Verizon is telling you a fib. These codes all indicate an issue on the carrier side, not the phone side. I have gotten a couple of these codes in the couple of years I've used Treos(650,700p&700wx) with my Alltel service. You just need to get a hold of the right person in tech support to help you sort it out. I'm assuming by looking at the screen shots, that you have good signal and call quality is OK. The easy answer for any carrier is to always blame the equipment, not their network.

i know!! thats what is aggravating me so much! they keep telling me to stop sending EMS or hard reset my phone, or this or that, when it is clearly not an issue with my specific device!

ill just keep calling back one after another till i find someone competent.. and a manager.

Posted by: Instantwill

Quote:

Originally Posted by EvilSpork

verizon isnt GSM though, its CDMA. interesting article though.

i tend to get error a LOT more in lower signal areas, though i still get them in very high signal area. generally i can make a phone call without much issue in the same place i get errors.

specifically at my house, where all those pictures were taken, i get still get errors.

ill try calling back tomorrow and try to get someone who isnt in india. so far they have been the least helpful.

i know!! thats what is aggravating me so much! they keep telling me to stop sending EMS or hard reset my phone, or this or that, when it is clearly not an issue with my specific device!

ill just keep calling back one after another till i find someone competent.. and a manager.

AHHH, the hard reset. I love it when they pull that out of their bag of tricks. That want fix anything unless you have a corrupted database. In which case you can download DbFixit or TealScan and run it to see if it will find any errors it can fix. Just keep after em, somebody somewhere at VZ surely can help you get it sorted out.

Posted by: EvilSpork

Quote:

Originally Posted by Instantwill

thats good to know, ill be sure to just tell them that ive done that already. see what they do then! HA!

Posted by: EvilSpork

i called verizon back AGAIN and this time got an answer!

for the 700p specifically, the software version Treo700p-1.10-VZW is out of date.
you need to update to version Treo700p_-1.10-VZW.
apparently this new update implements a fix in the palm OS that made it incompatible with MMS networks.

this should fix issues with MMS and MAYBE SMS. there should be a similar version for the 650. the 755p patch is not available "yet".
then of course the tech said he would call me back on my land line in 30 minutes when my phone was finished updating and what a surprise that he never called... *sigh*

we'll see if that fixes it. hopefully there is a similar patch for other carriers.

edit: a handy thing to know: dial #*#377 to get the palm crash log. this should tell you the last time the phone crashed and what caused it.

Posted by: EvilSpork

annnnnnndddddddddddddddddddddd

that didnt fix it. got a Destination Resource Shortage (35) last night.. *sigh*

Posted by: Instantwill

Verizon......it's the network.

Posted by: EvilSpork

Quote:

Originally Posted by Instantwill

Verizon......it's the network.

yeah. it is.....

also a new error code!

Posted by: EvilSpork

so i finally got something from verizon.

they insist its EMS still so i have a brand new phone to test out for a week or two without hot syncing to eliminate any possibility of an EMS.. so we'll see.

also before i activated this new phone i accidentally tried to send an SMS and got a destination resource shortage. so its pretty certain that error means that the phone and towers are having a communication failure.

Posted by: EvilSpork

HA! so i got the new 700p. i manually added a few names and went on my merry way being sure to tell all my friends to not send me EMS.

and guess what! SHOCKER! i still get the errors! *gasp*
so now ive gone through EVERY idea they have thrown at me for making it my fault. ITS THE NETWORK! ...

Posted by: Instantwill

Man, I'm sorry your having to go through so much crap to get the problem fixed. Maybe now they can start to locate the REAL problem.

Posted by: EvilSpork

Quote:

Originally Posted by Instantwill

Man, I'm sorry your having to go through so much crap to get the problem fixed. Maybe now they can start to locate the REAL problem.

finally theyre putting a fourth trouble ticket in to the verizon NRB (Newtork Repair Bureau).

he has 10 digital images of errors, plus i copied one and texted it to him, plus he has the combined info from the first 3 tickets plus everything i told him now.

so finally NRB will take an actual look at the problem instead of passing it off as user error as they have 3 times before. they even specifically noted to NOT make any more tickets on the issue as it was resolved as being user error. annnddddd NOPE!

so i may finally see verizon stepping up and admitting their mistake and trying to fix it soon!!!

verizon. ITS THE NETWORK!

Posted by: philed

i have been reading the same thread. i finally got so sick of "destination shortage errors" that i landed here. i am not ready to head to verizon yet...only because i dont have time, patience, insert reality here... please keep it going.

Posted by: EvilSpork

Quote:

Originally Posted by philed

i have been reading the same thread. i finally got so sick of "destination shortage errors" that i landed here. i am not ready to head to verizon yet...only because i dont have time, patience, insert reality here... please keep it going.

well so far ive sent 5 emails to the guy who was creating the work order this last time trying to get him to send me the NRB ticket number but i have had no response.

its been over a week with no word from verizon, so im going to call them as soon as i have time, which may be tonight.
have hope! we'll get there eventually!

Posted by: EvilSpork

great. so i got a call when i left my phone at home one day by accident. they told me to stop sending EMS even though i EXPLICITLY explained to them that i am now... *sigh*