[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 dmsanders 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: David Sanders (dmsanders) Date: 2012-10-19 00:31 Message: I've also encountered this issue as described, with opensips 1.8.0-tls. In addition to the described case, I've seen times where the field will look like sip:80.187.x.x:625 1, with a space present in the port number. This seems to suggest it isn't truncation. -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-17 01:35 Message: Hi Bogdan, No , I am not using that feature. Regards, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-16 10:40 Message: Are you using buffering and merging for multiple INSERTs ? http://www.opensips.org/Resources/DocsCoreFcn18#toc69 Regards, Bogdan -- 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
[OpenSIPS-Devel] SF.net SVN: opensips:[9348] trunk/modules/dialog/dlg_db_handler.c
Revision: 9348 http://opensips.svn.sourceforge.net/opensips/?rev=9348view=rev Author: vladut-paiu Date: 2012-10-19 08:36:17 + (Fri, 19 Oct 2012) Log Message: --- fixed mem leak run sync MI command under lock Modified Paths: -- trunk/modules/dialog/dlg_db_handler.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:[9349] branches/1.8/modules/dialog/dlg_db_handler.c
Revision: 9349 http://opensips.svn.sourceforge.net/opensips/?rev=9349view=rev Author: vladut-paiu Date: 2012-10-19 08:45:04 + (Fri, 19 Oct 2012) Log Message: --- backport from trunk (rev #9348) fixed mem leak run sync MI command under lock Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9348view=rev Modified Paths: -- branches/1.8/modules/dialog/dlg_db_handler.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:[9350] trunk
Revision: 9350 http://opensips.svn.sourceforge.net/opensips/?rev=9350view=rev Author: liviuchircu Date: 2012-10-19 08:47:49 + (Fri, 19 Oct 2012) Log Message: --- Fixed ds_ping_interval documentation and a compile warning. Modified Paths: -- trunk/modules/dispatcher/README trunk/modules/dispatcher/doc/dispatcher_admin.xml trunk/statistics.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-Patches-3575739 ] Follow resource-list references on RLS
Patches item #3575739, was opened at 2012-10-09 06:51 Message generated for change (Comment added) made by saghul You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=3575739group_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: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: saghul (saghul) Assigned to: Nobody/Anonymous (nobody) Summary: Follow resource-list references on RLS Initial Comment: Hi, This is the first patch of a series of patches to enhance presence support (including OMA) in OpenSIPS. The attached patch adds the ability to follow references from a rls-services to a resource-lists document. The diff is quite big not only because of the actual feature, but because I had to fix some bugs as I worked on the feature as well, and separating those was not really possible. I'm actively working on presence, so I'm willing to maintain this code, as well as fix any issues that may arise with it. So far I discovered none during testing :-) If I get a ok I can merge it to trunk myself and we take it from there. Regards, -- Saúl Ibarra Corretgé AG Projects -- Comment By: saghul (saghul) Date: 2012-10-19 04:38 Message: I just added a second patch, which adds a new mi command: rls_update_subscriptions, which needs to be called if the RLS services document or resource-lists was modified, in order to start new backend subscriptions or stop old ones if required. Please have a glance at this, the diff is so big and affects so many files that it's getting complicated to manage.These are new features which will go to trunk anyway, so if issues are discovered I'll get them fixed, I promise :-) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=3575739group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9351] trunk/modules/presence/presentity.c
Revision: 9351 http://opensips.svn.sourceforge.net/opensips/?rev=9351view=rev Author: saghul Date: 2012-10-19 11:42:14 + (Fri, 19 Oct 2012) Log Message: --- Fixed handling PUBLISH with Expires: 0 Send required NOTIFY requests after DB has been updated Modified Paths: -- trunk/modules/presence/presentity.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:[9352] branches/1.8/modules/presence/presentity.c
Revision: 9352 http://opensips.svn.sourceforge.net/opensips/?rev=9352view=rev Author: saghul Date: 2012-10-19 11:45:59 + (Fri, 19 Oct 2012) Log Message: --- Backport from trunk r9351 Fixed handling PUBLISH with Expires: 0 Send required NOTIFY requests after DB has been updated Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9351view=rev Modified Paths: -- branches/1.8/modules/presence/presentity.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:[9353] branches/1.7/modules/presence/presentity.c
Revision: 9353 http://opensips.svn.sourceforge.net/opensips/?rev=9353view=rev Author: saghul Date: 2012-10-19 11:47:35 + (Fri, 19 Oct 2012) Log Message: --- Backport from trunk r9351 Fixed handling PUBLISH with Expires: 0 Send required NOTIFY requests after DB has been updated Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9351view=rev Modified Paths: -- branches/1.7/modules/presence/presentity.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:[9354] trunk/modules
Revision: 9354 http://opensips.svn.sourceforge.net/opensips/?rev=9354view=rev Author: saghul Date: 2012-10-19 11:54:36 + (Fri, 19 Oct 2012) Log Message: --- Fixed handling of terminated subscriptions in PUA and RLS DB needs to be updated with the terminated state so that RLS can use this information in the RLMI part os the RLS NOTIFY. Also don't immediately delete the subscription from the PUA to allow the final NOTIFY to be processed. Modified Paths: -- trunk/modules/pua/send_subscribe.c trunk/modules/rls/resource_notify.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:[9355] branches/1.8/modules
Revision: 9355 http://opensips.svn.sourceforge.net/opensips/?rev=9355view=rev Author: saghul Date: 2012-10-19 11:57:49 + (Fri, 19 Oct 2012) Log Message: --- BAckport from trunk r9354 Fixed handling of terminated subscriptions in PUA and RLS DB needs to be updated with the terminated state so that RLS can use this information in the RLMI part os the RLS NOTIFY. Also don't immediately delete the subscription from the PUA to allow the final NOTIFY to be processed. Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9354view=rev Modified Paths: -- branches/1.8/modules/pua/send_subscribe.c branches/1.8/modules/rls/resource_notify.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:[9356] branches/1.7/modules
Revision: 9356 http://opensips.svn.sourceforge.net/opensips/?rev=9356view=rev Author: saghul Date: 2012-10-19 11:58:58 + (Fri, 19 Oct 2012) Log Message: --- Backport from trunk r9354 Fixed handling of terminated subscriptions in PUA and RLS DB needs to be updated with the terminated state so that RLS can use this information in the RLMI part os the RLS NOTIFY. Also don't immediately delete the subscription from the PUA to allow the final NOTIFY to be processed. Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9354view=rev Modified Paths: -- branches/1.7/modules/pua/send_subscribe.c branches/1.7/modules/rls/resource_notify.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-3578383 ] Multihomed B2B. Again.
Bugs item #3578383, was opened at 2012-10-19 07:18 Message generated for change (Tracker Item Submitted) made by nikbyte You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3578383group_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: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Altmann (nikbyte) Assigned to: Nobody/Anonymous (nobody) Summary: Multihomed B2B. Again. Initial Comment: B2B doesn't take attention on transport tag in RURI. For example: B2B receives UDP packet with transport=TCP in RURI, but whatever sends it via UDP. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3578383group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9357] branches/1.8/modules/dispatcher
Revision: 9357 http://opensips.svn.sourceforge.net/opensips/?rev=9357view=rev Author: liviuchircu Date: 2012-10-19 14:43:41 + (Fri, 19 Oct 2012) Log Message: --- Backport from trunk (rev #9350) Fixed ds_ping_interval documentation Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=9350view=rev Modified Paths: -- branches/1.8/modules/dispatcher/README branches/1.8/modules/dispatcher/doc/dispatcher_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-19 09:08 Message: Ok, last question - have you noticed a pattern on what kind of records have bogus port values ? like request, in or out, ? or maybe for replies ? It will help me to dig into the right code. Regards, Bogdan -- Comment By: David Sanders (dmsanders) Date: 2012-10-19 00:31 Message: I've also encountered this issue as described, with opensips 1.8.0-tls. In addition to the described case, I've seen times where the field will look like sip:80.187.x.x:625 1, with a space present in the port number. This seems to suggest it isn't truncation. -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-17 01:35 Message: Hi Bogdan, No , I am not using that feature. Regards, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-16 10:40 Message: Are you using buffering and merging for multiple INSERTs ? http://www.opensips.org/Resources/DocsCoreFcn18#toc69 Regards, Bogdan -- 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:
[OpenSIPS-Devel] [ opensips-Bugs-3578406 ] Postgres create DB error
Bugs item #3578406, was opened at 2012-10-19 09:45 Message generated for change (Tracker Item Submitted) made by tganzeboom You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=3578406group_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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Toine (tganzeboom) Assigned to: Nobody/Anonymous (nobody) Summary: Postgres create DB error Initial Comment: Downloaded the latest 1.8, but got this error: ERROR: relation dr_gateways_gwid_seq does not exist Also, I have to give my password multiple times. I have read this in earlier versions, but it seems to have come back? Error is also below, included this for clearity /opensips/1.8# opensipsdbctl create database engine 'postgres' loaded INFO: creating database opensips ... Password for user postgres: Password for user postgres: Creating core table: standard Password for user postgres: NOTICE: CREATE TABLE / UNIQUE will create implicit index version_t_name_idx for table version Creating core table: acc Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence acc_id_seq for serial column acc.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index acc_pkey for table acc NOTICE: CREATE TABLE will create implicit sequence missed_calls_id_seq for serial column missed_calls.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index missed_calls_pkey for table missed_calls Creating core table: domain Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence domain_id_seq for serial column domain.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index domain_pkey for table domain NOTICE: CREATE TABLE / UNIQUE will create implicit index domain_domain_idx for table domain Creating core table: group Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence grp_id_seq for serial column grp.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index grp_pkey for table grp NOTICE: CREATE TABLE / UNIQUE will create implicit index grp_account_group_idx for table grp NOTICE: CREATE TABLE will create implicit sequence re_grp_id_seq for serial column re_grp.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index re_grp_pkey for table re_grp Creating core table: permissions Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence address_id_seq for serial column address.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index address_pkey for table address Creating core table: registrar Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence aliases_id_seq for serial column aliases.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index aliases_pkey for table aliases Creating core table: usrloc Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence location_id_seq for serial column location.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index location_pkey for table location NOTICE: CREATE TABLE / UNIQUE will create implicit index location_account_contact_idx for table location Creating core table: msilo Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence silo_id_seq for serial column silo.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index silo_pkey for table silo Creating core table: alias_db Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence dbaliases_id_seq for serial column dbaliases.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index dbaliases_pkey for table dbaliases NOTICE: CREATE TABLE / UNIQUE will create implicit index dbaliases_alias_idx for table dbaliases Creating core table: uri_db Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence uri_id_seq for serial column uri.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index uri_pkey for table uri NOTICE: CREATE TABLE / UNIQUE will create implicit index uri_account_idx for table uri Creating core table: nathelper Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence nh_sockets_id_seq for serial column nh_sockets.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index nh_sockets_pkey for table nh_sockets Creating core table: speeddial Password for user postgres: NOTICE: CREATE TABLE will create implicit sequence speed_dial_id_seq for serial column speed_dial.id NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index speed_dial_pkey for table speed_dial NOTICE: CREATE TABLE / UNIQUE will create implicit index speed_dial_speed_dial_idx for table speed_dial Creating core table: avpops Password for user postgres: NOTICE: CREATE TABLE will create implicit
[OpenSIPS-Devel] SF.net SVN: opensips:[9358] trunk/modules/pi_http/http_fnc.c
Revision: 9358 http://opensips.svn.sourceforge.net/opensips/?rev=9358view=rev Author: osas Date: 2012-10-19 17:03:08 + (Fri, 19 Oct 2012) Log Message: --- pi_http: fix typo for DB_UPDATE command Modified Paths: -- trunk/modules/pi_http/http_fnc.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-3576351 ] sip_trace module bug
Bugs item #3576351, was opened at 2012-10-11 07:53 Message generated for change (Comment added) made by dmsanders 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: David Sanders (dmsanders) Date: 2012-10-19 16:24 Message: I only see it occurring on direction = 'in'. In addition, it only affects the fromip field. It seems to be truncated to 22 characters. If there is a space in the port number it is only if the fromip was less than 22 characters. For example udp:xx.xxx.x.xx:5060 1 is a pattern I see a lot. 1 seems to be the most common extra character, but I also see 0, 4, 7, 9, etc. -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-19 09:08 Message: Ok, last question - have you noticed a pattern on what kind of records have bogus port values ? like request, in or out, ? or maybe for replies ? It will help me to dig into the right code. Regards, Bogdan -- Comment By: David Sanders (dmsanders) Date: 2012-10-19 00:31 Message: I've also encountered this issue as described, with opensips 1.8.0-tls. In addition to the described case, I've seen times where the field will look like sip:80.187.x.x:625 1, with a space present in the port number. This seems to suggest it isn't truncation. -- Comment By: Dragos Oancea (dragosoancea) Date: 2012-10-17 01:35 Message: Hi Bogdan, No , I am not using that feature. Regards, Dragos -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2012-10-16 10:40 Message: Are you using buffering and merging for multiple INSERTs ? http://www.opensips.org/Resources/DocsCoreFcn18#toc69 Regards, Bogdan -- 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
