Re: [OpenSIPS-Devel] SF.net SVN: opensips:[9319] trunk/modules/b2b_logic/b2bl_db.c
Hi Ovidiu, Shouldn't be this backported ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 10/13/2012 08:34 PM, Ovidiu Sas wrote: Revision: 9319 http://opensips.svn.sourceforge.net/opensips/?rev=9319view=rev Author: osas Date: 2012-10-13 16:34:33 + (Sat, 13 Oct 2012) Log Message: --- b2b_logic: fix removal of expired tuples while loading them from db Modified Paths: -- trunk/modules/b2b_logic/b2bl_db.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9320] trunk/mem/f_malloc.c
Revision: 9320 http://opensips.svn.sourceforge.net/opensips/?rev=9320view=rev Author: razvancrainea Date: 2012-10-15 10:35:51 + (Mon, 15 Oct 2012) Log Message: --- Fixed used and real_used statistics calculation Modified Paths: -- trunk/mem/f_malloc.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9321] branches/1.8/mem/f_malloc.c
Revision: 9321 http://opensips.svn.sourceforge.net/opensips/?rev=9321view=rev Author: razvancrainea Date: 2012-10-15 10:47:39 + (Mon, 15 Oct 2012) Log Message: --- Backported from trunk (rev #9320): Fixed used and real_used statistics calculation Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9320view=rev Modified Paths: -- branches/1.8/mem/f_malloc.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9322] branches/1.7/mem/f_malloc.c
Revision: 9322 http://opensips.svn.sourceforge.net/opensips/?rev=9322view=rev Author: razvancrainea Date: 2012-10-15 10:47:41 + (Mon, 15 Oct 2012) Log Message: --- Backported from trunk (rev #9320): Fixed used and real_used statistics calculation Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9320view=rev Modified Paths: -- branches/1.7/mem/f_malloc.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3532144 ] set_count() may return 0
Bugs item #3532144, was opened at 2012-06-05 05:51 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3532144group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.8.x Status: Open Resolution: Fixed Priority: 7 Private: No Submitted By: Bogdan-Andrei Iancu (bogdan_iancu) Assigned to: Liviu Chircu (liviuchircu) Summary: set_count() may return 0 Initial Comment: When doing the counting, set_count() may return 0 (0 values for a pvar) - this will break the script. -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-15 04:10 Message: Liviu, please backport this fix to 1.8 and 1.7 branches. Thanks and regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3532144group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3576351 ] sip_trace module bug
Bugs item #3576351, was opened at 2012-10-11 07:53 Message generated for change (Comment added) made by dragosoancea You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3576351group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.8.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dragos Oancea (dragosoancea) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: sip_trace module bug Initial Comment: Hi The siptrace module reports a wrong value in the `fromip` field of the sip_trace table. For example , for this INVITE, coming from tls:80.187.x.x:62510 , I would expect the value tls:80.187.x.x:62510 to be added in the `fromip` field, but it's adding tls:80.187.x.x:625 instead . It's missing two digits from the port value. Also , sometimes it would put its local port (in my case 5061) instead of the remote port in the `fromip` or `toip` fields. INVITE sips:+49170738x...@sip.domain.com SIP/2.0 Call-Id: c64e6615c79ab23501ad13f2e1a58918@10.77.26.75 CSeq: 1 INVITE Via: SIP/2.0/TLS 10.77.26.75:59076;branch=z9hG4bK127109c14cd3b59c9ef9909b737982ab Max-Forwards: 70 From: +491713x sips:usern...@sip.domain.com;tag=yRkyOWfbq To: sips:+4917073xx...@sip.domain.com Contact: sips:00@80.187.x.x:62510;transport=tls Allow: ACK,BYE User-Agent: SomeUserAgent Content-Type: application/sdp Content-Length: 138 v=0 o=- 1349965870484 1349965870484 IN IP4 10.77.26.75 s=- c=IN IP4 10.77.26.75 t=0 0 m=audio 37566 RTP/AVP 0 a=rtpmap:0 PCMU/8000 The problem was observed with opensips 1.8.1-tls and opensips-1.7.2-tls . Cheers, Dragos -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-15 04:27 Message: Hi Bogdan, INVITE sips:+4917133xx...@sip.domain.com SIP/2.0 Call-Id: 6484f90259156c8d702a1cae0eb49f27@10.208.83.156 CSeq: 1 INVITE Via: SIP/2.0/TLS 10.208.83.156:53912;branch=z9hG4bK2929012bef3d8abb931df26bd8fa498c Max-Forwards: 70 From: +4917073x sips:xx...@sis.secusmart.com;tag=IhJICbbyh To: sips:+4917133xx...@sip.domain.com Contact: sips:xx@80.187.x.x:52316;transport=tls Allow: ACK,BYE User-Agent: SomeUserAgent Content-Type: application/sdp Content-Length: 142 v=0 o=- 1350298945023 1350298945023 IN IP4 10.208.83.156 s=- c=IN IP4 10.208.83.156 t=0 0 m=audio 58639 RTP/AVP 0 a=rtpmap:0 PCMU/8000 | INVITE || tls:80.187.x.x:5231 | tls:212.162.x.x:5061 | IhJICbbyh | in| 2012-10-15 13:02:24 | CRITICAL:siptrace:sip_trace: xXx to ip is [tls:212.162.x.x:5061] CRITICAL:siptrace:sip_trace: xXx from ip is [tls:80.187.x.x:52316] The log entries (printed with the patch you provided) look correct, the `fromip` and `toip` fields are showing truncated values in the sip_trace table for most of the request and replies. Cheers, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-12 06:30 Message: Dragos, apply this patch - it will print to logs (on critical level) the calculated FROMIP and TOIP values. When you find bogus entries in siptrace, you can try to correlate with the log to see if the values from logs are also truncated. Thanks and regards, Bogdan -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-12 04:51 Message: Hi Yes, it happens very often,I don't know why . Sometime it puts the correct values into the fields (for messages within the same dialog I could see some entries -requests or replies - added with the correct port , but some are missing one or two digits ), If you provide the patch I'll apply it. Cheers, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-12 04:22 Message: Can you reproduce that? if so, I will provide a small patch to print some extra logs - the idea is to see if the truncation comes from the siptrace or the mysql module Regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3576351group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9324] branches/1.8/modules/cfgutils
Revision: 9324 http://opensips.svn.sourceforge.net/opensips/?rev=9324view=rev Author: liviuchircu Date: 2012-10-15 12:04:00 + (Mon, 15 Oct 2012) Log Message: --- Backport from trunk (rev #9283) Fixed the cfgutils set_count() function issue, where script execution is stopped when returning 0 value. The result is now obtained by passing a pvar as the 2nd parameter. Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9283view=rev Modified Paths: -- branches/1.8/modules/cfgutils/README branches/1.8/modules/cfgutils/cfgutils.c branches/1.8/modules/cfgutils/doc/cfgutils_admin.xml This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3576351 ] sip_trace module bug
Bugs item #3576351, was opened at 2012-10-11 07:53 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3576351group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.8.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dragos Oancea (dragosoancea) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: sip_trace module bug Initial Comment: Hi The siptrace module reports a wrong value in the `fromip` field of the sip_trace table. For example , for this INVITE, coming from tls:80.187.x.x:62510 , I would expect the value tls:80.187.x.x:62510 to be added in the `fromip` field, but it's adding tls:80.187.x.x:625 instead . It's missing two digits from the port value. Also , sometimes it would put its local port (in my case 5061) instead of the remote port in the `fromip` or `toip` fields. INVITE sips:+49170738x...@sip.domain.com SIP/2.0 Call-Id: c64e6615c79ab23501ad13f2e1a58918@10.77.26.75 CSeq: 1 INVITE Via: SIP/2.0/TLS 10.77.26.75:59076;branch=z9hG4bK127109c14cd3b59c9ef9909b737982ab Max-Forwards: 70 From: +491713x sips:usern...@sip.domain.com;tag=yRkyOWfbq To: sips:+4917073xx...@sip.domain.com Contact: sips:00@80.187.x.x:62510;transport=tls Allow: ACK,BYE User-Agent: SomeUserAgent Content-Type: application/sdp Content-Length: 138 v=0 o=- 1349965870484 1349965870484 IN IP4 10.77.26.75 s=- c=IN IP4 10.77.26.75 t=0 0 m=audio 37566 RTP/AVP 0 a=rtpmap:0 PCMU/8000 The problem was observed with opensips 1.8.1-tls and opensips-1.7.2-tls . Cheers, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-15 05:04 Message: Could you check the table format ? Do desc siptrace and see what are the sizes of the fromip and toip fields in the table - maybe the truncating is done by db. -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-15 04:27 Message: Hi Bogdan, INVITE sips:+4917133xx...@sip.domain.com SIP/2.0 Call-Id: 6484f90259156c8d702a1cae0eb49f27@10.208.83.156 CSeq: 1 INVITE Via: SIP/2.0/TLS 10.208.83.156:53912;branch=z9hG4bK2929012bef3d8abb931df26bd8fa498c Max-Forwards: 70 From: +4917073x sips:xx...@sis.secusmart.com;tag=IhJICbbyh To: sips:+4917133xx...@sip.domain.com Contact: sips:xx@80.187.x.x:52316;transport=tls Allow: ACK,BYE User-Agent: SomeUserAgent Content-Type: application/sdp Content-Length: 142 v=0 o=- 1350298945023 1350298945023 IN IP4 10.208.83.156 s=- c=IN IP4 10.208.83.156 t=0 0 m=audio 58639 RTP/AVP 0 a=rtpmap:0 PCMU/8000 | INVITE || tls:80.187.x.x:5231 | tls:212.162.x.x:5061 | IhJICbbyh | in| 2012-10-15 13:02:24 | CRITICAL:siptrace:sip_trace: xXx to ip is [tls:212.162.x.x:5061] CRITICAL:siptrace:sip_trace: xXx from ip is [tls:80.187.x.x:52316] The log entries (printed with the patch you provided) look correct, the `fromip` and `toip` fields are showing truncated values in the sip_trace table for most of the request and replies. Cheers, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-12 06:30 Message: Dragos, apply this patch - it will print to logs (on critical level) the calculated FROMIP and TOIP values. When you find bogus entries in siptrace, you can try to correlate with the log to see if the values from logs are also truncated. Thanks and regards, Bogdan -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-12 04:51 Message: Hi Yes, it happens very often,I don't know why . Sometime it puts the correct values into the fields (for messages within the same dialog I could see some entries -requests or replies - added with the correct port , but some are missing one or two digits ), If you provide the patch I'll apply it. Cheers, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-12 04:22 Message: Can you reproduce that? if so, I will provide a small patch to print some extra logs - the idea is to see if the truncation comes from the siptrace or the mysql module Regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3576351group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3574453 ] b2b_logic: too small setup timeout when topology hiding
Bugs item #3574453, was opened at 2012-10-04 05:25 Message generated for change (Comment added) made by nikbyte You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3574453group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.8.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Altmann (nikbyte) Assigned to: Nobody/Anonymous (nobody) Summary: b2b_logic: too small setup timeout when topology hiding Initial Comment: When b2b creates topology hiding scenario, it setups too small call setup time: /* if it will not be confirmed - delete */ tuple-lifetime = 60 + get_ticks(); When alice calls bob and bob don't answer for 60 seconds, b2b send CANCEL to both sides. I think we should give possibility to configure this parameter, either in AVP or b2b_init_request flags like b2b_init_request(top hiding/t300). I'd can to write the patch after discussion about what method to use. -- Comment By: Nick Altmann (nikbyte) Date: 2012-10-15 05:10 Message: Here are two patches: 1. opensips_b2bl_tc_init_time_v1.patch Adds module param b2bl_th_init_timeout with default value 60 to setup initial b2b timeout for topology hiding scenario. 2. opensips_b2bl_tc_init_time_v1.patch Adds module parameter as previous patch, but also adds per b2b session flag t[number] for b2b_init_request. Usage examples: b2b_init_request(top hiding/t60), b2b_init_request(top hiding/t300). Number length is not fixed. You may choose. :-) If one or another patch will be applied, I'll add documentation patch for it. -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-12 07:04 Message: Hi Nick, Normally the lifetime is controlled via the scenario XML, so it is per scenario. Of course, the TH does not have a scenario XML. I would go for a module param or by a flag-like approach - depending if we want to control this per scenario (like for other cases) or per instance of scenario. Regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3574453group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3576351 ] sip_trace module bug
Bugs item #3576351, was opened at 2012-10-11 07:53 Message generated for change (Comment added) made by dragosoancea You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3576351group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.8.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dragos Oancea (dragosoancea) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: sip_trace module bug Initial Comment: Hi The siptrace module reports a wrong value in the `fromip` field of the sip_trace table. For example , for this INVITE, coming from tls:80.187.x.x:62510 , I would expect the value tls:80.187.x.x:62510 to be added in the `fromip` field, but it's adding tls:80.187.x.x:625 instead . It's missing two digits from the port value. Also , sometimes it would put its local port (in my case 5061) instead of the remote port in the `fromip` or `toip` fields. INVITE sips:+49170738x...@sip.domain.com SIP/2.0 Call-Id: c64e6615c79ab23501ad13f2e1a58918@10.77.26.75 CSeq: 1 INVITE Via: SIP/2.0/TLS 10.77.26.75:59076;branch=z9hG4bK127109c14cd3b59c9ef9909b737982ab Max-Forwards: 70 From: +491713x sips:usern...@sip.domain.com;tag=yRkyOWfbq To: sips:+4917073xx...@sip.domain.com Contact: sips:00@80.187.x.x:62510;transport=tls Allow: ACK,BYE User-Agent: SomeUserAgent Content-Type: application/sdp Content-Length: 138 v=0 o=- 1349965870484 1349965870484 IN IP4 10.77.26.75 s=- c=IN IP4 10.77.26.75 t=0 0 m=audio 37566 RTP/AVP 0 a=rtpmap:0 PCMU/8000 The problem was observed with opensips 1.8.1-tls and opensips-1.7.2-tls . Cheers, Dragos -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-15 05:32 Message: mysql desc sip_trace ; +-+--+--+-+-++ | Field | Type | Null | Key | Default | Extra | +-+--+--+-+-++ | id | int(10) unsigned | NO | PRI | NULL| auto_increment | | date| datetime | NO | MUL | 1900-01-01 00:00:01 | | | callid | varchar(255) | NO | MUL | | | | traced_user | varchar(128) | NO | MUL | | | | msg | text | NO | | NULL| | | method | varchar(50) | NO | | | | | status | varchar(128) | NO | | | | | fromip | varchar(50) | NO | MUL | | | | toip| varchar(50) | NO | | | | | fromtag | varchar(64) | NO | | | | | direction | varchar(4) | NO | | | | | time_stamp | timestamp| NO | | CURRENT_TIMESTAMP | | +-+--+--+-+-++ 12 rows in set (0.01 sec) They are varchar(50) , there should be enough space. Also , sometimes the same ip:port pair is inserted correctly - for example it could we wrong for the received INVITE, but it could be correct for the relayed BYE . -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-15 05:04 Message: Could you check the table format ? Do desc siptrace and see what are the sizes of the fromip and toip fields in the table - maybe the truncating is done by db. -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-15 04:27 Message: Hi Bogdan, INVITE sips:+4917133xx...@sip.domain.com SIP/2.0 Call-Id: 6484f90259156c8d702a1cae0eb49f27@10.208.83.156 CSeq: 1 INVITE Via: SIP/2.0/TLS 10.208.83.156:53912;branch=z9hG4bK2929012bef3d8abb931df26bd8fa498c Max-Forwards: 70 From: +4917073x sips:xx...@sis.secusmart.com;tag=IhJICbbyh To: sips:+4917133xx...@sip.domain.com Contact: sips:xx@80.187.x.x:52316;transport=tls Allow: ACK,BYE User-Agent: SomeUserAgent Content-Type: application/sdp Content-Length: 142 v=0 o=- 1350298945023 1350298945023 IN IP4 10.208.83.156 s=- c=IN IP4 10.208.83.156 t=0 0 m=audio 58639 RTP/AVP 0 a=rtpmap:0 PCMU/8000 | INVITE || tls:80.187.x.x:5231 | tls:212.162.x.x:5061 | IhJICbbyh | in| 2012-10-15 13:02:24 | CRITICAL:siptrace:sip_trace: xXx to ip is [tls:212.162.x.x:5061] CRITICAL:siptrace:sip_trace: xXx from ip is [tls:80.187.x.x:52316] The log entries (printed with the patch you provided) look correct, the `fromip` and `toip`
[OpenSIPS-Devel] SF.net SVN: opensips:[9326] branches/1.8/modules/b2b_logic/b2bl_db.c
Revision: 9326 http://opensips.svn.sourceforge.net/opensips/?rev=9326view=rev Author: osas Date: 2012-10-15 13:07:08 + (Mon, 15 Oct 2012) Log Message: --- b2b_logic: fix removal of expired tuples while loading them from db - backport from trunk: Rev 9319 Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9319view=rev Modified Paths: -- branches/1.8/modules/b2b_logic/b2bl_db.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9327] branches/1.7/modules/b2b_logic/b2bl_db.c
Revision: 9327 http://opensips.svn.sourceforge.net/opensips/?rev=9327view=rev Author: osas Date: 2012-10-15 13:07:57 + (Mon, 15 Oct 2012) Log Message: --- b2b_logic: fix removal of expired tuples while loading them from db - backport from trunk: Rev 9319 Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9319view=rev Modified Paths: -- branches/1.7/modules/b2b_logic/b2bl_db.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[9319] trunk/modules/b2b_logic/b2bl_db.c
But of course. Already done. -ovidiu On Mon, Oct 15, 2012 at 4:52 AM, Bogdan-Andrei Iancu bog...@opensips.org wrote: Hi Ovidiu, Shouldn't be this backported ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 10/13/2012 08:34 PM, Ovidiu Sas wrote: Revision: 9319 http://opensips.svn.sourceforge.net/opensips/?rev=9319view=rev Author: osas Date: 2012-10-13 16:34:33 + (Sat, 13 Oct 2012) Log Message: --- b2b_logic: fix removal of expired tuples while loading them from db Modified Paths: -- trunk/modules/b2b_logic/b2bl_db.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3577322 ] modules/drouting: document how to specify weights
Bugs item #3577322, was opened at 2012-10-15 06:56 Message generated for change (Tracker Item Submitted) made by shimaore You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3577322group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: docs Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: shimaore (shimaore) Assigned to: Nobody/Anonymous (nobody) Summary: modules/drouting: document how to specify weights Initial Comment: Although the documentation for the drouting module indicates we can assign weights to gateways or carriers, it does not say how. drouting.xml should be modified to add the specification, and maybe an example: listitemparalist of GWs/carriers (string) [...] For each ID (GW or carrier) you may specify a weight by appending quote=/quote, followed by a numerical weight, to the quotegwid/quote or the quotecarrierid/quote. [...] Example of list: quotegw1,gw4,#cr3/quote quotegw1=10,gw4=10,#cr3=80/quote -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3577322group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3577353 ] startup_route not executed
Bugs item #3577353, was opened at 2012-10-15 08:46 Message generated for change (Tracker Item Submitted) made by dragosoancea You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3577353group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: core Group: 1.8.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dragos Oancea (dragosoancea) Assigned to: Nobody/Anonymous (nobody) Summary: startup_route not executed Initial Comment: Hi I can confirm the exact same confusing behavior described here: http://lists.opensips.org/pipermail/users/2012-June/022120.html Regards, Dragos -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3577353group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3532144 ] set_count() may return 0
Bugs item #3532144, was opened at 2012-06-05 05:51 Message generated for change (Comment added) made by liviuchircu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3532144group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.8.x Status: Closed Resolution: Fixed Priority: 7 Private: No Submitted By: Bogdan-Andrei Iancu (bogdan_iancu) Assigned to: Liviu Chircu (liviuchircu) Summary: set_count() may return 0 Initial Comment: When doing the counting, set_count() may return 0 (0 values for a pvar) - this will break the script. -- Comment By: Liviu Chircu (liviuchircu) Date: 2012-10-15 09:53 Message: Backported to both 1.8 and 1.7 Liviu -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-15 04:10 Message: Liviu, please backport this fix to 1.8 and 1.7 branches. Thanks and regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3532144group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
