Hey OBT, no, the PRI is on the 8290 module, which is connected to virtual gateway cards as SIP trunks "trunk module". It would definitely be easier with a physical PRI card in the 620 cabs.
It's arrived. Setup in my office right now and working perfectly. Getting a complete set of videos soon, as soon as more phones and the DSS arrive. I may post links to the videos in the general forum so everyone can see some nostalgia (or nightmares of the past depending on how you look at it).
But, I can show you this for now
Dans,
Unfortunately, no. I pretty much exhausted all chances of that. This one came from Edmonton, Alberta. It was a steal for the system itself, but cost a small fortune to ship. It was immaculately taken care of in the tech support room of at an interconnect up there. I've got lots of spare cards, fuses, etc. Given the shape it's in and that I'm not likely to find another, it was worth it.
No idea if 5.03 allowed any sd card to work or not, I guess you could try it and let us know. I never saw in the 5.03 product bulletin that it enabled any sd card , only that in the US market it enabled full licenses.
When Samsung had a problem with their cards , they used Transcend cards . They work. I have used the 2gb cards like these
eManager is only for the phone system AFAIK - Strategy something or other is usually for the voicemail side. However, you should be able to find the Call Forward No Answer setting in eManager and turn it off for that extension.
Thanks, I'll look to see how to manage the voicemail side if we have to before it's replaced. What we settled on was using dial code #621 to deactivate the system call forward which seems to have done the trick on the handset.
Hello Everybody, I've been managing an IPK-1 system for about 12 years. ( IPK-I, pk192, R4.2sw, T1 DID, COI, 48 PBX stations, 48 SLI stations, Elite Mail )
It's an old system but it's been completely reliable and the staff is satisfied with it. But we need caller ID and that requires moving from T1 to PRI.
Reviewing the manuals and some older threads, especially by "doghart", I have come up with this work list of which I would greatly appreciate any comments or suggestions:
1) Must use MIFM-U20 ETU with KMM chip installed to capture caller ID numbers.
2) Must use PRI-U20 ETU on "newer" IPK systems.
3) Must remove COI trunks, evidently their presence in the system is not compatible with PRI.
4) Remove T1 ETU and replace with PRI ETU ( 7-1)
5) Delete the T1 trunk group, Build new, PRI trunk group: Telco must provide PRI D channel on time slot 24 span type: b8zs ( 1.13.xx) trunk type: WINK (3-14) trunk type DID (3-91) assign DID ( 1-1-20,21,22)
6) Set up CAP keys on the stations and remove any CO appearance keys. ( 4-12 ) Currently we are using both CAP and CO on the same phones.
Questions: Since I'm going from T1 to PRI will the master clock source change ? (can't see why it would ...) If the DID configuration is already programmed can it be reused with the PRI trunks? Is there any way to have a COI trunk group with a PRI ? (Currently I have dial-8 for CO trunks, dial-9 for T1.)
Yes Wifi seems to becoming more common. While waiting at a car salesman's desk, I looked to see if the network cable went to the phone, then the pc. I then saw the phone was only connected to a power supply, it was a Yealink phone.
It's surprising how cabling can simply be overlooked. Had a customer that moved into a nice and new remodeled facility with a large warehouse. There was no cable of any kind run to the only desk. The computer and Grandstream phone used Wifi, They needed a WiFi extender, but I was surprised how well the phone worked. That particular system with about 15 phones was hosted, The wired phones, like many of that company's hosted systems - experienced a somewhat significant audio delay.
Can you still access the voicemail by dialing 517, or does that ring to 500 as well? If the MOH isn't coming through either, it sounds a bit like the SVMi has crashed....
CPU battery down? The only thing the battery holds up is time and date, data base is non-volatile, outside of that yes, power surges can and do at times, corrupt data or as we all know knock out hardware.