Bluetooth Dial up network connection problem

[Kiwi_in_tok]

Hi,

Recently got a new bluetooth mobile (Sharp 902SH) and I have been setting it up for bluetooth with my hx4700.

I can bond the phone and PDA without issue and can set up the DUN for data access, however when I try to make a outgoing data call the PDA indicates it is dailing *99# (the number) however the mobile does not intiate any call.

During testing I enabled the manual dial option on the PDA and if I type in ATDT*99# from the terminal screen the phone makes the call and connects. I can't get any further as the manual option spoils the logon sequence however it does activate the phone to make the call.

This seems fairly standard AT commands so was a little confusing. I can also confirm that if I try to access the DUN to this number from my portable PC via my bluetooth dongle that it works fine!!!!

I have tried 3 different HP PDA all with the same issue in regards to making a data call via the DUN. However I have also tried the bluetooth dial access from the contact list for a voice call and this works fine.

Appreciate any thoughts / ideas as to why the phone is not activating when the PDA dials automatically when using DUN for a data call.??

Regards

Gareth

[Menneisyys]

Unfortunately, there're some models that just refuse to work together with PPC's. I had, for example, severe problems with the Siemens S55 - worked flawlessly with the dekstop abd Palm OS devices, just not with Pocket PC's. Nokia and, particularly, (Sony-)Ericsson phones have always been very easy to configure and use. Hope the Sharp is unlike Siemens models.

Some hints:
1, try using *99***1# as the virtual dial-in number.

2, if it doesn't work, add +CGDCONT=1,"IP","<APN>" as the extra string in the Options sub-menu on the last account setup-screen in Connectivity; and try both the *99***1# and the *99# "dial-in" numbers. (<APN> is the name of your GSM provider's APN name, e.g., "internet")

3, you can also give a shot to communicating over IrDA - I don't think it helps, but still can be tried.

[Kiwi_in_tok]

Menneisyys,

Thanks for your suggestions, after much trial and error I found out what the problem was.

I simply had to add z to the extra dial-string and remove IP header compression.

And away we go vodafone 3G access...

Thanks again Gareth

[Menneisyys]

I simply had to add z to the extra dial-string and remove IP header compression.

Yeah, some modems need to be reset (ATZ) before sending over any additional info (e.g., data account on-the-fly setting with +CGDCONT), or, even, dialing.

IP header compression helps almost nothing to save bandwidth. V.42bis, on the other hand, is much more important to have because RLE encoders like that can save up to 30-40% bandwidth. Did you try to enable it? It's mostly referred to as 'body compression' in mobile phones and is one of the latest parameters of CGDCONT too.

[Kiwi_in_tok]

If you mean "Use software compression" then yes I still have that enabled. However I am not sure how to confirm my throughput, I am looking for some traffic measuring software at the moment.