Okay, I will reply you quote by quote:
Do all ATA’s have seperate extensions in Asterisk sip.conf. [/quote]
Yes. All gatways have its own separate extension
They do register correctly.
[quote=“kpm850”]Then enter “sip debug” and make a call to one of your ATA’s and see
what debug info comes up. Keep making the call until you get the
one way audio or silence. [/quote]
Will try to do that and will post log later
Switch 3COM 4400
Each ATA has static private address.
[quote=“kpm850”]If there is a switch (or Hub), is it Uplinked through a router
and then to your Cable/DSL modem ?[/quote]
Asterisk has one ethernet interface with private IP address which connected to the same switch where ATAs are connected.
The reason to ask these questions is “one way audio generally is a NAT
issue”. Silence on either side, although intermitant, is packet loss.
Also, in the ATAs’ Graphic Interface, are the ATA’s set to NAT=yes ?
[quote=“kpm850”]Also, what codecs are being utilized and in what sequence are they listed ?
Are the ATA’s codecs set in proirity the way Asterisk SIP/IAX is ? [/quote]
[quote=“kpm850”]In Sip.conf, check to see if under [general] the bindaddr=0.0.0.0.
If set to 0.0.0.0 this is a “bind to all” interpretation to Asterisk.
However, Asterisk will bind to the “first available”. This may need
to be adjusted.
If bindaddr is set to your public or private address, it may need to be
set to one for all voice traffic including Asterisk and the ATA’s so all
voice traffic is directed one way allowing Asterisk to only bind
to one address.[/quote]
The Asterisk has 2 network interfaces.
eth1 = 192.168.1.227 [private ip]
eth2 = xx.xx.xx.227 [public ip]
One leg is connected to the local switch, where all the ATA’s are connected. ATA connects to Asterisk thru its local leg (eth1)
ATA ip - 192.168.1.204 Asterisk ip - 192.168.1.227
So I think NAT is not the issue as there should not be NAT translation in that case.
bindaddr is set to 0.0.0.0 as Asterisk should serve 2 legs. Public and Private simultaniously.
I thought that random call silience caused by TE110P card on Asterisk, but I found that there is the same problem when you make internal call from an extension to extension. (from one ATA to another)
I had some weeks when all been working just fine. Now - cannot guarantee any quility at all.
So ust crackig my head about that.
eth2 public xx.xx.xx.227
eth1 lan 192.168.1.227
|- ata1 DLINK DVG-2004s 192.168.1.204
|- ata2 DLINK DVG-2004s 192.168.1.205
|- ata3 Linksys SPA2102 192.168.1.206