sr-users March 2016

sr-users@lists.kamailio.org

88 participants
127 discussions

options_reply() - ruri contains username

by Alex Balashov

Hello, This may have been discussed before, but when options_reply() from the siputils module is used to respond to OPTIONS requests and those OPTIONS requests come in with an RURI containing a user part, the following error is emitted to the logs: LM_ERR("ruri contains username\n"); No reply for the OPTIONS ping is given in this scenario. OPTIONS pings against a username are very common, and I can find no justification for this check in my interpretation of RFC 3261 scripture. According to Section 11.1 ("Construction of an OPTIONS request"): An OPTIONS request is constructed using the standard rules for a SIP request as discussed in Section 8.1.1. Moreover, the example request line given in that very section is: OPTIONS sip:carol@chicago.com SIP/2.0 Might it perhaps be agreeable to remove this constraint? Or is there some rationale for its presence that I have simply failed to grasp? Thanks! -- Alex -- 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/

8 years, 8 months

Reg: Facing issue in Registration of SIP Client

by sainath.ellendula＠wipro.com

Hi Franz, On Successful completion of Registration of IMS client. Now, I was trying to REGISTER SIP Client, But REGISTER request failing with 403 forbidden- User unknown. Please find attachment of X-lite configuration and Tcpdump from #422. Could you please suggest me any changes has to be done. Thanks in advance!! Regards, Sainath The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

8 years, 8 months

Hello I am having problems pointing to a custom dispatcher table

by Humberto Rodriguez

Hello I am having problems pointing to a custom dispatcher table, when I use "dispatcher" as table, the kamailio service start running normal, but when I try to use for example "my_dispatcher" table the error shown bellow appears. I do not want to rebuilt the database, *my purpose is to have multiples dispatcher tables on the same server*, "dispatcher, my_dispatcher", "my_dispatcher_1", for example. The connection to the custom database is OK Thanks in advance for your help. ---------------------------------------------------------------------------------------- /var/log/messages Mar 3 14:03:00 kama-balance4 /usr/local/kamailio/sbin/kamailio[19153]: ERROR: dispatcher [dispatch.c:676]: init_ds_db(): invalid table version (found 0 , required 1, 2, 3 or 4)#012(use kamdbctl reinit) Mar 3 14:03:00 kama-balance4 /usr/local/kamailio/sbin/kamailio[19153]: ERROR: dispatcher [dispatcher.c:335]: mod_init(): could not initiate a connect to the database Mar 3 14:03:00 kama-balance4 /usr/local/kamailio/sbin/kamailio[19153]: ERROR: <core> [sr_module.c:970]: init_mod(): init_mod(): Error while initializing module dispatcher (/usr/local/kamailio/lib64/kamailio/modules/dispatcher.so)

8 years, 8 months

mariadb and sql_query_async: the db driver module doesn't support async query

by Daniel Tryba

So trying to push some inserts/updates to the background I added: async_workers=1 and replaced sql_xquery("ca", "$var(query)", "ra"); sql_result_free("ra"); with sql_query_async("ca", "$var(query)"); where: $var(query)="insert into CDR.callogs (accountcode,number) values ('"+$var(accountcode)+"',substring('"+$rU+"',1,4))"; Only to find out that the queries aren't inserted and the log contains: /usr/sbin/kamailio[24754]: ERROR: sqlops [sql_api.c:429]: sql_do_query_async(): the db driver module doesn't support async query The table is an InnoDB some insert delayed should give these kind of errors, but isn't the point of sql_query_async that it does the plain normal insert in a background task? Test machine: kamailio 4.2.5

8 years, 8 months

Kamailio 5.0 - db_cluster module sql_query_async support

by Daniel Tryba

If the backends for a dbcluster supports sql_query_async, sql_query_async should be available. At this moment (only tested with 4.3.x) async isn't supported.

8 years, 8 months

Kamailio v4.3.5 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v4.3.5 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.5. For more details about version 4.3.5 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2016/03/kamailio-v4-3-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

8 years, 8 months

Kamailio 5.0 - HTTP loading of config files

by Tim Chubb

As a suggestion for 5.0 being able to load config files from a URL, with any includes being taken relative to the URL would be a really handy feature. It would allow a central source for config files in a cluster and make it a much simpler process to push out changes to routing to all nodes.

8 years, 8 months

Releasing Kamailio v4.3.5

by Daniel-Constantin Mierla

Hello, it's been a while since the release of v4.3.4, therefore I am considering to release a new minor version from branch 4.3 next week, most probably on Thursday, March 3, 2016. As usual, if there you are aware of issues not reported to the tracker [1], do it as soon as possible to get a chance to be fixed before the release date. Cheers, Daniel [1] https://github.com/kamailio/kamailio/issues -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, March 7-9, 2016 - http://www.asipto.com

8 years, 8 months

change the to_tag on send_reply() or sl_send_reply()

by Uri Shacked

Hi, Is i possible to control the to_tag when i send my own stateless reply from kamailio. Thanks, Uri

8 years, 8 months

Handling of messages with manipulated Event header.

by Christopher Vella

Hi, I apologise if this is not the correct venue for such a question... I am running kamailio v4.3.4 (x86_64/linux) on debian Jessie, sourced from; deb http://deb.kamailio.org/kamailio jessie main In my routing logic I am handling SUBSCRIBE requests and striping extra Event package parameters appended to "ua-profile" event types. i.e.; Event: ua-profile;model=somemodel;vendor=somevendor;profile-type=user becomes; Event: ua-profile This is done with this code; } else if( is_method("SUBSCRIBE")) { subst('/ua-profile.*/ua-profile/') ; handle_subscribe(); t_release(); However, in such conditions "search_event()" doesn't correctly find the event. Even though it looks like it is searching for the right event type; start event= [ua-profile/7] handle_subscribe(): unsupported presence event ua-profile --- Begin debug ---- ]3(7664) DEBUG: <core> [re.c:457]: subst_run(): matched (332, 79): [Event: ua-profile;model=somemodel;vendor=somevendor;profile-type=user] with [Event: ua-profile]extops.c:680]: subst_f(): textops: replacing at offset 376[Event: ua-profile;model=somemodel;vendor=somevendor;profile-type=user] 13(7664) debug: textops [textops.c:696]: subst_f(): lst was 0x7fb391fd0da8 13(7664) error: *** cfgtrace:request_route=[presence] c=[/etc/kamailio/kamailio.cfg] l=365 a=24 n=handle_subscribe 13(7664) debug: presence [event_list.c:348]: search_event(): start event= [ua-profile/7] 13(7664) notice: presence [subscribe.c:1092]: handle_subscribe(): unsupported presence event ua-profile 13(7664) debug: tm [t_lookup.c:1011]: t_check_msg(): debug: t_check_msg: msg id=1 global id=1 t start=0x7fb388763290 13(7664) debug: tm [t_lookup.c:1083]: t_check_msg(): debug: t_check_msg: t already found! 13(7664) debug: <core> [mem/shm_mem.c:101]: _shm_resize(): warning:vqm_resize: resize(0) called 13(7664) debug: tm [t_reply.c:1591]: cleanup_uac_timers(): debug: cleanup_uac_timers: retr/fr timers reset 13(7664) debug: <core> [tcp_main.c:2196]: tcpconn_send_put(): send from reader (7664 (13)), reusing fd 13(7664) debug: <core> [tcp_main.c:2430]: tcpconn_do_send(): sending... 13(7664) debug: <core> [tcp_main.c:2464]: tcpconn_do_send(): after real write: c= 0x7fb38875ecf8 n=368 fd=9 13(7664) debug: <core> [tcp_main.c:2465]: tcpconn_do_send(): buf= sip/2.0 489 bad event via: sip/2.0/tcp 127.0.1.1:5060;branch=z9hg4bk-2999-1-0;rport=34679;received=192.168.88.88 cseq: 1 subscribe call-id: 1-2999(a)127.0.1.1 from: <sip:c.vella@albourne.com>;tag=1 to: <sip:provisioning@albourne.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-811a --- End debug --- As a test, I send another message with clean "Event: ua-profile" and this works , event= [ua-profile/7] is found. --- Begin debug --- ]4(7665) DEBUG: <core> [re.c:457]: subst_run(): matched (332, 18): [Event: ua-profile ] with [Event: ua-profile]extops.c:680]: subst_f(): textops: replacing at offset 376 [Event: ua-profile 14(7665) DEBUG: textops [textops.c:696]: subst_f(): lst was 0x7fb391fd0da8 14(7665) ERROR: *** cfgtrace:request_route=[PRESENCE] c=[/etc/kamailio/kamailio.cfg] l=365 a=24 n=handle_subscribe 14(7665) DEBUG: presence [event_list.c:348]: search_event(): start event= [ua-profile/7] 14(7665) DEBUG: presence [subscribe.c:1161]: extract_sdialog_info_ex(): 'Expires' header found, value= 3600 14(7665) DEBUG: presence [subscribe.c:1195]: extract_sdialog_info_ex(): 'To' header ALREADY PARSED: <sip:provisioning@albourne.com> 14(7665) DEBUG: presence [subscribe.c:1266]: extract_sdialog_info_ex(): generating to_tag 14(7665) DEBUG: sl [sl.c:329]: get_reply_totag(): totag stateful mode (tm) 14(7665) DEBUG: presence [subscribe.c:1326]: extract_sdialog_info_ex(): subs->contact= sip:c.vella@192.168.88.179:59206;transport=tcp - len = 46 14(7665) DEBUG: presence [subscribe.c:1043]: handle_subscribe(): subscription status= active - inserted 14(7665) DEBUG: presence [subscribe.c:554]: update_subscription(): update subscription 14(7665) DEBUG: presence [notify.c:115]: printf_subs(): pres_uri: sip:c.vella@albourne.com 14(7665) DEBUG: presence [notify.c:116]: printf_subs(): watcher_user@watcher_domain: c.vella(a)albourne.com 14(7665) DEBUG: presence [notify.c:117]: printf_subs(): to_user@to_domain: provisioning(a)albourne.com 14(7665) DEBUG: presence [notify.c:118]: printf_subs(): from_user@from_domain: c.vella(a)albourne.com 14(7665) DEBUG: presence [notify.c:119]: printf_subs(): callid/from_tag/to_tag: 1-3002(a)127.0.1.1/1/a6a1c5f60faecf035a1ae5b6e96e979a-1030 14(7665) DEBUG: presence [notify.c:120]: printf_subs(): local_cseq/remote_cseq: 0/1 14(7665) DEBUG: presence [notify.c:121]: printf_subs(): local_contact/contact: sip:192.168.88.85:5060;transport=tcp/sip:c.vella@192.168.88.179:59206;transport=tcp 14(7665) DEBUG: presence [notify.c:122]: printf_subs(): record_route: 14(7665) DEBUG: presence [notify.c:123]: printf_subs(): sockinfo_str: tcp:192.168.88.85:5060 14(7665) DEBUG: presence [notify.c:125]: printf_subs(): event: ua-profile 14(7665) DEBUG: presence [notify.c:126]: printf_subs(): status: active 14(7665) DEBUG: presence [notify.c:127]: printf_subs(): reason: 14(7665) DEBUG: presence [notify.c:128]: printf_subs(): version: 1 14(7665) DEBUG: presence [notify.c:129]: printf_subs(): expires: 3600 14(7665) DEBUG: presence [notify.c:131]: printf_subs(): updated/updated_winfo: -1/-1 14(7665) DEBUG: presence [subscribe.c:629]: update_subscription(): subscription not in dialog 14(7665) DEBUG: presence [subscribe.c:634]: update_subscription(): inserting in shtable 14(7665) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=1 T start=0x7fb388763290 14(7665) DEBUG: tm [t_lookup.c:1083]: t_check_msg(): DEBUG: t_check_msg: T already found! 14(7665) DEBUG: <core> [mem/shm_mem.c:101]: _shm_resize(): WARNING:vqm_resize: resize(0) called 14(7665) DEBUG: tm [t_reply.c:1591]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset 14(7665) DEBUG: <core> [tcp_main.c:2196]: tcpconn_send_put(): send from reader (7665 (14)), reusing fd 14(7665) DEBUG: <core> [tcp_main.c:2430]: tcpconn_do_send(): sending... 14(7665) DEBUG: <core> [tcp_main.c:2464]: tcpconn_do_send(): after real write: c= 0x7fb38875ecf8 n=399 fd=9 14(7665) DEBUG: <core> [tcp_main.c:2465]: tcpconn_do_send(): buf= SIP/2.0 202 OK Via: SIP/2.0/TCP 127.0.1.1:5060;branch=z9hG4bK-3002-1-0;rport=34680;received=192.168.88.88 CSeq: 1 SUBSCRIBE Call-ID: 1-3002(a)127.0.1.1 From: <sip:c.vella@albourne.com>;tag=1 To: <sip:provisioning@albourne.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-1030 Expires: 3600 Contact: <sip:192.168.88.85:5060;transport=tcp> --- End debug --- I suspect I am not understanding this correctly. Is there a proper way around this? I wonder if I am wrong to think that textops Module manipulates the actual request message? Thank you! Regards, -- Chris Vella Albourne Partners (Canada) Limited

8 years, 8 months

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 March 2016