Magix using U-verse lines

[holly7wood]

Thank you in advance for your help. Somewhat lengthy description of issue to follow. I must have checked 800 threads trying to find something that discussed this.

I have a Magix customer in key mode that acts like a answering service. They serve as the "office" for a number of non-profits and handle a number of administration duties for them, and each customer has 1-2 lines on the Magix. We recently converted 2 lines for one of the customers to U-verse to take advantage of the "find me anywhere" feature which allows the incoming calls to ring not only at the main site, but at a remote site simultaneously. We did this because one of the office personnel handling that particular customer moved out of state.

The remote person had U-verse installed with 2 lines. The ringing is working perfectly at the remote site. CID is coming through. However, the CID is no longer working at the Magix on these lines. I have tested the CID on the U-verse port and it is working. After this problem came to light, the customer told me that the same thing happened on 2 other lines that they converted to U-verse 6 months earlier. I did not participate in that conversion.

Checking down on whether I missed something - the lines are on the same ports as before. There are approx. 12 other lines on the system with no CID issues.

The question: Anyone ever hear of this before? Does U-verse CID not work on the Magix? Anyone have an idea why it wouldn't work?

Alas, the problem is, for good or bad, not many of my customers are still enjoying Merlins anymore, they're in the cloud, for good or bad, and I'm not as sharp as I once was.

Thanks again for any and all replies.

Holly7wood

 

[merlinman]

Well, Caller ID can be a pain. I have One T&R Line on my Magix that works GREAT, however, the other LINE which is really my Cell Phone Number that is converted into a T&R Line by a BLUETOOTH adapter, doesn't deliver Caller ID to my Magix. An issue similar to yours.

You can play around with the TOUCH TONE - LOOP START ID DELAY feature and see if that helps, but it gave me no joy no matter how I set it.

Good luck.

http://merlinmanswebpage.yolasite.com

 

[holly7wood]

Thanks merlinmam. Based on the lack of response, I thought I was in uncharted territory - the gap between the old and the new. I thought about the ID delay, but it was working fine before, and when I tested the line with a Caller ID phone, it seemed like the timing just just right.

Time to move on to other issues I guess.

Thanks again

 

[TouchToneTommy]

ID delay will just prevent the call from being presented to the telephone until either valid CID info is received, or the 2nd ring, whichever comes first.

The FSK data being received from the U-verse line is probably slightly out of spec, and the Magix doesn't recognize it for what it is. Partner systems also are touchy about CID from non-traditional lines.

 

[Dexman]

Consumer grade telephones are more tolerant of FSK deviation than Partner and Merlin systems which adhere to Bellcore standards.

I have Verizon FiOS at home. Caller ID works well with my Partner ACS R7.

Reach out to at&t and see if there is anything they can do to tighten the FSK signal so it can be read by the Magix.

I "FEATURE 00"

http://dexman.webs.com/

 

[CallGP]

Frontier Fios works well with Merlin Magix's.