sr-users May 2015

sr-users@lists.kamailio.org

80 participants
115 discussions

dbtext why is my user not recognised
by jaflong jaflong 18 May '15

18 May '15

cat > /usr/local/etc/kamailio/dbtext/subscriber username(str) password(str) ha1(str) domain(str) ha1b(str) user1:user1:xxx:10.1.1.1:xxx 9350) DEBUG: auth_db [authorize.c:498]: auth_check(): realm [10.31.8.1] table [subscriber] flags [1] 2(9350) DEBUG: auth [api.c:96]: pre_auth(): auth: digest-algo: MD5 parsed value: 1 2(9350) DEBUG: db_text [dbt_file.c:102]: dbt_load_file(): request for table [subscriber] 2(9350) DEBUG: db_text [dbt_file.c:109]: dbt_load_file(): db is [/usr/local/etc/kamailio/dbtext] 2(9350) DEBUG: db_text [dbt_file.c:124]: dbt_load_file(): loading file [/usr/local/etc/kamailio/dbtext/subscriber] 2(9350) DEBUG: db_text [dbt_tb.c:187]: dbt_table_new(): mtime is 1431951381 2(9350) DEBUG: db_text [dbt_file.c:480]: dbt_load_file(): error at row=0 col=0 c= 2(9350) ERROR: db_text [dbt_lib.c:307]: dbt_db_get_table(): could not load database from file [subscriber] 2(9350) ERROR: db_text [dbt_base.c:200]: dbt_query(): table subscriber does not exist! 2(9350) ERROR: auth_db [authorize.c:187]: get_ha1(): failed to query database 2(9350) exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=498 a=26 n=auth_challenge 2(9350) DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='10.31.8.1' 2(9350) DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'Proxy-Authenticate: Digest realm="10.31.8.1", nonce="VVnqGlVZ6O4l1T62BGADuI2p8uAnUYeu" regards

1 1

Setting up a presence AS with Kamailio IMS.
by Mihail Dakov 18 May '15

18 May '15

Hi all, I have successfully setup a Kamailio IMS environment using just a single machine running three kamailio instances. I am using kamailio 4.2.4 compiling it myself. I followed this guide: http://nil.uniza.sk/instant-messaging/simple/configuring-im-and-presence-ka… to setup a presence AS using the scscf instance. I used kamdbctl script to create the presence tables with one inconsistence with the guide. I had to create a db in which I created a couple of columns (table_name, table_version) to satisfy the kamdbctl script as it was failing when running "kamdbctl presence". At the moment the problem is that my kamailio instance is failing with the following error: scscf/scscf[5256]: ERROR: <core> [db.c:422]: db_table_version(): invalid type (3) or nul (0) version columns for presentity ... and then some time later: scscf/scscf[5256]: ERROR: <core> [db.c:440]: db_check_table_version(): querying version for table presentity scscf/scscf[5256]: ERROR: presence [presence.c:322]: mod_init(): error during table version check scscf/scscf[5256]: ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module presence (/home/ng40/kamailio-4.2.4/modules/presence/presence.so) scscf/scscf[5256]: DEBUG: cdp_avp [mod.c:224]: cdp_avp_destroy(): Destroying module cdp_avp I suspect that the problem relays on creating manually the db where I inserted the two columns mentioned above (table_name, table_version) so that I could execute "kamdbctl presence". Could someone assist me into solving this issue? br, md.

1 0

critical crash with dbtext
by jaflong jaflong 18 May '15

18 May '15

HI When using dbtext setup I receive a CRITICAL error and shut down. This is the debug log. My config settings are described below. Please advise how I should fo the correct dbtext config 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): acc 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): auth_db 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): debugger 9(21196) DEBUG: debugger [debugger_mod.c:179]: child_init(): rank is (-4) 9(21196) DEBUG: <core> [local_timer.c:74]: init_local_timer(): init_local_timer: timer_list between 0x9e7268 and 0xa2b268 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 8, 4, 0x7f5aaa402364), fd_no=0 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 9, 4, 0x7f5aaa4023f0), fd_no=1 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 10, 4, 0x7f5aaa40247c), fd_no=2 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 11, 4, 0x7f5aaa402508), fd_no=3 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 12, 4, 0x7f5aaa402594), fd_no=4 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 13, 4, 0x7f5aaa402620), fd_no=5 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 14, 4, 0x7f5aaa4026ac), fd_no=6 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 15, 4, 0x7f5aaa402738), fd_no=7 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 8 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 1, pid 21188 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 8, -1, 0x0) fd_no=8 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 9 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 2, pid 21189 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 9, -1, 0x0) fd_no=7 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 10 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 3, pid 21190 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 10, -1, 0x0) fd_no=6 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 11 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 4, pid 21191 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 11, -1, 0x0) fd_no=5 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 12 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 5, pid 21192 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 12, -1, 0x0) fd_no=4 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 13 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 6, pid 21193 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 13, -1, 0x0) fd_no=3 called 8(21195) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/dbtext 8(21195) DEBUG: db_text [dbt_lib.c:129]: dbt_cache_get_db(): looking for db /usr/local/etc/kamailio/dbtext! 8(21195) DEBUG: db_text [dbt_lib.c:139]: dbt_cache_get_db(): db already cached! 8(21195) DEBUG: <core> [sruid.c:101]: sruid_init(): root for sruid is [ulcx-5555c137-52cb-] (0 / 19) 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): acc 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): auth_db 8(21195) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/dbtext 8(21195) DEBUG: db_text [dbt_lib.c:129]: dbt_cache_get_db(): looking for db /usr/local/etc/kamailio/dbtext! 8(21195) DEBUG: db_text [dbt_lib.c:139]: dbt_cache_get_db(): db already cached! 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): debugger 8(21195) DEBUG: debugger [debugger_mod.c:179]: child_init(): rank is (-2) 8(21195) DEBUG: ctl [ctl.c:325]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x2682080 8(21195) DEBUG: ctl [ctl.c:332]: mod_child(): ctl: 0 io_listen_loop(1, 0x2682080) 8(21195) INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 8(21195) DEBUG: ctl [io_listener.c:257]: io_listen_loop(): io_listen_loop: adding socket 4, type 2, transport 3 (/tmp/kamailio_ctl) 8(21195) DEBUG: ctl [../../io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x7f5aaf2a36c0, 4, 2, 0x2682080), fd_no=0 --------------------------------------------- cd /usr/local/etc/kamailio mkdir dbtext cd dbtext --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/version table_name(str) table_version(int) subscriber:6 location:6 aliases:6 --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/location username(str) contact(str) expires(int) q(double) callid(str) cseq(int) --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/subscriber username(str) password(str) ha1(str) domain(str) ha1b(str) testuser:testuser:xxx:10.1.1.5:xxx --------------------------------------------- #!define DBURL "text:///usr/local/etc/kamailio/dbtext" #!endif --------------------------------------------- # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) #!endif # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) ---------------------------------------------

2 3

Repeated 200 OK from Enswitch
by Darren Campbell (Primar) 18 May '15

18 May '15

Hi all Experiencing a commonly reported issue where calls drop out after 30 seconds or so. Mainly because the provider hangs up after not recognising/receiving ACK in response to 200 OK. Unfortunately (or maybe fortunately), I haven't had much experience with Enswitch so was hoping someone in the community might help guide me as to which rules Enswitch might be using to match ACKs to calls in progress. Maybe there is another avenue I should be investigating. Here's a sample of the 200 OK and ACK that repeats. 13:44:04.155646 IP PROVIDERIP.5060 > 172.21.0.226.5060: SIP, length: 1058 E..>.M..?..Ug.v..........*J.SIP/2.0 200 OK^M Via: SIP/2.0/UDP 172.21.0.226;rport=5060;branch=z9hG4bKfe94.efbf7fbcaf8bd15243a61fdc9d6d1e78.0^M Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK65f00a0c;rport=5080^M Record-Route: <sip:PROVIDERIP;lr=on>^M Record-Route: <sip:172.21.0.226;r2=on;lr=on;ftag=as65919d92;nat=yes>^M Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=as65919d92;nat=yes>^M From: "asterisk" <sip:PROVIDERUSER@PROVIDERIP:5080>;tag=as65919d92^M To: <sip:PHONENUMBER@PROVIDERIP>;tag=as260fefaa^M Call-ID: 271ac7a174d613cd0b94504353733a2c@PROVIDERIP^M CSeq: 103 INVITE^M Server: Enswitch^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH^M Supported: replaces^M Contact: <sip:PHONENUMBER@PROVIDERMEDIAIP:5060>^M Content-Type: application/sdp^M Content-Length: 286^M ^M v=0^M o=root 2110894460 2110894461 IN IP4 PROVIDERMEDIAIP^M s=Asterisk PBX 11.3.0^M c=IN IP4 PROVIDERMEDIAIP^M t=0 0^M m=audio 15594 RTP/AVP 0 8 3 101^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8 PCMA/8000^M a=rtpmap:3 GSM/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-16^M a=ptime:20^M a=sendrecv^M 13:44:04.164519 IP 172.21.0.226.5060 > PROVIDERIP.5060: SIP, length: 525 E..)!A..@..v....g.v.......T.ACK sip:PHONENUMBER@PROVIDERIP:5060 SIP/2.0^M Via: SIP/2.0/UDP 172.21.0.226;branch=z9hG4bKfe94.472e9fc0479de79b4f176cc9585d8880.0^M Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK752b5264;rport=5080^M Route: <sip:PROVIDERIP;lr=on>^M Max-Forwards: 69^M From: "asterisk" <sip:PROVIDERUSER@PROVIDERIP:5080>;tag=as65919d92^M To: <sip:PHONENUMBER@PROVIDERIP>;tag=as260fefaa^M Contact: <sip:PROVIDERUSER@127.0.0.1:5080>^M Call-ID: 271ac7a174d613cd0b94504353733a2c@PROVIDERIP^M CSeq: 103 ACK^M User-Agent: Elastix 3.0^M Content-Length: 0^M

2 8

RADIUS Digest Problem
by Sanaii, Maziar 18 May '15

18 May '15

Hello there, I'm trying to configure Kamailio 4.2.4 to authenticate client REGISTERs against a test FreeRADIUS on the localhost, however I have yet to succeed. My installation includes Kamailio 4.2.4, radiusclient 1.1.6, FreeRADIUS 2.2.5 and all of them on a Debian 8.0 machine. I believe I have got all the configurations correct in kamailio.cfg, radiusclient.conf, radius servers file, and freeradius server since the communication between the components are ok. My problem is that when I use a SIP Client such as 3CX SoftPhone, FreeRADIUS gives me an answer included in SIPClient-LOCAL-RADIUS-NOK.txt. I have isolated the problem being in the Digest-Response part since I have ran some other tests that I have included in the zip file attached, but can't figure out why this shouldn't work. From what I have figured out, my SIP Client does not calculate the correct Digest-Response and I have seen this in all the clients I have tested so far. For example, my client sends "5f8dfe8aa4e13994b4ceade49ee0d3d4" although it's supposed to send "528f22527e9cf003df29ede9c243e615". I would really appreciate if you would point out what I did wrong in setting things up. I have done so much googling but have not found anything useful. Regards, Maziar Sanaii Ashtiani

2 1

XLOG To STDERR Not Working
by Nahum Nir 18 May '15

18 May '15

Hi All, I am using Kamailio 4.0.3 and can't logs. .cfg: #!define WITH_DEBUG ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 When the server starts there outputs about xlog: 0(20266) DEBUG: <core> [cfg.y:1791]: yyparse(): loading module xlog.so 0(20266) DEBUG: <core> [sr_module.c:499]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:522]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:564]: load_module(): load_module: trying to load </usr/lib64/kamailio/modules/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:343]: register_module(): register PV from: xlog 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20268) DEBUG: <core> [sr_module.c:935]: init_mod(): DEBUG: init_mod: xlog 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() At the beginning of the Main routing block I put: log("~~~~~~~~~~~~route~~~~~~~~~~~~~~~~~~~~\n"); xdbg("~~~~~~~~~ xdbg - route~~~~~~~~~~~~~~~~~~~~\n"); xlog("L_ALERT","~~~~~~~~~ xlog - route~~~~~~~~~~~~~~~~~~~~\n"); But nothing is logging when I send INVITEs Any help? Thanks, Nir

2 1

How to Change IP on Kamailio
by Mudasar Choudhary 18 May '15

18 May '15

Hi, Hope you are doing fine. Can you please assist me how can I change the IP for Kamailio. Right now its up on this IP: loading modules under /usr/lib/kamailio/modulesListing onudp: 98.212.180.96 [98.212.180.96] :5060tcp: 192.168.18.99 [192.168.18.99] :8888 I want to change both upd and tcp. Please advise. ThanksMudasar

2 1

Kamailio Load balancing multiple asterisk boxes
by Eric Koome 15 May '15

15 May '15

Hi I have two boxes with internal and external interfaces. Each has Kamailio at the public interface and asterisk on the internal one. Making calls within a box is fine but would like to load balance using the other asterisk box. However using dispatcher I have noticed packets are not being routed from Kamailo to the second asterisk. Packets from Kamailo are originating from the external interface and sent to the second asterisk box using private ip address. Off course this is not routable. I have tried masquerading but no joy. Do I need to change kamailio configuration? I want to have a set of asterisk boxes behind Kamailio using dispatcher. I'm I missing a trick? Eric

2 1

misc_radius and auth_radius configuration question
by Yasin CANER 15 May '15

15 May '15

Hello; i am testing to radius modules. i have found this tutorial http://www.kamailio.org/docs/openser-radius-1.0.x.html . it is old but i changed some variables. i configured radiusclient-ng and free radius. But kamailio cann't start because of 0(17813) ERROR: misc_radius [misc_radius.c:208]: mod_init(): misc_radius: can't get code for the SIP-AVP attribute 0(17813) ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module misc_radius (/usr/local/lib64/kamailio/modules/misc_radius.so) i already defined SIP-AVP in dictionary.kamailio. And when i set radius_config in misc_radius , it try to find in default path (/usr/local/etc/radiusclient-ng). So i linked to path /usr/local/etc/radiusclient-ng to solve this problem. ---- kamailio V 4.2.4 ---- ------------------dictionary.kamailio------------ #### Attributes ### ATTRIBUTE Sip-Method 101 integer # Schulzrinne, acc ATTRIBUTE Sip-Response-Code 102 integer # Schulzrinne, acc ATTRIBUTE Sip-Cseq 103 string # Schulzrinne, acc ATTRIBUTE Sip-To-Tag 104 string # Schulzrinne, acc ATTRIBUTE Sip-From-Tag 105 string # Schulzrinne, acc ATTRIBUTE Sip-Translated-Request-URI 107 string # Proprietary, acc ATTRIBUTE Sip-Src-IP 108 string # Proprietary, acc ATTRIBUTE Sip-Src-Port 109 string # Proprietary, acc ATTRIBUTE Digest-Response 206 string # Sterman, auth_radius ATTRIBUTE Sip-Uri-User 208 string # Proprietary, auth_radius ATTRIBUTE Sip-Group 211 string # Proprietary, group_radius ATTRIBUTE Sip-Rpid 213 string # Proprietary, auth_radius ATTRIBUTE SIP-AVP 225 string # Proprietary, avp_radius ATTRIBUTE Digest-Realm 1063 string # Sterman, auth_radius ATTRIBUTE Digest-Nonce 1064 string # Sterman, auth_radius ATTRIBUTE Digest-Method 1065 string # Sterman, auth_radius ATTRIBUTE Digest-URI 1066 string # Sterman, auth_radius ATTRIBUTE Digest-QOP 1067 string # Sterman, auth_radius ATTRIBUTE Digest-Algorithm 1068 string # Sterman, auth_radius ATTRIBUTE Digest-Body-Digest 1069 string # Sterman, auth_radius ATTRIBUTE Digest-CNonce 1070 string # Sterman, auth_radius ATTRIBUTE Digest-Nonce-Count 1071 string # Sterman, auth_radius ATTRIBUTE Digest-User-Name 1072 string # Sterman, auth_radius ### Acct-Status-Type Values ### #VALUE Acct-Status-Type Start 1 # RFC2866, acc #VALUE Acct-Status-Type Stop 2 # RFC2866, acc #VALUE Acct-Status-Type Failed 15 # RFC2866, acc ### Service-Type Values ### #VALUE Service-Type Call-Check 10 # RFC2865, uri_radius VALUE Service-Type Group-Check 12 # Proprietary, group_radius ##VALUE Service-Type Sip-Session 15 # Schulzrinne, acc, auth_radius VALUE Service-Type SIP-Caller-AVPs 30 # Proprietary, avp_radius VALUE Service-Type SIP-Callee-AVPs 31 # Proprietary, avp_radius ### Sip-Method Values ### VALUE Sip-Method Undefined 0 VALUE Sip-Method Invite 1 VALUE Sip-Method Cancel 2 VALUE Sip-Method Ack 4 VALUE Sip-Method Bye 8 VALUE Sip-Method Info 16 VALUE Sip-Method Options 32 VALUE Sip-Method Update 64 VALUE Sip-Method Register 128 VALUE Sip-Method Message 256 VALUE Sip-Method Subscribe 512 VALUE Sip-Method Notify 1024 VALUE Sip-Method Prack 2048 VALUE Sip-Method Refer 4096 VALUE Sip-Method Other 8192 ---------------------------Kamailio.cfg-------------------------------------------------------- #modparam("acc", "log_flag", FLT_ACC) modparam("acc_radius", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp") modparam("acc_radius", "radius_config","/etc/radiusclient-ng/radiusclient.conf") modparam("acc_radius", "radius_flag", FLT_ACC) modparam("acc_radius", "radius_missed_flag", FLT_ACCMISSED) modparam("acc_radius", "service_type", 15) modparam("misc_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("misc_radius", "group_service_type", 12) modparam("misc_radius", "uri_service_type", 10) modparam("misc_radius", "caller_extra", "Calling-Station-Id=$fu") modparam("misc_radius", "callee_extra", "SIP-URI-User=$rU;SIP-URI-Host=$rd") modparam("misc_radius", "group_extra", "My-Special=$avp(i:100)") modparam("misc_radius", "uri_extra", "Called-Station-Id=$tu") ------------------------------------------------------------------------------------------------ Thanks

3 6

t_lookup_request()
by Alex Balashov 13 May '15

13 May '15

Hello, From the documentation for t_lookup_request()[1], it is not clear whether it creates a new transaction if one does not exist: "Checks if a transaction exists. Returns a positive value if so, negative otherwise. Most likely you will not want to use it, as a typical application of a look-up is to introduce a new transaction if none was found. However this is safely (atomically) done using t_newtran." This language is quite unclear in the following respects: 1) Why would I not want to use it? 2) Does the "typical application" mean that t_lookup_request() _will_ create a new transaction if one does not exist? 3) Do I have some means of choosing whether to invoke t_lookup_request() in a "typical" or "atypical" application? 4) This statement "this is safely (atomically) done using t_newtran" implies that creating a new transaction using t_lookup_request() (which also implies that yes, it does create a new transaction) is "unsafe" and "non-atomic". Why is this? 5) Does this mean that the effect here would be to create two transactions? if(!t_lookup_request()) t_newtran(); -- Alex [1] http://kamailio.org/docs/modules/4.2.x/modules/tm.html#tm.f.t_lookup_request -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

← Newer
1
...
5
6
7
8
9
10
11
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users May 2015