Has anyone experienced CID problems? I'm just playing with this in my home, when I first hooked it up CID worked fine, placed about 10 calls. Hooked it up today CID very intermittent, tried another KSU same problem. I reset the KSU and phones it might work a time or two than back to intermittent. I bridged a CID box ahead of the KSU and get CID every time.

One thing I noticed even after the phones and the KSU were unplugged for a couple days they still came up with the correct ext numbers and named I'd entered, when I put the phones on the new KSU the ext numbers stayed the same, so the memory for the ext number must be in the phone, not the KSU. Don't know if any of this has to do with the CID problem or not. Thanks.

No, no, and no.

Caller ID stable.

2 minutes without power should dump KSU. Did you flip the switch three times?

The memory is in the KSU, not the sets. ?????

Of course, I could be wrong about all the above...just did the reset thing for a customer. She had to re-register the sets, redo the ringing, and VM. What can I say?
:shrug:

Yep all the above Ken. And when I put the sets on the new KSU the "non" admin set ext 302 came up on the new, freshly initialized KSU. That's why I said the "my extension is" must be in the sets and they were unplugged and the KSU had no power for over 48 hours.

No answer here....the last time I had one do that was the freebie I got for attending the Dealers Meeting....just did weird things. Paul said send it back...he wanted to play with it.

Will check with my installed base, get back to you.

Ken

Yes, Bill, many of the station-level programming items are actually stored within the phone itself. This includes speed dial entries, caller ID logs and of course, the extension number itself. The phone has a very limited memory retention time (a couple of minutes without power). If a phone is disconnected longer than that, it's possible that this stored information will be lost.

These are kind of like IP phones without the power requirements. Unlike traditional key systems where everything is stored in the KSU, the X-16 does distribute some of the intelligence to the phones themselves.

They do offer a "terminator" that can be plugged-in to an existing jack if a phone must be removed for an extended period of time to retain the system's settings. It is very inexpensive.

As for the manual and documentation for the X-16, I think that the whole set consists of about ten pages. There's just not much to it and 90% of the features are already set. With the exception of ringing programming, there's not really much else that you need to know.

Your right about the ease of programing Ed. I'm messing around with it again this am to see if I can correct the problem. Like I said everything was unplugged and in the box for over 48hrs.

hitechcomm, Ken, if you figure it out let me know, I'll post if I do also.

Here's what I did:

reset KSU
Hook up phone and reset phone
reset KSU again
power down and back up

CID worked one time, Don't forget two KSU's are acting the same. At this time I'm just using one phone, was using two when all this started.

NOTE: after all this went into CID history and all history from yesterday was still there, even after phone and system reset and being without power and unplugged all night.

Spoke to 2 of my customers, they did not notice CID problems, they will start taking notice.

Plugged in other set after removing the one I'd been using. Again after being unplugged all night it came up with the extension number I had assigned it and had CID history. Cleared all history, did the above proceedure and it came back as ext 301 as it should, CID worked one time.

Thanks Ken. I'm holding for tech support I've done all I can think of.

King couldn't help so left a message for XBlue.

OK while waiting for XBlue to call I powered down again, didn't reset anything, the only difference is I pulled the plug from the wall instead of pulling the adapter from the KSU, I've place 8 calls and CID appears to be working. :bang: Still going to run this by XBlue.

Bill, if you gently and quietly remove the cover, you'll see the teeny, tiny, micro, micro, micro switch, next to the power jack, that is labeled, "Improper Disconnect Punishment". But, you have to be quick, it runs to the darkest part of the cabinet when you take the cover off. One guess what it does! John C.

I must say I've done a lot of playing around trying to recreate the problem. Powering down is for at least 10 minutes. If I leave it powered down and never unplug the phones and power it back up all will work. Sometimes, not always, if I power down and unplug the phone than power back up after plugging in the phone it will fail, until I pull the plug from the wall about 10 seconds than all will work again. It doesn't seem to matter if I unplug the phone before or after powering down.

Now for sure the CID and other features that ED mentioned are stored in the set and not the KSU, I can clear all CID information from one phone, plug in my other phone and all the CID info is still there on the phone. Don't know if anyone else didn't know that but thought I'd throw it out there. The CID history will stay even if you reset the phone.

So bottom line CID is now working fine, but I can't come up with any definitive reason for what makes it fail at times when powering down the system. I pumped a lot of calls through it and I'm confident once it's working it will keep working.

I haven't heard back from XBlue yet they were going to try to recreate the problem also.

Bill:
I am having CID problems with a X-Blue sys I have been ask to install in a business office.I was woking with the system here in my home-shop on another problem when I noticed the CID was only coming in on about ever other call.
The thing I was working with was call pick-up on ringing line transfer from the auto attendant.I found out you cannot pick up a CO call transfer if you pick up the hand set and dial #,you have to dial # first then pickup the hand set. In the process testing this I made several calls, this is when I noticed the CID.This was on Thursday and I read your post that evening and went and unpluged the system.Friday AM pluged it back in and made 10 calls, failed on 2nd call the rest came in OK.
Exactly what did you do to clear you problem?
Went back today ,Sat tried 4 times ,faild 3.

Kenneth

All I did to correct it was unplug the AC from the wall, or transformer for about 10 seconds and plug back in. If I unplugged the adaptor at the KSU it wouldn't correct it. I also cleared all CID info from the station using the deleted all process. I must have places 30-40 calls and no problems since.

I'm still having problems with CID,but I think I have more than one problem.I connected a Partner ACS 3x8 and a CID phone to my line with the X-Blue and made 10-12 calls and the X-Blue failed to pick up CID twice and one time none of the phones got CID. So I am thinking I am not getting a signial from the CO every time.Need to put my but set and see if I can hear the data stream when the CID signial is sent.
I did what Bill did and disconnected from AC for 20-30 seconds but that didn't help.
As matter of fact I made 4 calls and none came in on the CID,so I re-set the KSU then I tested with all the phones on the line as I stated above.

Kenneth

Since I powered down from the source and not the KSU adapter I've had no problems. Let us know what you find Kenneth.

Well today I added a Norstar 8x24 with a M8 Id interface I am testing to my line and made 7 calls and CID came in,but on the 8th call the X-blue failed,the Norstar, the Partner and the CID phone caught the CI.Maybe I have too much "stuff" on my line? We have DSL, Digital TV and dial tone all coming in on a POTS line.So tomorrow I may take the X-Blue to my brother-in-laws home and test it there.I only have one line and a cell phone to test with here.

Kenneth

Thanks for the update Kenneth.

I never did hear back from XBlue so I assume they couldn't recreate the problem.

I just boxed mine up yesterday after letting it cook awhile and no more problems.

Bill, I had the same power issue here, but with an answering machine that wouldn't retain it's memory. If I pulled the plug at the machine end the contacts wouldn't engage the battery. However if I unplugged from the outlet, it would.

Must be a design thingy....

Must be. It was also a drive me nuts thingy.