sr-users November 2012

sr-users@lists.kamailio.org

85 participants
125 discussions

ERROR: presence not working correctly with Kamailio 3.3.2-1.1 and Postgresql 9.1
by Robert Verspuy 05 Nov '12

05 Nov '12

Hi All, I've got a problem with Kamailio 3.3.2-1.1 on CentOS 6.3 with locally postgresql 8.4.13-1.el6_3 libraries, connected to a remote postgresql91-9.1.6-1PGDP.rhel6 server The presence module tries to insert a record in the presentity table, with some xml in the body column. But the body value in the postgresql table is not represented as a string '<?xml ...etc' But encodes as '\x3c3f786d6c2076657273696f6e3d27312e302720656e636f64696e673d275554462...etc' This gives problems when the presense module is trying to send out a notify based on the value in the database. With debugging, this gives the error: Entity: line 1: parser error : Start tag expected, '<' not found x3c3f786d6c2076657273696f6e3d27312e302720656e636f64696e673d275554462d38273f3e3c The \x in front of the hex encodes string is not properly interpreted by postgresql or kamailio. The body column of the table presentity is a bytea column, and I believe postgresql 9 outputs these bytea columns a bit differently then postgresql 8. When I try to run the sql statement: insert into presentity (domain,username,event,etag,sender,body,received_time,expires ) values ('newsip.lifexs.nl','00086','presence','a.1352107949.18632.27.0','','<?xml version=''1.0'' encoding=''UTF-',1343534532,1345213723) On the postgresql 9.1 server locally, I still get the '\x3c3f786d6c... etc' value in the database. The bytea_output setting in postgresql 9 is now standard set to 'hex' in stead of escape. I've changed the bytea_output setting in postgresql.conf to 'escape', and then the presence is working without any issues. So maybe the database module of postgresql has to be changed to pick up these bytea encodings properly? Because i think kamailio should work correctly with the default postgresql settings. With kind regards, Robert Verspuy -- *Exa-Omicron* Eenspan 8-K 3897 AL Zeewolde http://exa.nl

1 0

Entries in PUA List and RLS Watchers List
by Sangeeta Shah 03 Nov '12

03 Nov '12

Hello All, I am hoping the authors of the RLS/PUA modules can answer this question since I am not sure what's going on. I have the rls module enabled, with the following config spec: # ------rls module params ------ modparam("rls", "db_url", DBURL) modparam("rls", "db_mode", 2) modparam("rls", "integrated_xcap_server", 1) modparam("rls", "to_presence_code" ,10) modparam("rls", "server_address", "sip:rls@ip:5060") #!endif and modparam("pua_reginfo", "default_domain", "ip") modparam("pua_reginfo", "server_address", "sip:reginfo@ip") modparam("pua", "db_mode", 2) So for both I have DB_MODE set to DB ONLY. For whatever reason, even though all I am doing is bringing up my client I see over 250+ entries in the rls_watchers table for the same watcher and over 100 entries in the pua list table for the same presentity? Anyone have any idea what would be triggering this. There is definitely not anymore more than the normal messaging going on between the client and the server. Only error I see in the syslog: Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11745]: ERROR: db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry '1350937406' for key 'expires_idx' Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11744]: DEBUG: presence [subscribe.c:1216]: subs->contact= sip:rls@ip:5060 - len = 25 Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11761]: DEBUG: <core> [db_val.c:117]: converting STRING [8475551001] Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11746]: DEBUG: <core> [parser/msg_parser.c:626]: method: <SUBSCRIBE> Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11745]: ERROR: <core> [db_query.c:210]: error while submitting query Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11744]: DEBUG: rls [rls.h:241]: did= 41826031568472f9-11752@127.0.0.1;533cb9e91f4b999cf76861cbb9ed54ed-93a3;a6a1c5f60faecf035a1ae5b6e96e979a-464d Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11761]: DEBUG: <core> [db_val.c:117]: converting STRING [10.50.251.12] Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11746]: DEBUG: <core> [parser/msg_parser.c:628]: uri: <sip:8475551001@ip> Oct 22 15:22:22 RCS-Presence /usr/local/sbin/kamailio[11745]: ERROR: pua [pua_db.c:1149]: DB insert failed -- Sangeeta Shah

5 18

Error while "Make All"
by Techie Sup 02 Nov '12

02 Nov '12

Hello, I followed the instruction mentioned in Kamailio website. When I do a make all, I get the error. Please let me know how to fix this. I am new to Kamailio. ------------------- Package mono-2 was not found in the pkg-config search path. Perhaps you should add the directory containing `mono-2.pc' to the PKG_CONFIG_PATH environment variable No package 'mono-2' found Package mono-2 was not found in the pkg-config search path. Perhaps you should add the directory containing `mono-2.pc' to the PKG_CONFIG_PATH environment variable No package 'mono-2' found Package mono-2 was not found in the pkg-config search path. Perhaps you should add the directory containing `mono-2.pc' to the PKG_CONFIG_PATH environment variable No package 'mono-2' found Package mono-2 was not found in the pkg-config search path. Perhaps you should add the directory containing `mono-2.pc' to the PKG_CONFIG_PATH environment variable No package 'mono-2' found Package mono-2 was not found in the pkg-config search path. Perhaps you should add the directory containing `mono-2.pc' to the PKG_CONFIG_PATH environment variable No package 'mono-2' found CC (gcc) [M app_mono.so] app_mono_api.o In file included from app_mono_api.c:37: app_mono_api.h:27:26: warning: mono/jit/jit.h: No such file or directory app_mono_api.h:28:39: warning: mono/metadata/environment.h: No such file or directory In file included from app_mono_api.c:37: app_mono_api.h:35: error: expected specifier-qualifier-list before ‘MonoDomain’ app_mono_api.c:39:39: warning: mono/metadata/mono-config.h: No such file or directory app_mono_api.c:49: error: expected specifier-qualifier-list before ‘MonoDomain’ app_mono_api.c: In function ‘sr_mono_load_script’: app_mono_api.c:93: error: ‘sr_mono_load_t’ has no member named ‘next’ app_mono_api.c: In function ‘mono_sr_init_load’: app_mono_api.c:139: warning: implicit declaration of function ‘mono_config_parse’ app_mono_api.c:141: error: ‘sr_mono_load_t’ has no member named ‘domain’ app_mono_api.c:148: error: ‘sr_mono_load_t’ has no member named ‘domain’ app_mono_api.c:148: warning: implicit declaration of function ‘mono_jit_init’ app_mono_api.c:149: error: ‘sr_mono_load_t’ has no member named ‘domain’ app_mono_api.c:157: error: ‘sr_mono_load_t’ has no member named ‘assembly’ app_mono_api.c:157: warning: implicit declaration of function ‘mono_domain_assembly_open’ app_mono_api.c:157: error: ‘sr_mono_load_t’ has no member named ‘domain’ app_mono_api.c:158: error: ‘sr_mono_load_t’ has no member named ‘assembly’ app_mono_api.c:162: error: ‘sr_mono_load_t’ has no member named ‘next’ app_mono_api.c: In function ‘mono_sr_initialized’: app_mono_api.c:208: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c: In function ‘app_mono_exec’: app_mono_api.c:230: error: ‘sr_mono_env_t’ has no member named ‘msg’ app_mono_api.c:237: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c:246: error: ‘sr_mono_env_t’ has no member named ‘assembly’ app_mono_api.c:246: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c:247: error: ‘sr_mono_env_t’ has no member named ‘assembly’ app_mono_api.c:256: warning: implicit declaration of function ‘mono_jit_exec’ app_mono_api.c:256: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c:256: error: ‘sr_mono_env_t’ has no member named ‘assembly’ app_mono_api.c:257: warning: implicit declaration of function ‘mono_environment_exitcode_get’ app_mono_api.c:261: warning: implicit declaration of function ‘mono_jit_cleanup’ app_mono_api.c:261: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c: In function ‘app_mono_run’: app_mono_api.c:282: error: ‘sr_mono_env_t’ has no member named ‘msg’ app_mono_api.c:284: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c:284: error: ‘sr_mono_load_t’ has no member named ‘domain’ app_mono_api.c:285: error: ‘sr_mono_env_t’ has no member named ‘assembly’ app_mono_api.c:285: error: ‘sr_mono_load_t’ has no member named ‘assembly’ app_mono_api.c:286: error: ‘sr_mono_env_t’ has no member named ‘assembly’ app_mono_api.c:291: warning: implicit declaration of function ‘mono_domain_set’ app_mono_api.c:291: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c:298: error: ‘sr_mono_env_t’ has no member named ‘domain’ app_mono_api.c:298: error: ‘sr_mono_env_t’ has no member named ‘assembly’ app_mono_api.c: At top level: app_mono_api.c:310: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token app_mono_api.c:314: error: expected declaration specifiers or ‘...’ before ‘MonoString’ app_mono_api.c: In function ‘sr_mono_log’: app_mono_api.c:316: warning: implicit declaration of function ‘mono_string_to_utf8’ app_mono_api.c:316: error: ‘text’ undeclared (first use in this function) app_mono_api.c:316: error: (Each undeclared identifier is reported only once app_mono_api.c:316: error: for each function it appears in.) app_mono_api.c:316: warning: assignment makes pointer from integer without a cast app_mono_api.c:318: warning: implicit declaration of function ‘mono_free’ app_mono_api.c: At top level: app_mono_api.c:321: error: expected ‘)’ before ‘*’ token app_mono_api.c:328: error: expected ‘)’ before ‘*’ token app_mono_api.c:338: error: expected ‘)’ before ‘*’ token app_mono_api.c:408: error: ‘sr_mono_api_version’ undeclared here (not in a function) app_mono_api.c:410: error: ‘sr_mono_err’ undeclared here (not in a function) app_mono_api.c:411: error: ‘sr_mono_dbg’ undeclared here (not in a function) app_mono_api.c:412: error: ‘sr_mono_modf’ undeclared here (not in a function) app_mono_api.c: In function ‘sr_mono_load_class_core’: app_mono_api.c:420: warning: implicit declaration of function ‘mono_add_internal_call’ app_mono_api.c: At top level: app_mono_api.c:427: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token app_mono_api.c:478: error: expected ‘)’ before ‘*’ token app_mono_api.c:530: error: expected ‘)’ before ‘*’ token app_mono_api.c:579: error: expected ‘)’ before ‘*’ token app_mono_api.c:632: error: expected ‘)’ before ‘*’ token app_mono_api.c:679: error: expected ‘)’ before ‘*’ token app_mono_api.c:729: error: ‘sr_mono_pv_gets’ undeclared here (not in a function) app_mono_api.c:729: error: initializer element is not constant app_mono_api.c:729: error: (near initialization for ‘_sr_M_export_pv[0].method’) app_mono_api.c:730: error: ‘sr_mono_pv_geti’ undeclared here (not in a function) app_mono_api.c:730: error: initializer element is not constant app_mono_api.c:730: error: (near initialization for ‘_sr_M_export_pv[1].method’) app_mono_api.c:731: error: ‘sr_mono_pv_seti’ undeclared here (not in a function) app_mono_api.c:731: error: initializer element is not constant app_mono_api.c:731: error: (near initialization for ‘_sr_M_export_pv[2].method’) app_mono_api.c:732: error: ‘sr_mono_pv_sets’ undeclared here (not in a function) app_mono_api.c:732: error: initializer element is not constant app_mono_api.c:732: error: (near initialization for ‘_sr_M_export_pv[3].method’) app_mono_api.c:733: error: ‘sr_mono_pv_unset’ undeclared here (not in a function) app_mono_api.c:733: error: initializer element is not constant app_mono_api.c:733: error: (near initialization for ‘_sr_M_export_pv[4].method’) app_mono_api.c:734: error: ‘sr_mono_pv_is_null’ undeclared here (not in a function) app_mono_api.c:734: error: initializer element is not constant app_mono_api.c:734: error: (near initialization for ‘_sr_M_export_pv[5].method’) app_mono_api.c:750: error: expected ‘)’ before ‘*’ token app_mono_api.c:801: error: expected ‘)’ before ‘*’ token app_mono_api.c:850: error: expected ‘)’ before ‘*’ token app_mono_api.c:895: error: expected ‘)’ before ‘*’ token app_mono_api.c:930: error: ‘sr_mono_hdr_append’ undeclared here (not in a function) app_mono_api.c:930: error: initializer element is not constant app_mono_api.c:930: error: (near initialization for ‘_sr_M_export_hdr[0].method’) app_mono_api.c:931: error: ‘sr_mono_hdr_remove’ undeclared here (not in a function) app_mono_api.c:931: error: initializer element is not constant app_mono_api.c:931: error: (near initialization for ‘_sr_M_export_hdr[1].method’) app_mono_api.c:932: error: ‘sr_mono_hdr_insert’ undeclared here (not in a function) app_mono_api.c:932: error: initializer element is not constant app_mono_api.c:932: error: (near initialization for ‘_sr_M_export_hdr[2].method’) app_mono_api.c:933: error: ‘sr_mono_hdr_append_to_reply’ undeclared here (not in a function) app_mono_api.c:933: error: initializer element is not constant app_mono_api.c:933: error: (near initialization for ‘_sr_M_export_hdr[3].method’) make[1]: *** [app_mono_api.o] Error 1 make: *** [modules] Error 1 Regards Selvam

3 4

Kamailio WebSocket support
by Owen Lynch 02 Nov '12

02 Nov '12

Hi, I see Peter Dunkley's websocket work is not in the latest 3.3 release (3.3.2). What is the road map for this? Thanks, Owen Lynch

2 1

Re: [SR-Users] Kamailio and sylkserver integration
by Vijay Thakur 01 Nov '12

01 Nov '12

Thanks for your reply. Will you please explain that how can i forward calls from kamailio to sylkserver. Regards, VJ++ Message: 7 Date: Wed, 31 Oct 2012 08:26:50 +0100 From: "Olle E. Johansson"<oej(a)edvina.net> Subject: Re: [SR-Users] Kamailio and sylkserver integration To: "SIP Router - Kamailio \(OpenSER\) and SIP Express Router \(SER\) - Users Mailing List"<sr-users(a)lists.sip-router.org> Message-ID:<D7F883EA-4231-4D21-A79F-BB3449F972B1(a)edvina.net> Content-Type: text/plain; charset=us-ascii 31 okt 2012 kl. 06:49 skrev Vijay Thakur<vijay.thakur(a)loopmethods.com>: > Dear Sir, > > Is there any one in the list who have set up (integrated) Kamailio with sylkserver for conference. There is very less available information on the internet on this topic. All the required changes are made in sylkserver config files. > Kindly advise for required changes in Kamailio. As far as I understand, Sylkserver is just a SIP server. Forward calls from kamailio to sylkserver using any of the forwarding commands. /O -- * Olle E. Johansson -oej(a)edvina.net * Kamailio & SIP Masterclass Miami FL December 2012 *http://edvina.net/training/

2 1

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 November 2012