On 6/8/15 1:18 AM, Luca Bertoncello wrote:
Hi list!
Another day, another problem...
I'm checking with Nagios my Asterisk at home, and since yesterday I noticed
that, after my IP changes (Deutsche Telekom drop the DSL-line every 24 hours,
so that I have a new IP every day), the peer of an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/14/2015 01:48 PM, Luca Bertoncello wrote:
Guenther Boelter gboel...@gmail.com schrieb:
Don't use Port 5061, your SIP-port should be always even like
5060, 5062, 5064 or 5066.
Could you please explain why? I see in /etc/services, that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guenther Boelter gboel...@gmail.com schrieb:
that's what Deutsche Telekom has told me. I'm using it since a few
month in Germany and it works well.
OK, thanks.. I'm using port 5060, so I think, it would not be a problem...
It depends from which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/08/2015 01:18 PM, Luca Bertoncello wrote:
Hi list!
Another day, another problem... I'm checking with Nagios my
Asterisk at home, and since yesterday I noticed that, after my IP
changes (Deutsche Telekom drop the DSL-line every 24 hours,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guenther Boelter gboel...@gmail.com schrieb:
Don't use Port 5061, your SIP-port should be always even like 5060,
5062, 5064 or 5066.
Could you please explain why?
I see in /etc/services, that 5060 is the port for SIP and 5061 for SIP-TLS,
but I
Hi list!
Another day, another problem...
I'm checking with Nagios my Asterisk at home, and since yesterday I noticed
that, after my IP changes (Deutsche Telekom drop the DSL-line every 24 hours,
so that I have a new IP every day), the peer of an VoIP-provider I use is
UNREACHABLE.
Yesterday I
