Hello,
I have setup Kamailio(v1.5) and Rtpproxy(v1.2.1) on a Centos5.4 linux box. Kamailio's config file has been edited to include Nat and mysql support. With Kamailio running, i started rtpproxy using
rtpproxy -l ip_addrs -s udp:127.0.0.1:7722 -a -r /var/log -F
However rtpproxy does not seem to be recording any session. I read that the -a switch can be used to record all sessions.
Am i missing a switch/doing something wrong while invoking rtpproxy ?
Regards, Vikram.
Hello,
On 1/12/10 1:11 AM, Vikram Ragukumar wrote:
Hello,
I have setup Kamailio(v1.5) and Rtpproxy(v1.2.1) on a Centos5.4 linux box. Kamailio's config file has been edited to include Nat and mysql support. With Kamailio running, i started rtpproxy using
rtpproxy -l ip_addrs -s udp:127.0.0.1:7722 -a -r /var/log -F
However rtpproxy does not seem to be recording any session. I read that the -a switch can be used to record all sessions.
Am i missing a switch/doing something wrong while invoking rtpproxy ?
maybe you must give parameter -S /path/to/spool/dir as well. See man rtpproxy.
Cheers, Daniel
Daniel,
Thank you for your reply.
----------------------- | CentOS5.4 | ----------- -------- | ---- --- ---- | | CentOS5.4 | |Internet|--|eth0|---|br0|---|eth1|----| Asterisk | -------- | ---- --- ---- | ----------- | Kamailio + rtpproxy | -----------------------
br0 has a static Public IPv4 address a.b.c.d, and acts as a bridge between eth0 and eth1. Both eth0 and eth1 do not have IPv4 addresses.
The box running Asterisk also has a public IPv4 address a.b.c.e
The default config file for Kamailio Kamailo.cfg has been edited to include Nat and mysql support. I need Kamailio to function as a proxy by forwarding all SIP signaling information to Asterisk.
Rtpproxy is started using rtpproxy -l a.b.c.d -s udp:127.0.0.1:7722 -r /var/log -a -S /root/rtpproxy
then Kamailio is started to listen on 127.0.0.1:5060 and a.b.c.d:5060
I make a test call using x-lite softphone registered with Asterisk, however rtpproxy does not seem to record the session at all. I have checked the directory to make sure the permissions are alright.
Is there something i am missing here ?
Thanks and Regards, Vikram.
Daniel-Constantin Mierla wrote:
Hello,
On 1/12/10 1:11 AM, Vikram Ragukumar wrote:
Hello,
I have setup Kamailio(v1.5) and Rtpproxy(v1.2.1) on a Centos5.4 linux box. Kamailio's config file has been edited to include Nat and mysql support. With Kamailio running, i started rtpproxy using
rtpproxy -l ip_addrs -s udp:127.0.0.1:7722 -a -r /var/log -F
However rtpproxy does not seem to be recording any session. I read that the -a switch can be used to record all sessions.
Am i missing a switch/doing something wrong while invoking rtpproxy ?
maybe you must give parameter -S /path/to/spool/dir as well. See man rtpproxy.
Cheers, Daniel
On Tuesday 12 January 2010 17:46:15 Vikram Ragukumar wrote:
Daniel,
Thank you for your reply.
----------------------- | CentOS5.4 | ------------------- | ---- --- ---- | | CentOS5.4 |
|Internet|--|eth0|---|br0|---|eth1|----| Asterisk |
-------- | ---- --- ---- | -----------
| Kamailio + rtpproxy | -----------------------br0 has a static Public IPv4 address a.b.c.d, and acts as a bridge between eth0 and eth1. Both eth0 and eth1 do not have IPv4 addresses.
Why did you use a bridge interface (br0) between Kamailio and Asterisk ? ... did you know that you will overload your kamailio machine without need .. ?
The box running Asterisk also has a public IPv4 address a.b.c.e
The default config file for Kamailio Kamailo.cfg has been edited to include Nat and mysql support. I need Kamailio to function as a proxy by forwarding all SIP signaling information to Asterisk.
For that you don't need a bridge interface
Rtpproxy is started using rtpproxy -l a.b.c.d -s udp:127.0.0.1:7722 -r /var/log -a -S /root/rtpproxy
then Kamailio is started to listen on 127.0.0.1:5060 and a.b.c.d:5060
I make a test call using x-lite softphone registered with Asterisk, however rtpproxy does not seem to record the session at all. I have checked the directory to make sure the permissions are alright.
If your softphone is directly registered agains Asterisk, and not to your kamailio server ... Kamailio will not handle the signaling, so it will never instruct rtpproxy to do anything.
Is there something i am missing here ?
Yes, your network schema is totally wrong
Raúl-
On Tuesday 12 January 2010 17:46:15 Vikram Ragukumar wrote:
Daniel,
Thank you for your reply.
----------------------- | CentOS5.4 | ------------------- | ---- --- ---- | | CentOS5.4 |
|Internet|--|eth0|---|br0|---|eth1|----| Asterisk |
-------- | ---- --- ---- | -----------
| Kamailio + rtpproxy | -----------------------br0 has a static Public IPv4 address a.b.c.d, and acts as a bridge between eth0 and eth1. Both eth0 and eth1 do not have IPv4 addresses.
Why did you use a bridge interface (br0) between Kamailio and Asterisk ? ... did you know that you will overload your kamailio machine without need .. ?
This is a customer requirement, otherwise we wouldn't do it. The customer wants the Asterisk server and some other servers on a different LAN segment. We can remove the bridge for testing.
The box running Asterisk also has a public IPv4 address a.b.c.e
The default config file for Kamailio Kamailo.cfg has been edited to include Nat and mysql support. I need Kamailio to function as a proxy by forwarding all SIP signaling information to Asterisk.
For that you don't need a bridge interface
Rtpproxy is started using rtpproxy -l a.b.c.d -s udp:127.0.0.1:7722 -r /var/log -a -S /root/rtpproxy
then Kamailio is started to listen on 127.0.0.1:5060 and a.b.c.d:5060
I make a test call using x-lite softphone registered with Asterisk, however rtpproxy does not seem to record the session at all. I have checked the directory to make sure the permissions are alright.
If your softphone is directly registered agains Asterisk, and not to your kamailio server ... Kamailio will not handle the signaling, so it will never instruct rtpproxy to do anything.
Thanks Raúl... we'll change the registration and re-test.
-Jeff
On Wednesday 13 January 2010 06:58:43 Jeff Brower wrote:
Raúl- This is a customer requirement, otherwise we wouldn't do it. The customer wants the Asterisk server and some other servers on a different LAN segment. We can remove the bridge for testing.
Ok, but there is no need to do a bridge interface on the proxy for having the rest of the servers on other lan segment.
If your softphone is directly registered agains Asterisk, and not to your kamailio server ... Kamailio will not handle the signaling, so it will never instruct rtpproxy to do anything.
Thanks Raúl... we'll change the registration and re-test.
Take into account that if kamailio does't handle the signaling, you could not use rtpproxy as media-recorder. It seems like your customer whant something like a transparent recorder in front of Asterisk, but if it is that what they want ... you are facing the wrong way with kamailio+rtpproxy
Best Regards
Jeff Brower schrieb:
Raúl-
On Tuesday 12 January 2010 17:46:15 Vikram Ragukumar wrote:
Daniel,
Thank you for your reply.
----------------------- | CentOS5.4 | ------------------- | ---- --- ---- | | CentOS5.4 |
|Internet|--|eth0|---|br0|---|eth1|----| Asterisk |
-------- | ---- --- ---- | -----------
| Kamailio + rtpproxy | -----------------------br0 has a static Public IPv4 address a.b.c.d, and acts as a bridge between eth0 and eth1. Both eth0 and eth1 do not have IPv4 addresses.
Why did you use a bridge interface (br0) between Kamailio and Asterisk ? ... did you know that you will overload your kamailio machine without need .. ?
This is a customer requirement, otherwise we wouldn't do it. The customer wants the Asterisk server and some other servers on a different LAN segment. We can remove the bridge for testing.
With a bridge interface you do not have different LAN segments. A bridge bridges multiple LAN segments into a single one. Probably they want to have some kind of security for their Asterisk server, but using a bridge interface connects the Internet and the LAN segment transparently. Maybe you have to teach the customer.
For separating the networks, it would be better (from security point of view), to NOT use a bridge interface, but do the bridging on application layer. Therefore Kamailio supports "multi-homing" and therefore rtpproxy has a "bridge-mode".
----------------------- | | | -Kamailio- | ----------- | / | \ | -------- | ------- | ------- | | CentOS5.4 | | | | |Internet|--| eth0 | | | eth1 |---| Asterisk | | | | -------- | ------- | ------- | ----------- | \ V / | | -rtpproxy- | -----------------------
In this setup, if you disable routing on the Kamailio server, there is no direct connection possible between the Internet and the Asterisk server. Only data which passed either Kamailio or rtpproxy can get from the Internet into the LAN segment.
In this case, Kamailio+rtpproxy are working in SBC-like style.
regards Klaus
Klaus-
Jeff Brower schrieb:
Raúl-
On Tuesday 12 January 2010 17:46:15 Vikram Ragukumar wrote:
Daniel,
Thank you for your reply.
----------------------- | CentOS5.4 | ------------------- | ---- --- ---- | | CentOS5.4 |
|Internet|--|eth0|---|br0|---|eth1|----| Asterisk |
-------- | ---- --- ---- | -----------
| Kamailio + rtpproxy | -----------------------br0 has a static Public IPv4 address a.b.c.d, and acts as a bridge between eth0 and eth1. Both eth0 and eth1 do not have IPv4 addresses.
Why did you use a bridge interface (br0) between Kamailio and Asterisk ? ... did you know that you will overload your kamailio machine without need .. ?
This is a customer requirement, otherwise we wouldn't do it. The customer wants the Asterisk server and some other servers on a different LAN segment. We can remove the bridge for testing.
Thanks for your reply Klaus.
With a bridge interface you do not have different LAN segments. A bridge bridges multiple LAN segments into a single one.
Yes I was not clear... I just meant they wanted to keep the Asterisk server on a different segment for their reasons, and use a bridge to the Kamailio server.
Probably they want to have some kind of security for their Asterisk server, but using a bridge interface connects the Internet and the LAN segment transparently. Maybe you have to teach the customer.
Very possible. Once we have it working both ways (with/without bridge), I have a feeling the bridge may cause enough issues -- or not enough advantages -- and it will be easier to convince them to re-think.
For separating the networks, it would be better (from security point of view), to NOT use a bridge interface, but do the bridging on application layer. Therefore Kamailio supports "multi-homing" and therefore rtpproxy has a "bridge-mode".
----------------------- | | | -Kamailio- | ----------- | / | \ |-------- | ------- | ------- | | CentOS5.4 | | | | |Internet|--| eth0 | | | eth1 |---| Asterisk | | | | -------- | ------- | ------- | ----------- | \ V / | | -rtpproxy- | -----------------------
In this setup, if you disable routing on the Kamailio server, there is no direct connection possible between the Internet and the Asterisk server. Only data which passed either Kamailio or rtpproxy can get from the Internet into the LAN segment.
In this case, Kamailio+rtpproxy are working in SBC-like style.
In this setup, can Kamailio allow non-SIP protocols (HTTP, SSH, etc) to pass to the Asterisk server and/or other servers?
-Jeff
On Wednesday 13 January 2010, Jeff Brower wrote:
[..] In this setup, can Kamailio allow non-SIP protocols (HTTP, SSH, etc) to pass to the Asterisk server and/or other servers?
Hi Jeff,
kamailio is only a SIP proxy, but you could use other application level proxies (e.g. squid for http), and of course also just us normal IP routing on the machine.
Cheers,
Henning
Henning-
On Wednesday 13 January 2010, Jeff Brower wrote:
[..] In this setup, can Kamailio allow non-SIP protocols (HTTP, SSH, etc) to pass to the Asterisk server and/or other servers?
Hi Jeff,
kamailio is only a SIP proxy, but you could use other application level proxies (e.g. squid for http), and of course also just us normal IP routing on the machine.
Thanks. For now we kept the bridge config in place so no problem with other protocols. We changed the softphone config to use the Kamailio server as outbound proxy -- it seems to be working.
-Jeff
-
Daniel-Constantin Mierla -
Henning Westerholt -
Jeff Brower -
Klaus Darilion -
Raúl Alexis Betancor Santana -
Vikram Ragukumar