Odd CO Issue 1

[bostech]

Was wondering if anyone has ever heard of or experienced this:

A quick (1 second) data burst on a Verizon POTS line exactly every 30 minutes.

When I tested, I had my butt set connected directly to the CO line. No equipment between me and the demarc.

Thanks for any ideas?

 

[jrgood0852]

Almost sounds like it may be a DSL or ADSL circuit. You would have to verify with Verizon. If you have a DSL filter and put it inline and it goes away, you know this is the case.

 

[misseditbythatmuch]

I had an experience like this. In my case, it was cross talk from a leased line used by the local water company to send SCADA signals to a central pump control.

 

[jrgood0852]

I think missed hit it. If it were DSL, now that I think about it, you would have a much more frequent tic...tic...tic noise on the line. Or could be trying to sync to a time clock or such.

 

[bostech]

Thanks for the replies.

Yea, if it was a DSL handshake, it would be more frequent and the burst duration would be a bit longer.

But, I like Missed's idea. I'm supposed to do a vendor meet tomorrow. We'll see how that works out.

Thanks again.

 

[EmuDan]

Are they copper POTS lines or are they using FIOS. I think I read somewhere on here that people were having trouble with the FIOS because it is sending a MWI signal every 30 minutes or so..

Dan

Live every day as if wild dogs were chasing you!!
Wild dogs....everyday....LIVE!!!

 

[bostech]

It is copper.

But, the MWI is very interesting. The customer did say that they had carrier VM put on the line recently.

Thanks Emu!!!!

I'll let you know.

 

[bostech]

I did a search for MWI issues and found this:

[link thread940-1701754]Link[/url]

Looks like this is what I have going on.

Thanks again Emu!!! Star for ya!!

 

[bostech]

Well, it wasn't MWI or VM for that matter. Both were removed from the line and the problem persisted.

The Verizon tech also changed the pairs the line comes over. This line was being fed from a slick out on the street that was fed over a fiber trunk. The other lines at the site are fed over direct copper pairs to the CO. He moved the problem line to a direct copper pair. Still no solution.

We even tried a DSL filter. No fix.

He finally got contact with a CO tech that had heard of the issue. He said that they've been getting complaints from alarm co.'s where this data burst is triggering alarms. They think it's coming from a piece of equipment at a particular CO that feeds to the smaller local CO's in the area.

So, we'll see where this goes.

Again, thanks for everyone's responses.

 

[jrgood0852]

Alarm makes sense. A POTS line associated with an alarm does in fact get "checked" periodically from the alarm company for conectivity. I bet that is what this is.

 

[curlycord]

Jr I think your confused on "alarms", nothing to do with a local alarm company.
Alarm code from one CO to another, not from outgoing from local alarm company.

First he said there is nothing on the line between him and demarc.
Second per above it is at the CO and generates alarms, nothing to do with the local alarm company's aside from the fact they are receiving these transmissions to their onsite equipment.








=----(((((((((()----=
curlycord

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca

 

[telemarksman]

could be a pair gain problem?

just saying

alwayslearning

 

[jrgood0852]

I hear ya, curly. Duelly noted.

Always look out for the next guy because it may be you!

 

[jrgood0852]

Dually that is....(I think I'm killing this word!)

Always look out for the next guy because it may be you!

 

[curlycord]

lol I didn't even notice but then again it's actually "Duly", just one of those word spelled a gazillion ways.

=----(((((((((()----=
curlycord

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca

 

[yankblan]

It IS a MWI problem; even with no voicemail enabled. It polls every 30 minutes, and it is built that way. To the IP Office (since FP1), it "sounds" like a CLID signal, therefore it picks up and rings phones or AA; aka ghost calls.

The new Bell Fiber used to disable it on a per case basis at first, but now they don't, since every time they make a change it resets the programming. They shoveled the problem back to the manufacturers; I can't blame em even if it affects my job; Mitel MCD/5000 and BCMs don't have this problem. Didn't test on a 3CX or Cisco.

http://interconnexionsld.ca/