Re: [SR-Users] prevent relaying to myself
Am 26.02.2014 22:48, schrieb Henry Fernandes: Is there a way to prevent relaying requests to myself in route[RELAY]? To relyable prevent this (eg. the destination IP address (your server IP address) may be hidden behind others domain) you have to check the destination in the branch route. regards Klaus ___ 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
Re: [SR-Users] Replacing an ACME Packet Net-Net SBC
For sure I would use Kamailio as an SBC, but nevertheless I see these sortcoming in Kamailio (I don't know hov other SBCs handle this) - config changes require a restart: most of the time this goes fast, but sometimes processes may fail to start (ports not freed by the OS, ...). Further, statefull cal handling/filtering will be interrupted by the restart. - multiple 'virtual' SBCs. I may want to have multiple SBC instances on my SBC. If I want to separate them (optionally different config, or crashes should not crash other instances), then I need to start multiple Kamailio servers. Combined with plenty of workers per Kamailio and high private instance this may eat my servers memory. - registration forwarding: If you have a registrar which does not support Path, and you can not change the behavior of the registrar, then usually you have to rewrite the Contact header in REGISTER requests and responses. There is no method in Kamailio to properly do this nice and transparently in all headers. There are plenty of functions to mangle with the contacts in many ways, but the logic is hard to implement. And for paranoid security I would add a B2BUA. regards Klaus Am 27.02.2014 10:43, schrieb Carsten Bock: Hi Luis, i wouldn't be too sure of that: - HMR can be done with Text-Ops - all the SIP-Routing options can be done by routing-logic (e.g. by Route-Header, by Time of day, by method, ...) The only thing missing here, is maybe acting as a B2BUA and proper support for Session-Timers (which are end-to-end). But if you combine Kamailio with e.g. a SEMS-SBC, you won't miss a thing. One can even discuss, if a B2BUA and Session-Timers are a required feature for an SBC. If you go for the commercial Big-Brother of SEMS (Frafos ABC-SBC), you even get live-failovers without service-interruption as with an AcmePacket-SBC; together with a web-based frontend for administering your services. The difficulty is, that you have to implement the routing logic for Kamailio youself instead of having a CLI or a Windows App for administering your SBC. After working with AcmePacket, Kamailio and SEMS, i don't miss any feature of AcmePacket. Just my $0.02, Carsten 2014-02-27 10:29 GMT+01:00 Luis Silva luisfilsi...@gmail.com: Don't understand how is it possible to compare Kamailio with the Acme Packet SBC. Just to give an example, the DoS mechanism available on the AP SBC can't be compared with any other solution available on the market. You will also have HMRs, SIP Routing options out-of-the-box (like time of the day routing, sip method based, cost based, traffic classification based, lb, trunk group, enum,lrt, multistage, route header based, redirect, etc etc) and infinite number of features that you will for sure miss if you plan on making that replacement. On Thu, Feb 27, 2014 at 8:54 AM, Olle E. Johansson o...@edvina.net wrote: On 27 Feb 2014, at 07:29, Alex Balashov abalas...@evaristesys.com wrote: No howto for that, and more than there is a howto for developing a messenger and selling it to Facebook for $20bn. Damn. I can stop googling now then. /O :-) ___ 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 ___ 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 ___ 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
Re: [SR-Users] How to configure Kamailio + Asterisk (on same server) to route between several disjoint networks?
Am 27.02.2014 23:43, schrieb Alex Villacís Lasso: Is this setup recognizable as an already-solved problem (minus the localhost trick)? How is it done correctly? I think your setup is too complex. If I didn't missed your requirements I think you can do it this way: From routing point of view, you could do the setup with Asterisk, without KAmailio. IF you need Kamailio too (for whatever features) then what about this: | Server | || client1---net1---| IP1:5060 Kamailio |---\ | | \ client2---net2---| IP2:5060 Kamailio |--\ | || / / | 0.0.0.0:5070 Asterisk |--- | 0.0.0.0:1-2: Asterisk RTP | Block port 5070 from outside with iptables, so clients are forced through Kamailio. For the communication between Asterisk and Kamailio use the same socket as for the communication with the clients and Kamailio, eg: client1-IP --- IP1:5060 --- Kamailio IP1:5060 | IP1:5070 \ Asterisk / IP2:5070 --- | client2-IP --- IP2:5060 --- Kamailio IP2:5060 Asterisk usually uses the local routing table to find the IP address to put in the SDP. As the communication with client 1 is via Kamailio IP1 and with client 2 via Kamailio IP2, Asterisk should populate the SDP correctly. Further, if you configure Kamailio with mhomed=1 and forward to ASterisk always using the proper IP, e.g a request which is received on IP1:5060 is forwarded to IP1:5070, then also the Route/Record-Route and Via headers should be populated correctly. For REGISTER routing I think it is best to use Path header (new Asterisks should support this). regards Klaus PS: I have not tried it but I am quite sure it should work. ___ 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
[SR-Users] XAVP in 3.1.6
Hi
I'm trying to use XAVP but the script is showing parsing error.
Do i need to include any module? I rebuild kamailio using the flag
WITH_XAVP but didn' help.
route[0]
{
$xavp(a=bar) = 'bar';
}
S-154:~ # /usr/sbin/kamailio -c -f /etc/kamailio/kam86x2.cfg
loading modules under
/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/
0(20184) ERROR: core [pvapi.c:516]: error searching pvar xavp
0(20184) ERROR: core [pvapi.c:720]: wrong char [a/97] in [$xavp(a=bar)]
at [6 (5)]
0(20184) : core [cfg.y:3461]: parse error in config file
/etc/kamailio/kam86x2.cfg, line 555, column 5-17: unknown script pseudo
variable $xavp(a=bar)
ERROR: bad config file (1 errors)
Segmentation fault (core dumped)
S-154:~ # /usr/sbin/kamailio -V
version: kamailio 3.1.6 (i386/linux) af51bc
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, PKG_SIZE 25MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: af51bc
compiled on 14:11:43 Feb 28 2014 with gcc 4.7.1
THANKS
___
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
Re: [SR-Users] geoip crash
Daniel-Constantin Mierla writes: I just pushed a patch to master, but I didn't have the geoip libs installed, thus no test. If everything is ok, you can backport at your convenience, otherwise I will do it when I get the first chance. i tried and noticed that i don't have a working master at this time, only 4.1. -- juha ___ 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
