sr-users May 2012

sr-users@lists.kamailio.org

84 participants
140 discussions

Re: [SR-Users] FW: (Devel) Segmentation fault using pua_dialoginfo

by Daniel-Constantin Mierla

Hello, interesting that the output of bt shows inline core_hash function prototype with same parameters as publ_cback_func, not being able to spot eventual wrong parameter values. Anyhow, in the gdb, can you do the commands: frame 1 p *hentity and send the output? Let's see the value of the pub uri for which hashing function crashes. What are the parameters for pua and pua_dialog info you set in the config file? Cheers, Daniel On 5/15/12 11:53 AM, Charles Chance wrote: > > Hi Daniel, > > As per your previous reply (sorry, I deleted it accidentally), please > find attached output of 'bt full' as requested. > > Best regards and thanks again, > > Charles > > ------------------------------------------------------------------------ > > *From:*Charles Chance [mailto:charles.chance@sipcentric.com] > *Sent:* 13 May 2012 11:21 > *To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) > -Users Mailing List' > *Subject:* (Devel) Segmentation fault using pua_dialoginfo > > Hi, > > Currently testing devel version and experiencing the following when > using pua_dialoginfo: > > ------------------------------------- > > Program terminated with signal 11, Segmentation fault. > > #0 core_hash (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at > ../../hashes.h:279 > > 279 v=(*p<<24)+(p[1]<<16)+(p[2]<<8)+p[3]; > > (gdb) bt > > #0 core_hash (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at > ../../hashes.h:279 > > #1 publ_cback_func (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at > send_publish.c:246 > > #2 0x002861d6 in run_trans_callbacks_internal (cb_lst=0xb3d7e370, > type=1024, trans=0xb3d7e330, params=0xbfcc31c8) at t_hooks.c:290 > > #3 0x002864d6 in run_trans_callbacks (type=1024, trans=0x200, > req=0x0, rpl=0xb7bea008, code=200) at t_hooks.c:317 > > #4 0x002afb28 in local_reply (t=0xb3d7e330, p_msg=0xb7bea008, > branch=0, msg_status=200, cancel_data=0xbfcc345c) at t_reply.c:2001 > > #5 0x002b2b45 in reply_received (p_msg=0xb7bea008) at t_reply.c:2350 > > #6 0x0809d5f4 in forward_reply (msg=0xb7bea008) at forward.c:790 > > #7 0x080e11a9 in receive_msg ( > > buf=0x82c4fa0 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP > xx.xx.xx.xxx;branch=z9hG4bKc13b.25313b6.0\r\nTo: > sip:000094@xx.xx.xx.xxx;tag=03373b1b433b65504ea28bd3d9e6db76.d7f2\r\nFrom: > sip:000094@xx.xx.xx.xxx;tag=4cc17c2c75cb82fa"..., len=393, > rcv_info=0xbfcc3648) at receive.c:270 > > #8 0x0817801b in udp_rcv_loop () at udp_server.c:544 > > #9 0x080b0426 in main_loop () at main.c:1633 > > #10 0x080b3d02 in main (argc=11, argv=0xbfcc3924) at main.c:2546 > > (gdb) up > > #1 publ_cback_func (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at > send_publish.c:246 > > 246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE); > > (gdb) p hentity->pres_uri > > Cannot access memory at address 0x8 > > (gdb) p *hentity > > Cannot access memory at address 0x0 > > ------------------------------------- > > Your time is greatly appreciated... > > Charles > -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

12 years

kamdbctl create changing mysql root password

by Tim King

This is not the first time I have had this issue during installation, but this time around I am having difficulty figuring out what I am doing wrong. Mysql is up and working, and client works. I can connect to it with the client and run queries without issue. When I run kamdbctl create I get the following. INFO: test server charset INFO: creating database openser ... ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) ERROR: Creating core tables failed! It creates the database but than fails to create tables. From this point I can no longer connect to mysql with what was my root password. I have to go through the process of resetting my root password before I can log back into mysql. How is this script chaning or corrupting my mysql root password? This is the relevant content of my kamctlrc file: # $Id$ # # The Kamailio configuration file for the control tools. # # Here you can set variables used in the kamctl and kamdbctl setup # scripts. Per default all variables here are commented out, the control tools # will use their internal default values. ## your SIP domain SIP_DOMAIN=sbc.mydomain.net ## chrooted directory # $CHROOT_DIR="/path/to/ chrooted/directory" ## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, DBTEXT, or SQLITE # by default none is loaded # # If you want to setup a database with kamdbctl, you must at least specify # this parameter. DBENGINE=MYSQL ## database host DBHOST=localhost ## database name (for ORACLE this is TNS name) DBNAME=openser # database path used by dbtext, db_berkeley or sqlite # DB_PATH="/usr/local/etc/kamailio/dbtext" ## database read/write user DBRWUSER=root ## password for database read/write user DBRWPW="mypassword" ## database read only user DBROUSER=root ## password for database read only user DBROPW="mypassword" ## database super user (for ORACLE this is 'scheme-creator' user) DBROOTUSER="root"

12 years

kamdbctl create changing mysql root password

by Tim King

This is not the first time I have had this issue during installation, but this time around I am having difficulty figuring out what I am doing wrong. Mysql is up and working, and client works. I can connect to it with the client and run queries without issue. When I run kamdbctl create I get the following. INFO: test server charset INFO: creating database openser ... ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) ERROR: Creating core tables failed! It creates the database but than fails. From this point I can no longer connect to mysql with what was my root password. I have to go through the process of resetting my root password before I can log back into mysql. How is this script chaning or corrupting my mysql root password? This is the relevant content of my kamctlrc file: # $Id$ # # The Kamailio configuration file for the control tools. # # Here you can set variables used in the kamctl and kamdbctl setup # scripts. Per default all variables here are commented out, the control tools # will use their internal default values. ## your SIP domain SIP_DOMAIN=sbc.mydomain.net ## chrooted directory # $CHROOT_DIR="/path/to/chrooted/directory" ## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, DBTEXT, or SQLITE # by default none is loaded # # If you want to setup a database with kamdbctl, you must at least specify # this parameter. DBENGINE=MYSQL ## database host DBHOST=localhost ## database name (for ORACLE this is TNS name) DBNAME=openser # database path used by dbtext, db_berkeley or sqlite # DB_PATH="/usr/local/etc/kamailio/dbtext" ## database read/write user DBRWUSER=root ## password for database read/write user DBRWPW="mypassword" ## database read only user DBROUSER=root ## password for database read only user DBROPW="mypassword" ## database super user (for ORACLE this is 'scheme-creator' user) DBROOTUSER="root"

12 years

Kamailio CS_Dirty

by Albert Petit

Hello, On a Kamailio deployment it seems some users get to a wrong state and permanently keeping in: CS_DIRTY Expires==0 for some long times (even half an hour). When they're in this status seems system cannot reach them. Normally , when working on USRLoc mode 2 if the registration expires usually what I observed is that it just not appears on 'kamctl ul show' The affected users are seen like this: AOR:: blue4 Contact:: sip:Blue4@192.168.101.6:5700 Q= Expires:: deleted Callid:: efc560dc2dbd248d4d1f9d39633773df Cseq:: 49995 User-agent:: PoC-client/OMA1.0 Genaker_X-Platform_IMS_SDK/v2.0 State:: CS_DIRTY Flags:: 0 Cflag:: 0 Socket:: udp:10.133.21.141:6666 Methods:: 8143 The refresh from the clients seem to come intime however some users (and not all) got to this CS_DIRTY state instead of being removed or refreshed. The client refresh looks to arrive in-time so it should be refreshed. Which could be a common cause (misconfiguration?) for this type of problem? If not, could enable debug mode for usrloc or I need to enable for full kamailio? Thanks Albert

12 years

Question about dialog module (state 1)

by Ricardo Martinez

Hello. I’m using the dialog module to keep control of simultaneous calls. In some cases, and I’m still trying to find why this happens, the dialog stays in “STATE:: 1”, which according to the docs is a dialog which no provisional response has been sent yet. Is there a way to eliminate this kind of dialogs??? When I list the dialogs I can see : dialog:: hash=2523:2040584107 state:: 1 ref_count:: 1 timestart:: 0 timeout:: 0 callid:: 25b8e5354ca0850a4d0bd9c43eeb617a(a)pxext.redvoiss.net from_uri:: sip:557100052213@pxext.redvoiss.net from_tag:: as10dc7c85 caller_contact:: sip:557100052213@200.68.19.44:5060 caller_cseq:: 103 caller_route_set:: caller_bind_addr:: udp:64.76.154.110:5060 callee_bind_addr:: to_uri:: sip:0981985480@pxext.redvoiss.net to_tag:: callee_contact:: callee_cseq:: callee_route_set:: when I try to eliminate this dialog : kamctl fifo dlg_terminate_dlg 25b8e5354ca0850a4d0bd9c43eeb617a(a)pxext.redvoiss.net 500 command 'dlg_terminate_dlg' failed Thanks in advance, Regards, Ricardo Martinez.-

12 years

[SIREMIS] send MI Commands to multiple kamailio servers

by SamyGo

Hello all, Following through the manual at : http://kb.asipto.com/siremis:install32x:mi-commands I'm able to send MI commands on external/remote server But next hurdle is how can I define multiple remote servers i.e <Remote name="remote0" address="127.0.0.1" port="8033"/> <Remote name="remote1" address="192.168.2.156" port="8033"/> <Remote name="remote2" address=" 192.168.2.150" port="8033"/> Is there any already working configuration else I think I may need to start a surgery on siremisMICommands.php file and make it loop over the remote tag and disptach commands until loop ends. is there any "MI-proxy" sort of thing available !!? Regards, Sammy.

12 years

Pickup group implementation in Kamailio

by M.C.

Hi all, I want to implement a "group pickup" (asterisk like) with Kamailio and Snom phones. I found in the changelog this comment: "- an useful application - call pickup: - INVITE comes in, callee is in a pickup group - store callid, cseq, etc in database or notify the other phones in the group (easy to do for snom phones and extra programmable buttons) via uac_req_send() - send a remote control command telling which call to pickup (callid, cseq) and where to redirect. In config, call t_cancel_callid(). in failure route for INVITE catch the cancelled transaction (flag is set), get the new destination (e.g., stored in htable) and forward the invite there"" regarding new functions in tmx module, but I have found no examples in kamailio documentation. Is this the way to implement a group pickup in kamailio? Regards, Matteo

12 years

FW: (Devel) Segmentation fault using pua_dialoginfo

by Charles Chance

Hi Daniel, As per your previous reply (sorry, I deleted it accidentally), please find attached output of 'bt full' as requested. Best regards and thanks again, Charles _____ From: Charles Chance [mailto:charles.chance@sipcentric.com] Sent: 13 May 2012 11:21 To: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: (Devel) Segmentation fault using pua_dialoginfo Hi, Currently testing devel version and experiencing the following when using pua_dialoginfo: ------------------------------------- Program terminated with signal 11, Segmentation fault. #0 core_hash (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at ../../hashes.h:279 279 v=(*p<<24)+(p[1]<<16)+(p[2]<<8)+p[3]; (gdb) bt #0 core_hash (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at ../../hashes.h:279 #1 publ_cback_func (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at send_publish.c:246 #2 0x002861d6 in run_trans_callbacks_internal (cb_lst=0xb3d7e370, type=1024, trans=0xb3d7e330, params=0xbfcc31c8) at t_hooks.c:290 #3 0x002864d6 in run_trans_callbacks (type=1024, trans=0x200, req=0x0, rpl=0xb7bea008, code=200) at t_hooks.c:317 #4 0x002afb28 in local_reply (t=0xb3d7e330, p_msg=0xb7bea008, branch=0, msg_status=200, cancel_data=0xbfcc345c) at t_reply.c:2001 #5 0x002b2b45 in reply_received (p_msg=0xb7bea008) at t_reply.c:2350 #6 0x0809d5f4 in forward_reply (msg=0xb7bea008) at forward.c:790 #7 0x080e11a9 in receive_msg ( buf=0x82c4fa0 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP xx.xx.xx.xxx;branch=z9hG4bKc13b.25313b6.0\r\nTo: sip:000094@xx.xx.xx.xxx;tag=03373b1b433b65504ea28bd3d9e6db76.d7f2\r\nFrom: sip:000094@xx.xx.xx.xxx;tag=4cc17c2c75cb82fa"..., len=393, rcv_info=0xbfcc3648) at receive.c:270 #8 0x0817801b in udp_rcv_loop () at udp_server.c:544 #9 0x080b0426 in main_loop () at main.c:1633 #10 0x080b3d02 in main (argc=11, argv=0xbfcc3924) at main.c:2546 (gdb) up #1 publ_cback_func (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at send_publish.c:246 246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE); (gdb) p hentity->pres_uri Cannot access memory at address 0x8 (gdb) p *hentity Cannot access memory at address 0x0 ------------------------------------- Your time is greatly appreciated. Charles

12 years

modify connection information field from a 200 OK response

by Openser Kamailio

hi, I try to change the IP address in connection information field from a 200 OK request passing through Kamailio. I want the IP address of the Kamailio in connection information. So, I've tried rtpproxy_answer("","@IP kamailio"), rtppproxy_offer("","@IP kamailio), rtpproxy_manage("","@IP kamailio"). It didn't change anything. Thanks for Help!

12 years

why is tcp_send failing?

by Juha Heinanen

i have been wondering why kamailio refuses to forward bye to $du sip:192.26.99.39:8000;transport=tcp;lr;ftag=a8266461a81c723o0 wireshark shows that it is not even trying to set up tcp connection to the destination and with telnet i can verify that tcp connection can be set up. debug at level 3 is below. -- juha May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: rr [loose.c:776]: URI to be processed: 'sip:192.26.99.39:8000;transport=tcp;lr;ftag=a8266461a81c723o0' May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: rr [loose.c:785]: Next URI is a loose router ... May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_lookup.c:1379]: DEBUG: t_newtran: msg id=5 , global msg id=5 , T on entrance=(nil) May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_lookup.c:527]: t_lookup_request: start searching: hash=30919, isACK=0 May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_lookup.c:485]: DEBUG: RFC3261 transaction matching failed May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_lookup.c:709]: DEBUG: t_lookup_request: no transaction found May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_hooks.c:374]: DBG: trans=0xb486de58, callback type 1, id 0 entered May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: <core> [md5utils.c:67]: DEBUG: MD5 calculated: d28c87700c1c48b71a3b7f63090bf160 May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: <core> [dns_cache.c:3400]: dns_sip_resolve(192.26.99.39, 0, 0), ip, ret=0 May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: <core> [msg_translator.c:204]: check_via_address(192.98.100.135, 192.168.0.145, 0) May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: ERROR: tm [../../forward.h:171]: msg_send: ERROR: tcp_send failed May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_fwd.c:1365]: t_send_branch: send to 192.26.99.39:8000 (2) failed May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: ERROR: tm [t_fwd.c:1383]: ERROR: t_send_branch: sending request on branch 0 failed May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_funcs.c:361]: ERROR:tm:t_relay_to: t_forward_nonack returned error May 12 15:58:30 sars /usr/sbin/sip-proxy[25453]: DEBUG: tm [t_funcs.c:369]: -477 error reply generation delayed

12 years

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

Jump to page:

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 2012