Am 16. September 2015 18:48:16 MESZ, schrieb Daniel Heckl
:
>Sebastian,
>
>If I have understood you correctly, the SIP communication is now via
>NAT instead forwarded ports. For safety, it is much better.
>
>I think it is not because of a UDP timeout, but rather because of
Sebastian,
If I have understood you correctly, the SIP communication is now via NAT
instead forwarded ports. For safety, it is much better.
I think it is not because of a UDP timeout, but rather because of a NAT
timeout. For this is "qualify" exactly the right thing to let the NAT port
On 14.09.2015, at 21:58, Sebastian Kemper wrote:
> So I got rid of the firewall rule that opened the RTP ports. And then it
> dawned on me that I don't even need to open the 5060 port. The REGISTER
> requests established a UDP connection that the kernel's conntrack module
On Tue, Apr 14, 2015 at 08:26:07AM +0200, Sebastian Kemper wrote:
> On Thu, Apr 02, 2015 at 11:33:38PM +0200, Daniel Heckl wrote:
> > I do not want set allowguest=yes. The problem is, there is no official
> > list with ip addresses of Telekom Germany. But I think all ip
> > addresses comes from
On Thu, Apr 02, 2015 at 11:33:38PM +0200, Daniel Heckl wrote:
I do not want set allowguest=yes. The problem is, there is no official
list with ip addresses of Telekom Germany. But I think all ip
addresses comes from the ip range 217.0.0.0/13.
Hello Daniel,
Judging by the lists I found I think
On Tue, Apr 14, 2015 at 09:38:22AM +0200, Daniel Heckl wrote:
Sebastian,
Your code sounds good, I'm curious how it goes on.
First the linux machine had the Google Public DNS 8.8.8.8 as DNS
server. After I changed it to the via PPPoE assigned DNS servers, i
had no changes any more. But we
On 4/2/15 3:28 PM, Daniel Heckl wrote:
Scott, I have changed the configuration as said it and will test it.
I’m curious.
Can you briefly explain what insecure=invite,port does?
;insecure=port ; Allow matching of peer by IP address without
; matching port number
;insecure=invite ; Do not
Okay, Scott, I think we are on the wrong path. Maybe I'm wrong though.
I will summarize again briefly the problems together:
The peer ip address could be another than the ip address of incoming invites
After an re-register the REGISTER is send to the new SIP server, answered with
OK. But the
That sounds like asterisk was working 100% correctly. If you receive an
INVITE from an unknown IP address, then it should fail. Unless you want to
allow anonymous, which is genearlly a very bad idea.
If you are registering to IP X, but the provider may be transmitting
invites from any number of
Actually, the IP address is still used to identify the incoming invite.
With the insecure=port option set, Asterisk will presume the invite to
still match the trunk account even if the NAT router has mangled (changed)
the port number. My suspicion is that when the new register goes out, it's
I do not want set allowguest=yes. The problem is, there is no official list
with ip addresses of Telekom Germany. But I think all ip addresses comes from
the ip range 217.0.0.0/13.
I have now the following addition to sip.conf. I think it is the only safe
option. Or what would you say?
Ok, I have tested dnsmgr. This is not a solution, the situation has not
changed. With dnsmgr I can not place outbound calls. I do not know why and what
dnsmgr really do.
My current solution is as follows:
Say allowguest=yes, configure the default context that there can not be placed
outbound
I'd be curious if setting
insecure=invite,port
makes any difference either (without alllowguest on).
On Thu, Apr 2, 2015 at 9:03 AM, Daniel Heckl daniel.he...@gmail.com wrote:
Ok, I have tested dnsmgr. This is not a solution, the situation has not
changed. With dnsmgr I can not place
Scott, I have changed the configuration as said it and will test it. I’m
curious.
Can you briefly explain what insecure=invite,port does?
;insecure=port ; Allow matching of peer by IP address without
; matching port number
;insecure=invite; Do not
Scott, thank you four your reply.
I had already though about both options, but the problem is, that after an ip
change AND a new registration the ip address of the peer is not updated
automatically. INVITES are answered with 401.
Only after a sip reload the peer works again.
That can't be
Subject: Re: [asterisk-users] Update peer IP address
Scott, thank you four your reply.
I had already though about both options, but the problem is, that after an ip
change AND a new registration the ip address of the peer is not updated
automatically. INVITES are answered with 401.
Only
John,
thank you four your answer. I think you have misunderstood the problem. It’s
about a ip address change of the sip trunk, not of my asterisk server.
Kind regards,
Daniel
Am 01.04.2015 um 16:40 schrieb Tech Support aster...@voipbusiness.us
mailto:aster...@voipbusiness.us:
If I
On 4/1/15 10:48 AM, Daniel Heckl wrote:
John,
thank you four your answer. I think you have misunderstood the
problem. It’s about a ip address change of the sip trunk, not of my
asterisk server.
You would probably benefit by enabling the DNS Manager to allow for
dynamic IP changes:
# cat
On Tue, Mar 31, 2015 at 12:36:34PM +0200, Daniel Heckl wrote:
Hello Sebastian,
I had already seen this list of the hosts, but it is not active. All
servers with which my Asterisk has been communicated are not listed.
A port scan, to eventually update the list, found hundreds of servers
On Wed, Apr 01, 2015 at 11:00:56AM -0400, Andres wrote:
On 4/1/15 10:48 AM, Daniel Heckl wrote:
John,
thank you four your answer. I think you have misunderstood the
problem. It’s about a ip address change of the sip trunk, not of my
asterisk server.
You would probably benefit by
Hello Sebastian,
I had already seen this list of the hosts, but it is not active. All servers
with which my Asterisk has been communicated are not listed.
A port scan, to eventually update the list, found hundreds of servers provided
in the address range 217.0.0.0/13 with open port 5060, some
Maybe someone could elaborate on my first question again.
If the ip address changes while a REGISTER period, the ip address of the peer
isn't been updated. How can asterisk update the ip address of the peer?
Am 31.03.2015 um 12:36 schrieb Daniel Heckl daniel.he...@gmail.com:
Hello
You have two options for dealing with an IP change during the registration
period:
1) set the registration time to shorter period of time to minimize the
downtime
2) detect that the IP address has changed via whatever method available,
and then issue a sip reload CLI command to asterisk, which
Hello
I use Asterisk 11 with FreePBX 12. Our SIP Provider is Telekom Germany. We have
sometimes problems with incoming and outgoing calls. I hope I can explain it
understandable.
For example, Asterisk sends a REGISTER to 217.0.23.68 (tel.t-online.de
http://tel.t-online.de/), the message is
On Mon, Mar 30, 2015 at 06:31:46PM +0200, Daniel Heckl wrote:
Hello
I use Asterisk 11 with FreePBX 12. Our SIP Provider is Telekom
Germany. We have sometimes problems with incoming and outgoing calls.
I hope I can explain it understandable.
Hello Daniel,
I'll find myself in the same
25 matches
Mail list logo