[OpenSIPS-Users] Changing IP's and Data Centers
Hi, We currently have a set up in one data center with OpenSipS listening on IP 200.200.200.200. In the new data center we have the same set up on IP: 201.201.201.201. We want to have a grace period for customers. Is there any way that we can sent 200.200.200.200 to forward all it's traffic to 201.201.201.201 ? I tried to do it in the past (forgot what routing logic I used) and it did not work with try to authenticate a user. Any pointers on how to configure something like this ? Thanks. Dovid ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] nathelper memory error
Bogdan, We have on average 2500-2600 registerd users. Once it goes over 2800-2900 we start seeing the error. Regards, Dovid - Original Message - From: Bogdan-Andrei Iancu To: users@lists.opensips.org Sent: Friday, June 24, 2011 17:43 Subject: Re: [OpenSIPS-Users] nathelper memory error Hi Dovid, db_mode 3 has some inefficient way of doing things, like NAT pinging - in order to do it, it has to query in DB for all nated records - probably in your case, you have too many registered users for a single query to handle . How many records do you actually have ? Regards, Bogdan On 06/15/2011 05:53 AM, Dovid Bender wrote: Hi, We are using OpenSIPs (opensips-1.4.3-tls yes I know we should upgrade...) and it seems that ever since we set db_mode to 3 we started getting the erros below: Jun 14 20:12:14 peter /sbin/opensips[4434]: ERROR:db_mysql:db_mysql_convert_rows: no private memory left Jun 14 20:12:15 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:16 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:20 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:51 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory We have fork set to 24 and modparam( usrloc, fetch_rows, 500 ). TIA. Dovid -- Bogdan-Andrei Iancu OpenSIPS solutions and know-how -- ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] ICE How-To
Hi Saul, After enabling ICE for the account it worked. Thanks, Liviu From: Saúl Ibarra Corretgé s...@ag-projects.com To: OpenSIPS users mailling list users@lists.opensips.org Sent: Fri, June 24, 2011 6:06:21 PM Subject: Re: [OpenSIPS-Users] ICE How-To Hi, On Jun 24, 2011, at 5:01 PM, Barsan Liviu wrote: Hello, We were doing as suggested below and we got: 2011-06-24 17:50:17 Registered contact sip:fmwkphsx@192.168.6.100:37289 for sip:vm@80.97.X.X at 80.97.X.X:5060;transport=udp (expires in 600 seconds). Detected NAT type: Blocked vm@80.97.X.X /rtp Output of RTP statistics and ICE negotiation results on console is now activated vm@80.97.X.X /audio bll@80.97.X.X Initiating SIP session from 'sip:vm@80.97.X.X' to 'sip:bll@80.97.X.X' via sip:80.97.X.X:5060;transport=udp... Audio session established using G722 codec at 16000Hz Audio RTP endpoints 192.168.6.100:5 - 80.97.X.X:50006 Remote SIP User Agent is Bria 3 release 3.2.1 stamp 62387 2011-06-24 17:51:18 RTP statistics: RTT=0 ms, packet loss=0.0%, jitter RX/TX=0/0 ms SIP session with sip:b...@80.97.xx ended by remote party Session duration was 10 seconds From this is missing the ICE negotiation as you pasted below, this means that we do not have a working ICE? Did you enable ICE on the account you are using from sip-session? You need to use the sip-settings script for that. Also check the SIP trace and see if the SDP contains ICE data. -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] 1.7 Dialogue errors
Hi, Just doing some load testing on 1.7 and I am getting the following errors occurring. CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg ERROR:rtpproxy:timeout_listener_process: Wrong formatted message received from rtpproxy [118.921329779 1529.1978833588 ] I also get a lot more ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy? The only obvious problems this seems to be causing is incorrectly time stamped cdr records where the timestamp contains 0. Any ideas as to what this can be? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Registrant module
Hi, What triggers the registrant module to begin registering? I have a config on a test server which seemed to trigger the registration within about 30 seconds of starting opensips. I have moved the exact same config file over to another server with a high load on it to do some load testing but now the register does not seem to trigger at all? Any ideas? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 1.7 Dialogue errors
Hi Chris, What svn version are you using? The first critical log appears when you try a BYE for a dialog in EARLY state (without a 200OK). But this errors should have been suppressed in the latest svn version. The second error appears because there are two dialog identifiers in the received command and OpenSIPS doesn't handle them properly. The last error appears when an error occurs in RTPProxy. The latest svn verison also has implemented proper handling of RTPProxy errors. Regards, Razvan Crainea OpenSIPS Developer On 27.06.2011 11:01, Chris Martineau wrote: Hi, Just doing some load testing on 1.7 and I am getting the following errors occurring. CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg ERROR:rtpproxy:timeout_listener_process: Wrong formatted message received from rtpproxy [118.921329779 1529.1978833588 ] I also get a lot more ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy? The only obvious problems this seems to be causing is incorrectly time stamped cdr records where the timestamp contains 0. Any ideas as to what this can be? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Load balancer not able to send the calls to second sip server
Hi Robert, Thanks for looking into my problem, here I am pasting my opensips.cfg file- ### Global Parameters # debug=6 log_stderror=no log_facility=LOG_LOCAL0 fork=yes children=4 port=5060 listen=udp:x.x.x.x:5060 ### Modules Section mpath=//lib/opensips/modules/ loadmodule db_mysql.so loadmodule signaling.so loadmodule sl.so loadmodule tm.so loadmodule rr.so loadmodule maxfwd.so loadmodule usrloc.so loadmodule registrar.so loadmodule textops.so loadmodule mi_fifo.so loadmodule uri.so loadmodule xlog.so loadmodule acc.so loadmodule siptrace.so loadmodule auth.so loadmodule auth_db.so loadmodule alias_db.so loadmodule domain.so loadmodule permissions.so loadmodule group.so loadmodule drouting.so loadmodule avpops.so loadmodule dialplan.so loadmodule aaa_radius.so loadmodule dialog.so loadmodule load_balancer.so #-- avpops params - modparam(avpops, db_url, mysql://opensips:opensipsrw@localhost /opensips) modparam(avpops, avp_table, usr_preferences) #-- load the dpid field to a pseudo-variable $avp(s:dpid) -- modparam(auth_db, load_credentials, $avp(s:rpid)=rpid ;$avp(s:countrycode)=contrycode;$avp(s:areacode)=areacode) modparam(dialplan, db_url,mysql://opensips:opensipsrw@localhost /opensips) ## attribute of the matched line will be store in the $avp(s:dest) modparam(dialplan, attrs_pvar, $avp(s:dest)) # - drouting params - #modparam(drouting, sort_order, 0) modparam(drouting, use_domain, 1) modparam(drouting,db_url, mysql://opensips:opensipsrw@localhost /opensips) modparam(drouting, probing_interval, 60) modparam(drouting, probing_from, sip:pinger@x.x.x.x) modparam(drouting, probing_method, OPTIONS) modparam(drouting, probing_reply_codes, 501, 403, 404) # - Group #modparam(permissions, db_mode, 1) modparam(group,db_url,mysql://opensips:opensipsrw@localhost/opensips) # - Permissions #modparam(permissions, db_mode, 1) modparam(permissions,db_url,mysql://opensips:opensipsrw@localhost /opensips) # - mi_fifo params - modparam(mi_fifo, fifo_name, /tmp/opensips_fifo) modparam(mi_fifo, fifo_mode, 0666) modparam(dialog, dlg_flag, 13) modparam(dialog, db_mode, 1) modparam(dialog, db_url, mysql://opensips:opensipsrw@localhost /opensips) modparam(dialog, timeout_avp, $avp(i:30)) modparam(dialog, default_timeout, 3600) # - rr params - # add value to ;lr param to cope with most of the UAs modparam(rr, enable_full_lr, 1) # do not append from tag to the RR (no need for this script) modparam(rr, append_fromtag, 0) # - Load Balancer - modparam(load_balancer, db_url,mysql://opensips:opensipsrw@localhost /opensips) modparam(load_balancer, probing_interval, 60) modparam(load_balancer, probing_method, INFO) modparam(load_balancer, probing_from, sip:1000@x.x.x.x) modparam(load_balancer, db_table, load_balancer) modparam(load_balancer, probing_reply_codes, 501, 403, 404) # - registrar params - /* uncomment the next line not to allow more than 10 contacts per AOR */ #modparam(registrar, max_contacts, 10) # - usrloc params - modparam(usrloc, db_mode, 0) /* uncomment the following lines if you want to enable DB persistency for location entries */ modparam(usrloc, db_mode, 2) modparam(usrloc, db_url, mysql://opensips:opensipsrw@localhost /opensips) # - uri params - modparam(uri, use_uri_table, 0) # - acc params - /* what sepcial events should be accounted ? */ modparam(acc, early_media, 0) modparam(acc, report_ack, 0) modparam(acc, report_cancels, 0) modparam(acc, detect_direction, 0) modparam(acc, failed_transaction_flag, 1) modparam(acc, log_level, 1) modparam(acc, log_flag, 1) modparam(acc, log_missed_flag, 1) modparam(acc, db_flag, 1) modparam(acc, db_missed_flag, 2) modparam(acc, aaa_url, radius:/etc/radiusclient-ng/radiusclient.conf) # Point the configuration file modparam(acc, service_type, 15) # Set the service_type to 15 modparam(acc, aaa_flag, 1) modparam(acc, aaa_missed_flag, 1) modparam(acc, aaa_extra, via=$hdr(Via[*]); \ Digest-User-Name=$Au; \ Calling-Station-Id=$from; \ Called-Station-Id=$to; \ Sip-Translated-Request-URI=$ru; \ Sip-RPid=$avp(s:rpid); \ Source-IP=$avp(s:source_ip); \ Source-Port=$avp(s:source_port); \ SIP-Proxy-IP=$avp(s:sip_proxy_ip); \ Canonical-URI=$avp(s:can_uri); \ Divert-Reason=$avp(s:divert_reason); \ User-Agent=$hdr(user-agent); \ Contact=$hdr(contact); \ Event=$hdr(event); \
Re: [OpenSIPS-Users] Load balancer not able to send the calls to second sip server
HI Robert, Here I forwarding the OPensips LB table content,it may help- mysql select * from load_balancer; ++--+---+---++-+ | id | group_id | dst_uri | resources | probe_mode | description | +++---+---+---+-+ | 1 |2| sip:OpenSIPs@x.x.x.1 | sip=5 | 2 | SW#1| | 2 |2| sip:OpenSIPs@x.x.x.2 | sip=4 | 2 | SW#2| ++--+---+---++-+ 2 rows in set (0.00 sec) Regards Tushar On Mon, Jun 13, 2011 at 7:40 AM, Tushar Jain tusshar.j...@gmail.com wrote: Hi Robert, Thanks for looking into my problem, here I am pasting my opensips.cfg file- ### Global Parameters # debug=6 log_stderror=no log_facility=LOG_LOCAL0 fork=yes children=4 port=5060 listen=udp:x.x.x.x:5060 ### Modules Section mpath=//lib/opensips/modules/ loadmodule db_mysql.so loadmodule signaling.so loadmodule sl.so loadmodule tm.so loadmodule rr.so loadmodule maxfwd.so loadmodule usrloc.so loadmodule registrar.so loadmodule textops.so loadmodule mi_fifo.so loadmodule uri.so loadmodule xlog.so loadmodule acc.so loadmodule siptrace.so loadmodule auth.so loadmodule auth_db.so loadmodule alias_db.so loadmodule domain.so loadmodule permissions.so loadmodule group.so loadmodule drouting.so loadmodule avpops.so loadmodule dialplan.so loadmodule aaa_radius.so loadmodule dialog.so loadmodule load_balancer.so #-- avpops params - modparam(avpops, db_url, mysql://opensips:opensipsrw@localhost /opensips) modparam(avpops, avp_table, usr_preferences) #-- load the dpid field to a pseudo-variable $avp(s:dpid) -- modparam(auth_db, load_credentials, $avp(s:rpid)=rpid ;$avp(s:countrycode)=contrycode;$avp(s:areacode)=areacode) modparam(dialplan, db_url,mysql://opensips:opensipsrw@localhost /opensips) ## attribute of the matched line will be store in the $avp(s:dest) modparam(dialplan, attrs_pvar, $avp(s:dest)) # - drouting params - #modparam(drouting, sort_order, 0) modparam(drouting, use_domain, 1) modparam(drouting,db_url, mysql://opensips:opensipsrw@localhost /opensips) modparam(drouting, probing_interval, 60) modparam(drouting, probing_from, sip:pinger@x.x.x.x) modparam(drouting, probing_method, OPTIONS) modparam(drouting, probing_reply_codes, 501, 403, 404) # - Group #modparam(permissions, db_mode, 1) modparam(group,db_url,mysql://opensips:opensipsrw@localhost /opensips) # - Permissions #modparam(permissions, db_mode, 1) modparam(permissions,db_url,mysql://opensips:opensipsrw@localhost /opensips) # - mi_fifo params - modparam(mi_fifo, fifo_name, /tmp/opensips_fifo) modparam(mi_fifo, fifo_mode, 0666) modparam(dialog, dlg_flag, 13) modparam(dialog, db_mode, 1) modparam(dialog, db_url, mysql://opensips:opensipsrw@localhost /opensips) modparam(dialog, timeout_avp, $avp(i:30)) modparam(dialog, default_timeout, 3600) # - rr params - # add value to ;lr param to cope with most of the UAs modparam(rr, enable_full_lr, 1) # do not append from tag to the RR (no need for this script) modparam(rr, append_fromtag, 0) # - Load Balancer - modparam(load_balancer, db_url,mysql://opensips:opensipsrw@localhost /opensips) modparam(load_balancer, probing_interval, 60) modparam(load_balancer, probing_method, INFO) modparam(load_balancer, probing_from, sip:1000@x.x.x.x) modparam(load_balancer, db_table, load_balancer) modparam(load_balancer, probing_reply_codes, 501, 403, 404) # - registrar params - /* uncomment the next line not to allow more than 10 contacts per AOR */ #modparam(registrar, max_contacts, 10) # - usrloc params - modparam(usrloc, db_mode, 0) /* uncomment the following lines if you want to enable DB persistency for location entries */ modparam(usrloc, db_mode, 2) modparam(usrloc, db_url, mysql://opensips:opensipsrw@localhost /opensips) # - uri params - modparam(uri, use_uri_table, 0) # - acc params - /* what sepcial events should be accounted ? */ modparam(acc, early_media, 0) modparam(acc, report_ack, 0) modparam(acc, report_cancels, 0) modparam(acc, detect_direction, 0) modparam(acc, failed_transaction_flag, 1) modparam(acc, log_level, 1) modparam(acc, log_flag, 1) modparam(acc, log_missed_flag, 1) modparam(acc, db_flag, 1) modparam(acc, db_missed_flag, 2) modparam(acc, aaa_url, radius:/etc/radiusclient-ng/radiusclient.conf) # Point the configuration file modparam(acc, service_type, 15) # Set the service_type to 15 modparam(acc, aaa_flag, 1) modparam(acc, aaa_missed_flag, 1) modparam(acc,
Re: [OpenSIPS-Users] i cant login in...
did you enable the xmlrpc on your opensips.cfg ? if you are using fifo you can change on global file to use fifo 2011/6/16 Kevin Disher dishernos...@gmail.com when i try and log in through the main page or using the password recovery link i get this error sorry -- cannot connect to xmlrpc server 111 - Connection refused p.s. i just made my account but it has been confirmed... ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 1.7 Dialogue errors
Hi Razvan, Loaded this up on Thursday? Where do I check the specific svn version that is running? Are you saying that the second error is fixed in the latest svn? Regards Chris From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan Crainea Sent: 27 June 2011 09:28 To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] 1.7 Dialogue errors Hi Chris, What svn version are you using? The first critical log appears when you try a BYE for a dialog in EARLY state (without a 200OK). But this errors should have been suppressed in the latest svn version. The second error appears because there are two dialog identifiers in the received command and OpenSIPS doesn't handle them properly. The last error appears when an error occurs in RTPProxy. The latest svn verison also has implemented proper handling of RTPProxy errors. Regards, Razvan Crainea OpenSIPS Developer On 27.06.2011 11:01, Chris Martineau wrote: Hi, Just doing some load testing on 1.7 and I am getting the following errors occurring. CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg ERROR:rtpproxy:timeout_listener_process: Wrong formatted message received from rtpproxy [118.921329779 1529.1978833588 ] I also get a lot more ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy? The only obvious problems this seems to be causing is incorrectly time stamped cdr records where the timestamp contains 0. Any ideas as to what this can be? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 1.7 Dialogue errors
Hi Chris, You can find your svn version by executing 'opensips -V'. The second error is not fixed yet, but I am working on a patch. I'll let you know as soon as I finish. Regards, Razvan Crainea OpenSIPS Developer On 27.06.2011 12:31, Chris Martineau wrote: Hi Razvan, Loaded this up on Thursday? Where do I check the specific svn version that is running? Are you saying that the second error is fixed in the latest svn? Regards Chris *From:*users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Razvan Crainea *Sent:* 27 June 2011 09:28 *To:* users@lists.opensips.org *Subject:* Re: [OpenSIPS-Users] 1.7 Dialogue errors Hi Chris, What svn version are you using? The first critical log appears when you try a BYE for a dialog in EARLY state (without a 200OK). But this errors should have been suppressed in the latest svn version. The second error appears because there are two dialog identifiers in the received command and OpenSIPS doesn't handle them properly. The last error appears when an error occurs in RTPProxy. The latest svn verison also has implemented proper handling of RTPProxy errors. Regards, Razvan Crainea OpenSIPS Developer On 27.06.2011 11:01, Chris Martineau wrote: Hi, Just doing some load testing on 1.7 and I am getting the following errors occurring. CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg ERROR:rtpproxy:timeout_listener_process: Wrong formatted message received from rtpproxy [118.921329779 1529.1978833588 ] I also get a lot more ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy? The only obvious problems this seems to be causing is incorrectly time stamped cdr records where the timestamp contains 0. Any ideas as to what this can be? Regards Chris ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Changing IP's and Data Centers
Hi Dovid, Depends on the services / functionalities you have on main proxy, but you can make a small proxy configuration just to relay everything to the new address. Of course you need to take care of IP-based routing / authentication, about nat traversal (if any), about registration part, etc. Or you can simply setup on old IP an SIP redirect server pointing to the new IP. Regards, Bogdan On 06/27/2011 10:26 AM, Dovid Bender wrote: Hi, We currently have a set up in one data center with OpenSipS listening on IP 200.200.200.200. In the new data center we have the same set up on IP: 201.201.201.201. We want to have a grace period for customers. Is there any way that we can sent 200.200.200.200 to forward all it's traffic to 201.201.201.201 ? I tried to do it in the past (forgot what routing logic I used) and it did not work with try to authenticate a user. Any pointers on how to configure something like this ? Thanks. Dovid ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS solutions and know-how ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] nathelper memory error
Hi Dovid, yeah, that will be a bit too much for a single query - as said, in db mode 3 (DB ONLY), each time there is a need for NAT pinging, all contacts from DB are loaded. This query does not have fetch support (progressive loading into memory), so it loads everything at once. If you cannot use a different DB mode , please open a bug report on this. Regards, Bogdan On 06/27/2011 10:30 AM, Dovid Bender wrote: Bogdan, We have on average 2500-2600 registerd users. Once it goes over 2800-2900 we start seeing the error. Regards, Dovid - Original Message - *From:* Bogdan-Andrei Iancu mailto:bog...@opensips.org *To:* users@lists.opensips.org mailto:users@lists.opensips.org *Sent:* Friday, June 24, 2011 17:43 *Subject:* Re: [OpenSIPS-Users] nathelper memory error Hi Dovid, db_mode 3 has some inefficient way of doing things, like NAT pinging - in order to do it, it has to query in DB for all nated records - probably in your case, you have too many registered users for a single query to handle . How many records do you actually have ? Regards, Bogdan On 06/15/2011 05:53 AM, Dovid Bender wrote: Hi, We are using OpenSIPs (opensips-1.4.3-tls yes I know we should upgrade...) and it seems that ever since we set db_mode to 3 we started getting the erros below: Jun 14 20:12:14 peter /sbin/opensips[4434]: ERROR:db_mysql:db_mysql_convert_rows: no private memory left Jun 14 20:12:15 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:16 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:20 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:51 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory We have fork set to 24 and modparam( usrloc, fetch_rows, 500 ). TIA. Dovid -- Bogdan-Andrei Iancu OpenSIPS solutions and know-how ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 1.7 Dialogue errors
Hi Chris, I have just committed a fix for the rtpproxy module in trunk that properly handles multiple RTPProxy notification commands. Regards, Razvan Crainea OpenSIPS Developer On 27.06.2011 12:31, Chris Martineau wrote: Hi Razvan, Loaded this up on Thursday? Where do I check the specific svn version that is running? Are you saying that the second error is fixed in the latest svn? Regards Chris *From:*users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Razvan Crainea *Sent:* 27 June 2011 09:28 *To:* users@lists.opensips.org *Subject:* Re: [OpenSIPS-Users] 1.7 Dialogue errors Hi Chris, What svn version are you using? The first critical log appears when you try a BYE for a dialog in EARLY state (without a 200OK). But this errors should have been suppressed in the latest svn version. The second error appears because there are two dialog identifiers in the received command and OpenSIPS doesn't handle them properly. The last error appears when an error occurs in RTPProxy. The latest svn verison also has implemented proper handling of RTPProxy errors. Regards, Razvan Crainea OpenSIPS Developer On 27.06.2011 11:01, Chris Martineau wrote: Hi, Just doing some load testing on 1.7 and I am getting the following errors occurring. CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg ERROR:rtpproxy:timeout_listener_process: Wrong formatted message received from rtpproxy [118.921329779 1529.1978833588 ] I also get a lot more ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy? The only obvious problems this seems to be causing is incorrectly time stamped cdr records where the timestamp contains 0. Any ideas as to what this can be? Regards Chris ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Custom RADIUS digest auth. request
Salut Tiberiu, Normally, the auth username is taken from TO hdr (for REGISTER) or from FROM hdr (non-REGISTER) - both username and domain part. So probably, in your case, the IP comes from the FROM hdr. Also, opensips allows you to pass a custom SIP URI for auth, as a second optional param to the aaa_proxy_auth() : http://www.opensips.org/html/docs/modules/1.6.x/auth_aaa.html Currently this is not supported for aaa_www_auth() (for REGISTER) can be simply done, if this solves your problem. Regards, Bogdan On 06/24/2011 05:25 PM, Tiberiu Breana wrote: Hello. I'm trying to simulate a mobility situation where a User Agent Client is connecting to a foreign SIP proxy. My setup is something like this: UA --- F-SIP --- F-AAA | | H-SIP --- H-AAA The user is registered on the H-AAA server. I want to authenticate him through H-AAA, but the aaa_www_authorize function sends the username as user@Foreign SIP IP, regardless of what username I choose in my softphone. So there's no way to detect the user's home domain (that my UAC provides). I know I could make a custom radius_send_auth, but I wanted to follow protocol and keep the digest mechanism for registering. Or is there a way to make a custom digest auth to work with the register process? Any advice is appreciated! Regards, Tiberiu ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS solutions and know-how ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] drouting - dr_reload (performance)
Hi, I just found out what caused these issues, simple solution, thanks for your hints! If debug level is set to 0 it works just fine + reload is really fast (wether set via fifo debug or in config). At level3 you can see lots of debugging messages when reloading, also the load goes up and the blocking occurs. At debug level 0 reload goes really fast and no blocking at all. So it really seems to be related to the xlogs/debugging. Everything is working fine for me now (at debug0). Thanks again. BR Max M. Am 25.06.2011 13:54, schrieb Bogdan-Andrei Iancu: Hi Max, 100K rule is nothing for the dr module (disregarding the how fast the DB is or not). Maybe the so called locking is about overall load or DB load - using some xlogs and benchmarking module, you can try to see if there is an actual blocking in the do_routing() function. Regards, Bogdan On 06/24/2011 06:13 PM, Max Mühlbronner wrote: Hi, yes, i tried several times. I should have mentioned the dr_rules has quite a few (about 100k entries). I did notice it on a production server running 1.6.2 but also was able to replicate the same behavior when testing with the same Database/dr_rules on 1.6.4-tls. I will try to take a deeper look into the issue, will try to send some traces / logs if there is something which looks like it could be related. BR Max M. Am 24.06.2011 16:40, schrieb Bogdan-Andrei Iancu: Hi Max, the reload is done in a separate process and only when done, the routing data (in mem) is swapped, so while loading new data, opensips will still use the old one - it should not block and wait for reload. Are you sure is there any blocking ? What version are you using ? Regards, Bogdan On 06/16/2011 03:48 PM, Max Mühlbronner wrote: Hello, Opensips seems to not route my requests while reloading the drouting rules from Database. Probably the DB operations are blocking the remaining operations? Any idea if this is normal behavior, or misconfiguration on my side? Does anyone know a solution for reloading while still receiving traffic, so if the rules become quite big it will not take the service down while reloading via mi (fifo dr_reload / webinterface..)? Best Regards Max M. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] db_postgres connections to a remote db
I'm looking for some clarification as to how db_postgres behaves when connecting to a remote database. OpenSIPS connects to the remote db when pulling down new configuration for drouting, permissions, and a couple other modules. The cdr records (acc module) are written locally. It seems that the opensips process continues to open new connections to the remote database without closing them. It eventually eats up all the configured connections on the database until they have to be manually removed. Is there a configuration option I'm missing somewhere that could be causing this behavior? I'm running a newer version of 1.6.4 though not the latest from svn. Thanks, Ryan ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips-cp - same gw ip / different GW Types
Hi,
i just came across another weird issue. There are two Gateways in
routing, both got the same IP, but two different Gateway types as
defined in opensips-cp. (type 7 / type 8)
I got some checks in my script to check for the gw Type and do some
action depending on the type of Gw used in Routing.
if (goes_to_gw(7)) {
do something...
}
if (goes_to_gw(8)) {
do something...
}
There is one corresponding Rule in opensips-cp which routes to GW1 (gw
type8...) , GW2 is not used at all...!
I can see in traces / related to the gw settings in opensips-cp
(PRI-Prefix/...) it is going to the correct gw1 (remember both got same
ip, so i can judge by looking at the prefix). But somehow the check for
gateway-types (if goes_to_gw) always thinks its the wrong gateway
type?`? If it is gw_type 8 it thinks it is 7.. (Basically it just takes
the type from gw2 --- which is not used - also marked red in opensips-cp
because not used at all. It seems like it is matching the ip two times,
and is taking the type which is lower - e.g. 7 instead of 8).
Did anyone experience something like this, is it just me or is there
something wrong with the way i am using the types and gws?`Maybe it is
not intended to be used this way?
BR
Max M.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Registrant module
Thanks... -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Ovidiu Sas Sent: 27 June 2011 13:14 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Registrant module Have you read the README file? http://www.opensips.org/html/docs/modules/devel/registrant.html#id248659 http://www.opensips.org/html/docs/modules/devel/registrant.html#id249123 If something is not working as documented or the documentation is incomplete, please let me know. Regards, Ovidiu Sas On Mon, Jun 27, 2011 at 4:23 AM, Chris Martineau ch...@ghosttelecom.com wrote: Hi, What triggers the registrant module to begin registering? I have a config on a test server which seemed to trigger the registration within about 30 seconds of starting opensips. I have moved the exact same config file over to another server with a high load on it to do some load testing but now the register does not seem to trigger at all? Any ideas? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] drouting - dr_reload (performance)
Hi Max, It may be related to syslog performance - check if you have the async written enabled in syslog for the the opensips file. Regards, Bogdan On 06/27/2011 03:40 PM, Max Mühlbronner wrote: Hi, I just found out what caused these issues, simple solution, thanks for your hints! If debug level is set to 0 it works just fine + reload is really fast (wether set via fifo debug or in config). At level3 you can see lots of debugging messages when reloading, also the load goes up and the blocking occurs. At debug level 0 reload goes really fast and no blocking at all. So it really seems to be related to the xlogs/debugging. Everything is working fine for me now (at debug0). Thanks again. BR Max M. Am 25.06.2011 13:54, schrieb Bogdan-Andrei Iancu: Hi Max, 100K rule is nothing for the dr module (disregarding the how fast the DB is or not). Maybe the so called locking is about overall load or DB load - using some xlogs and benchmarking module, you can try to see if there is an actual blocking in the do_routing() function. Regards, Bogdan On 06/24/2011 06:13 PM, Max Mühlbronner wrote: Hi, yes, i tried several times. I should have mentioned the dr_rules has quite a few (about 100k entries). I did notice it on a production server running 1.6.2 but also was able to replicate the same behavior when testing with the same Database/dr_rules on 1.6.4-tls. I will try to take a deeper look into the issue, will try to send some traces / logs if there is something which looks like it could be related. BR Max M. Am 24.06.2011 16:40, schrieb Bogdan-Andrei Iancu: Hi Max, the reload is done in a separate process and only when done, the routing data (in mem) is swapped, so while loading new data, opensips will still use the old one - it should not block and wait for reload. Are you sure is there any blocking ? What version are you using ? Regards, Bogdan On 06/16/2011 03:48 PM, Max Mühlbronner wrote: Hello, Opensips seems to not route my requests while reloading the drouting rules from Database. Probably the DB operations are blocking the remaining operations? Any idea if this is normal behavior, or misconfiguration on my side? Does anyone know a solution for reloading while still receiving traffic, so if the rules become quite big it will not take the service down while reloading via mi (fifo dr_reload / webinterface..)? Best Regards Max M. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS solutions and know-how ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is always incrementing
Hi John,
So you are saying that opensipsctl ul show shows only 2 records while
the statistic shows more ??
Regards,
Bogdan
On 06/25/2011 10:37 PM, John Quick wrote:
Bogdan,
Here is a snippet showing the significant parts from the script that I use
for handling REGISTER requests, but I think there is only one line that is
unusual.
modparam(usrloc, nat_bflag, 6)
modparam(usrloc, db_mode, 2)
modparam(usrloc, use_domain, 1)
modparam(registrar, default_q, 800)
modparam(registrar, received_avp, $avp(s:rcv))
sl_send_reply(100, Trying);
if (client_nat_test(2)) {
setbflag(6);
fix_nated_register();
force_rport();
}
if (!aaa_www_authorize()) {
www_challenge(,0);
exit;
};
if (!db_check_to()) {
sl_send_reply(401, Unauthorized);
exit;
};
consume_credentials();
if (!save(location)) {
log(1, ***--REGISTER: location save failed!\n);
sl_reply_error();
}
In case the consume_credentials() function was causing the fault, I repeated
my tests with that line commented out. However, the counter is still going
up.
There is no ul dump option in opensipsctl, but there is a ul show
function. It shows the correct information:
[root@centos6v log]# opensipsctl fifo get_statistics usrloc:
usrloc:registered_users = 3
usrloc:aliases-users = 0
usrloc:aliases-contacts = 0
usrloc:aliases-expires = 0
usrloc:location-users = 3
usrloc:location-contacts = 2
usrloc:location-expires = 1
[root@centos6v log]# opensipsctl ul show
Domain:: location table=512 records=2
AOR:: 1...@suse-sip.com
Contact:: sip:1002@192.168.0.60:6050 Q=1
Expires:: 3551
Callid:: 3c2670ace4cd-m9fekwu548ay
Cseq:: 6
User-agent:: snom360/7.3.30
State:: CS_SYNC
Flags:: 0
Cflag:: 0
Socket:: udp:192.168.0.116:5060
Methods:: 7999
AOR:: 1...@suse-sip.com
Contact:: sip:1003@192.168.0.67:5060;transport=udp Q=0.8
Expires:: 3288
Callid:: b939e48a7188d2cf
Cseq:: 4400
User-agent:: Aastra 6731i/2.6.0.1008
State:: CS_SYNC
Flags:: 0
Cflag:: 0
Socket:: udp:192.168.0.116:5060
Methods:: 7807
Domain:: aliases table=512 records=0
John
-Original Message-
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: 25 June 2011 12:51
To: users@lists.opensips.org; John Quick
Subject: Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is
always incrementing
Hi John,
As the statistic is know to work well, I suspect something strange with your
setup (like re-registrations are actually new registers). So, in the same
time, please check the content of user location via:
opensipsctl ul dump
Just to see the actual records.
Regards,
Bogdan
On 06/24/2011 06:15 PM, John Quick wrote:
Hi Bogdan
Yes, I can confirm that registered_users shows the same value through
the fifo get_statistics request and the SNMP MIB value. The statistic
that appears to show the correct number of registered users is
usrloc:location-contacts
Here is the complete list of usrloc statistics on my test server today
- only one UA is registered at the moment:
# opensipsctl fifo get_statistics usrloc:
usrloc:registered_users = 14
usrloc:aliases-users = 0
usrloc:aliases-contacts = 0
usrloc:aliases-expires = 0
usrloc:location-users = 14
usrloc:location-contacts = 1
usrloc:location-expires = 13
Sorry I cannot maintain the thread on this reply - I am only receiving
digests from this forum and have forgotten my login details so cannot
change it.
John Quick
Message: 2
Date: Fri, 24 Jun 2011 16:47:12 +0300
From: Bogdan-Andrei Iancubog...@opensips.org
Subject: Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is
always incrementing
To: users@lists.opensips.org
Message-ID:4e049560.5020...@opensips.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi John,
That stat is related to the internal statistic registered_users
provided by the usrloc module. Can you confirm that opensipsctl fifo
get_statistics registered_users gives thesame value as via SNMP ?
Regards,
Bogdan
On 06/23/2011 12:49 PM, John Quick wrote:
Using SNMPStats with version 1.6.2 of OpenSIPS, the value reported
for openserSIPRegCurrentUsers does not indicate the number of UA's
currently registered. It shows a value that is always increasing over
time.
I am testing with 3 registered devices. There are three records in
the location table. However, openserSIPRegCurrentUsers now has a
value of
12 and it increments by 1 approximately every 20 minutes. I would
guess it is
[OpenSIPS-Users] 408 cdr issue
Hi, Have a strange issue whereby if opensips generates a 408 timeout on a call after having got as far as a 183 response from the far end, it generates a cdr in both the acc db and the missed calls db? If the 408 comes from the far end this doesn't happen. This seems to happen in 1.6 and 1.7. Any ideas? Many thanks Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 404 Contact not found
Hello Nick,
Checking the functions, found several issues with contact searching via
the MI commands. The attached patch should fix the problem - please
apply it, recompile and test again and let me know if works as expected.
Regards,
Bogdan
On 06/27/2011 05:10 PM, n...@uni-petrol.com wrote:
Dear Bogdan!
I have matching mode 1 - CONTACT and CALLID based matching algorithm:
modparam(usrloc, matching_mode, 1)
Output of ul_dump fifo command:
# opensipsctl fifo ul_dump
AOR:: u...@domain.com
Contact:: sip:user@10.10.10.31:5060 Q=0
Expires:: 152
Callid:: 2725345640@10_10_10_31
Cseq:: 6
User-agent:: C470 IP02223000
Received:: sip:81.222.81.68:5060
State:: CS_SYNC
Flags:: 0
Cflag:: 64
Socket:: udp:OSIPSIP:5060
Methods:: 5695
# opensipsctl fifo ul_rm_contact location u...@domain.com
sip:user@10.10.10.31:5060
404 Contact not found
And because of this error opensips-cp can't delete registered contact
when I press delete button.
On Fri, 24 Jun 2011 16:54:42 +0300, Bogdan-Andrei Iancu wrote:
Hi Nick,
Do you use a specific value for matching_mode in usrloc module ?
Also, could you post the output of opensipsctl ul dump - post only
relevant record.
Regards,
Bogdan
On 06/21/2011 03:12 PM, n...@uni-petrol.com [5]wrote:
Dear All! opensips: opensips_trunk rev 7915 I have strange problem.
When I try to delete contact fifo command ul_show_contact can't find
AOR but fifo comman ul_show contact show it. # opensipsctl fifo
ul_show_contact location u...@domain.com [1] Contact::
;q=0;expires=109;flags=0x0;cflags=0x0;socket=;methods=0x143F;user_agent=
# opensipsctl fifo ul_rm_contact location u...@domain.com [2]
sip:user@UAC:5060 404 Contact not found Thanks in advance!
___ Users mailing list
Users@lists.opensips.org [3]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users [4]
--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and know-how
Index: modules/usrloc/urecord.c
===
--- modules/usrloc/urecord.c(revision 8040)
+++ modules/usrloc/urecord.c(working copy)
@@ -550,3 +550,12 @@
}
+/* similar to get_ucontact, but does not use callid and cseq
+ to be used from MI functions where we have only contact */
+int get_simple_ucontact(urecord_t* _r, str* _c, struct ucontact** _co)
+{
+ *_co = contact_match( _r-contacts, _c);
+ return (*_co)?0:1;
+}
+
+
Index: modules/usrloc/ul_mi.c
===
--- modules/usrloc/ul_mi.c (revision 8040)
+++ modules/usrloc/ul_mi.c (working copy)
@@ -292,7 +292,7 @@
}
contact = node-next-next-value;
- ret = get_ucontact( rec, contact, mi_ul_cid, MI_UL_CSEQ+1, con);
+ ret = get_simple_ucontact( rec, contact, con);
if (ret 0) {
unlock_udomain( dom, aor);
return 0;
@@ -503,23 +503,26 @@
goto lock_error;
c = 0;
} else {
- if (get_ucontact( r, contact, mi_ul_cid, MI_UL_CSEQ+1, c) 0)
+ if (get_simple_ucontact( r, contact, c) 0)
goto lock_error;
}
get_act_time();
- ci.callid = mi_ul_cid;
ci.user_agent = mi_ul_ua;
- ci.cseq = MI_UL_CSEQ;
/* 0 expires means permanent contact */
if (ci.expires!=0)
ci.expires += act_time;
if (c) {
+ /* update contact record */
+ ci.cseq = c-cseq;
if (update_ucontact( r, c, ci) 0)
goto release_error;
} else {
+ /* new contact record */
+ ci.callid = mi_ul_cid;
+ ci.cseq = MI_UL_CSEQ;
if ( insert_ucontact( r, contact, ci, c) 0 )
goto release_error;
}
Index: modules/usrloc/urecord.h
===
--- modules/usrloc/urecord.h(revision 8040)
+++ modules/usrloc/urecord.h(working copy)
@@ -139,6 +139,8 @@
struct ucontact** _co);
int get_ucontact(urecord_t* _r, str* _c, str* _callid, int _cseq,
struct ucontact** _co);
+int get_simple_ucontact(urecord_t* _r, str* _c, struct ucontact** _co);
+
#endif /* URECORD_H */
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Registrant module
Hi, It says it's sitting in state 6 incorrect credentials but I cannot see it retrying. I have left the retry at default 100 so I would expect it to be regularly trying but I see nothing. Is there anyway to restart this process or force a register without restarting the system? Regards Chris -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Ovidiu Sas Sent: 27 June 2011 13:14 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Registrant module Have you read the README file? http://www.opensips.org/html/docs/modules/devel/registrant.html#id248659 http://www.opensips.org/html/docs/modules/devel/registrant.html#id249123 If something is not working as documented or the documentation is incomplete, please let me know. Regards, Ovidiu Sas On Mon, Jun 27, 2011 at 4:23 AM, Chris Martineau ch...@ghosttelecom.com wrote: Hi, What triggers the registrant module to begin registering? I have a config on a test server which seemed to trigger the registration within about 30 seconds of starting opensips. I have moved the exact same config file over to another server with a high load on it to do some load testing but now the register does not seem to trigger at all? Any ideas? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is always incrementing
Yes.
John
-Original Message-
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: 27 June 2011 14:49
To: john.qu...@smartvox.co.uk
Cc: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is
always incrementing
Hi John,
So you are saying that opensipsctl ul show shows only 2 records while the
statistic shows more ??
Regards,
Bogdan
On 06/25/2011 10:37 PM, John Quick wrote:
Bogdan,
Here is a snippet showing the significant parts from the script that I
use for handling REGISTER requests, but I think there is only one line
that is unusual.
modparam(usrloc, nat_bflag, 6)
modparam(usrloc, db_mode, 2)
modparam(usrloc, use_domain, 1)
modparam(registrar, default_q, 800) modparam(registrar,
received_avp, $avp(s:rcv))
sl_send_reply(100, Trying);
if (client_nat_test(2)) {
setbflag(6);
fix_nated_register();
force_rport();
}
if (!aaa_www_authorize()) {
www_challenge(,0);
exit;
};
if (!db_check_to()) {
sl_send_reply(401, Unauthorized);
exit;
};
consume_credentials();
if (!save(location)) {
log(1, ***--REGISTER: location save failed!\n);
sl_reply_error();
}
In case the consume_credentials() function was causing the fault, I
repeated my tests with that line commented out. However, the counter
is still going up.
There is no ul dump option in opensipsctl, but there is a ul show
function. It shows the correct information:
[root@centos6v log]# opensipsctl fifo get_statistics usrloc:
usrloc:registered_users = 3
usrloc:aliases-users = 0
usrloc:aliases-contacts = 0
usrloc:aliases-expires = 0
usrloc:location-users = 3
usrloc:location-contacts = 2
usrloc:location-expires = 1
[root@centos6v log]# opensipsctl ul show
Domain:: location table=512 records=2
AOR:: 1...@suse-sip.com
Contact:: sip:1002@192.168.0.60:6050 Q=1
Expires:: 3551
Callid:: 3c2670ace4cd-m9fekwu548ay
Cseq:: 6
User-agent:: snom360/7.3.30
State:: CS_SYNC
Flags:: 0
Cflag:: 0
Socket:: udp:192.168.0.116:5060
Methods:: 7999
AOR:: 1...@suse-sip.com
Contact:: sip:1003@192.168.0.67:5060;transport=udp Q=0.8
Expires:: 3288
Callid:: b939e48a7188d2cf
Cseq:: 4400
User-agent:: Aastra 6731i/2.6.0.1008
State:: CS_SYNC
Flags:: 0
Cflag:: 0
Socket:: udp:192.168.0.116:5060
Methods:: 7807
Domain:: aliases table=512 records=0
John
-Original Message-
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: 25 June 2011 12:51
To: users@lists.opensips.org; John Quick
Subject: Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is
always incrementing
Hi John,
As the statistic is know to work well, I suspect something strange
with your setup (like re-registrations are actually new registers).
So, in the same time, please check the content of user location via:
opensipsctl ul dump
Just to see the actual records.
Regards,
Bogdan
On 06/24/2011 06:15 PM, John Quick wrote:
Hi Bogdan
Yes, I can confirm that registered_users shows the same value through
the fifo get_statistics request and the SNMP MIB value. The statistic
that appears to show the correct number of registered users is
usrloc:location-contacts
Here is the complete list of usrloc statistics on my test server
today
- only one UA is registered at the moment:
# opensipsctl fifo get_statistics usrloc:
usrloc:registered_users = 14
usrloc:aliases-users = 0
usrloc:aliases-contacts = 0
usrloc:aliases-expires = 0
usrloc:location-users = 14
usrloc:location-contacts = 1
usrloc:location-expires = 13
Sorry I cannot maintain the thread on this reply - I am only
receiving digests from this forum and have forgotten my login details
so cannot change it.
John Quick
Message: 2
Date: Fri, 24 Jun 2011 16:47:12 +0300
From: Bogdan-Andrei Iancubog...@opensips.org
Subject: Re: [OpenSIPS-Users] SNMPStats - openserSIPRegCurrentUsers is
always incrementing
To: users@lists.opensips.org
Message-ID:4e049560.5020...@opensips.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi John,
That stat is related to the internal statistic registered_users
provided by the usrloc module. Can you confirm that opensipsctl fifo
get_statistics registered_users gives thesame value as via SNMP ?
Regards,
Bogdan
On 06/23/2011 12:49 PM, John Quick wrote:
Using SNMPStats with version 1.6.2 of
Re: [OpenSIPS-Users] Registrant module
If an account reaches state 6 (incorrect credentials) no REGISTER requests will be generated for that account. The credentials for that account must be updated in the config (uac parameter) and then the server must be restarted. Regards, Ovidiu Sas On Mon, Jun 27, 2011 at 11:00 AM, Chris Martineau ch...@ghosttelecom.com wrote: Hi, It says it's sitting in state 6 incorrect credentials but I cannot see it retrying. I have left the retry at default 100 so I would expect it to be regularly trying but I see nothing. Is there anyway to restart this process or force a register without restarting the system? Regards Chris -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Ovidiu Sas Sent: 27 June 2011 13:14 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Registrant module Have you read the README file? http://www.opensips.org/html/docs/modules/devel/registrant.html#id248659 http://www.opensips.org/html/docs/modules/devel/registrant.html#id249123 If something is not working as documented or the documentation is incomplete, please let me know. Regards, Ovidiu Sas On Mon, Jun 27, 2011 at 4:23 AM, Chris Martineau ch...@ghosttelecom.com wrote: Hi, What triggers the registrant module to begin registering? I have a config on a test server which seemed to trigger the registration within about 30 seconds of starting opensips. I have moved the exact same config file over to another server with a high load on it to do some load testing but now the register does not seem to trigger at all? Any ideas? Regards Chris ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Implementing CDRtool
Hello l'm looking to implement CDRTool in my business, but looking on Google I did not find any complete example (set OpenSIPS, radius, cdrtool prices, etc), just certain parts. Does anyone know of a tutorial especially for set of cdrtool (prices, suppliers, prepaid, etc.)?. I have a question too, I like the different departments have 1000 minutes of national calls and once surpassed deducted from your prepaid account. Could do this with Quota? What are some examples of how you could do?. For transfers are accounted for another user, use diverter_avp_id, right?. Can you make that part of the transfer is acountedd to a user and the other party to another?. Thanks Regards Anto ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Custom RADIUS digest auth. request
Thanks, I solved it before reading this mail. I just logged in to post the
solution when I saw your reply :)
So, here's the solution for anyone interested in forwarding authentication
requests through freeRADIUS servers:
I used aaa_proxy_authorize (which seems fairly logical, since I am using a
foreign server for authentication) like this:
aaa_proxy_authorize(, $fu), where $fu is the URI of the From header
(which should contain your home domain).
To allow RADIUS forwarding, the desired realm should be declared in
freeRADIUS' proxy.conf, along with its corresponding IP and shared secret:
home_server HomeServerName {
type = auth
ipaddr = RADIUS server IP address to which requests should be forwarded
port = 1812
secret = xxx #shared with the foreign RADIUS
server
}
home_server_pool PoolName {
type = fail-over
home_server = HomeServerName
}
realm RealmName { #RealmName is the domain specified in the
From URI
auth_pool = PoolName
}
One more thing, you need to declare the RADIUS proxy's IP and shared secret
in the home RADIUS clients.conf file.
That's it. Enjoy!
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Custom RADIUS digest auth. request
Communication problems here. Seems like my mail was cut off to early. Here's
the rest:
realm RealmName { #RealmName is the domain specified in the
From URI
auth_pool = PoolName
}
One more thing, you need to declare the RADIUS proxy's IP and shared secret
in the home RADIUS clients.conf file.
That's it. Enjoy!
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
