RS232 to MCA and CTIA (3905)

[overlayx]

Hi all,

I've had no problems connecting (through Hyperterm) to my MCA's on my 3820's and 2216's, but now need to do something similar with my new 3905's (fitted with CTIA adapters).

The problem is that it doesn't seem to work!? I'd get a message string back from the MCA's but there's nothing from the 3905 - not a peep.

I'm using the same RS-232 cable (and the phone, of course) successfully with the CTIA telephony driver for TAPI, but being able to get a message back from the phone just through Hyperterm would make my life extremely easier.

With the 3820/2216 I also had the option of setting RS232 comms parameters through the telsets data parameter display options, but the 3905 doesn't seem to have that feature.

Any ideas on what I'm doing wrong?

Cheers.

 

[pansophic]

This is just a guess, but do you have Hardware Flow control set in Hyperterminal? If not, you may not be asserting RTS, so the 3905 may not think that there is anything connected to send data to.

As I recall, you have to set Hardware flow control, save the terminal configuration, close Hyperterminal and then restart Hyperterminal.

I haven't used the 3905 at all, so this is just a guess, but generally, if RS-232 (V.24) devices aren't responding the way that you expect them to, it is because you are not asserting the proper control leads.
pansophic

 

[overlayx]

Thanks for the reply, pansophic, I was getting to think that my message was invisible.

Actually there's been a small update since I sent my original message. It's gone from the '... not a peep ...' from the 3905 to a horrid stream of symbols. I'm fairly sure that it's not 7 or 8 bit issues, or even data rate or stop bit settings. There are only so many options and I've tried them all. I'm reasonably sure that what's changed is the protocol.

There's always been something useful streaming out of the back of all the Nortel telsets until now, but I suspect that they've decided to change the protocol for some reason for the 3905's.

If it wasn't for the fact that the first party TAPI drivers are crud, I wouldn't even bother with this solution to get a bit more info.

So, does anyone know the details of the new protocol streaming out of the back of the new 3905's? ( ... not holding my breath here...)

Cheers.