Nortel 350 ADSI (Analog Display Services Interface) CPE | Demo
Вставка
- Опубліковано 3 жов 2024
- A working demo (finally!) of an ADSI-capable telephone with Asterisk's (now fixed) ADSI functionality, using the GetCPEID() application. The phone used here is the Nortel 350 "US West Home Receptionist" phone.
If you install Asterisk using PhreakScript, the enhanced version of Asterisk installed includes the ADSI bug fix: github.com/Int...
Thank you.
I've used a Aastra/Nortel 390 handset for many years. (From what I can tell, the phone uses the M38869MFA microcontroller, a battery-backed CY62128BLL-70SI CMOS SRAM, an 24C02W6 erial EPROM, and more.)
I never liked the idea of putting information into something if I could not get it back out. For example: the 200-entry directory in the phone.
On the circuit board is a 6-pad "J5" header which I suspect is a serial port. The pads are somewhat accessible through a manufactured hole in the back of the phone. What do you think about trying to interface with such phones directly through such a port connected to a computer running a terminal program?
Do you know if the data be backed up, updated, and otherwise managed via Astersik?
Thank you.
Edit...
ADSI commercial from 1998
ua-cam.com/video/kqy8x5my5ow/v-deo.html
That's a great question... as far as I know, ADSI is really only used for downloading programs *to* the phone, and I don't think there's a way to do it in the other direction. The specs do have a provision for, in later editions of the protocol, 2-way FSK communications and possibly that was done with this use case in mind, but I don't know of any common CPE that support that.
Asterisk currently wouldn't support it either way, but if the protocol allowed it then it could be added. I've recently added support for on-hook programming (you can expect another video about this soon).
Realistically, I think the server should be the "source of truth" regarding as much as possible, with a download to synchronize in one direction probably being the best way to do things.
@@InterLinked1 Thank you for entertaining the idea. :) Phone recovery or backup service would be interesting. I bought my phone from the telco as a private customer, not as a business.
Yes, unfortunately looking through the ADSI spec, I don't see any provision for updating the local directory using the protocol. I think the built-in directory is separate from the ADSI functionality and really just a local directory. I tend to not use things like that.
What might be interesting is an ADSI-based directory, e.g. a "Directory" softkey on the home screen can simply call up a Directory service that then allows you to interactively search the directory using the ADSI protocol. This would be centralized so there would be no need to maintain anything in the phone. It would be a little bit slower perhaps but that would solve the synchronization issue.
May I ask, when you press hold on one of these what does the caller hear (if anything)? I am thinking of getting a Bell one from Facebook Marketplace. Don't know much about how to simulate all the ADSI stuff (I take it you have a PBX?) but I think nonetheless, it would be a good phone for me instead of just the cruddy little VTech (cheapest phone one could get at Walmart) I have.
Nothing, pressing hold on the phone is a local hold (as opposed to Dial Call Hold, the MVP/Centrex feature, where the switch holds the call for you, perhaps furnishing hold music to the caller). Hold at the phone itself just places a load on the line to keep the line in use even when you hang up the handset, it's all low-level electrical stuff, no smarts to it.