Re: [OpenSIPS-Devel] PATCH: use all SRV records for mediaproxy dispatcher entries
Hi, On Oct 24, 2012, at 6:11 AM, Henk Hesselink wrote: > Hi, > > The mediaproxy relay only uses the first SRV record returned for each > entry in the dispatcher line in the config file. The attached patch > changes that to use all returned records. This makes it possible to > group dispatchers, and also means the config file doesn't need to be > changed (and the relay restarted) every time the list of dispatchers > changes. The patch is against mediaproxy 2.4.2. > Thanks for the patch, I'll have a look at it. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] PATCH: use all SRV records for mediaproxy dispatcher entries
Hi,
The mediaproxy relay only uses the first SRV record returned for each
entry in the dispatcher line in the config file. The attached patch
changes that to use all returned records. This makes it possible to
group dispatchers, and also means the config file doesn't need to be
changed (and the relay restarted) every time the list of dispatchers
changes. The patch is against mediaproxy 2.4.2.
Regards,
Henk Hesselink
--- relay.py-2.4.2 2010-07-15 11:28:32.0 +0200
+++ relay.py2012-10-24 03:09:51.360810895 +0200
@@ -257,9 +257,10 @@
return KeepRunning
def _cb_got_srv(self, (answers, auth, add), port):
-for answer in answers:
-if answer.type == dns.SRV and answer.payload and
answer.payload.target != dns.Name("."):
-return str(answer.payload.target), port
+srvs = [(str(answer.payload.target), port) for answer in answers
+if answer.type == dns.SRV and answer.payload and
answer.payload.target != dns.Name(".")]
+if len(srvs):
+return srvs
raise DomainError
def _eb_no_srv(self, failure, addr, port):
@@ -272,7 +273,12 @@
def _cb_got_all(self, results):
if not self.shutting_down:
-dispatchers = [result[1] for result in results if result[0] and
result[1] is not None]
+dispatchers = []
+for dispatcher in [result[1] for result in results if result[0]
and result[1] is not None]:
+if type(dispatcher) == type([]):
+dispatchers.extend(dispatcher)
+else:
+dispatchers.append(dispatcher)
self.update_dispatchers(dispatchers)
def update_dispatchers(self, dispatchers):
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9376] trunk/modules/rls/notify.c
Revision: 9376 http://opensips.svn.sourceforge.net/opensips/?rev=9376&view=rev Author: saghul Date: 2012-10-23 13:33:01 + (Tue, 23 Oct 2012) Log Message: --- RLS: Fixed memory leak xmlFree was used to free a document, instead of xmlFreeDoc Modified Paths: -- trunk/modules/rls/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
Re: [OpenSIPS-Devel] Patch for RLS/USRLOC module
Hi, On Jun 19, 2012, at 7:38 PM, BNML wrote: > Hi, > > Attached is a patch that allow one to store an AVP in a column of the > "location" table, so that you get the info back when you will do the > lookup. It can be sometime usefull. I will quickly upload it also it on > the tracker. An invalid XDMS's document could lead to invalid pointer > dereference, attached is a fix for RLS module. > > I profit from that mail to inform devel's users that we are seeking > someone to get a job there : > http://www.andrexen.com/wp-content/uploads/2012/04/HR-SEARCH-ANDREXEN-FR-SIP-ENGINEER-201204.pdf > I just applied the RLS fix on trunk r9375, thanks! Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[9375] trunk/modules/rls/subscribe.c
Revision: 9375 http://opensips.svn.sourceforge.net/opensips/?rev=9375&view=rev Author: saghul Date: 2012-10-23 13:28:11 + (Tue, 23 Oct 2012) Log Message: --- Fixed potential invalid pointer dereference Credits to BNML Modified Paths: -- trunk/modules/rls/subscribe.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-3578406 ] Postgres create DB error
Bugs item #3578406, was opened at 2012-10-19 09:45 Message generated for change (Comment added) made by tganzeboom You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3578406&group_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: Fixed Priority: 5 Private: No Submitted By: Toine (tganzeboom) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) 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
[OpenSIPS-Devel] [ opensips-Bugs-3578383 ] Path+usrloc+b2b=lost transport (Multihomed B2B. Again.)
Bugs item #3578383, was opened at 2012-10-19 07:18
Message generated for change (Comment added) made by nikbyte
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3578383&group_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: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: Path+usrloc+b2b=lost transport (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.
--
>Comment By: Nick Altmann (nikbyte)
Date: 2012-10-23 03:27
Message:
Here is my patch for path module:
1. To add transport to first route if transport != udp.
2. To parse transport tag when doing path_rr_callback.
opensips_path_tcp_v1.patch
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-10-23 01:42
Message:
The problem is fixed on b2b, before b2b_init_request:
if (($du != null) && ($hdr(Route) =~ ";transport=tcp")) $du = "sip:" + $dd
+ ":" + $dp + ";transport=tcp";
But I think the path module needs to be patched:
1. To add transport to first route if transport != udp.
2. To parse transport tag when doing path_rr_callback.
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-10-21 22:18
Message:
I have mixed multiple opensips setup with b2b, usrloc, path and another
modules.
I deeply investigated the problem and it's not in b2b.
In my setup b2b sometimes receives packets with preloaded routes using path
module with use_received=1.
I found that when REGISTER passes from one opensips to another, path module
adds something like:
with enable_double_path=0:
with enable_double_path=1 (I use this):
,
Then it saved by save("table", "p0") on second opensips in database.
The next step is call from second opensips.
It receives INVITE, calls lookup("table") and adds preloaded route:
Route:
,
then sends it to first (b2b) opensips.
b2b-opensips receives this packet and in debug I see:
Oct 22 08:40:57 opensips-test-2-1 opensips[20655]: DBG:rr:after_loose:
Topmost route URI: 'sip:2.2.2.2;r2=on;lr;received=sip:8.8.8.8:55947' is me
Oct 22 08:40:57 opensips-test-2-1 opensips[20655]: DBG:rr:run_rr_callbacks:
callback id 0 entered with
Oct 22 08:40:57 opensips-test-2-1 opensips[20655]: DBG:core:parse_params:
Parsing params for:[r2=on;lr;received=sip:8.8.8.8:55947]
then, in script output
$du=sip:8.8.8.8:55947
As expected, b2b uses $du to route the packet, ignoring $ru.
So, it lost transport because transport is in second Route header.
--
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-10-21 08:14
Message:
Hi Nick,
If running in debug mode, when the initial request is processed by opensips
you should have a log like:
tm:t_uac: next_hop=
Could you confirm that the "uri" you have there points is the same as RURI
you had is script before triggering the b2b, and it still contain the
"transport" parameter.
Thanks and regards,
Bogdan
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3578383&group_id=232389
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-3579464 ] Postgres create DB error
Bugs item #3579464, was opened at 2012-10-23 02:22 Message generated for change (Comment added) made by tganzeboom You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3579464&group_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: Deleted Resolution: None >Priority: 1 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
[OpenSIPS-Devel] [ opensips-Bugs-3579464 ] Postgres create DB error
Bugs item #3579464, was opened at 2012-10-23 02:22 Message generated for change (Comment added) made by tganzeboom You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3579464&group_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
[OpenSIPS-Devel] [ opensips-Bugs-3579464 ] Postgres create DB error
Bugs item #3579464, was opened at 2012-10-23 02:22 Message generated for change (Tracker Item Submitted) made by tganzeboom You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3579464&group_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_s
[OpenSIPS-Devel] [ opensips-Bugs-3578383 ] Path+usrloc+b2b=lost transport (Multihomed B2B. Again.)
Bugs item #3578383, was opened at 2012-10-19 07:18
Message generated for change (Comment added) made by nikbyte
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3578383&group_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: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: Path+usrloc+b2b=lost transport (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.
--
>Comment By: Nick Altmann (nikbyte)
Date: 2012-10-23 01:42
Message:
The problem is fixed on b2b, before b2b_init_request:
if (($du != null) && ($hdr(Route) =~ ";transport=tcp")) $du = "sip:" + $dd
+ ":" + $dp + ";transport=tcp";
But I think the path module needs to be patched:
1. To add transport to first route if transport != udp.
2. To parse transport tag when doing path_rr_callback.
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-10-21 22:18
Message:
I have mixed multiple opensips setup with b2b, usrloc, path and another
modules.
I deeply investigated the problem and it's not in b2b.
In my setup b2b sometimes receives packets with preloaded routes using path
module with use_received=1.
I found that when REGISTER passes from one opensips to another, path module
adds something like:
with enable_double_path=0:
with enable_double_path=1 (I use this):
,
Then it saved by save("table", "p0") on second opensips in database.
The next step is call from second opensips.
It receives INVITE, calls lookup("table") and adds preloaded route:
Route:
,
then sends it to first (b2b) opensips.
b2b-opensips receives this packet and in debug I see:
Oct 22 08:40:57 opensips-test-2-1 opensips[20655]: DBG:rr:after_loose:
Topmost route URI: 'sip:2.2.2.2;r2=on;lr;received=sip:8.8.8.8:55947' is me
Oct 22 08:40:57 opensips-test-2-1 opensips[20655]: DBG:rr:run_rr_callbacks:
callback id 0 entered with
Oct 22 08:40:57 opensips-test-2-1 opensips[20655]: DBG:core:parse_params:
Parsing params for:[r2=on;lr;received=sip:8.8.8.8:55947]
then, in script output
$du=sip:8.8.8.8:55947
As expected, b2b uses $du to route the packet, ignoring $ru.
So, it lost transport because transport is in second Route header.
--
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-10-21 08:14
Message:
Hi Nick,
If running in debug mode, when the initial request is processed by opensips
you should have a log like:
tm:t_uac: next_hop=
Could you confirm that the "uri" you have there points is the same as RURI
you had is script before triggering the b2b, and it still contain the
"transport" parameter.
Thanks and regards,
Bogdan
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3578383&group_id=232389
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
