On my installation I have problems with SIP echo, but not all the times.
When I phone to a specific destination from an ISDN line I have no echo, but when they transfer me to another ext on their PBX echo comes. When they switch me back to previous ext, there is no echo again. Their PBX is a Panasonic.
Is this a SIP problem on my PBX?
Can anyone has a HowTo about tuning SIP?
my SIP Phones=Planet VIP-152
SIP codec=uLaw
my PBX = * 1.2.13
I’ve read these days about echo cancellation and learned that this is a GREAT problem, remaining unsolved(?).
I was trying to eliminate it (checked network, changed codecs), but nothing happened.
Is the only way buying another ISDN BRI card than AVMC4?
Should I buy hardware only from Digium?
Please help.
Filippos
If you dont have a problem unless you call this user, Then the problem is on THEIR pbx not yours. and as you say its only when they transfer you to a particular extension, Then the Problem is with likely to be with that extension.
Ok let’s go to the source. In pure VoIP or ISDN environment ecko is possible only as a result of the poor design of UA (endpoint, terminal, soft/hardphone) with a feedback from a speaker to a mic. In this case YOU are causing the problem. Other story when your voice is getting converted to 2-wire line inside PSTN. It uses special transformers which separate analog signals going in oposite directions. This is the major source of the problem. Besides that if you have a problem with one specific extension of one specific PBX should it indicate the problem with that extension. Could you give me a link to the article which claims that ecko doesn’t exist in analog PBXs? I’d be interesting in contacting the author and discuss some aspects of the theory of telecommunications.
I totaly understand that it’s much easyer to make you feel guilty becuse you use “noname” brand PBX (Asterisk in eyes of management) and they installed and use for years some kind of Avaya and just don’t wont to think that it could have a problem too.
Back in days I was working on experimental implementation of drivers for one of ISDN cards and had exactly the same problem, it was extremely sensentive to ecko from the PSTN and was working just fine in pure ISND environment. The only fix was to implement EC and autogain algorithms in the driver.
As far as I know, the other end of line is ISDN and this end too, so the problem exists between them?
The same problem occurs and in another installation, where our end is ISDN and the other is ISDN with wireless analog phone or an overseas connection.
Filippos
I thought that the problem was caused by the AVM-C4, but yesterday I’ve replaced it with a Digium B410P which has the same problem even if it has Echo Correction.