Quote:
Originally Posted by ctylor
I think Voxalot made a change that must have caused a bug. Even I have had random problems (not as severe as yours), between two Linksys Sipuras calling each other's Voxalot accounts.
My problem is that the call would work fine for 10 or 20 minutes and then the incoming audio would cut out for me, but my outgoing would be fine and the other side could hear me. If I just wait like 20 to 40 seconds, the incoming audio would be restored. And it would intermittently do this throughout the call. These are two Sipuras whose settings haven't changed in two years! So I speculate it must be a new Voxalot bug.
I am not sure I fixed it, but what I did on mine is change my settings from this:
NAT Support Parameters heading:
Handle VIA received: No
Handle VIA rport: No
Insert VIA received: No
Insert VIA rport: No
Substitute VIA Addr: Yes
Send Resp To Src Port: Yes
STUN Enable: Yes
STUN Test Enable: No
STUN Server: stun.xten.com
EXT IP: (blank)
EXT RTP Port Min: (blank)
NAT Keep Alive Intvl: 28
To this:
NAT Support Parameters heading:
Handle VIA received: Yes
Handle VIA rport: Yes
Insert VIA received: Yes
Insert VIA rport: Yes
Substitute VIA Addr: No
Send Resp To Src Port: No
STUN Enable: Yes
STUN Test Enable: No
STUN Server: stun.xten.com
EXT IP: (blank)
EXT RTP Port Min: (blank)
NAT Keep Alive Intvl: 20
So far the problem hasn't returned, but this could just be voodoo manipulation and not actually be fixing anything. It is some kind of NAT/router bug we're seeing, so it makes sense to attack the NAT/STUN settings in our ATA to try to fix it.
|
I also had also similar problem, but I was able to improve this incoming audio, now I face this silence still some time.
Try
NAT Keep Alive Intvl: 15