Switch Tech working on data drop on radio 3.27

[madman34]

Greetings all,
I am an old Nortel NI engineer working in a Verizon switch room. My specialty is the Nortel CDMA platform, including the data equipment as well. I sit in a room where a toy cell provides a super signal so I am ideally suited to test this stuff. Mostly I am working on the dreaded data drop problem that we are having with the 3.27 radio, and so far I am finding that there is a problem, but not too bad and I am not finished gathering data. The device I will log into on a slow night is called the RNC, which is the box that controls, connects, and administers to the DOMs at the sites. So far I find that running 3.27 and SelectRadio I do get random dropps and reconnects, however with Resco Pocket Radio I do not seem to have the drops at all, well at least for the last 30 minutes that I have been listening to it. SelectRadio would drop sometimes in 1 minute and sometimes in 3 minutes but would never go over 4 minutes and sometimes would not be able to get going on its own. Resco is not at 32 minutes and not a drop or glitch. I am not sure why as i have not logged into the RNC to monitor what is happening with the session, but either Resco pre-buffers a lot farther ahead, which would make the connection outage come back before you run out of data, or perhaps Resco keeps the session alive by constantly pushing traffig up the reverse link, like an internet 'keep alive' program and SelectRadio may not do this, allowing the session to go 'dormant' state. This is very possible scenario as the dormant state is valid and a means of bandwidth management. If the system does not see a handshake within a certain time, triggered by the mobile as set by a timer value in the radio, it will put the mobile in a dormant session state. What I will do when I get some time is launch WMWIFIRouter and hook to my laptop or just teather with ICS and ping Yahoo for a very long period of time, or perhaps run a net keep alive on the laptop and stream XM thru it and see if it dies.



Anyone running Resco Pocket Radio out there getting better results than they do with SelectRadio ?????


I will keep this thread up until I get a log from the RNC and we will know what exactly is happening, but I vote for a timer value getting altered in the new Radio build that is giving trouble.

[illuminarok]

Umm, have Verizon task you to find the problem?

If so, what will you do to fix it? If not, is there any way for you to modify a radio driver as it exist now without have access to source code? Why would they modify any setting that already work fine by just upgrade to Rev.A and GPS?

Now, when I run the 3.27 radio, maybe 1 time in 50 time I have perfect connection to my VPN in Japan. There is no trouble at all on that occurrence. I can stay connect for hours. BUT, 49 times out of 50, I will be random disconnect every 3 or 4 minutes, sometimes as short as 20 seconds. If I got lucky by the 1 in 50 chance, I will have no trouble. So, how can it be "timer" issue? I think that it may be an incompatibility with the network and the EVDO Rev.A that is brought in by the 3.27 driver. If nothing else change but sometimes the data connection works fine, then obviously something else is happening.

I have never use 3.27 radio on non WinMo 6.1 ROM and I have also never use WinMo 6.1 on 1.40 or 1.47 radio either. Couldn't this be a WinMo 6.1 issue as well?

The bottom line is, 3.27 radio driver and random disconnects are correlated, but what is the cause? It may be any number of things, please check it and tell us the result, like you said - if you can.

Thanks,

Hiromitsu

[madman34]

Attached is a log from the DOM/RNC connection between my unit and the network and what is going on. Someone else please feel free to offer any analysis you would care to but it looks like with SelectRadio running here is what happens: The session never dies even when the audio skips and SelectRadio re-connects, but what happens is that the PPP session (RN session) breaks and gets renewed, the session stays and does not go dormant. When it finally gets the 'tuner error' the PPP dropps and does not recover, and the session goes dormant. The interesting thing is that clicking another channel or launching any other program brings the session out of dormant and renews the PPP connection. Resco Pocket Radio never dies for me, and I can tether to my PC either with cable or Wi-Fi and ping yahoo.com until the battery dies and never skip a beat. I am thinking that a parm in the new radio ROM has been tweaked either for power management or for making REV-A or GPS work better and maybe they did not realize that it would effect the streaming media like it has, and as I said Resco does not crap out but SelectRadio does very badly. I am not finished yet, but I would like to get a ping utility, ftp, telnet, both client and daemons for my device so maybe I can run a long ping to somewhere while running SelectRadio to see if that helps. So anyone out there have this stuff ????? i will be looking and test more and attach more logs when I get these. Keep Moving Forward.

[madman34]

I am useing SelectRadio and Resco Pocket Radio in the unit as test software. Listening to SelectRadio tab is Radioio channel 70's Rock 128kbps, and it drops like a rock regularly. I am now teathered with WMWIFIrouter 0.95 and on the Radioio web page and streaming the same channel on my PC for the last 30 minutes without so much as a skip. Useing NetPerSec to monitor the connection shows 136.1k average download and 3.9 k average upload speed, so I am leaning towards a compatibility issue between the SelectRadio app not keeping the network alive. This as I have said before might be a trim of a timer or a power management change in the ROM or radio ROM. Just more food for thought. Anyone feel free to chime in with results or ways for me to persue this.

And No I only work for Verizon in the switchroom, I was not tasked by them to look into this, it is a personal quest.

[pflatlyne]

Perhaps this is whats holding up the sprint rom. If this is so,then its good news,as it implies that it may be fixed in the final release.

[madman34]

Greetings all,
Tonight sitting in the switchroom I loaded up VxUTIL and started pinging yahoo.com 99999999 times once per second and launched SelectRadio on the usual station aand got some interesting results. First, the pings went flawlessly and never missed a ping, SelectRadio dropped out as usual 2 or 3 times then got the 'tuner error' message as usual, but as I said the ping never skipped a beat nor in the network did the PPP session fall down. Resco Pocket Radio clicks along without ever skipping as usual with or without the pinging going on. Next test is for me to find the URL for the channel I am testing with in SelectRadio and get it imported into Resco Pocket Radio and see what happens. Anyone know how to get the URL for Radioio channels ??????? I will find this and post back.

[illuminarok]

Maybe try to load on your PC in WinAMP or something, then examine the .pls file?

[Jason_25]

One way to find the URL is to use the Titan's WIFI, and run tcpdump or equivalent on the wireless router or one connected to it. Assuming you have that capability.

Also, maybe your fancy CDMA gear has an option like that.

[madman34]

Heres some more food for thought. I got the URL and loaded it up in Resco and played it at the same time as SelectRadio and though there was a time shift between the streams, each could be heard at the same time. Anoying, yes. Revealing, yes. The same stream stayed up in Resco but dropped out and reconnected and eventually got tuner error in SelectRadio as Resco clicked right along. So although the bad performance of SelectRadio is related to the REV-A radio and ROM upgrade, it is a problem with SelectRadio and how it handles a stream differently from Resco that makes it a problem. It is important to note that the actual data session and PPP stay up and will not drop as long as the net is kept alive. The dormant state was caused by SelectRadio dropping the connection, as opposed to the connection dropping and halting SelectRadio.

When I go in tonight during the maintenance window I will turn off the REV-A on the toy cell and see if the problem with SelectRadio stays or goes.

[gc14]

I don't mean to play devils advocate or be the ass here cuz i'm sure you're working hard....but from what i can see....all that you've proven is that there's an issue with SelectRadio dropping the connection. That is all well and good for people who care about streaming radio on their phone because they'll all make sure to use resco, but that still does absolutely nothing for the tons of people out there ready to punch a hole in their wall because their connection craps out while on aim, or surfing the web, or using their slingbox. Luckily, my connection doesn't drop all that often, every once in a while, but I've read countless other posts with people losing their connection quite frequently while using many other programs that use the data network.