Le 02/06/2012 19:18, Administrator TOOTAI a écrit :
Le 30/05/2012 15:02, Andres a écrit :
Considering that you made progress on your initial problem by setting
nat=force_rport (resulting in connected calls with no audio) and now
you're mentioning the use of externaddr, I'd recommend a very
Le 30/05/2012 15:02, Andres a écrit :
Considering that you made progress on your initial problem by setting
nat=force_rport (resulting in connected calls with no audio) and now
you're mentioning the use of externaddr, I'd recommend a very
careful reading of the NAT SUPPORT section of
Administrator TOOTAI wrote:
10.0.70.12 is the IP of Asterisk server (kvm virtual machine) which is
replaced by externaddr parameter from sip.conf.
If you have other ideas, welcome ;-)
Considering that you made progress on your initial problem by setting
nat=force_rport (resulting in
Considering that you made progress on your initial problem by setting
nat=force_rport (resulting in connected calls with no audio) and now
you're mentioning the use of externaddr, I'd recommend a very
careful reading of the NAT SUPPORT section of sip.conf.sample in the
configs directory of the
Le 30/05/2012 14:44, Matthew J. Roth a écrit :
Considering that you made progress on your initial problem by setting
nat=force_rport (resulting in connected calls with no audio) and now
you're mentioning the use of externaddr, I'd recommend a very
careful reading of the NAT SUPPORT section of
Hi Matthew
Le 28/05/2012 19:28, Matthew J. Roth a écrit :
Administrator TOOTAI wrote:
we are upgrading our Asterisk production server from 1.6.24 to 1.8.12
version and face the following problem: one of our peer
(voicetrading.com) doesn't accept our calls anymore, we receive a
timeout error
Administrator TOOTAI wrote:
We tested this setting this WE, effectively this problem disappear but
another appears: call get connected but no audio. We installed Asterisk
10.3.1 - connection and no audio too, so same behaviour.
We did read those files, don't see which parameter we could
Le 29/05/2012 14:50, Matthew J. Roth a écrit :
Is that really the response that you received? 77.77.777.77 is not a
valid IP address (the 3rd octet is greater than 255), so if that's
what you're getting than your configuration is fine and the remote
end (or some proxy) is now the problem.
Administrator TOOTAI wrote:
we are upgrading our Asterisk production server from 1.6.24 to 1.8.12
version and face the following problem: one of our peer
(voicetrading.com) doesn't accept our calls anymore, we receive a
timeout error Packet timed out after 32000ms with no response.
Hi list,
we are upgrading our Asterisk production server from 1.6.24 to 1.8.12
version and face the following problem: one of our peer
(voicetrading.com) doesn't accept our calls anymore, we receive a
timeout error Packet timed out after 32000ms with no response.
Switching back to 1.6 make
10 matches
Mail list logo
