[richardsbd]

So we just got free (!) upgrades from BB7290 to BB8700c from AT&T for all our old devices (82 of 'em), and after upgrading and issuing about half of them, my boss comes to me and asks, "Why can't I send a PIN message now?"

She had had a year-old Cingular-branded 8700c (v. 4.1.0.377 handheld OS), but it 'malfunctioned' and so was replaced with one of the new AT&T-branded 8700c (v. 4.2.1.96 handheld OS).

The old device was activated to the same BES as the new device (same IT Policy), and the 'send' command was available in the 'compose PIN' menu.

The new device, however, is able to receive and compose PIN messages, but the 'send' command is missing from the menu (and, yes, the To: field is populated).

My first thought was that the IT Policy had been modified on the BES, but after working with the office that manages the servers, and after additional testing of my own (took one of the new devices, downgraded the OS to v.4.1.0.377, activated it to the BES, and there is no problem - 'send' command is there), we've ruled out the IT Policy as a factor.

I also had the presence of mind to check one of the new devices, right out of the box, and before activating it to the BES the 'send' command is available on the compose PIN menu - it can send PIN messages!!!

The problem only manifests itself after the handheld is activated (EAed) to the BES - which is running version 4.1.x.x BES software (I can't get any more precise on the BES version, sorry).

So, has anyone else seen an issue where an 8700c with v. 4.2.1.96 handheld OS, after Enterprise Activating to a BES server on v. 4.1 software (Windows 2003), no longer has a 'send' option on the PIN menu?

To reiterate answers to hdawg's questions on my other post:

- the device can receive PIN messages
- the OS is out of the box from AT&T (not an upgrade)
- all other functions work as expected
- this is on corporate BES (not BIS)
- all devices have the same 'issue'

TIA,