Hello,
Well, this is still problem for me.
Best,
Teijo
17.7.2014 11:22, g.aloi...@gmail.com kirjoitti:
Hello,
I have:
allowguest=no
contactpermit=kamailio.ip.addr.ess
I also have tried the approach that I have peer kamailio, but then all
calls seems to go to to the context defined for
Hello,
Can you elaborate on your issue. who is handling registration and how is the
call flow?
Regards
Cibin
On 19-Jul-2014, at 4:34 pm, Teijo g.aloi...@gmail.com wrote:
Hello,
Well, this is still problem for me.
Best,
Teijo
17.7.2014 11:22, g.aloi...@gmail.com kirjoitti:
Hello,
The problem are unauthenticated calls - calls from somebody from
outside to my server. Kamailio accepts these calls, because destination
is my server. This happen if somebody calls to
some_extens...@my.public.ip.address. My public IP refers to the address
both Kamailio and Asterisk
Hello,
Let me understand this. You have an extension 4000 which is online. If some one
which is not even a registered user calls the extension 4000 using
4...@your.public.ip.address, the call will get connected. Correct if I am
wrong.
As far as I understand , you have configured this box as a
Yes, you are correct. But let's say that user A is online. Now somebody
from somewhere calls sip:5...@my.public.ip.address. What happens is as
follows: Suppose that 5000 is extension which should only has limited
access, for example users A and B have this extension in their contexts.
Now
Hello,
Is this part of your setup to allow anyone to call any extension, but handle
this unauthenticated calls in a different context? If so, will the following
entry works for you?
Create a peer of kamailio in sip.conf
[kamailio]
Type=peer
Host=kamailio ip
Port= kamailio port
.
.
.
context=
Hello,
I'd like to allow calls to my users from anyone, but I'd like to have
control over those calls so that I could suppose that they go tocontext
I want - let's say that that context would be unauth. But as said, this
is not the case currently.
Sorry, but I cannot figure out what
Hello,
There is a message Possible Security issue with Kamailio - Asterisk
Realtime integration in Asterisk users mailing list:
http://lists.digium.com/pipermail/asterisk-users/2013-February/277633.html
I think the problem I have is somewhat similar.
Should I suppose that there is a
Hello,
Try allow allowguest=no in sip.conf [general] context and create a peer for
kamailio in sip.comf
Regards
Cibin
On 17-Jul-2014, at 12:52 pm, g.aloi...@gmail.com wrote:
Hello,
There is a message Possible Security issue with Kamailio - Asterisk Realtime
integration in Asterisk
Hello,
Try allow allowguest=no in sip.conf [general] context and create a peer for
kamailio in sip.comf
Regards
Cibin
On 17-Jul-2014, at 12:52 pm, g.aloi...@gmail.com wrote:
Hello,
There is a message Possible Security issue with Kamailio - Asterisk Realtime
integration in Asterisk
Hello,
I have:
allowguest=no
contactpermit=kamailio.ip.addr.ess
I also have tried the approach that I have peer kamailio, but then all
calls seems to go to to the context defined for kamailio peer. I do not
know how I could in that case handle individual calls - for example
determine if
Hello,
Has anybody any solution or suggestion?
If I for example launch MicroSIP (no doubt it could be some other SIP
client), and simply call:
sip:some_extens...@my.public.ip.address
call is established, if there is online user/users. Naturally this
incoming call should be handled by
Hello,
If one places call, and tell that my from domain is your Kamailio's
IP, call is established, because Asterisk accepts requests from
Kamailio. One problem is that it's unpredictable in this case what is
the context where thiskind of call is handled by Asterisk.
This situation requires
Well, this
*if (from_uri!=myself uri!=myself)*
Means neither source nor destination is our user. Which implies that if our
domain is A, then call from domain B to C is not possible. However, calls
from B or C to A and A to B or C are possible. That is way an
unauthorized user gets passed and
Hello,
I'm using Kamailio version 4.1.4+precise (amd64).
I have followed Kamailio 4.0.x and Asterisk 11.3.0 Realtime Integration
using Asterisk Database
(http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb).
One main difference in my setup compared to that one is that
15 matches
Mail list logo
