Re: [SR-Users] sip_capture schema?
10/4/2012 8:49 AM, Juha Heinanen wrote: Juha Heinanen writes: also, looks like sipcapture module README is missing many of module's params. is this module still supported or has it become obsolete? perhaps obsolete, because my sip proxy crashed at start when in added loading of sipcapture module. no, it's not obsolete. I will add HEPv3 support soon and update the README file too. please show your kamailio.conf Wbr, Alexandr -- juha Program terminated with signal 11, Segmentation fault. #0 0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) where #0 0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbebebca46e in mt_init () at sipcapture.c:343 #2 0x7fbebebcb389 in mod_init () at sipcapture.c:470 #3 0x004f2339 in init_mod (m=0x7fbec2b9d4a0) at sr_module.c:936 #4 0x004f220d in init_mod (m=0x7fbec2b9d7c8) at sr_module.c:933 #5 0x004f220d in init_mod (m=0x7fbec2b9dcb8) at sr_module.c:933 #6 0x004f220d in init_mod (m=0x7fbec2b9e130) at sr_module.c:933 #7 0x004f220d in init_mod (m=0x7fbec2ba0900) at sr_module.c:933 #8 0x004f220d in init_mod (m=0x7fbec2ba0c60) at sr_module.c:933 #9 0x004f220d in init_mod (m=0x7fbec2ba0fc0) at sr_module.c:933 #10 0x004f220d in init_mod (m=0x7fbec2ba13d8) at sr_module.c:933 #11 0x004f220d in init_mod (m=0x7fbec2ba17e8) at sr_module.c:933 #12 0x004f220d in init_mod (m=0x7fbec2ba1b10) at sr_module.c:933 #13 0x004f220d in init_mod (m=0x7fbec2ba2450) at sr_module.c:933 #14 0x004f220d in init_mod (m=0x7fbec2ba2c70) at sr_module.c:933 #15 0x004f220d in init_mod (m=0x7fbec2ba3550) at sr_module.c:933 #16 0x004f220d in init_mod (m=0x7fbec2ba8ea8) at sr_module.c:933 #17 0x004f220d in init_mod (m=0x7fbec2ba9480) at sr_module.c:933 #18 0x004f220d in init_mod (m=0x7fbec2ba98c0) at sr_module.c:933 #19 0x004f220d in init_mod (m=0x7fbec2ba9c58) at sr_module.c:933 #20 0x004f220d in init_mod (m=0x7fbec2ba9f88) at sr_module.c:933 #21 0x004f220d in init_mod (m=0x7fbec2baa608) at sr_module.c:933 #22 0x004f220d in init_mod (m=0x7fbec2baa9a0) at sr_module.c:933 #23 0x004f220d in init_mod (m=0x7fbec2baade8) at sr_module.c:933 #24 0x004f220d in init_mod (m=0x7fbec2bab658) at sr_module.c:933 #25 0x004f220d in init_mod (m=0x7fbec2babc28) at sr_module.c:933 #26 0x004f220d in init_mod (m=0x7fbec2bac000) at sr_module.c:933 #27 0x004f220d in init_mod (m=0x7fbec2bac6c8) at sr_module.c:933 #28 0x004f220d in init_mod (m=0x7fbec2bacc30) at sr_module.c:933 #29 0x004f220d in init_mod (m=0x7fbec2bacf58) at sr_module.c:933 #30 0x004f220d in init_mod (m=0x7fbec2bad360) at sr_module.c:933 #31 0x004f220d in init_mod (m=0x7fbec2badb80) at sr_module.c:933 #32 0x004f220d in init_mod (m=0x7fbec2bae2e0) at sr_module.c:933 #33 0x004f220d in init_mod (m=0x7fbec2bae738) at sr_module.c:933 #34 0x004f220d in init_mod (m=0x7fbec2baf2e8) at sr_module.c:933 #35 0x004f220d in init_mod (m=0x7fbec2baf540) at sr_module.c:933 #36 0x004f249b in init_modules () at sr_module.c:963 #37 0x00468e6b in main (argc=17, argv=0x7fffceacf4c8) at main.c:2504 ___ 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] [snmpstats] openserSIPRegRejectedRegistrations not being updated
Ok, I have resorted to reading the source code. It looks like rejected_ registrations is only updated if save() fails, which does not exactly fit my needs - I need a counter to log authentication failures. Does anyone know if there is an SNMP counter that could help me to achieve this? Or should I just call save() with some invalid parameters, to trigger the update? Any advice? Thank you, Anatoly. On Wed, Oct 3, 2012 at 3:28 PM, Anatoly Ivanov wrote: > Hi, > > I am observing weird behavior of snmpstats.so - I > see openserSIPRegAcceptedRegistrations being updated, > but openserSIPRegRejectedRegistrations stays at zero. > Could somebody please explain under what conditions this counter is > being incremented? > > I am using auth_radius, so I suspect I simply do not reject failed > registartions the 'proper' way, thus causing the counter to stay at 0. > > Thank you, > Anatoly. > > ___ 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] Client info
Hello All, I am trying to use Kamailio 3.3 configured as a presence server and rls server with integrated XCAP. I am trying to test the presence and rls functionality with clients such as Jitsi (doesn't seem to support rls and doesn't let me specify presence rules per contact) and Boghe (doesn't seem to be behaving as expected!). Anyone recommend other clients that work for the functionality I described above. Thanks, Sangeeta -- Sangeeta Shah ___ 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] Kamailio LCR - From Uri
Fatima Chahrour writes: > Sorry, where can I find the 'man pcresyntax' for syntax? if you are not running linux, see this: http://regexkit.sourceforge.net/Documentation/pcre/pcresyntax.html > Can you please give me an example on what could a from-uri look like? > Am now using empty string wich is matching with any ip as mentioned > below, but I need to route calls coming from specific IP's instead! this should work for you: @1.2.3.4 where 1.2.3.4 is the ip. -- 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
Re: [SR-Users] sipcapture unsupported family
10/4/2012 5:23 PM, Juha Heinanen wrote: Alexandr Dubovikov writes: http://code.google.com/p/homer/wiki/Kamailio kamailio example includes calls of sip_capture() function, which is not documented in README. based on README i got the impression that once i give 'sip_capture on' mi command, all packets are captured automatically. ok, but the issue in your last mail has nothing to do how you are calling the sip_capture function: directly in kamailio config or through mi command. just change the capture port to 9060 and send HEP traffic there. Wbr, Alexandr -- 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 ___ 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] Kamailio LCR - From Uri
Hi juha, Sorry, where can I find the 'man pcresyntax' for syntax? Can you please give me an example on what could a from-uri look like? Am now using empty string wich is matching with any ip as mentioned below, but I need to route calls coming from specific IP's instead! Thanks in advance and Kind Regards, F Chahrour On Oct 2, 2012, at 4:10 PM, Juha Heinanen wrote: > Fatima Chahrour~Vanrise Support writes: > >> I suppose that the From_uri column in LCR module meets my requirement, yet >> am not able to make it work and confused after reading several docs. > >> My question is in what form should the from_uri column be? Is the ip >> enough? > > i my opinion syntax of from uri is pretty well described in README: > > From-URI pattern and Request-URI pattern are regular expressions (see > 'man pcresyntax' for syntax), an empty string, or NULL. An empty or NULL > From-URI pattern, Request-URI pattern or prefix matches anything. > > -- 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 ___ 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] Presence with RLS and integrated XCAP on Kamailio 3.3
Hello All, Does anyone have presence working on Kamailio 3.3 with integrated XCAP. In theory my setup should work. I have two clients: Client A: Registers with the presence server Subscribe 1 - event = reg Subscribe 2 - event = presence.winfo Subscribe 3 - event = presence Publishes its status I see entries in the foll databases for A: Active Watchers DB: presence, presence.winfo, and reg event entries Watchers DB: No entries Presentity: presence, reg, and presence entries PUA list: 1 entry RLS watchers: No entries RLS presentity list: No entries XCAP List: 3 entries - rls services, resource list, and pres rules Client B: Registers with the presence server Subscribe 1 - event = presence.winfo Subscribe 2 - event = presence Subscribe 3 - event = message-summary Publishes its status I see entries in the foll databases for B: Active Watchers DB: message-summary, presence.winfo Watchers DB: 1 entry - with B as the presentity and A as the watcher Presentity: reg, presence PUA list: 1 entry RLS watchers: No entries RLS presentity list: No entries XCAP List: 2 entries resource-lists, pres rules My first question is - Is this all correct or is something going missing? Now the real problem: When Client A adds Client B to it's contact list, on Client A I see the following message: Client B Package (presence), Pending (Subscribe). This information from what I gather is coming back from the periodic notifies for the server because of the presence.winfo event. However, the notify going out to Client B does not have any indication that Client A is a watcher and needs to be authorized. This should be the case per RFC 3857. Excerpts from notifies to client A and client B: Client A NOTIFY sip:8475551001@10.51.2.181:58150;transport=udp SIP/2.0 Via: SIP/2.0/UDP 10.50.251.12;branch=z9hG4bKdcef.e5df11e.0 To: sip:8475551001@10.50.251.12;tag=1988526 From: sip:8475551001@10.50.251.12;tag=a6a1c5f60faecf035a1ae5b6e96e979a-c52c CSeq: 3 NOTIFY Call-ID: 19607474-addd-0ffb-a9da-031235052e9d Content-Length: 347 User-Agent: kamailio (3.3.1 (x86_64/linux)) Max-Forwards: 70 Event: presence.winfo Contact: Subscription-State: active;expires=3180 Content-Type: application/watcherinfo+xml sip:8475551002@10.50.251.12 Client B: NOTIFY sip:8475551002@10.50.0.113:5060;transport=udp;registering_acc=10_50_251_12 SIP/2.0 Via: SIP/2.0/UDP 10.50.251.12;branch=z9hG4bK7f71.6fca9e81.0 To: sip:8475551002@10.50.251.12;tag=a30db42f From: sip:8475551002@10.50.251.12;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6692 CSeq: 3 NOTIFY Call-ID: f71666432f236f38c7c4dc467b4483e0@0.0.0.0 Content-Length: 195 User-Agent: kamailio (3.3.1 (x86_64/linux)) Max-Forwards: 70 Event: presence.winfo Contact: Subscription-State: active;expires=3600 Content-Type: application/watcherinfo+xml Also the frequency of notifies to client B is a lot less for event: presence.winfo. Any help is greatly appreciated since I've been trying to get presence to work for a few weeks now and keep running into new problems. Thanks, Sangeeta -- Sangeeta Shah ___ 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] sipcapture unsupported family
Alexandr Dubovikov writes: > http://code.google.com/p/homer/wiki/Kamailio kamailio example includes calls of sip_capture() function, which is not documented in README. based on README i got the impression that once i give 'sip_capture on' mi command, all packets are captured automatically. -- 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
Re: [SR-Users] sipcapture unsupported family
What kind of traffic are you sending to sipcapture?
It should be HEP encoded.
Dragos
On 10/04/2012 06:11 PM, Juha Heinanen wrote:
after adding a few module params
modparam("sipcapture", "db_url", "MYSQL_SIP_PROXY_USAGE_URL")
modparam("sipcapture", "table_name", "sip_capture")
modparam("sipcapture", "hep_capture_on", 1)
modparam("sipcapture", "capture_node", "EXTERNAL_HOSTNAME")
i restarted my sip proxy and started to get these kind of errors to
syslog:
Oct 4 18:09:02 siika /usr/sbin/sip-proxy[22914]: ERROR: sipcapture
[sipcapture.c:733]: ERROR: sipcapture:hep_msg_received: unsupported family [71]
why they appear and how to turn them off?
-- 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
___
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] sipcapture unsupported family
10/4/2012 5:11 PM, Juha Heinanen wrote:
after adding a few module params
modparam("sipcapture", "db_url", "MYSQL_SIP_PROXY_USAGE_URL")
modparam("sipcapture", "table_name", "sip_capture")
modparam("sipcapture", "hep_capture_on", 1)
modparam("sipcapture", "capture_node", "EXTERNAL_HOSTNAME")
i restarted my sip proxy and started to get these kind of errors to
syslog:
Oct 4 18:09:02 siika /usr/sbin/sip-proxy[22914]: ERROR: sipcapture
[sipcapture.c:733]: ERROR: sipcapture:hep_msg_received: unsupported family [71]
why they appear and how to turn them off?
probably you are recieving normal SIP messages, not HEP. Can you change
capture port to 9060 and duplicate all SIP messages to this port.
or follow these instructions:
http://code.google.com/p/homer/wiki/Kamailio
http://code.google.com/p/homer/wiki/HOWTO
Wbr,
Alexandr
-- 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
___
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] sipcapture unsupported family
after adding a few module params
modparam("sipcapture", "db_url", "MYSQL_SIP_PROXY_USAGE_URL")
modparam("sipcapture", "table_name", "sip_capture")
modparam("sipcapture", "hep_capture_on", 1)
modparam("sipcapture", "capture_node", "EXTERNAL_HOSTNAME")
i restarted my sip proxy and started to get these kind of errors to
syslog:
Oct 4 18:09:02 siika /usr/sbin/sip-proxy[22914]: ERROR: sipcapture
[sipcapture.c:733]: ERROR: sipcapture:hep_msg_received: unsupported family [71]
why they appear and how to turn them off?
-- 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
Re: [SR-Users] sip_capture schema?
Indeed, I have replicated the crash.
I'll commit a fix, but in the meantime, you should set the "table_name"
parameter : this is the name of the table (or tables) that are used to
insert the captured data.
You can write:
modparam("sipcapture", "table_name", "sip_capture");
Dragos
On 10/04/2012 05:05 PM, Juha Heinanen wrote:
Alexandr Dubovikov writes:
no, it's not obsolete. I will add HEPv3 support soon and update the
README file too.
that is very good. please also include db schema in lib/srdb1/schema.
please show your kamailio.conf
i don't yet have any sipcapture params set in the config. i just added
line
loadmodule "sipcapture"
and restarted my proxy, which resulted in the crash.
-- 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
___
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] sip_capture schema?
10/4/2012 4:31 PM, Juha Heinanen wrote: Alexandr Dubovikov writes: without any additional modules ? anyway I will check it too. no, with lots of other modules. below is list up to sipcapture, but i don't think it matters. -- juha ok. i will check. Wbr, Alexandr loadpath "/usr/lib/sip-proxy/modules" loadmodule "app_lua" loadmodule "auth" loadmodule "avpops" loadmodule "db_mysql" loadmodule "tm" loadmodule "lcr" loadmodule "cfg_rpc" loadmodule "ctl" loadmodule "dialplan" loadmodule "enum" loadmodule "geoip" loadmodule "ipops" loadmodule "mediaproxy" loadmodule "mi_rpc" loadmodule "mtree" loadmodule "sanity" loadmodule "sdpops" loadmodule "sipcapture" ___ 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] sip_capture schema?
Alexandr Dubovikov writes: > without any additional modules ? anyway I will check it too. no, with lots of other modules. below is list up to sipcapture, but i don't think it matters. -- juha loadpath "/usr/lib/sip-proxy/modules" loadmodule "app_lua" loadmodule "auth" loadmodule "avpops" loadmodule "db_mysql" loadmodule "tm" loadmodule "lcr" loadmodule "cfg_rpc" loadmodule "ctl" loadmodule "dialplan" loadmodule "enum" loadmodule "geoip" loadmodule "ipops" loadmodule "mediaproxy" loadmodule "mi_rpc" loadmodule "mtree" loadmodule "sanity" loadmodule "sdpops" loadmodule "sipcapture" ___ 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] sip_capture schema?
10/4/2012 4:05 PM, Juha Heinanen wrote: Alexandr Dubovikov writes: no, it's not obsolete. I will add HEPv3 support soon and update the README file too. that is very good. please also include db schema in lib/srdb1/schema. please show your kamailio.conf i don't yet have any sipcapture params set in the config. i just added line loadmodule "sipcapture" and restarted my proxy, which resulted in the crash. without any additional modules ? anyway I will check it too. Wbr, Alexandr -- 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 ___ 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] kamailio and app_python
2012/10/3 Daniel-Constantin Mierla : > Hello, Hi Daniel, > the best would be to enhance the module to be able to get/set > pseudo-variables. I am not a python guy at all, so I cannot help much, > however I can assist with the C side in kamailio if someone starts > development and has questions about PVs. I had to change to lua scripting in order to use pvs. > Calling config functions with parameters from embedded interpreters exposes > the risk of memory leaks, so it is better to avoid it. Anyhow, added headers > are not visible immediately (even when done form config file), unless you > call msg_apply_changes(). Oh. Thanks. > As a workaround for now, I suggest you put your token somehow in request uri > (e.g., a parameter). As I said before, I had to use lua scripts in order to be able to use pvs. Thanks a lot for your reply. ___ 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] sip_capture schema?
Alexandr Dubovikov writes: > no, it's not obsolete. I will add HEPv3 support soon and update the > README file too. that is very good. please also include db schema in lib/srdb1/schema. > please show your kamailio.conf i don't yet have any sipcapture params set in the config. i just added line loadmodule "sipcapture" and restarted my proxy, which resulted in the crash. -- 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
Re: [SR-Users] sip_capture schema?
10/4/2012 8:49 AM, Juha Heinanen wrote: Juha Heinanen writes: also, looks like sipcapture module README is missing many of module's params. is this module still supported or has it become obsolete? perhaps obsolete, because my sip proxy crashed at start when in added loading of sipcapture module. no, it's not obsolete. I will add HEPv3 support soon and update the README file too. please show your kamailio.conf Wbr, Alexandr -- juha Program terminated with signal 11, Segmentation fault. #0 0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) where #0 0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbebebca46e in mt_init () at sipcapture.c:343 #2 0x7fbebebcb389 in mod_init () at sipcapture.c:470 #3 0x004f2339 in init_mod (m=0x7fbec2b9d4a0) at sr_module.c:936 #4 0x004f220d in init_mod (m=0x7fbec2b9d7c8) at sr_module.c:933 #5 0x004f220d in init_mod (m=0x7fbec2b9dcb8) at sr_module.c:933 #6 0x004f220d in init_mod (m=0x7fbec2b9e130) at sr_module.c:933 #7 0x004f220d in init_mod (m=0x7fbec2ba0900) at sr_module.c:933 #8 0x004f220d in init_mod (m=0x7fbec2ba0c60) at sr_module.c:933 #9 0x004f220d in init_mod (m=0x7fbec2ba0fc0) at sr_module.c:933 #10 0x004f220d in init_mod (m=0x7fbec2ba13d8) at sr_module.c:933 #11 0x004f220d in init_mod (m=0x7fbec2ba17e8) at sr_module.c:933 #12 0x004f220d in init_mod (m=0x7fbec2ba1b10) at sr_module.c:933 #13 0x004f220d in init_mod (m=0x7fbec2ba2450) at sr_module.c:933 #14 0x004f220d in init_mod (m=0x7fbec2ba2c70) at sr_module.c:933 #15 0x004f220d in init_mod (m=0x7fbec2ba3550) at sr_module.c:933 #16 0x004f220d in init_mod (m=0x7fbec2ba8ea8) at sr_module.c:933 #17 0x004f220d in init_mod (m=0x7fbec2ba9480) at sr_module.c:933 #18 0x004f220d in init_mod (m=0x7fbec2ba98c0) at sr_module.c:933 #19 0x004f220d in init_mod (m=0x7fbec2ba9c58) at sr_module.c:933 #20 0x004f220d in init_mod (m=0x7fbec2ba9f88) at sr_module.c:933 #21 0x004f220d in init_mod (m=0x7fbec2baa608) at sr_module.c:933 #22 0x004f220d in init_mod (m=0x7fbec2baa9a0) at sr_module.c:933 #23 0x004f220d in init_mod (m=0x7fbec2baade8) at sr_module.c:933 #24 0x004f220d in init_mod (m=0x7fbec2bab658) at sr_module.c:933 #25 0x004f220d in init_mod (m=0x7fbec2babc28) at sr_module.c:933 #26 0x004f220d in init_mod (m=0x7fbec2bac000) at sr_module.c:933 #27 0x004f220d in init_mod (m=0x7fbec2bac6c8) at sr_module.c:933 #28 0x004f220d in init_mod (m=0x7fbec2bacc30) at sr_module.c:933 #29 0x004f220d in init_mod (m=0x7fbec2bacf58) at sr_module.c:933 #30 0x004f220d in init_mod (m=0x7fbec2bad360) at sr_module.c:933 #31 0x004f220d in init_mod (m=0x7fbec2badb80) at sr_module.c:933 #32 0x004f220d in init_mod (m=0x7fbec2bae2e0) at sr_module.c:933 #33 0x004f220d in init_mod (m=0x7fbec2bae738) at sr_module.c:933 #34 0x004f220d in init_mod (m=0x7fbec2baf2e8) at sr_module.c:933 #35 0x004f220d in init_mod (m=0x7fbec2baf540) at sr_module.c:933 #36 0x004f249b in init_modules () at sr_module.c:963 #37 0x00468e6b in main (argc=17, argv=0x7fffceacf4c8) at main.c:2504 ___ 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
[SR-Users] TLS support in Kamailio
Hi List I have a specific requiremnt where I want Kamailio proxy need to work as a intermideiate proxy . The endpoints will talk to Kamailio using UDP as transport and Kamailio should interact with main proxy using TLS. Is this scenario possible with Kamailio ? If so, can you give me some pointer how can I acheive it. Thanks Kamal Net clooud systems Bangalore ___ 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] sip_capture schema?
Hi, This module is not obsolete. Which version are you using? I'll also take a look at the crash. Please give me the module parameters that you used for sipcapture. Here is the documentation for 3.4: http://www.kamailio.org/docs/modules/3.4.x/modules/sipcapture.html Dragos On 10/04/2012 09:49 AM, Juha Heinanen wrote: Juha Heinanen writes: also, looks like sipcapture module README is missing many of module's params. is this module still supported or has it become obsolete? perhaps obsolete, because my sip proxy crashed at start when in added loading of sipcapture module. -- juha Program terminated with signal 11, Segmentation fault. #0 0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) where #0 0x7fbec39ebcb9 in strtok () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbebebca46e in mt_init () at sipcapture.c:343 #2 0x7fbebebcb389 in mod_init () at sipcapture.c:470 #3 0x004f2339 in init_mod (m=0x7fbec2b9d4a0) at sr_module.c:936 #4 0x004f220d in init_mod (m=0x7fbec2b9d7c8) at sr_module.c:933 #5 0x004f220d in init_mod (m=0x7fbec2b9dcb8) at sr_module.c:933 #6 0x004f220d in init_mod (m=0x7fbec2b9e130) at sr_module.c:933 #7 0x004f220d in init_mod (m=0x7fbec2ba0900) at sr_module.c:933 #8 0x004f220d in init_mod (m=0x7fbec2ba0c60) at sr_module.c:933 #9 0x004f220d in init_mod (m=0x7fbec2ba0fc0) at sr_module.c:933 #10 0x004f220d in init_mod (m=0x7fbec2ba13d8) at sr_module.c:933 #11 0x004f220d in init_mod (m=0x7fbec2ba17e8) at sr_module.c:933 #12 0x004f220d in init_mod (m=0x7fbec2ba1b10) at sr_module.c:933 #13 0x004f220d in init_mod (m=0x7fbec2ba2450) at sr_module.c:933 #14 0x004f220d in init_mod (m=0x7fbec2ba2c70) at sr_module.c:933 #15 0x004f220d in init_mod (m=0x7fbec2ba3550) at sr_module.c:933 #16 0x004f220d in init_mod (m=0x7fbec2ba8ea8) at sr_module.c:933 #17 0x004f220d in init_mod (m=0x7fbec2ba9480) at sr_module.c:933 #18 0x004f220d in init_mod (m=0x7fbec2ba98c0) at sr_module.c:933 #19 0x004f220d in init_mod (m=0x7fbec2ba9c58) at sr_module.c:933 #20 0x004f220d in init_mod (m=0x7fbec2ba9f88) at sr_module.c:933 #21 0x004f220d in init_mod (m=0x7fbec2baa608) at sr_module.c:933 #22 0x004f220d in init_mod (m=0x7fbec2baa9a0) at sr_module.c:933 #23 0x004f220d in init_mod (m=0x7fbec2baade8) at sr_module.c:933 #24 0x004f220d in init_mod (m=0x7fbec2bab658) at sr_module.c:933 #25 0x004f220d in init_mod (m=0x7fbec2babc28) at sr_module.c:933 #26 0x004f220d in init_mod (m=0x7fbec2bac000) at sr_module.c:933 #27 0x004f220d in init_mod (m=0x7fbec2bac6c8) at sr_module.c:933 #28 0x004f220d in init_mod (m=0x7fbec2bacc30) at sr_module.c:933 #29 0x004f220d in init_mod (m=0x7fbec2bacf58) at sr_module.c:933 #30 0x004f220d in init_mod (m=0x7fbec2bad360) at sr_module.c:933 #31 0x004f220d in init_mod (m=0x7fbec2badb80) at sr_module.c:933 #32 0x004f220d in init_mod (m=0x7fbec2bae2e0) at sr_module.c:933 #33 0x004f220d in init_mod (m=0x7fbec2bae738) at sr_module.c:933 #34 0x004f220d in init_mod (m=0x7fbec2baf2e8) at sr_module.c:933 #35 0x004f220d in init_mod (m=0x7fbec2baf540) at sr_module.c:933 #36 0x004f249b in init_modules () at sr_module.c:963 #37 0x00468e6b in main (argc=17, argv=0x7fffceacf4c8) at main.c:2504 ___ 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
