sr-users May 2012

sr-users@lists.kamailio.org

84 participants
140 discussions

installing the kamailio-devel problem with db_mysql

by Uri Shacked

Hi, i am trying to install the devel version using git. did the changes on the modules,lst file to include "db_mysql" i have mysql5.5 already installed with the shared components and client... i have no mysql.h file... so, the "make all" of kamailio failes... any ideas ? BR, Uri

11 years, 11 months

Presence dialoginfo expiry

by Tais Plougmann Hansen

Hi, I have presence/pua_dialoginfo set up and working well with 3.2.3. The only problem I'm facing right now is dialog event expiry from presentity. If there's no call activity for a while, the dialog event will expire and should a client reboot after this, they'll start up with unknown state in BLF subscriptions. I.e. question marks in the display on Aastra phones and will stay that way until there's new call activity. Is there a way to keep dialog events fresh even without call activity? I've tried setting override_lifetime very high (604800) but the events still managed to get removed after an hour or so. -- Tais Plougmann Hansen OSD Consulting ApS

11 years, 11 months

Re: [SR-Users] Change the Server field on the SIP dialog

by Charles Chance

Actually, for your version the documentation is at http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#server_header but it's the same thing :) Regards, Charles http://www.sipcentric.com -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Charles Chance Sent: 18 May 2012 11:12 To: sal(a)kom-1.com; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER)-Users Mailing List' Subject: Re: [SR-Users] Change the Server field on the SIP dialog Hi, Have you tried setting server_header? See here for more info: http://www.kamailio.org/wiki/cookbooks/3.2.x/core#server_header Regards, Charles http://www.sipcentric.com ________________________________________ From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Sal Aguilar Sent: 17 May 2012 19:00 To: sr-users(a)lists.sip-router.org Subject: [SR-Users] Change the Server field on the SIP dialog Hi Kamailio/SIP Router List: I turn to you guys since I could find a straight forward answer (it seems my google skills have dimished) on the wiki. Yesterday evening, my boss asked me about the possibility of replacing the value of the Server field, that our Kamailio 3.1 SIP Dispatcher is sending to customers. I want to know if this can be accomplished by adding a statement into the kamailio.cfg or is there something else needed. Below is a sample of the SIP dialog that we are currently sending to customers. Call-ID: 0a63682b2d021cbf4ddeac4833fe1b10(a)192.168.1.2. CSeq: 102 INVITE. Server: kamailio (3.1.4 (x86_64/linux)). Content-Length: 0. Your feedback would be greatly appreciated. Salvador Aguilar Email: sal(a)kom-1.com USA: +1.305.523.9581 Colombia: +57.1.381.9533 Mobile: +505.8672.4725 KOM 1 Communication ~more than just talk. www.kom-1.com ________________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2176 / Virus Database: 2425/5006 - Release Date: 05/17/12 _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2176 / Virus Database: 2425/5006 - Release Date: 05/17/12

11 years, 11 months

Change the Server field on the SIP dialog

by Sal Aguilar

Hi Kamailio/SIP Router List: I turn to you guys since I could find a straight forward answer (it seems my google skills have dimished) on the wiki. Yesterday evening, my boss asked me about the possibility of replacing the value of the Server field, that our Kamailio 3.1 SIP Dispatcher is sending to customers. I want to know if this can be accomplished by adding a statement into the kamailio.cfg or is there something else needed. Below is a sample of the SIP dialog that we are currently sending to customers. Call-ID: 0a63682b2d021cbf4ddeac4833fe1b10(a)192.168.1.2. CSeq: 102 INVITE. Server: kamailio (3.1.4 (x86_64/linux)). Content-Length: 0. Your feedback would be greatly appreciated. Salvador Aguilar Email: <mailto:sal@kom-1.com> sal(a)kom-1.com USA: +1.305.523.9581 Colombia: +57.1.381.9533 Mobile: +505.8672.4725 KOM 1 Communication ~more than just talk. www.kom-1.com <http://www.kom-1.com/>

11 years, 11 months

sdpops command not working

by Grégoire Vandendeurpel

Hello, I use Kamailio 3.2.3 and I used the command from the sdpops module " sdp_remove_media("video");" But when i restarted kamailio, this error appeared: 0(2623) ERROR: <core> [cfg.y:3393]: cfg. parser: failed to find command sdp_remove_media 0(2623) : <core> [cfg.y:3532]: parse error in config file /etc/kamailio/kamailio.cfg, line 721, column 27: unknown command, missing loadmodule? Do You know why ? Cause I loeded the sdpops module. Thanks in advance for your help -- *Grégoire Vandendeurpel, * * * *IT Sector*

11 years, 11 months

Question about LCR ping option

by Fabian Borot

Hello I am using kamailio 1.5.2. Our kamailio server has multiple IPs, and 1 of them happens to be a private IP for management purposes. When enabling the "ping" feature of the LCR module the machine sends the OPTIONS messages from the private IP. I need it to use at least any of the public IPs and if I can specify it it would be even better. I tried using the directive "ping from" with one of the public IPs but it only uses it to populate the "From" header, not to send the message from. One option could be to configure the configuration file with the "listen" directive including only the public IPs. However, there are more than 50 IPs, is there a limit to the number of IPs? I tried with a subnet and it is not allowed. Is there any other work around? txs a lot fborot

11 years, 11 months

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

by Daniel-Constantin Mierla

Hello, the content of ps->param is pretty much all invalid. So looks like a callback on a freed/invalid parameter, could be a double-callback execution. Set debug=3 and send all the messages for such case -- it might be quite a lot of them, so send them to my email address, the mailing list has a limit of message size. Cheers, Daniel On 5/17/12 2:13 PM, Charles Chance wrote: > > Hi, > > Requested output as follows: > > (gdb) frame 1 > > #1 publ_cback_func (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8) > > at send_publish.c:246 > > 246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE); > > (gdb) p *ps > > $2 = {req = 0x0, rpl = 0xb7c30340, param = 0xb3dc3ff4, code = 412, > flags = 0, > > branch = 0, t_rbuf = 0x0, dst = 0x0, send_buf = {s = 0x0, len = 0}} > > (gdb) p *(ua_pres_t*)(*ps->param) > > $3 = {id = {s = 0x20455942 <Address 0x20455942 out of bounds>, > > len = 980445555}, pres_uri = 0x40323531, event = 875444279, > > expires = 875703856, desired_expires = 858861105, flag = 808794676, > > db_flag = 1394618421, cb_param = 0x322f5049, next = 0xa0d302e, > > ua_flag = 979462486, etag = { > > s = 0x50495320 <Address 0x50495320 out of bounds>, len = 808333871}, > > tuple_id = {s = 0x5044552f <Address 0x5044552f out of bounds>, > > len = 775436064}, body = 0x322e3034, content_type = { > > s = 0x312e3134 <Address 0x312e3134 out of bounds>, len = 1648047155}, > > watcher_uri = 0x636e6172, call_id = { > > s = 0x397a3d68 <Address 0x397a3d68 out of bounds>, len = 1647593320}, > > to_tag = {s = 0x3435634b <Address 0x3435634b out of bounds>, > > len = 842149473}, from_tag = { > > s = 0x63306461 <Address 0x63306461 out of bounds>, len = 808334648}, > > cseq = 1767246349, version = 1394621025, outbound_proxy = 0x322f5049, > > extra_headers = 0x552f302e, record_route = { > > s = 0x31205044 <Address 0x31205044 out of bounds>, len = 825111097}, > > remote_contact = {s = 0x312e3836 <Address 0x312e3836 out of bounds>, > > len = 976498224}, contact = { > > s = 0x36373135 <Address 0x36373135 out of bounds>, len = 1701985073}} > > Yes, it is a test server so very happy to arrange for remote access if > required. In the meantime, I will do a little more digging to try to > find out why entity is null. > > Cheers, > > Charles > -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

11 years, 11 months

dlz-ldap-enum - expose LDAP data to Kamailio via ENUM

by Daniel Pocock

I've recently released a dlz ENUM module for the bind9 nameserver: http://www.opentelecoms.org/dlz-ldap-enum Basically, it handles ENUM queries from Kamailio, Asterisk, FreeSWITCH, repro, Lumicall, searches for the phone number in LDAP, and if found, returns the email address as both a SIP address and Jabber address This should make it even easier than ever before to get federated VoIP up and running using email addresses interchangeably with phone numbers. If the data already exists in LDAP as an address book, then just install bind9, install the module and you're up and running. Regards, Daniel

11 years, 11 months

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

by Daniel-Constantin Mierla

Hello, can you print in frame one: p *ps p *(ua_pres_t*)(*ps->param) I wonder why entity is null Is this a test system where eventually one can get remote access for live troubleshooting while you are testing? Cheers, Daniel On 5/16/12 2:02 PM, Charles Chance wrote: > > Hi Daniel, > > It happens every time but I just can't seem to pinpoint the cause. > Those parameters were initially unset and it still happened -- I added > them later in an attempt to diagnose. > > I removed them and re-ran, which produces a slightly different > backtrace... > > Program terminated with signal 11, Segmentation fault. > > #0 core_hash (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8) at > ../../hashes.h:277 > > 277 end=s1->s+s1->len; > > (gdb) bt > > #0 core_hash (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8) at > ../../hashes.h:277 > > #1 publ_cback_func (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8) at > send_publish.c:246 > > #2 0x005041d6 in run_trans_callbacks_internal (cb_lst=0xb3dc8e78, > type=1024, trans=0xb3dc8e38, params=0xbfcdd5d8) at t_hooks.c:290 > > #3 0x005044d6 in run_trans_callbacks (type=1024, trans=0x200, > req=0x0, rpl=0xb7c30340, code=412) at t_hooks.c:317 > > #4 0x0052db28 in local_reply (t=0xb3dc8e38, p_msg=0xb7c30340, > branch=0, msg_status=412, cancel_data=0xbfcdd86c) at t_reply.c:2001 > > #5 0x00530b45 in reply_received (p_msg=0xb7c30340) at t_reply.c:2350 > > #6 0x0809d5f4 in forward_reply (msg=0xb7c30340) at forward.c:790 > > #7 0x080e11a9 in receive_msg ( > > buf=0x82c4fa0 "SIP/2.0 412 Conditional request failed\r\nVia: > SIP/2.0/UDP xx.xx.xx.xxx;branch=z9hG4bK7058.f06a8876.0\r\nTo: > sip:152@xx.xx.xx.xxx:5060;tag=03373b1b433b65504ea28bd3d9e6db76.331b\r\nFrom: > sip:152@xx.xx.xx."..., len=374, rcv_info=0xbfcdda58) 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=0xbfcddd34) at main.c:2546 > > ...although the root cause appears to be the same: > > (gdb) frame 0 > > #0 core_hash (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8) at > ../../hashes.h:277 > > 277 end=s1->s+s1->len; > > (gdb) p *s1 > > Cannot access memory at address 0x40323531 > > (gdb) frame 1 > > #1 publ_cback_func (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8) at > send_publish.c:246 > > 246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE); > > (gdb) p *hentity > > Cannot access memory at address 0x0 > > The PUBLISH seems to be sent ok for both caller/callee for states > trying/confirmed. On tear-down however, it appears to crash somewhere > after sending state terminated for the callee as demonstrated by the > log... > > May 16 11:48:57 ws1 /usr/local/kamailio-devel/sbin/kamailio[31954]: > INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish > for URI sip:000091@xx.xx.xx.xxx:5060 > > May 16 11:48:57 ws1 /usr/local/kamailio-devel/sbin/kamailio[31953]: > INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish > for URI sip:000091@ xx.xx.xx.xxx:5060 > > May 16 11:48:57 ws1 /usr/local/kamailio-devel/sbin/kamailio[31953]: > INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish > for URI sip:152@ xx.xx.xx.xxx:5060 > > May 16 11:48:57 ws1 /usr/local/kamailio-devel/sbin/kamailio[31953]: > INFO: <core> [mem/f_malloc.c:529]: freeing a free fragment > (0xb3dc7c18/0xb3dc7c20) - ignore > > May 16 11:49:08 ws1 /usr/local/kamailio-devel/sbin/kamailio[31958]: > INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish > for URI sip:000091@ xx.xx.xx.xxx:5060 > > May 16 11:49:08 ws1 /usr/local/kamailio-devel/sbin/kamailio[31958]: > INFO: pua_dialoginfo [dialog_publish.c:386]: CALLING dialog_publish > for URI sip:152@ xx.xx.xx.xxx:5060 > > May 16 11:49:08 ws1 /usr/local/kamailio-devel/sbin/kamailio[31953]: > ERROR: presence [presentity.c:784]: No E_Tag match a.1337165329.31958.1.0 > > May 16 11:49:09 ws1 /usr/local/kamailio-devel/sbin/kamailio[31941]: > ALERT: <core> [main.c:785]: child process 31958 exited by a signal 11 > > I've attached the records from the presentity table also, as the > presence module doesn't appear to be matching the PUBLISHes with > existing records. > > Thanks again for your time, > > Charles > > ------------------------------------------------------------------------ > > *From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] > *Sent:* 16 May 2012 08:15 > *To:* Charles Chance > *Cc:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) > -Users Mailing List' > *Subject:* Re: FW: (Devel) Segmentation fault using pua_dialoginfo > > Hello, > > hmm, hentity is null even a check for its value is done above ... > > Is this reproducible or happens from time to time? What are the values > you set for $avp(s:puburis_caller) and $avp(s:puburis_callee)? > > Can you try without parameters: > > modparam("pua_dialoginfo", "use_pubruri_avps", 1) > modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)") > modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)") > > These were added by a recent contribution, I want to see if they are > the reason. > > Cheers, > Daniel > > On 5/16/12 12:00 AM, Charles Chance wrote: > >> Hi Daniel, >> >> I tried to check that already, but it's not there: >> >> (gdb) frame 1 >> >> #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 >> >> Cannot access memory at address 0x0 >> >> Config parameters are: >> >> modparam("pua", "db_url", "mysql://user:pass@xx.xx.xx.xxx/dbname" >> <mailto:mysql://user:pass@xx.xx.xx.xxx/dbname>) >> >> modparam("pua", "db_table", "kam_pua") >> >> modparam("pua_dialoginfo", "caller_confirmed", 1) >> >> modparam("pua_dialoginfo", "include_localremote", 0) >> >> modparam("pua_dialoginfo", "override_lifetime", 300) >> >> modparam("pua_dialoginfo", "use_pubruri_avps", 1) >> >> modparam("pua_dialoginfo", "pubruri_caller_avp", >> "$avp(s:puburis_caller)") >> >> modparam("pua_dialoginfo", "pubruri_callee_avp", >> "$avp(s:puburis_callee)") >> >> Cheers, >> >> Charles >> >> ------------------------------------------------------------------------ >> >> *From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] >> *Sent:* 15 May 2012 21:58 >> *To:* Charles Chance >> *Cc:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) >> -Users Mailing List' >> *Subject:* Re: FW: (Devel) Segmentation fault using pua_dialoginfo >> >> 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=03373b1b433b65504ea28bd3d9e6db76.d7f2%5Cr%5CnFrom>: >>> 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://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda >> >> ------------------------------------------------------------------------ >> >> No virus found in this message. >> Checked by AVG - www.avg.com <http://www.avg.com> >> Version: 2012.0.2171 / Virus Database: 2425/5000 - Release Date: 05/15/12 >> > > > -- > Daniel-Constantin Mierla -http://www.asipto.com > http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda > > ------------------------------------------------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com <http://www.avg.com> > Version: 2012.0.2176 / Virus Database: 2425/5001 - Release Date: 05/15/12 > -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

11 years, 11 months

un-suscribe

by Davis Doe

Please i would not like to receive mail from the kamailio group thanks davis

11 years, 11 months

← Newer
1
2
3
4
5
6
7
8
9
...
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