Hi, Henrik...
Please, never, ever, forget to copy the list in a thread initiated
there... other may be "curious" on it... ;)
About your configuration, it seems that you just need a 'simple forward'
server. It's very simple to accomplish... Make a simple forward
configuration script (you can start with the provided one and cut all
registration and whistles). Just be aware of all security issues binded
to this choice.
Ok... you still can load any of the control modules (pike, p.ex.) and
have some prevention, but even so it's not your best choice.
Edson.
Em 29/08/2011 12:13, Henrik Aagaard Sørensen escreveu:
Hi Edson.
I do know the different definitions as SIP-Proxy, SIP-Server etc. (I hope).
That's why I want Kamailio to act as a SIP-Proxy, not a SIP-Server, as
it does currently.
As I've understood Kamailio and SIP-Router is pretty much the same
thing. Going to sip-router.org <http://sip-router.org> for downloads
also refers to Kamailio.
So shouldn't it be possible to use Kamailio as SIP-Proxy? Or have I
misunderstood that.
I do not want my Kamailio to take registrations etc. It should just
forward SIP messages between client and SIP-Server, as I'm not allowed
to register towards my current SIP-Server with my current IP. But my
server, where the Kamailio is running, is allowed with it's IP.
2011/8/29 Edson - Lists <4li...@gmail.com <mailto:4li...@gmail.com>>
Hi, Henrik...
Sip-Router is "just" a SIP Proxy... but a dam good one...
You have to take a step back... You are mixing concepts when
affirming that SR is playing SIP-Server roles... Please take a
better look on the definitions (SIP-Proxy, SIP-Server, Registrar,
etc) and find wich system play each role.
In your actual scenario they are mixed concepts.
Draw your target scenario with all the alternatives. You will find
many of them. Only them you will be able to point the roles each
component can and will have to play in the chosen scenario. Each of
this "play alternatives" (roles played by each component) will give
You Pros and Cons (security, scalability, velocity, etc, etc, etc) ...
Make Your choice, try to implement it and this list will be able to
help you when problems on SR (SER or KAMAILIO flavors) configuration
come to play.
Edson.
Em 29/08/2011 11:46, Henrik Aagaard Sørensen escreveu:
This is my current setup, which works:
SIP client <-> SIP server.
As I've currently moved to another country I would like to be
able to do
the following setup:
SIP client <-> Kamailio SIP proxy <-> SIP server.
As the SIP server only accept packets from specific IP's.
Is it possible?
I've managed to setup a simple Kamailio installation on my
server, which
does have a valid IP for the SIP server.
With the Kamailio installation I've also enabled NAT with RTPProxy.
My problem is now, that the Kamailio installation doesn't work as a
simple proxy, but actually takes registrations etc. and acts as a
"full-blown" SIP server.
It should only take SIP messages and transfer them between
clients and
server.
Any ideas?
_________________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users
<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
