sr-users January 2011

sr-users@lists.kamailio.org

66 participants
111 discussions

Looking for the RTP Proxy
by Mallik 13 Jan '11

13 Jan '11

Dear sir, we re looking for RTP proxy training or solution, can you please give us more details on this thanking you with regards Mallik

1 0

How to test xhttp with wget or curl
by mayamatakeshi 13 Jan '11

13 Jan '11

Hello, can someone give me a sample of calling to xhttp from curl or wget? I have this in my kamailio.cfg: listen=tcp:192.168.2.105:80 loadmodule "xhttp.so" event_route[xhttp:request] { xhttp_reply("200", "OK", "text/html", "<html><body>OK - [$si:$sp]</body></html>"); } But when I try wget or curl, kamailio closes the connection without sending a response: [root@centos55-02105 tmp]# curl http://192.168.2.105/test curl: (52) Empty reply from server [root@centos55-02105 tmp]# wget http://192.168.2.105/test --2011-01-14 00:11:49-- http://192.168.2.105/test Connecting to 192.168.2.105:80... connected. HTTP request sent, awaiting response... No data received. I see this in the log file: Jan 14 00:04:47 centos55-02105 /usr/local/sbin/kamailio[10479]: ERROR: <core> [tcp_read.c:904]: ERROR: tcp_read_req: bad request, state=7, error=4 buf: GET /test HTTP/1.0^M User-Agent: Wget/1.11.4 Red Hat modified^M Accept: */*^M Host: 192.168.2.105^M Connection: Keep-Alive^M ^M parsed: GET /test HTTP/1.0^M User-Agent: Wget/1.11.4 Red Hat modified^M Accept: */*^M Host: 192.168.2.105^M Connection: Keep-Alive^M ^M br, takeshi

2 3

Dispatcher Setting
by Bernhard Suttner 13 Jan '11

13 Jan '11

Hi, I am using the Dispatcher module to load-balance the calls to several freeswitch servers. On which responses within the failure_route should be a fallback to another server (dst_next_dst())? I am sure, that on a 408 response there should be a fallback but whats about other 4XX responses and 5XX or 6XX? Thanks in advance. Best regards, Bernhard Suttner

2 2

OpenIMSCore and Kamalio Integration
by "Andrés S. García Ruiz" 13 Jan '11

13 Jan '11

Hi everybody, I'm trying to deploy an IMS network with OpenIMSCore and Kamailio. Since OpenIMSCore has been already tested along with Mobicents, now I want substitute Mobicents for Kamailio. I've also successfully installed Kamailio. I can run it without any problem, but when SIP Publish messages arrive at Kamalio, it answers with "407 Proxy Authentication Required". The IMS presentity is already registered against the OpenIMSCore. How can I solve that problem? The publish message sent: PUBLISH sip:testuser01@open-ims.test SIP/2.0 Route: <sip:ciervo.inf.um.es:5060;lr>, <sip:iscmark@scscf.open-ims.test:6060;lr;s=1;h=0;d=0;a=7369703a74657374757365723031406f70656e2d696d732e74657374> Call-ID: K28QO9PYAE5vn3RNdYOkIEddMEd6yDiqeAW7DwSt6XV. CSeq: 1 PUBLISH From: "testuser01" <sip:testuser01@open-ims.test>;tag=ff123bda To: "testuser01" <sip:testuser01@open-ims.test> Via: SIP/2.0/UDP 155.54.210.135:6060;branch=z9hG4bKa31a.6cba1cd2.0 Via: SIP/2.0/UDP 155.54.210.134:4060;branch=z9hG4bKa31a.71481d13.0;i=1 Via: SIP/2.0/TCP 155.54.190.166:8060;rport=41624;branch=z9hG4bK-d8754z-ce7487ff34be55f9-1---d8754z- Max-Forwards: 15 Content-Type: application/pidf+xml Expires: 30000 Event: presence Contact: <sip:testuser01@155.54.190.166:8060> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite IMS-OSGi-Client 0.1 CVS-Mon_Nov_29_10-14-33_CET_2010 Content-Length: 451 P-Asserted-Identity: <sip:testuser01@open-ims.test> P-Charging-Vector: icid-value="P-CSCFabcd000000004cf3708400000002";icid-generated-at=155.54.210.134;orig-ioi="open-ims.test" <?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' entity='sip:testuser01@open-ims.test'><tuple id='t6b9a6ab3'><status><basic>open</basic></status></tuple><dm:person id='p34b126e5'><rpid:activities><rpid:Online/></rpid:activities><dm:note>Online</dm:note></dm:person></presence> Kamailio answer: SIP/2.0 407 Proxy Authentication Required Call-ID: K28QO9PYAE5vn3RNdYOkIEddMEd6yDiqeAW7DwSt6XV. CSeq: 1 PUBLISH From: "testuser01" <sip:testuser01@open-ims.test>;tag=ff123bda To: "testuser01" <sip:testuser01@open-ims.test>;tag=b27e1a1d33761e85846fc98f5f3a7e58.3d3a Via: SIP/2.0/UDP 155.54.210.135:6060;branch=z9hG4bKa31a.6cba1cd2.0 Via: SIP/2.0/UDP 155.54.210.134:4060;branch=z9hG4bKa31a.71481d13.0;i=1 Via: SIP/2.0/TCP 155.54.190.166:8060;rport=41624;branch=z9hG4bK-d8754z-ce7487ff34be55f9-1---d8754z- Proxy-Authenticate: Digest realm="open-ims.test", nonce="TPNwMkzzbwZRE1piAM8yHaXGsXvwS16v" Server: kamailio (3.1.0 (i386/linux)) Content-Length: 0 Kamailio log: 5(15391) DEBUG: <core> [parser/msg_parser.c:628]: SIP Request: 5(15391) DEBUG: <core> [parser/msg_parser.c:630]: method: <PUBLISH> 5(15391) DEBUG: <core> [parser/msg_parser.c:632]: uri: <sip:testuser01@open-ims.test> 5(15391) DEBUG: <core> [parser/msg_parser.c:634]: version: <SIP/2.0> 5(15391) DEBUG: <core> [parser/msg_parser.c:165]: get_hdr_field: cseq <CSeq>: <1> <PUBLISH> 5(15391) DEBUG: <core> [parser/parse_to.c:803]: end of header reached, state=10 5(15391) DEBUG: <core> [parser/msg_parser.c:185]: DEBUG: get_hdr_field: <To> [45]; uri=[sip:testuser01@open-ims.test] 5(15391) DEBUG: <core> [parser/msg_parser.c:187]: DEBUG: to body ["testuser01" <sip:testuser01@open-ims.test> ] 5(15391) DEBUG: <core> [parser/parse_via.c:1287]: Found param type 232, <branch> = <z9hG4bKa31a.6cba1cd2.0>; state=16 5(15391) DEBUG: <core> [parser/parse_via.c:2300]: end of header reached, state=5 5(15391) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers: Via found, flags=2 5(15391) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers: this is the first via 5(15391) DEBUG: <core> [receive.c:145]: After parse_msg... 5(15391) DEBUG: <core> [receive.c:186]: preparing to run routing scripts... 5(15391) DEBUG: <core> [parser/parse_via.c:1287]: Found param type 232, <branch> = <z9hG4bKa31a.71481d13.0>; state=6 5(15391) DEBUG: <core> [parser/parse_via.c:1287]: Found param type 236, <i> = <1>; state=16 5(15391) DEBUG: <core> [parser/parse_via.c:2300]: end of header reached, state=5 5(15391) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers: Via found, flags=100 5(15391) DEBUG: <core> [parser/msg_parser.c:526]: parse_headers: this is the second via 5(15391) DEBUG: <core> [parser/parse_via.c:1287]: Found param type 235, <rport> = <41624>; state=6 5(15391) DEBUG: <core> [parser/parse_via.c:1287]: Found param type 232, <branch> = <z9hG4bK-d8754z-ce7487ff34be55f9-1---d8754z->; state=16 5(15391) DEBUG: <core> [parser/parse_via.c:2300]: end of header reached, state=5 5(15391) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers: Via found, flags=100 5(15391) DEBUG: maxfwd [mf_funcs.c:85]: value = 15 5(15391) DEBUG: <core> [parser/msg_parser.c:199]: DEBUG: get_hdr_body : content_length=451 5(15391) DEBUG: <core> [parser/msg_parser.c:101]: found end of header 5(15391) DEBUG: <core> [parser/parse_to.c:174]: DEBUG: add_param: tag=ff123bda 5(15391) DEBUG: <core> [parser/parse_to.c:803]: end of header reached, state=29 5(15391) DEBUG: sanity [mod_sanity.c:217]: all sanity checks passed 5(15391) DEBUG: siputils [checks.c:73]: no totag 5(15391) DEBUG: tm [t_lookup.c:1081]: DEBUG: t_check_msg: msg id=1 global id=0 T start=0xffffffff 5(15391) DEBUG: tm [t_lookup.c:528]: t_lookup_request: start searching: hash=41274, isACK=0 5(15391) DEBUG: tm [t_lookup.c:485]: DEBUG: RFC3261 transaction matching failed 5(15391) DEBUG: tm [t_lookup.c:711]: DEBUG: t_lookup_request: no transaction found 5(15391) DEBUG: tm [t_lookup.c:1150]: DEBUG: t_check_msg: msg id=1 global id=1 T end=(nil) 5(15391) DEBUG: <core> [socket_info.c:501]: grep_sock_info - checking if host==us: 13==9 && [open-ims.test] == [127.0.0.1] 5(15391) DEBUG: <core> [socket_info.c:504]: grep_sock_info - checking if port 5060 matches port 5060 5(15391) DEBUG: <core> [socket_info.c:501]: grep_sock_info - checking if host==us: 13==14 && [open-ims.test] == [155.54.190.245] 5(15391) DEBUG: <core> [socket_info.c:504]: grep_sock_info - checking if port 5060 matches port 5060 5(15391) DEBUG: <core> [socket_info.c:501]: grep_sock_info - checking if host==us: 13==9 && [open-ims.test] == [127.0.0.1] 5(15391) DEBUG: <core> [socket_info.c:504]: grep_sock_info - checking if port 5060 matches port 5060 5(15391) DEBUG: <core> [socket_info.c:501]: grep_sock_info - checking if host==us: 13==14 && [open-ims.test] == [155.54.190.245] 5(15391) DEBUG: <core> [socket_info.c:504]: grep_sock_info - checking if port 5060 matches port 5060 5(15391) DEBUG: auth_db [authorize.c:239]: realm value [open-ims.test] 5(15391) DEBUG: auth [api.c:85]: auth:pre_auth: Credentials with realm 'open-ims.test' not found 5(15391) DEBUG: auth_db [authorize.c:257]: not authenticated 5(15391) DEBUG: auth [challenge.c:102]: build_challenge_hf: realm='open-ims.test' 5(15391) DEBUG: auth [challenge.c:236]: auth: 'Proxy-Authenticate: Digest realm="open-ims.test", nonce="TPNwMkzzbwZRE1piAM8yHaXGsXvwS16v" ' 5(15391) DEBUG: sl [sl.c:278]: reply in stateless mode (sl) 5(15391) DEBUG: <core> [msg_translator.c:207]: check_via_address(155.54.210.135, 155.54.210.135, 0) 5(15391) DEBUG: <core> [usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil) 5(15391) DEBUG: <core> [usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil) 5(15391) DEBUG: <core> [usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil) 5(15391) DEBUG: <core> [usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil) 5(15391) DEBUG: <core> [usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil) 5(15391) DEBUG: <core> [usr_avp.c:646]: DEBUG:destroy_avp_list: destroying list (nil) 5(15391) DEBUG: <core> [receive.c:289]: receive_msg: cleaning up Thanks in advance, Andrés. -- ----------------------- Andrés S. García Ruiz ----------------------- e-mail: asgarcia(a)um.es Teléfono: (+34) 868 888258 Dpto. de Ingeniería de la Información y las Comunicaciones Facultad de Informática Universidad de Murcia 30100 Campus de Espinardo

5 13

set_dlg_profile not working?
by Ricardo Martinez 12 Jan '11

12 Jan '11

Hello. I’m trying to count the calls to a specific gateway. So I’m using the dialog module. This route is done before the final relay. route[CHANNELS] { if( is_method("INVITE") ) { if(!isflagset(31) ) { # user has max channel limit set as preference if(is_avp_set("$avp(s:channels)") && avp_check("$avp(s:channels)", "gt/s:0")) { # get current calls for uuid xlog("L_INFO","[$ci] : avp_channels existe y es mayor que 0 ?"); if (get_profile_size("gws","$rd","$var(calls)")) { xlog("L_INFO","Actualmente el gateway $rd tiene $var(calls) llamadas simultaneas\n"); } # check within limit if($avp(s:channels) > $var(calls)) { xlog("L_INFO", "CHANNELS : terminador '$rd' tiene '$var(calls)' de '$avp(s:channels)' active calls before this one\n"); $var(setprofile) = 1; } else { xlog("L_INFO", "Call crtl: user channel limit exceeded [$var(calls)/$avp(s:channels)]\n"); send_reply("487", "Request Terminated: Channel limit exceeded"); exit; } } else { xlog("L_INFO","[$ci] : the value if channels is $avp(s:channels)"); if( !is_avp_set("$avp(s:channels)") ) { xlog("L_INFO","[$ci] : avp_channel not set"); }; if(!avp_check("$avp(s:channels)", "gt/s:0") ) { xlog("L_INFO","[$ci] : avp_channel menor que 0?"); }; $var(setprofile) = 0; } } if($var(setprofile) > 0) { * if ( set_dlg_profile("gws","$rd") ) {* * xlog("L_INFO","set_dlg_profile exitoso");* } } When i made the call and try to see the profile with this command : [root@sipvoiss kamailio]# kamctl fifo profile_get_size gws 10.0.0.220 profile:: name=gws value=10.0.0.220 count=0 I’m not seeing the call added to the profile, despite the fact I using the * set_dlg_profile("gws","$rd")* What could be happening? This is part of the debug : Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] INVITE dominio:10.0.0.208 LOCAL DOMAIN Jan 11 18:07:03 .: DEBUG: misc_radius [functions.c:212]: success Jan 11 18:07:03 .: DEBUG: misc_radius [functions.c:133]: AVP 'tranum'/0=' sip:02444444444@10.0.0.208 <sip%3A02444444444(a)10.0.0.208>'/0 has been added Jan 11 18:07:03 .: DEBUG: misc_radius [functions.c:133]: AVP 'channels'/0='2'/0 has been added Jan 11 18:07:03 .: DEBUG: avpops [avpops_impl.c:1047]: 1 avps were processed Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] INVITE con dominio:10.0.0.208 checks de usuario via avp_radius OK Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] CHECKS SECTION :: INVITE:sip:02444444444@10.0.0.208 <INVITE%3Asip%3A02444444444(a)10.0.0.208>checks ok... Jan 11 18:07:03 .: DEBUG: lcr [lcr_mod.c:1748]: added matched_gws[0]=[1, 4, 1, 8207736] Jan 11 18:07:03 .: DEBUG: lcr [lcr_mod.c:1645]: added gw_uri_avp <1|1|4|550|3700771904||5060||1|0> with weight <8207736> Jan 11 18:07:03 .: DEBUG: lcr [lcr_mod.c:1911]: r_uri < sip:5504444444@10.0.0.220:5060>, dst_uri <> Jan 11 18:07:03 .: DEBUG: lcr [lcr_mod.c:2015]: added ruri_user_avp <02444444444> Jan 11 18:07:03 .: DEBUG: lcr [lcr_mod.c:2050]: added flags_avp <0> Jan 11 18:07:03 .: DEBUG: lcr [lcr_mod.c:2057]: added defunct_gw_avp <3700771904> Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] Ruta LCR : cambiando sip:02444444444@10.0.0.208 <sip%3A02444444444(a)10.0.0.208> por sip:5504444444@10.0.0.220:5060 Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] : entro en ruta 39 de call control Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] : no esta seteado el flag 31 Jan 11 18:07:03 .: DEBUG: avpops [avpops_impl.c:1180]: check <2> against <0> as str /16 Jan 11 18:07:03 .: INFO: <script>: [ 71492292-34f2-a3ed-814e-0002a400d53d(a)10.0.0.214] : avp_channels existe y es mayor que 0 ? Jan 11 18:07:03 .: INFO: <script>: Actualmente el gateway 10.0.0.220 tiene 0 llamadas simultaneas Jan 11 18:07:03 .: INFO: <script>: CHANNELS : terminador '10.0.0.220' tiene '0' de '2' active calls before this one Jan 11 18:07:03 .: INFO: <script>: set_dlg_profile exitoso Thanks in advance, *Regards,* *Ricardo.-*

2 5

AFTER MAINTENANCE DIALOG MODULE NOT WORKING
by Phillman25 Kyriacou 12 Jan '11

12 Jan '11

Hi I performed the following maintenance actions to my server that is currently installed with kamailio v3.1 cd /usr/local/src/kamailio-3.1.0/kamailio git pull origin make all make install After this action the dialog module is not working, after investigation, i found out that the following entry is causing this issue: modparam("dialog", "db_mode", 1) In my syslog i find the following errors: Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7397]: CRITICAL: dialog [dlg_db_handler.c:117]: BUG - db connection found already open Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 33 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 34 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7397]: ERROR: dialog [dialog.c:620]: failed to connect to database (rank=24) Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7397]: ERROR: <core> [sr_module.c:832]: init_mod_child(): Error while initializing module dialog (/usr/local/lib/kamailio/modules_k/dialog.so) Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7397]: ERROR: <core> [pt.c:481]: ERROR: fork_tcp_process(): init_child failed for process 30, pid 7397, "tcp receiver child=7" Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7397]: ERROR: <core> [tcp_main.c:4811]: ERROR: tcp_main: fork failed: Success Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 37 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 43 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 30 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 41 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 5 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7396]: WARNING: <core> [db_id.c:281]: identical DB URLs, but different DB connection pid [7396/7349] Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7391]: INFO: <core> [main.c:807]: INFO: signal 15 received Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 47 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7396]: CRITICAL: dialog [dlg_db_handler.c:117]: BUG - db connection found already open Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7396]: ERROR: dialog [dialog.c:620]: failed to connect to database (rank=23) Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7396]: ERROR: <core> [sr_module.c:832]: init_mod_child(): Error while initializing module dialog (/usr/local/lib/kamailio/modules_k/dialog.so) Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7396]: ERROR: <core> [pt.c:481]: ERROR: fork_tcp_process(): init_child failed for process 29, pid 7396, "tcp receiver child=6" Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 39 Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7396]: ERROR: <core> [tcp_main.c:4811]: ERROR: tcp_main: fork failed: Success Jan 11 16:45:54 SipProxy /usr/local/sbin/kamailio[7398]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 45 Only the dialog module is facing this problem Has anyone faced this before? Thanks Phillip

2 2

mi_fifo question
by Ricardo Martinez 11 Jan '11

11 Jan '11

Hello. I’m trying to use the kamctl command to get information about dialogs. I’m using the next line : kamctl fifo profile_get_size:kamailio_fifo and I’m getting the next output in the log file : Jan 11 12:34:38 /usr/local/sbin/kamailio[15051]: ERROR: mi_fifo [fifo_fnc.c:223]: open error (/tmp/kamailio_fifo:openser_receiver_15073): No such file or directory Jan 11 12:34:38 /usr/local/sbin/kamailio[15051]: ERROR: mi_fifo [fifo_fnc.c:484]: cannot open reply pipe /tmp/kamailio_fifo:openser_receiver_15073 What I’m doing wrong? This is part of the configuration file : # ----- mi_fifo params ------ modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo") modparam("mi_fifo", "fifo_group", 0) modparam("mi_fifo", "fifo_group", "root") modparam("mi_fifo", "fifo_user", 0) modparam("mi_fifo", "fifo_user", "root") and this is the file kamailio_fifo in the /tmp directory : [root@kamailio]# ls -la /tmp total 52 drwxrwxrwt. 4 root root 4096 Jan 11 12:38 . dr-xr-xr-x. 25 root root 4096 Jan 7 09:25 .. drwxrwxrwt 2 root root 4096 Jan 7 09:25 .ICE-unix *prw-rw---- 1 root root 0 Jan 11 12:34 kamailio_fifo* drwx------ 2 root root 4096 Jan 11 09:54 ssh-gpTCQ12700 Hope someone could help me. Regards, Ricardo.-

2 3

Re: [SR-Users] Avp_write missing modules ?
by Alex Balashov 10 Jan '11

10 Jan '11

Please keep the discussion on list - cc: the list. I see no indication in the documentation that avp_write() is a function that exists, even going back to 1.4.x. On 01/10/2011 04:54 PM, Amit Nepal wrote: > Kamailio 3.1 > > Thank You > Amit Nepal > Systems Administrator > Phoenix Internet > Phone: 602-385-0731 > 602-234-0917#112 > http://www.phoenixinternet.net > > > On 1/10/2011 2:50 PM, Alex Balashov wrote: >> On 01/10/2011 04:48 PM, Amit Nepal wrote: >>> I am getting missing loadmodule issue with avp_write. I have the >>> following statement on line 11 and i am getting this error. Could you >>> please help me on this. But i can load from db using avp_db_load and i >>> can delete avp values but only avp_write is not working. >>> >>> >>> avp_write("$ruri", "s:fwd_blind"); >>> >>> loading modules under >>> /usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/ >>> 0(2361) : <core> [cfg.y:3412]: parse error in config file >>> /usr/local/etc/kamailio/cfgs/pstn.cfg, line 11, column 39: unknown >>> command, missing loadmodule? >>> >>> ERROR: bad config file (1 errors) >> >> Which version of Kamailio? >> -- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/

3 5

Avp_write missing modules ?
by Amit Nepal 10 Jan '11

10 Jan '11

I am getting missing loadmodule issue with avp_write. I have the following statement on line 11 and i am getting this error. Could you please help me on this. But i can load from db using avp_db_load and i can delete avp values but only avp_write is not working. avp_write("$ruri", "s:fwd_blind"); loading modules under /usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/ 0(2361) : <core> [cfg.y:3412]: parse error in config file /usr/local/etc/kamailio/cfgs/pstn.cfg, line 11, column 39: unknown command, missing loadmodule? ERROR: bad config file (1 errors) Thank you Amit

2 1

Problem with contact header parsing and get_redirects
by Stefan Prelle 10 Jan '11

10 Jan '11

Hi folks, Since upgrading vom Kamailio 1.5 to 3.1 I have a problem using get_redirects from the uac_redirect module. It seems that there is a problem with parsing the Contact header from the received 302. This is my script excerpt: if (t_check_status("3[0-9][0-9]")) { get_redirects("*"); if (!t_relay()) { xlog("L_ERR","t_relay failed\n"); } } Some 302 messages lead (as expected) to INVITEs send to targets in the Contact header, for others t_relay fails. A working example would be Contact:<sip:+49406686100@192.168.0.1:5060;user=phone>;q=0.5,<sip: +49406686100@192.168.0.2:5060;user=phone>;q=0.25 It fails on Contact: sip:+49406686100@192.168.0.1:5060 The following log messages appear when calling get_redirects (and failing t_relay): kamailio[7372]: DEBUG: uac_redirect [rd_funcs.c:74]: resume branch=0 kamailio[7372]: DEBUG: uac_redirect [rd_funcs.c:81]: checking branch=0 (added=0) kamailio[7372]: DEBUG: uac_redirect [rd_funcs.c:85]: branch=0 is a redirect (added=0) kamailio[7372]: WARNING: <core> [mem/q_malloc.c:366]: qm_malloc(0x82ba320, 32) called from <core>: parser/msg_parser.c: parse_headers(339) kamailio[7372]: WARNING: <core> [mem/q_malloc.c:406]: qm_malloc(0x82ba320, 32) returns address 0x8311d94 frag. 0x8311d7c (size=32) on 1 -th hit kamailio[7372]: DEBUG: uac_redirect [rd_funcs.c:233]: contact hdr not found in sh_rpl The Contact header that fails obviously has no parameters for the URI and contact itself. As far as I understand the RFC 3261 BNF this is valid. The 302 response is by the way created by kamailio when using the LCR module (like this) if (!load_gws("1")) {... exit;} if (!next_gw()) {... exit; } sl_send_reply("302", "Not here"); Did I miss anything when upgrading or is this a problem with the parser? Cheers, Stefan

2 5

← 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 January 2011