BCM50 PRI has echo 1

[DigitelD]

USLEC has no clue what is causing echo on a newly installed BCM50 that is current with updates. I have changed the line build and still there is echo. It is only when the employee speaks. The caller sounds just fine. It is on incoming, outgoing, local and long distance. There is no consistancy. It can be any phone at any time. They are wanting Nortel to get involved and make a change that only they could (if it is even possible). Has anyone experienced this before?

SHK Certified (School of Hard Knocks)

 

[CBasicAsslember]

Sounds like VoIP. See my previous post:

http://www.tek-tips.com/viewthread.cfm?qid=1310327

 

[DigitelD]

This is not VOIP it is a PRI echoing problem.

SHK Certified (School of Hard Knocks)

 

[DigitelD]

And, the phones are digital.

SHK Certified (School of Hard Knocks)

 

[phillip3606]

Have Telco change DB Level At Central office to nominal.

 

[DigitelD]

I will give them the suggestion but at this point they, with all respect, are clueless.

SHK Certified (School of Hard Knocks)

 

[cook1082]

Internal is good?

 

[DigitelD]

Yes, it is only the employee on an outside call that gets the echo.

SHK Certified (School of Hard Knocks)

 

[cook1082]

New BCM 50 1.0 or 2.0

 

[CBasicAsslember]

This is not VOIP it is a PRI echoing problem.

The 2 are not mutually exclusive.

http://www.uslec.com/dynamic-t-voip.aspx

 

[DigitelD]

cook1082, it is a BCM50 Rls.1.
CBasicAsslember, then what would the solution be? We have already changed the only setting that can be changed. What can I tell them?

SHK Certified (School of Hard Knocks)

 

[CBasicAsslember]

If they are in fact using VoIP, and there is a solution, it will be out of your hands. First thing I would do is try to get them to verify that they are using VoIP. I would also try to confirm that latency was indeed significant by doing a loop back test. A simple loopback would involve making 2 calls to the site in question from another site that is not on VoIP. Set up 2 phones side by side at the site in question. Make 2 connections to the remote site and then conference the calls at the remote site. Speak into one of the phones while listening on the other. The delay you hear, if any, will be the latency. If you can hear a delay then latency is going to be a problem.

At this point, provided you have audible latency, there are several things you might want to consider.

1) Get the provider to address the latency.
2) Inform and demonstrate the delay to the customer. There is no incentive for the provider to listen to you, they will listen to the customer.
3) If the present provider is unwilling, or unable, to address the problem consider switching providers.

I realize there can be a lot of politics involved here. The provider is going to tell the customer that it isn't their problem. You have to show the customer that it is indeed their problem. With the customer on your side you will have a lot more leverage to get the problem addressed.

 

[DigitelD]

Forgive my ignorance here. Are you telling me that the PRI can be using VOIP?

SHK Certified (School of Hard Knocks)

 

[cook1082]

That is possable. I have herd of this.

 

[biv343]

I've had a couple customers get those types of circuits - the only place that the PRI "exists" is between the router and the BCM. The connection between their router and their softswitch/CO is IP.

The technology is out there, and it's getting more prevalent.

 

[CBasicAsslember]

Are you telling me that the PRI can be using VOIP?

Yes. The provider will provide a T1 interface but converts it to IP to pass through their network. I have customers that have such an arrangement.

 

[teekow]

It may be worth investigating an external echo canceller and will cost about $9000 for the cheapest version from Tellabs. I spent 2 months and about 200 hours between techs, PMs, CO personnel, engineers, customer, etc. before I said to hell with it and bought an echo canceller. In my case, I had all VOIP handsets using an ISDN PRI and got Nortel to pay for the echo canceller. The most compelling evidence was that their old phone system sounded fine with the same PRI. I don't know if that is the case in your scenario. There can be ISDN PRIs out there that work for years on a TDM system but once VOIP handsets are introduces, you notice the latency in the form of echo.

Good Luck
Rob

 

[vztech]

you may already have these but if not you should consider.

PEPS 1.0
BCM050.139
BCM050.125
BCM050.096

It's only dialtone-VZ

 

[DigitelD]

This system is current, except for the ones that came in a few days ago. I have never seen this problem be the BCM.

SHK Certified (School of Hard Knocks)

 

[SNSSMIS]

Teekow is right, the TELCO can install Echo Cancell Device in the CO. I have had LD Providers Place Echo Cancel Devices on T1 circuits in the past.

Reference...
teekow (Vendor) 16 Jan 07 8:15
It may be worth investigating an external echo canceller and will cost about $9000 for the cheapest version from Tellabs. I spent 2 months and about 200 hours between techs, PMs, CO personnel, engineers, customer, etc. before I said to hell with it and bought an echo canceller. In my case, I had all VOIP handsets using an ISDN PRI and got Nortel to pay for the echo canceller. The most compelling evidence was that their old phone system sounded fine with the same PRI. I don't know if that is the case in your scenario. There can be ISDN PRIs out there that work for years on a TDM system but once VOIP handsets are introduces, you notice the latency in the form of echo.

Good Luck
Rob

SNSSMIS