sr-users

sr-users@lists.kamailio.org

20 participants
37472 discussions

why is while loop not terminated?
by jh＠tutpro.com 24 Mar '10

24 Mar '10

i'm in the process of enhancing enum mudule enum_query, so that suffic param can be given in a pseudo variable. before committing to git, i tested if the new version is working correctly, and for that purpose wrote this kind of route: route [PERFORM_ENUM_QUERIES] { xlog("L_INFO", "suffix_list = <$var(suffix_list)>\n"); $var(i) = 0; $var(domain) = $(var(domain_list){s.select,0,,}); while ($var(domain) != "") { xlog("L_INFO", "Query $var(i) for $var(domain)\n"); if (enum_query("$var(domain)")) { xlog("L_INFO", "Return success!\n"); return(1); }; $var(i) = $var(i) + 1; $var(domain) = $(var(domain_list){s.select,$var(i),,}); }; return(-1); } looks like the enhanced enum_query works as expected, but the while loop is not terminating by the return(1) statement (see below). i'm puzzled. have i done some stupid mistake that i cannot see? -- juha Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: suffix_list = <e164.test.fi.> Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: enum [enum.c:724]: Got suffix <e164.test.fi.> Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Return success! Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: ERROR: <core> [action.c:1144]: ERROR: runaway while (1342, 25): more then 100 loops

1 1

what is $name?
by jh＠tutpro.com 24 Mar '10

24 Mar '10

i made a typo in script and wrote $domain instead of $var(domain). then i started sip router and didn't get any error messages. what does $name stand for when $name is not any of the ones listed in SIP Router Pseudo-Variables document? -- juha

2 2

Re: [Kamailio-Users] Establish Call on different network.
by john david 24 Mar '10

24 Mar '10

Dear all, started rtpproxy, enabled nat in cfg file. but still there is only connection between two client from different network, unable to get audio if used kamailio server. something more that i should add, except rtpproxy and enabling nathelper from cfg file. or else is there any way to debug where it get stuck. Thanks in advance.

2 1

[Kamailio-Users] need help on xilte
by false 24 Mar '10

24 Mar '10

Hi all i use kamailio sip proxy, its version is: [root@localhost kamailio]# /opt/sbin/kamctl fifo version Server:: kamailio (3.0.1 (i386/linux)) i use 2 xlite softphones to register to sip proxy and register successfull and use xlite make call to another xlite softphone and get 488 Not Accept Here all sip proxy, xlite softphones in the same LAN please help to fix in the sip proxy that doesnt check the SDP Thank you Ha` and the debug log: DEBUG: tm [t_reply.c:1059]: ->>>>>>>>> T_code=100, new_code=488 DEBUG: tm [t_lookup.c:1080]: DEBUG: t_check_msg: msg id=2 global id=2 T start=0xb60ae9f0 DEBUG: tm [t_lookup.c:1152]: DEBUG: t_check_msg: T already found! DEBUG: tm [t_reply.c:1549]: DEBUG: relay_reply: branch=0, save=0, relay=0 DEBUG: <core> [msg_translator.c:1876]: old size: 500, new size: 440 DEBUG: <core> [msg_translator.c:1894]: build_res_from_sip_res: copied siz ontent-Length: 0ull "SDP: Incompatible media format: no common codec."19-1--d87543-;rport=51020 "Tốt hơn, thoáng gọn hơn, nhanh hơn -Trải nghiệm Yahoo! Mail mới hôm nay! http://vn.mail.yahoo.com"

2 1

[Kamailio-Users] need help on ACC modules
by false 24 Mar '10

24 Mar '10

Hi all i use the kamailio version 3.0.1 and try to understand ACC module and found the tutorial http://www.voice-system.ro/docs/uac/ does it still work with kamailio 3.0.1, could you please present a working config with kamailio 3.0.1 How to work with the uac-create.sql, the sip account from VOIP provider username: x.x.x.x password: x.x.x.x outbound proxy: x.x.x.x domain name: sbc.net expired time : 3600s what info should i insert into database l_uuid: l_username: l_domain: r_username: r_domain: realm: auth_username: auth_password: auth_proxy: expires: when i start the sip server with acc module and got error and the config parameter: modparam("uac", "reg_db_url","mysql://openser:openserrw@localhost/openser") DEBUG: <core> [sr_module.c:617]: find_param_export: parameter <reg_db_url> not found in module <uac> ERROR: <core> [modparam.c:143]: set_mod_param_regex: parameter <reg_db_url> not found in module <uac> ERROR: <core> [modparam.c:143]: set_mod_param_regex: parameter <reg_db_url> not found in module <uac> Thank you Phần mềm chống virus và adware miễn phí đã có cùng Yahoo! Thanh Công Cụ. Tải về ngay! Tải ngay. http://vn.toolbar.yahoo.com/

2 1

[Kamailio-Users] Kamailio+asterisk
by Marcus Kvarsell 24 Mar '10

24 Mar '10

Hello everyone! If i want to have Kamailio as front-end and 3 asterisk as back-end. Sip-registration should be done by Kamailio, and usage of meet-me rooms by asterisk-servers which should be load-balanced by Kamailio. is it possible of creating outgoing call with Kamailio and when call is answered, realtime route this call dynamically based on some information coming from unixODBC source, to a meet-me room? any help appreciated!! Regards / Marcus

3 2

[Serusers] Check out my photos on Facebook
by Sarfaraz Chougule 24 Mar '10

24 Mar '10

Hi, I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. Thanks, Sarfaraz To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=520931674&k=54EUZ6Q3QT2BXJMFYDYVPVWZWUKJ64&r Already have an account? Add this email address to your account http://www.facebook.com/n/?merge_accounts.php&e=serusers%40iptel.org&c=71a7… was invited to join Facebook by Sarfaraz Chougule. If you do not wish to receive this type of email from Facebook in the future, please click on the link below to unsubscribe. http://www.facebook.com/o.php?k=679489&u=557896866&mid=213a1b7G2140d4a2G0G8 Facebook's offices are located at 1601 S. California Ave., Palo Alto, CA 94304.

1 0

[Kamailio-Users] Establish Call on different network.
by john david 24 Mar '10

24 Mar '10

Hello all, I am using kamailio server, it works properly when connection is in between two clients between same lan. But when I connecting between two client who are on different proxy and behind different NAT, call has been established but no audio or video get transferred. What are the changed i suppose to do, or any parameters should get enabled while compilation, Thanks in advance.

2 1

[Kamailio-Users] dinner in berlin, thursday, march 25, 19:00
by Daniel-Constantin Mierla 23 Mar '10

23 Mar '10

Hello, couple of developers from SIP and VoIP area are in Berlin this week and plan to meet for dinner and beer Thursday, March 25, 19:00 at the traditional place by now: Lemke Brauhaus Luisenplatz 1, 10585 Berlin Across the corner with Charlottenburg Castle http://www.brauhaus-lemke.com/index.php?area=4 If you are around, just pop up. You can write me if you need more details about how to get there. Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

1 0

[Kamailio-Users] Shared memory
by Bruno Machado 23 Mar '10

23 Mar '10

I have some questions regarding the shared memory. I'm working with the version 1.5.2 and its environment is quite simple. It does'nt storage any informations in the memory, like dialplan, contacts of subscribers, carrierroute, LCR and etc. The only purpose of this server is being a redirect server. Some calls have several possible destinations, reaching easily 12 contacts. The config.h's constant MAX_BRANCHES is set in 12, the default number. Ok. Like I said, almost the requests have more than 12 possible contacts. When it happens, Kamailio logs these messages: /usr/local/kamailio-1.5.2/sbin/kamailio[26188]: ERROR:core:append_branch: max nr of branches exceeded /usr/local/kamailio-1.5.2/sbin/kamailio[26188]: ERROR:pv:pv_set_branch: append_branch action failed Ok. It is not a problem. It is an error but it does not stop the system. The SIP messages still flowing normally. The server works for several days, 24/7 without functional errors, receiving five hundred thousand requests per day . But, usually at the weekends and the clock tells 2:30 am, the company's cell phone rings bringing a message: 'the system is down'. Kamailio shows: /usr/local/kamailio-1.5.2/sbin/kamailio[25492]: ERROR:core:add_avp: no more shm mem /usr/local/kamailio-1.5.2/sbin/kamailio[25492]: ERROR:exec:exec_avp: unable to add avp Kamailio stills running but it is not possible to route any request. All the new incoming calls generates the same error: 'no more shm mem'. I changed the size of shared memory, running Kamailio with '-m 64', but the server stopped again after some days. I see the options: - increase MAX_BRANCHES - increase again 'm' parameter (but it will just add more some days in the running time) - reduce the maximum number of contacts to 11 of the script that returns them to Kamailio So, my doubts are: - is it possible to have a memory leak when the message "max nr of branches exceeded" is showed? - changing '-m parameter' to a higher value, like 256, could affect the performance? tks friends bruno machado ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com

2 4

Jump to page:

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