sr-users

sr-users@lists.kamailio.org

22 participants
37573 discussions

[Users] openser and SEMS
by Helmut Kuper 12 Jun '07

12 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I changed a few modules (groups, ringtone, voicebox, ...) of openser and sems to my needs. Maybe the changes are of interest for you. So what's the official way to send the modifications back to openser and sems ? regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGblo+4tZeNddg3dwRAt7eAJ48RKKYuF0pxaG6atZAO2rbYXkbygCeIGDr YiEWSevCPxfZoWUYWVXN0dY= =aWGn -----END PGP SIGNATURE-----

3 2

[Users] Re: Memory issues
by Papadopoulos Georgios 12 Jun '07

12 Jun '07

Hello, We have exactly the same problem. Openser after a few hours starts loging "out of memory" errors and soon after that it cannot process any messages. I am using 1.2 branch from SVN and the last export that I got was at the begining of June, the revision number was 2333. Today I was able to catch the problem while it is happening and I did a memory dump on the process that run out of memory (process 4197). ps shows that this process is a receiver with id=1 and child=0. I have not restarted the server yet, but pretty soon I will have to restart because more processes will run out of memory. If there is some additional information (statistics, ngrep etc) that I could gather while the server is still running, please let me know. I don't have quick access to a public ftp site, so if someone can take a look at the log file and the memory dump, please let me know and I will email it (1MB). thank you for any help. George Date: Mon, 11 Jun 2007 17:52:08 +0200 From: Klaus Darilion <klaus.mailinglists(a)pernau.at> Subject: Re: [Users] Memory issues To: Christian <mailing-lists(a)switzernet.com> Cc: users(a)openser.org Message-ID: <466D6FA8.9010201(a)pernau.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Christian wrote: > Thank you Bogdan, > > For the moment I am not very sure to switch to SVN branch (this is a > production server, so every minor bug can be dramatic) SVN != unstable SVN is the code repository. In the repository there are different branches. E.g. there is 1.1: openser 1.1 branch 1.2: openser 1.2 branch trunk: openser development branch Thus, you should update to the 1.2 branch from SVN. This is the currents table release with all bugfixes: > But I will at least upgrade to 1.2.1 asap, and see if the issue gets > solved. 1.2.1 is a snapshot taken from 1.2 branch regards klaus > The main issue here is that the memory leak doesn't crash openser, but > puts it in a state where messages are accepted but not relayed. > Shouldn't it rather send a SIP error reply (500 I guess), so that > handover on other servers gets properly handled? > > Regards, > Christian > > > > Bogdan-Andrei Iancu a ιcrit : >> it looks like PKG memory problem. >> Christian, try to update to the latest 1.2 version from SVN and see >> if the problem disappears - there were some pkg mem leak fixed >> since the 1.2 release. >> >> regards, >> bogdan >> >> >> Klaus Darilion wrote: >>> http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory <http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory> >>> >>> Make sure to use newest 1.2 (make a SVN checkout of /branches/1.2/ ) >>> >>> regards >>> klaus >>> >>> Christian wrote: >>>> Hi All, >>>> >>>> I have a recurrent memory problem with openser 1.2.0. In this case >>>> it only acts as a SIP router. No registration, accounting etc. and >>>> only approx. 20 simultaneous calls. >>>> >>>> Here is the problem: everything works fine (calls from/to PSTN >>>> through different SIP servers), but after a few days, "out of >>>> memory" errors start to occur. After this, calls don't work >>>> anymore, even if openser continues to run. >>>> >>>> Here is a part of the log, showing the first errors: >>>> >>>> Jun 5 17:25:43 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_res: out of mem Jun 5 17:25:43 localhost >>>> SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer >>>> Jun 5 17:25:43 localhost SER[27772]: ERROR: via_builder: out of >>>> memory Jun 5 17:25:43 localhost SER[27772]: ERROR: build_local: no >>>> via header got from builder Jun 5 17:25:43 localhost SER[27772]: >>>> ERROR: attempt to build a CANCEL failed Jun 5 17:25:50 localhost >>>> SER[27772]: ERROR: >>>> build_res_buf_from_sip_res: out of mem Jun 5 17:25:50 localhost >>>> SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer >>>> Jun 5 17:25:50 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_req: out of memory ; needs 410 Jun 5 >>>> 17:26:11 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_res: out of mem Jun 5 17:26:11 localhost >>>> SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer >>>> Jun 5 17:26:11 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_req: out of memory ; needs 404 Jun 5 >>>> 17:26:25 localhost SER[27772]: eval_elem: no more memory Jun 5 >>>> 17:26:25 localhost SER[27772]: do_assign: no value in right >>>> expression Jun 5 17:26:25 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_res: out of mem Jun 5 17:26:25 localhost >>>> SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer >>>> Jun 5 17:26:25 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_req: out of memory ; needs 420 Jun 5 >>>> 17:26:25 localhost SER[27771]: ERROR:forward_reply: no 2nd via >>>> found in reply Jun 5 17:26:31 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_res: out of mem Jun 5 17:26:31 localhost >>>> SER[27772]: ERROR:forward_reply: building rpl from req failed Jun >>>> 5 17:26:33 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_res: out of mem Jun 5 17:26:33 localhost >>>> SER[27772]: ERROR:forward_reply: building rpl from req failed Jun >>>> 5 17:26:38 localhost SER[27772]: ERROR: insert_new_lump_after: >>>> out of memory >>>> Jun 5 17:26:38 localhost SER[27772]: ERROR: insert_new_lump_before: >>>> out of memory >>>> Jun 5 17:26:38 localhost SER[27772]: insert_RR(): Error while >>>> inserting conditional lump Jun 5 17:26:38 localhost SER[27772]: >>>> ERROR: subst_str: mem. >>>> allocation error (res->s) >>>> Jun 5 17:26:38 localhost SER[27772]: ERROR: do_action: memory >>>> allocation failure Jun 5 17:26:38 localhost SER[27772]: ERROR: >>>> build_res_buf_from_sip_req: out of memory ; needs 375 Jun 5 >>>> 17:26:38 localhost SER[27772]: ERROR: mk_proxy: memory allocation >>>> failure Jun 5 17:26:38 localhost SER[27772]: >>>> ERROR:tm:t_forward_nonack: >>>> failure to add branches >>>> >>>> At this point, similar errors continue to appear and the only way >>>> to recover is to restart openser. >>>> Nothing unusual seems to cause the initial error. The output of >>>> "top" appears to be fine after the "crash", and there is still >>>> plenty free memory on the server. >>>> >>>> >>>> Could anybody give me some hints on how to solve the problem? I >>>> suspect a portion of the config file where the record-route headers >>>> are split on multiple lines (for compatibility issues with another >>>> SIP proxy). It's the only place where variables are used. You can >>>> find it here: >>>> >>>> http://switzernet.com/people/christian-lathion/files/070605-openser <http://switzernet.com/people/christian-lathion/files/070605-openser> >>>> -config-part.txt >>>> >>>> >>>> Otherwise the config file is quite usual, with basic processing and >>>> routing of SIP packets. >>>> >>>> Regards, >>>> Christian >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)openser.org >>>> http://openser.org/cgi-bin/mailman/listinfo/users <http://openser.org/cgi-bin/mailman/listinfo/users> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)openser.org >>> http://openser.org/cgi-bin/mailman/listinfo/users <http://openser.org/cgi-bin/mailman/listinfo/users> >>> >> > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users <http://openser.org/cgi-bin/mailman/listinfo/users> Disclaimer The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.

1 0

[Users] Error: udp_send
by Josh Tressler 11 Jun '07

11 Jun '07

All: I am receiving the following error below and I'm unable to determine the cause. I am new to OpenSER, so if it is something obvious, please let me know. This is currently installed on a CentOS 5 box with mysql 5. My configuration file is listed below. This happens as soon as I try to place a call that should get sent to asterisk running on the same machine. ====================== Jun 11 14:38:00 poll /usr/local/sbin/openser[13403]: START ROUTE 3 Jun 11 14:38:00 poll /usr/local/sbin/openser[13403]: START ROUTE 1 Jun 11 14:38:00 poll /usr/local/sbin/openser[13403]: ERROR: udp_send: sendto(sock,0xb60b0d00,899,0,0xb60af0c4,16): Operation not permitted(1) Jun 11 14:38:00 poll /usr/local/sbin/openser[13403]: msg_send: ERROR: udp_send failed Jun 11 14:38:00 poll /usr/local/sbin/openser[13403]: ERROR:tm:t_forward_nonack: sending request failed ====================== Thanks, Josh ====================== # ----------- global configuration parameters ------------------------ debug=3 log_facility=LOG_LOCAL7 fork=yes log_stderror=no children=5 check_via=yes dns=no rev_dns=no #dns_use_search_list=no #dns_servers_no=2 disable_dns_blacklist=true listen=X.X.X.X:5060 alias="cacti.dev.lcl" alias="X.X.X.X" # ------------------ module loading ---------------------------------- #set module path mpath="/usr/local/lib/openser/modules/" loadmodule "mysql.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "xlog.so" loadmodule "auth.so" loadmodule "auth_db.so" loadmodule "domain.so" loadmodule "acc.so" loadmodule "uri_db.so" loadmodule "alias_db.so" loadmodule "avpops.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- modparam("usrloc", "db_mode", 2) modparam("usrloc", "timer_interval", 3) # -- auth params -- modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") # -- define db connection for other modules -- modparam("acc|auth_db|avpops|group|speeddial|uri_db|usrloc|domain|alias_ db", "db_url", "mysql://USERNAME:PASSWORD@localhost/openser") modparam("mysql", "auto_reconnect", 1) modparam("mysql", "ping_interval", 300) # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # -- acc params -- modparam("acc", "log_level", 1) modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 3) # -- tm params -- modparam("tm", "fr_timer", 35) modparam("tm", "fr_inv_timer", 30) modparam("tm", "noisy_ctimer", 1) # -- avp params -- modparam("avpops", "avp_table", "usr_preferences") # ------------------------- request routing logic ------------------- # main routing logic route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; if (!method=="REGISTER") record_route(); if (loose_route()) { append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (!uri==myself) { append_hf("P-hint: outbound\r\n"); route(1); }; if(method!="REGISTER" && method!="ACK") { setflag(1); }; #do not send to voicemail if BYE or CANCEL #is used to end call before user pickup or timeout if(method=="CANCEL" || method=="BYE") { setflag(10); }; #if (uri==myself) { if (method=="ACK") { route(1); exit; } if (method=="CANCEL") { route(1); exit; } if (method=="INVITE") { route(3); exit; } else if (method=="REGISTER") { route(2); exit; }; #} route(1); } route[1] { xlog("L_INFO", "START ROUTE 1\n"); if (!t_relay()) { sl_reply_error(); }; } route[2] { sl_send_reply("100", "Trying"); if (!www_authorize("","subscriber")) { www_challenge("","0"); exit; } if (!check_to()) { sl_send_reply("403", "Spoofed To-URI Detected"); exit; } consume_credentials(); if (!save("location")) { sl_reply_error(); } } route[3] { xlog("L_INFO", "START ROUTE 3\n"); if (!is_uri_host_local()) { route(1); return; }; if (!lookup("location")) { route(4); return; }; t_on_failure("1"); route(1); } route[4] { xlog("L_INFO", "ROUTE BLOCK 4\n"); if (!proxy_authorize("cacti.dev.lcl","subscriber")) { proxy_challenge("cacti.dev.lcl","0"); return; } else if (!check_from()) { sl_send_reply("403", "Use From=ID"); return; }; xlog("L_INFO", "Call OUT\n"); rewritehostport("127.0.0.1:5065"); # append_branch(); t_on_failure("1"); route(1); } failure_route[1] { xlog("L_INFO", "FAILURE ROUTE 1\n"); if (t_check_status("487")) { return; }; } ======================

1 0

Re: [Serusers] need help!
by SIP 11 Jun '07

11 Jun '07

http://www.iptel.org/faq/why_does_ser_fail_to_start_with_an_error_load_modu… N. Mukesh Prajapati wrote: > i m getting following error: > > 0(14333) ERROR: load_module: could not open module > </usr/lib/ser/modules/mysql.so>: libmysqlclient.so.12: cannot open > shared object file: No such file or directory > 0(14333) parse error (15,13-14): failed to load module > ERROR: bad config file (1 errors) > > > */SIP <sip(a)arcdiv.com>/* wrote: > > What's the EXACT error when you start SER? > > N. > > > > Mukesh Prajapati wrote: > > > > hi, > > > > I m trying to add my-sql support to my SER. i install SER with .deb > > package. > > I uncommented the lines regarding my-sql.so module.... > > now when i try to start server it's giving error like "bad > > configuration file" > > can anybody halp me in this regard? > > > > thnx > > mukesh > > > > > ------------------------------------------------------------------------ > > We won't tell. Get more on shows you hate to love > > > > (and love to hate): Yahoo! TV's Guilty Pleasures list. > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > ------------------------------------------------------------------------ > Pinpoint customers > <http://us.rd.yahoo.com/evt=48250/*http://searchmarketing.yahoo.com/arp/spon…>who > are looking for what you sell.

1 0

[Users] Memory issues
by Christian 11 Jun '07

11 Jun '07

Hi All, I have a recurrent memory problem with openser 1.2.0. In this case it only acts as a SIP router. No registration, accounting etc. and only approx. 20 simultaneous calls. Here is the problem: everything works fine (calls from/to PSTN through different SIP servers), but after a few days, "out of memory" errors start to occur. After this, calls don't work anymore, even if openser continues to run. Here is a part of the log, showing the first errors: Jun 5 17:25:43 localhost SER[27772]: ERROR: build_res_buf_from_sip_res: out of mem Jun 5 17:25:43 localhost SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer Jun 5 17:25:43 localhost SER[27772]: ERROR: via_builder: out of memory Jun 5 17:25:43 localhost SER[27772]: ERROR: build_local: no via header got from builder Jun 5 17:25:43 localhost SER[27772]: ERROR: attempt to build a CANCEL failed Jun 5 17:25:50 localhost SER[27772]: ERROR: build_res_buf_from_sip_res: out of mem Jun 5 17:25:50 localhost SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer Jun 5 17:25:50 localhost SER[27772]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 410 Jun 5 17:26:11 localhost SER[27772]: ERROR: build_res_buf_from_sip_res: out of mem Jun 5 17:26:11 localhost SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer Jun 5 17:26:11 localhost SER[27772]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 404 Jun 5 17:26:25 localhost SER[27772]: eval_elem: no more memory Jun 5 17:26:25 localhost SER[27772]: do_assign: no value in right expression Jun 5 17:26:25 localhost SER[27772]: ERROR: build_res_buf_from_sip_res: out of mem Jun 5 17:26:25 localhost SER[27772]: ERROR:tm:relay_reply: no mem for outbound reply buffer Jun 5 17:26:25 localhost SER[27772]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 420 Jun 5 17:26:25 localhost SER[27771]: ERROR:forward_reply: no 2nd via found in reply Jun 5 17:26:31 localhost SER[27772]: ERROR: build_res_buf_from_sip_res: out of mem Jun 5 17:26:31 localhost SER[27772]: ERROR:forward_reply: building rpl from req failed Jun 5 17:26:33 localhost SER[27772]: ERROR: build_res_buf_from_sip_res: out of mem Jun 5 17:26:33 localhost SER[27772]: ERROR:forward_reply: building rpl from req failed Jun 5 17:26:38 localhost SER[27772]: ERROR: insert_new_lump_after: out of memory Jun 5 17:26:38 localhost SER[27772]: ERROR: insert_new_lump_before: out of memory Jun 5 17:26:38 localhost SER[27772]: insert_RR(): Error while inserting conditional lump Jun 5 17:26:38 localhost SER[27772]: ERROR: subst_str: mem. allocation error (res->s) Jun 5 17:26:38 localhost SER[27772]: ERROR: do_action: memory allocation failure Jun 5 17:26:38 localhost SER[27772]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 375 Jun 5 17:26:38 localhost SER[27772]: ERROR: mk_proxy: memory allocation failure Jun 5 17:26:38 localhost SER[27772]: ERROR:tm:t_forward_nonack: failure to add branches At this point, similar errors continue to appear and the only way to recover is to restart openser. Nothing unusual seems to cause the initial error. The output of "top" appears to be fine after the "crash", and there is still plenty free memory on the server. Could anybody give me some hints on how to solve the problem? I suspect a portion of the config file where the record-route headers are split on multiple lines (for compatibility issues with another SIP proxy). It's the only place where variables are used. You can find it here: http://switzernet.com/people/christian-lathion/files/070605-openser-config-… Otherwise the config file is quite usual, with basic processing and routing of SIP packets. Regards, Christian

3 4

[Users] Interaction Presence Agent - Presence User Agent
by Schumann Sebastian 11 Jun '07

11 Jun '07

Dear all, I have a question for understanding: I have implemented one OpenSER as Registrar and one OpenSER as Presence Agent plus XCAP Server 1.0.0. This is all working so far with newest SVN Release (Big Thanks to Ovidiu and Anca for the hint) of OpenSER. Now I want to deploy a Web-Front-End for user interaction with the Presence Core, because not all clients used are SIMPLE capable. User of non-capable devices should be able to just login and change their presence state. They do not necessarily have to be registered at the registrar, why PUA+ pua_usrloc on registrar side is no choice. I was thinking about another OpenSER deployed as PUA plus the pua_mi module for a solution. It gets commands from Web-Frontend via PHP, forwarded to the FIFO with pua_mi module. The problem I have now is that the messages are sent just once. Means a user changes his presence state, PUA sends a PUBLISH to PA but after the expiry the user appears to be offline. Is there any possiblitiy to let the PUA send messages constantly, when the user selects online - means all the time until offline is selected? I was thinking about many possiblities (cronjob or shellscript running all the time during online time and sending data to FIFO) but they are more or less just work-arounds. Best regards Sebastian Sebastian Schumann Diploma Student Architecture and Design Department Slovak Telekom, a. s. T-Com, Operations Unit Production and Service Division Innovations and Enterprise Solution Subunit Address: Namestie Slobody 6, 817 62 Bratislava, Slovakia Office: Room 232, Jarabinkova 1, 821 09 Bratislava, Slovakia +421 910 643010 (mobile) sebastian.schumann(a)t-com.sk http://www.t-com.sk

2 2

[Serusers] problem with MESSAGE and un-REGISTER
by KUMAR 11 Jun '07

11 Jun '07

hi all, I've started using SER 2.0 rc1 and am having a bit of problems with UA behind NAT. I'm using Windows Messenger 5.1 as the UA. Everything works fine when both UAs are not behind NAT. But when I place one of the UAs behind NAT, then, here's what happens, in this order UA Behind Nat ----------MESSAGE------>UA outside NAT..............ok UA outside NAT-----------MESSAGE------->UA behind NAT.............OK UA behind NAT------------MESSAGE------->UA outside NAT.............message is stored by msilo module and sent after some time. The log shows: MSILO: the downstream UA doesn't support MESSAGEs Notice that this only happens once a message from outside of NAT is sent to UA inside NAT. I am using RTP Proxy for NAT solution which is on the same system as SER. Moreover, I also cannot signout using the Windows Messenger. However, when I tested using XLite, None of the above mentioned problems arose. Can anyone please suggest me as to where the problem might be. The ser.cfg that I'm using is the one from the iptel site, the one with NAT & RTPproxy. I am also attaching the ser.cfg. Thank you in advance. Kumar

2 7

[Serusers] Presence pa module - no NOTIFY messages sent
by tzieleniewski 11 Jun '07

11 Jun '07

Hi, I am using SER rel_2_0_0. I am trying to set up a presence server as a simple PA. I am using xlite UA and when UA registers and subscribes to a particular user presence Event SER doesn't sent a NOTIFY according to the 'time_interval' module parameter. It only responses with the 'immediate NOTIFY' with the closed status tuple. According to my configuration SER should sent a NOTIFY every 15 seconds and it doesn't do it at all. I kindly ask for your feedback. Below I attached my module configuration and messages exchanged with UA. # -- pa params -- modparam("pa", "default_expires",300) modparam("pa", "max_subscription_expiration", 3600) modparam("pa", "max_publish_expiration", 3600) modparam("pa", "use_db", 1) modparam("pa", "use_callbacks", 1) modparam("pa", "watcherinfo_notify", 0) modparam("pa", "use_offline_winfo", 0) modparam("pa", "offline_winfo_expiration", 259200) modparam("pa", "auth", "none") modparam("pa", "winfo_auth", "implicit") modparam("pa", "pres_rules_file", "presence-rules.xml") modparam("pa", "ignore_408_on_notify", 0) modparam("pa", "timer_interval", 15) modparam("pa", "default_priority_percentage", 0) modparam("pa", "auth_rules_refresh_time", 300) modparam("pa", "async_auth_queries", 1) modparam("pa", "max_auth_requests_per_tick", 600) # U 2007/06/04 16:52:16.423720 192.168.0.229:7060 -> 192.168.0.165:5160 SUBSCRIBE sip:sen@voip.rd.touk.pl SIP/2.0. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport. Max-Forwards: 70. Contact: <sip:hulk@192.168.0.229:7060>. To: <sip:sen@voip.rd.touk.pl>. From: "hulk(a)voip.rd.touk.pl"<sip:hulk@voip.rd.touk.pl>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Accept: multipart/related, application/rlmi+xml, application/pidf+xml. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Event: presence. Content-Length: 0. . # U 2007/06/04 16:52:16.471312 192.168.0.165:5160 -> 192.168.0.229:7060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.229:7060;branch=z9hG4bK-d87543-da69e92af464fa08-1--d87543-;rport=7060. To: <sip:sen@voip.rd.touk.pl>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. From: "hulk(a)voip.rd.touk.pl"<sip:hulk@voip.rd.touk.pl>;tag=8e1a6d2f. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 1 SUBSCRIBE. Expires: 300. Contact: <sip:192.168.0.165:5160>. Server: Sip EXpress router (2.0.0-rc2 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5160 "Noisy feedback tells: pid=25995 req_src_ip=192.168.0.229 req_src_port=7060 in_uri=sip:sen@voip.rd.touk.pl out_uri=sip:sen@voip.rd.touk.pl via_cnt==1". . # U 2007/06/04 16:52:16.471328 192.168.0.165:5160 -> 192.168.0.229:7060 NOTIFY sip:hulk@192.168.0.229:7060 SIP/2.0. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. To: "hulk(a)voip.rd.touk.pl"<sip:hulk@voip.rd.touk.pl>;tag=8e1a6d2f. From: <sip:sen@voip.rd.touk.pl>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. CSeq: 10 NOTIFY. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. Content-Length: 208. User-Agent: Sip EXpress router(2.0.0-rc2 (x86_64/linux)). Max-Forwards: 70. Event: presence. Content-Type: application/pidf+xml;charset="UTF-8". Contact: <sip:192.168.0.165:5160>. Subscription-State: active;expires=300. . <?xml version="1.0" encoding="UTF-8"?>. <presence xmlns="urn:ietf:params:xml:ns:pidf" entity="pres:sen@voip.rd.touk.pl">. .<tuple id="none">. ..<status><basic>closed</basic></status>. .</tuple>. </presence>. # U 2007/06/04 16:52:16.572189 192.168.0.229:7060 -> 192.168.0.165:5160 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.0.165:5160;branch=z9hG4bK967b.6e9cb884.0. Contact: <sip:hulk@192.168.0.229:7060>. To: "hulk(a)voip.rd.touk.pl"<sip:hulk@voip.rd.touk.pl>;tag=8e1a6d2f. From: <sip:sen@voip.rd.touk.pl>;tag=5b4167208bb1319f0333e26fe8df2283-d4d1. Call-ID: MGYxYTg5ZjEyYWM1NzA4NjgwOGRlODNjNTNiZmZkNmQ.. CSeq: 10 NOTIFY. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . . Cheers TOmasz

2 9

[Users] Insert a Header into ACK message
by fancy 11 Jun '07

11 Jun '07

Dear All: I've tried many methods to add Max-Forwarsd header into ACK message (message 8), all methods I tried were fail. According to RFC 3261 8.1.1.6, Max-Forwards must exist in this ACK message. Can anyone tell me how to add a header into ACK message? Thank you very much. UA11 : NUT(Proxy 1) : UA12 | : | : | |-------:------->| : | 1. INVITE |<------:--------| : | 2. 407 |-------:------->| : | 3. ACK | : | : | |-------:------->| : | 4. INVITE | : |-------:------->| 5. INVITE |<------:--------| : | 6. 100 | : | : | | : |<------:--------| 7. 486 (Busy Here) | : | : | | : |-------:------->| 8. ACK | : | : | |<------:--------| : | 9. 486 | : | : | |-------:------->| : |10. ACK | : | : | Best Regards, Fangyu Ling

1 0

[Serusers] problems with ser.cfg
by Kirk McCalla 08 Jun '07

08 Jun '07

Hello I am new to ser. I just loaded my ser and mysql and they are up and running. I am using CENTOS for my operating system. I am trying to configure the ser.cfg file and I keep getting this error. ERROR: load_module: could not open module </usr/lib/ser/modules/mysql.so>: /usr/lib/libmysqlclient.so.14: cannot restore segment prot after reloc: Permission denied Now I have libmysqlclient.so.14 loaded and mysql.so is also loaded [root@localhost lib]# find libmysqlclient.so.14 libmysqlclient.so.14 [root@localhost lib]# I cant seee where I could be going wrong here. I load just fine when I dont have the loadmodule "/usr/lib/ser/modules/mysql.so" uncomented. This is my config file # $Id: auth-mysql.cfg 46 2006-01-25 04:21:30Z /CN=Paul Hazlett/emailAddress=paul(a)onsip.org $ debug=3 fork=no log_stderror=yes sten=192.168.0.102 # put your server IP address here port=5060 children=4 dns=no rev_dns=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser" loadmodule "/usr/lib/ser/modules/mysql.so" loadmodule "/usr/lib/ser/modules/sl.so" loadmodule "/usr/lib/ser/modules/tm.so" loadmodule "/usr/lib/ser/modules/rr.so" loadmodule "/usr/lib/ser/modules/maxfwd.so" loadmodule "/usr/lib/ser/modules/usrloc.so" loadmodule "/usr/lib/ser/modules/registrar.so" loadmodule "/usr/lib/ser/modules/uri_db.so" loadmodule "/usr/lib/ser/modules/auth.so" loadmodule "/usr/lib/ser/modules/auth_db.so" modparam("auth_db|uri_db|usrloc", "db_url", "mysql://ser:heslo@localhost /ser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("usrloc", "db_mode", 2) modparam("rr", "enable_full_lr", 1) route { # ----------------------------------------------------------------- # Sanity Check Section # ----------------------------------------------------------------- if (!mf_process_maxfwd_header("10")) { sl_send_reply("483", "Too Many Hops"); break; }; if (msg:len > max_len) { sl_send_reply("513", "Message Overflow"); break; }; # ----------------------------------------------------------------- # Record Route Section # ----------------------------------------------------------------- if (method!="REGISTER") { record_route(); }; # ----------------------------------------------------------------- # Loose Route Section # ----------------------------------------------------------------- if (loose_route()) { route(1); break; }; # ----------------------------------------------------------------- # Call Type Processing Section # ----------------------------------------------------------------- if (uri!=myself) { route(1); break; }; if (method=="ACK") { route(1); break; } else if (method=="INVITE") { route(3); break; } else if (method=="REGISTER") { route(2); break; }; lookup("aliases"); if (uri!=myself) { route(1); break; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); break; }; route(1); } route[1] { # ----------------------------------------------------------------- # Default Message Handler # ----------------------------------------------------------------- if (!t_relay()) { sl_reply_error(); }; } route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ---------------------------------------------------------------- sl_send_reply("100", "Trying"); if (!www_authorize("","subscriber")) { www_challenge("","0"); break; }; if (!check_to()) { sl_send_reply("401", "Unauthorized"); break; }; consume_credentials(); if (!save("location")) { sl_reply_error(); }; } route[3] { # ----------------------------------------------------------------- # INVITE Message Handler # ----------------------------------------------------------------- if (!proxy_authorize("","subscriber")) { proxy_challenge("","0"); break; } else if (!check_from()) { sl_send_reply("403", "Use From=ID"); break; }; consume_credentials(); lookup("aliases"); if (uri!=myself) { route(1); break; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); break; }; route(1); }

3 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