Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Brett,
You should have used the script in scripts/mysql/b2b_create.sql . What
you have missed is inserting in version table the version number for the
new tables
INSERT INTO version (table_name, table_version) values ('b2b_entities','1');
INSERT INTO version (table_name, table_version) values ('b2b_logic','1');
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/28/2010 01:46 AM, Brett Woollum wrote:
Hi Anca,
I tried to install from the 1.6 branch and I am getting errors about
the database version for b2b_entities:
Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]:
ERROR:core:db_check_table_version: invalid version 0 for table
b2b_entities found, expected 1
Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]:
ERROR:b2b_entities:mod_init: error during table version check
Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]:
ERROR:core:init_mod: failed to initialize module b2b_entities
Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]:
ERROR:core:main: error while initializing modules
Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]:
NOTICE:presence:destroy: destroy module ...
I used /usr/local/sbin/opensipsdbctl create to make the tables.
Is there information available that would tell me what modifications I
need to make to the b2b_entities table for it to work properly?
Brett Woollum
br...@woollum.com
- Original Message -
From: Anca Vamanu a...@opensips.org
To: users@lists.opensips.org
Sent: Tuesday, October 26, 2010 4:06:16 AM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently
Working/Not Working (Bug?)
Hi Brett,
Sorry, I was mistaken, I tested wrongly with 1.6 the first time. It
does work with 1.6 also, you can update from the 1.6 branch and check.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/26/2010 01:41 PM, Anca Vamanu wrote:
Hi Brett,
I have just tried your scenario with trunk and I see the 200 OK
reply. I have checked with 1.6 and indeed it seems to be a
problem. I think I will backport the changes in these two modules
- even though they are quite a lot, but there is no point in
debugging on old code when this problem is fixed.
So, I suggest for you to update from trunk, at least these two
modules - b2b_entities and b2b_logic.
Be aware that you will have to install the database tables also.
Regards,
--
Anca Vamanu
www.voice-system.ro
___ 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] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Got it.
I've updated the MySQL table and started OpenSIPS (which is version 1.6 from
the SVN head). I tried the calling again (with 2 transfers) and I now see the
202 Accepted message which is correct, but the second transfer is still failing
with the same error:
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:do_assign: no
value in right expression
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:do_assign:
error at line: 314
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:siptrace:sip_trace:
cannot parse FROM header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:rr:record_route:
From parsing failed
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:tm:new_t: no valid
From in INVITE
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:tm:t_newtran: new_t
failed
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:siptrace:trace_sl_onreply_out: cannot parse FROM header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2999]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2999]:
ERROR:core:parse_from_header: bad from header
Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2999]:
ERROR:b2b_entities:b2b_tm_cback: cannot parse From header
The call trace shows that OpenSIPS is not originating the new call leg out to
the phone that the call was transferred to (probably because of the error
above). I don't see any errors in the call trace with regard to the REFER
message (or any others) sent by the phones. The REFER looks the same with
different extensions for the first transfer and the second transfer. It seems
like OpenSIPS is just not handling the second transfer correctly.
Brett Woollum
br...@woollum.com
- Original Message -
From: Anca Vamanu a...@opensips.org
To: users@lists.opensips.org
Sent: Thursday, October 28, 2010 1:31:44 AM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not
Working (Bug?)
Hi Brett,
You should have used the script in scripts/mysql/b2b_create.sql . What you have
missed is inserting in version table the version number for the new tables
INSERT INTO version (table_name, table_version) values ('b2b_entities','1');
INSERT INTO version (table_name, table_version) values ('b2b_logic','1');
Regards,
--
Anca Vamanu www.voice-system.ro
On 10/28/2010 01:46 AM, Brett Woollum wrote:
Hi Anca,
I tried to install
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
opensipsdbctl should be able to properly create the b2b tables in 1.6 now (I defined them in the list of EXTRA_MODULES). Regards, Ovidiu Sas On Thu, Oct 28, 2010 at 5:39 PM, Brett Woollum br...@woollum.com wrote: Got it. I've updated the MySQL table and started OpenSIPS (which is version 1.6 from the SVN head). I tried the calling again (with 2 transfers) and I now see the 202 Accepted message which is correct, but the second transfer is still failing with the same error: Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:b2b_entities:b2b_prescript_f: cannot parse From header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:do_assign: no value in right expression Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:do_assign: error at line: 314 Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:siptrace:sip_trace: cannot parse FROM header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:rr:record_route: From parsing failed Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:tm:new_t: no valid From in INVITE Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:tm:t_newtran: new_t failed Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:siptrace:trace_sl_onreply_out: cannot parse FROM header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2998]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2999]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2999]: ERROR:core:parse_from_header: bad from header Oct 28 14:16:40 sip01 /usr/local/sbin/opensips[2999]: ERROR:b2b_entities:b2b_tm_cback: cannot parse From header The call trace shows that OpenSIPS is not originating the new call leg out to the phone that the call was transferred to (probably because of the error above). I don't see any errors in the call trace with regard to the REFER message (or any others) sent by the phones. The REFER looks the same with different extensions for the first transfer and the second transfer. It seems like OpenSIPS is just not handling the second transfer correctly. Brett Woollum br...@woollum.com - Original Message - From: Anca Vamanu a...@opensips.org To: users@lists.opensips.org Sent: Thursday, October 28, 2010 1:31:44 AM GMT -08:00 US/Canada Pacific Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?) Hi Brett, You should have used the script in scripts/mysql/b2b_create.sql . What you have missed is inserting in version table the version number for the new tables INSERT INTO version (table_name, table_version) values
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Anca, I tried to install from the 1.6 branch and I am getting errors about the database version for b2b_entities: Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]: ERROR:core:db_check_table_version: invalid version 0 for table b2b_entities found, expected 1 Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]: ERROR:b2b_entities:mod_init: error during table version check Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]: ERROR:core:init_mod: failed to initialize module b2b_entities Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]: ERROR:core:main: error while initializing modules Oct 27 15:45:30 sip01 /usr/local/sbin/opensips[15672]: NOTICE:presence:destroy: destroy module ... I used /usr/local/sbin/opensipsdbctl create to make the tables. Is there information available that would tell me what modifications I need to make to the b2b_entities table for it to work properly? Brett Woollum br...@woollum.com - Original Message - From: Anca Vamanu a...@opensips.org To: users@lists.opensips.org Sent: Tuesday, October 26, 2010 4:06:16 AM GMT -08:00 US/Canada Pacific Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?) Hi Brett, Sorry, I was mistaken, I tested wrongly with 1.6 the first time. It does work with 1.6 also, you can update from the 1.6 branch and check. Regards, -- Anca Vamanu www.voice-system.ro On 10/26/2010 01:41 PM, Anca Vamanu wrote: Hi Brett, I have just tried your scenario with trunk and I see the 200 OK reply. I have checked with 1.6 and indeed it seems to be a problem. I think I will backport the changes in these two modules - even though they are quite a lot, but there is no point in debugging on old code when this problem is fixed. So, I suggest for you to update from trunk, at least these two modules - b2b_entities and b2b_logic. Be aware that you will have to install the database tables also. Regards, -- Anca Vamanu www.voice-system.ro ___ 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] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Brett,
I have just tried your scenario with trunk and I see the 200 OK reply. I
have checked with 1.6 and indeed it seems to be a problem. I think I
will backport the changes in these two modules - even though they are
quite a lot, but there is no point in debugging on old code when this
problem is fixed.
So, I suggest for you to update from trunk, at least these two modules -
b2b_entities and b2b_logic.
Be aware that you will have to install the database tables also.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/21/2010 07:05 AM, Brett Woollum wrote:
Anca,
I've discovered that the REFER messages sent from the phones to the
OpenSIPS server/B2BUA are not receiving a 202 Accepted reply from the
B2BUA module, and as a result, the phones continue to re-send the
REFER's. The B2BUA module doesn't recognize the additional REFER's
because it has already torn down the original call leg. As a result
the additional REFER's are processed in the route script which is
wrong and causes the 404 Not Found errors.
Here is what's happening: (assume a call already exists):
The phone sends a REFER to the B2BUA
The B2BUA sends BYE back to the phone
The B2BUA invites the new leg of the call to the other phone
The original phone continues to send REFER's to the B2BUA module,
which responds with 404 Not Found's
I believe there should be a 202 Accepted sent from the B2BUA module to
the phone in response to the first REFER message, not a BYE (or maybe
both Accepted and BYE). But there is no 202 Accepted coming from the
B2BUA module to the phone.
Scroll to the bottom of http://www.woollum.com/temp/opensips.txt to
view my B2BUA XML config, which specifies that the B2BUA should
respond with a 202 Accepted before ending the call leg. This is not
happening like it should
I am running OpenSIPS 1.6.3 on CentOS 5.5 x64 (on an AMD platform).
Brett Woollum
br...@woollum.com
- Original Message -
From: Anca Vamanu a...@opensips.org
To: users@lists.opensips.org
Sent: Tuesday, October 19, 2010 2:20:15 AM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently
Working/Not Working (Bug?)
Hi Brett,
No, you needn't add anything else in your configuration file except
for the b2b_init_request for the initial Invite and the B2BUA should
know to handle the REFER that comes inside that dialog. What happens
is the the B2BUA does not find a matching dialog for that REFER
message .. I don't know why that is. I will examine the traces you
posted and try to reproduce this in the following days and let you know.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/19/2010 09:05 AM, Brett Woollum wrote:
Hello again Anca,
I've done more debugging, and I've found that the REFER packets
are all targeting my B2BUA address and getting a 404 response. It
seems to still be working, but I'm wondering if this is what is
causing the problem after the 2nd transfer.
In my log at http://www.woollum.com/temp/opensips_trace.html, you
can see the 404 Not Found's occurring at packet 9177. This one in
particular is generated for the packet above it (9175) that has
sip:b2...@1.2.3.4 in the header of the packet.
I've configured my B2BUA module with this entry:
modparam(b2b_entities, server_address, sip:b2...@1.2.3.4:5060)
and this is the config file that is creating the errors:
if (uri==myself) {
if (method==REGISTER) {
save(location);
exit;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup(location)) {
xlog(USRLOC LOOKUP: ERROR 404 - NOT FOUND $fu-$ru);
sl_send_reply(404, Not Found);
exit;
};
append_hf(P-hint: usrloc applied\r\n);
};
And this is what is generated in the OpenSIPS log:
Oct 18 22:56:42 sip01 /usr/local/sbin/opensips[4425]: USRLOC
LOOKUP: ERROR 404 - NOT FOUND sip:1...@1.2.3.4-sip:b2...@1.2.3.4:5060
Is there something I need to add to my configuration that handles
packets with b2...@1.2.3.4 as the destination ($ru)?
Brett Woollum
br...@woollum.com
- Original Message -
From: Brett Woollum br...@woollum.com
To: OpenSIPS users mailling list users@lists.opensips.org
Sent: Monday, October 18, 2010 5:09:34 PM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently
Working/Not Working (Bug?)
Hi Anca,
I set debug=6 but it does not appear to print any more detailed
information to my log (/var/log/messages).
I reviewed the sip trace I posted at
http://www.woollum.com/temp/opensips_trace.html and I still cannot
find any packets that are missing the header. The error log I
posted at http://www.woollum.com/temp/opensips.txt says that the
To field, From field, and RR field could not be parsed. It seems
as though the B2BUA module tried to open a new leg but didn't send
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Brett, Sorry, I was mistaken, I tested wrongly with 1.6 the first time. It does work with 1.6 also, you can update from the 1.6 branch and check. Regards, -- Anca Vamanu www.voice-system.ro On 10/26/2010 01:41 PM, Anca Vamanu wrote: Hi Brett, I have just tried your scenario with trunk and I see the 200 OK reply. I have checked with 1.6 and indeed it seems to be a problem. I think I will backport the changes in these two modules - even though they are quite a lot, but there is no point in debugging on old code when this problem is fixed. So, I suggest for you to update from trunk, at least these two modules - b2b_entities and b2b_logic. Be aware that you will have to install the database tables also. Regards, -- Anca Vamanu www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Anca,
I've discovered that the REFER messages sent from the phones to the OpenSIPS
server/B2BUA are not receiving a 202 Accepted reply from the B2BUA module, and
as a result, the phones continue to re-send the REFER's. The B2BUA module
doesn't recognize the additional REFER's because it has already torn down the
original call leg. As a result the additional REFER's are processed in the
route script which is wrong and causes the 404 Not Found errors.
Here is what's happening: (assume a call already exists):
The phone sends a REFER to the B2BUA
The B2BUA sends BYE back to the phone
The B2BUA invites the new leg of the call to the other phone
The original phone continues to send REFER's to the B2BUA module, which
responds with 404 Not Found's
I believe there should be a 202 Accepted sent from the B2BUA module to the
phone in response to the first REFER message, not a BYE (or maybe both Accepted
and BYE). But there is no 202 Accepted coming from the B2BUA module to the
phone.
Scroll to the bottom of http://www.woollum.com/temp/opensips.txt to view my
B2BUA XML config, which specifies that the B2BUA should respond with a 202
Accepted before ending the call leg. This is not happening like it should
I am running OpenSIPS 1.6.3 on CentOS 5.5 x64 (on an AMD platform).
Brett Woollum
br...@woollum.com
- Original Message -
From: Anca Vamanu a...@opensips.org
To: users@lists.opensips.org
Sent: Tuesday, October 19, 2010 2:20:15 AM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not
Working (Bug?)
Hi Brett,
No, you needn't add anything else in your configuration file except for the
b2b_init_request for the initial Invite and the B2BUA should know to handle the
REFER that comes inside that dialog. What happens is the the B2BUA does not
find a matching dialog for that REFER message .. I don't know why that is. I
will examine the traces you posted and try to reproduce this in the following
days and let you know.
Regards,
--
Anca Vamanu www.voice-system.ro
On 10/19/2010 09:05 AM, Brett Woollum wrote:
Hello again Anca,
I've done more debugging, and I've found that the REFER packets are all
targeting my B2BUA address and getting a 404 response. It seems to still be
working, but I'm wondering if this is what is causing the problem after the 2nd
transfer.
In my log at http://www.woollum.com/temp/opensips_trace.html , you can see the
404 Not Found's occurring at packet 9177. This one in particular is generated
for the packet above it (9175) that has sip:b2...@1.2.3.4 in the header of
the packet.
I've configured my B2BUA module with this entry:
modparam(b2b_entities, server_address, sip:b2...@1.2.3.4:5060 )
and this is the config file that is creating the errors:
if (uri==myself) {
if (method==REGISTER) {
save(location);
exit;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup(location)) {
xlog(USRLOC LOOKUP: ERROR 404 - NOT FOUND $fu-$ru);
sl_send_reply(404, Not Found);
exit;
};
append_hf(P-hint: usrloc applied\r\n);
};
And this is what is generated in the OpenSIPS log:
Oct 18 22:56:42 sip01 /usr/local/sbin/opensips[4425]: USRLOC LOOKUP: ERROR 404
- NOT FOUND sip:1...@1.2.3.4 - sip:b2...@1.2.3.4:5060
Is there something I need to add to my configuration that handles packets with
b2...@1.2.3.4 as the destination ($ru)?
Brett Woollum
br...@woollum.com
- Original Message -
From: Brett Woollum br...@woollum.com
To: OpenSIPS users mailling list users@lists.opensips.org
Sent: Monday, October 18, 2010 5:09:34 PM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not
Working (Bug?)
Hi Anca,
I set debug=6 but it does not appear to print any more detailed information to
my log (/var/log/messages).
I reviewed the sip trace I posted at
http://www.woollum.com/temp/opensips_trace.html and I still cannot find any
packets that are missing the header. The error log I posted at
http://www.woollum.com/temp/opensips.txt says that the To field, From field,
and RR field could not be parsed. It seems as though the B2BUA module tried to
open a new leg but didn't send the information along? Does that make sense?
From the log earlier:
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hello again Anca,
I've done more debugging, and I've found that the REFER packets are all
targeting my B2BUA address and getting a 404 response. It seems to still be
working, but I'm wondering if this is what is causing the problem after the 2nd
transfer.
In my log at http://www.woollum.com/temp/opensips_trace.html, you can see the
404 Not Found's occurring at packet 9177. This one in particular is generated
for the packet above it (9175) that has sip:b2...@1.2.3.4 in the header of
the packet.
I've configured my B2BUA module with this entry:
modparam(b2b_entities, server_address, sip:b2...@1.2.3.4:5060)
and this is the config file that is creating the errors:
if (uri==myself) {
if (method==REGISTER) {
save(location);
exit;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup(location)) {
xlog(USRLOC LOOKUP: ERROR 404 - NOT FOUND $fu-$ru);
sl_send_reply(404, Not Found);
exit;
};
append_hf(P-hint: usrloc applied\r\n);
};
And this is what is generated in the OpenSIPS log:
Oct 18 22:56:42 sip01 /usr/local/sbin/opensips[4425]: USRLOC LOOKUP: ERROR 404
- NOT FOUND sip:1...@1.2.3.4-sip:b2...@1.2.3.4:5060
Is there something I need to add to my configuration that handles packets with
b2...@1.2.3.4 as the destination ($ru)?
Brett Woollum
br...@woollum.com
- Original Message -
From: Brett Woollum br...@woollum.com
To: OpenSIPS users mailling list users@lists.opensips.org
Sent: Monday, October 18, 2010 5:09:34 PM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not
Working (Bug?)
Hi Anca,
I set debug=6 but it does not appear to print any more detailed information to
my log (/var/log/messages).
I reviewed the sip trace I posted at
http://www.woollum.com/temp/opensips_trace.html and I still cannot find any
packets that are missing the header. The error log I posted at
http://www.woollum.com/temp/opensips.txt says that the To field, From field,
and RR field could not be parsed. It seems as though the B2BUA module tried to
open a new leg but didn't send the information along? Does that make sense?
From the log earlier:
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE STARTING INVITE
null sip:sa...@1.2.3.4
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:rr:record_route:
From parsing failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:new_t: no valid
From in INVITE
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:t_newtran: new_t
failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_to:
unexpected char [] in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]:
ERROR:b2b_entities:b2b_tm_cback: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE 8 ENDING INVITE
null sip:sa...@10.20.1.225:5062
Oct 12 19:34:17 sip01 /usr/local/sbin/opensips[5168]:
ERROR:b2b_entities:b2b_prescript_f: No dialog found, callid= [B2B.50.3250981],
method=REFER Brett Woollum
br...@woollum.com
- Original Message -
From: Anca Vamanu a...@opensips.org
To: users@lists.opensips.org
Sent: Thursday, October 14, 2010 12:45:19 AM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not
Working (Bug?)
Hi Brett,
You need to run a network trace and catch the message for which you get this
error:
ERROR:core:parse_to: unexpected char [] in status 5:
You
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Brett,
No, you needn't add anything else in your configuration file except for
the b2b_init_request for the initial Invite and the B2BUA should know to
handle the REFER that comes inside that dialog. What happens is the the
B2BUA does not find a matching dialog for that REFER message .. I don't
know why that is. I will examine the traces you posted and try to
reproduce this in the following days and let you know.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/19/2010 09:05 AM, Brett Woollum wrote:
Hello again Anca,
I've done more debugging, and I've found that the REFER packets are
all targeting my B2BUA address and getting a 404 response. It seems to
still be working, but I'm wondering if this is what is causing the
problem after the 2nd transfer.
In my log at http://www.woollum.com/temp/opensips_trace.html, you can
see the 404 Not Found's occurring at packet 9177. This one in
particular is generated for the packet above it (9175) that has
sip:b2...@1.2.3.4 in the header of the packet.
I've configured my B2BUA module with this entry:
modparam(b2b_entities, server_address, sip:b2...@1.2.3.4:5060)
and this is the config file that is creating the errors:
if (uri==myself) {
if (method==REGISTER) {
save(location);
exit;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup(location)) {
xlog(USRLOC LOOKUP: ERROR 404 - NOT FOUND $fu-$ru);
sl_send_reply(404, Not Found);
exit;
};
append_hf(P-hint: usrloc applied\r\n);
};
And this is what is generated in the OpenSIPS log:
Oct 18 22:56:42 sip01 /usr/local/sbin/opensips[4425]: USRLOC LOOKUP:
ERROR 404 - NOT FOUND sip:1...@1.2.3.4-sip:b2...@1.2.3.4:5060
Is there something I need to add to my configuration that handles
packets with b2...@1.2.3.4 as the destination ($ru)?
Brett Woollum
br...@woollum.com
- Original Message -
From: Brett Woollum br...@woollum.com
To: OpenSIPS users mailling list users@lists.opensips.org
Sent: Monday, October 18, 2010 5:09:34 PM GMT -08:00 US/Canada Pacific
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently
Working/Not Working (Bug?)
Hi Anca,
I set debug=6 but it does not appear to print any more detailed
information to my log (/var/log/messages).
I reviewed the sip trace I posted at
http://www.woollum.com/temp/opensips_trace.html and I still cannot
find any packets that are missing the header. The error log I posted
at http://www.woollum.com/temp/opensips.txt says that the To field,
From field, and RR field could not be parsed. It seems as though the
B2BUA module tried to open a new leg but didn't send the information
along? Does that make sense?
From the log earlier:
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char []
in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char []
in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE STARTING
INVITEnull sip:sa...@1.2.3.4
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char []
in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:rr:record_route:
From parsing failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char []
in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:new_t: no valid
From in INVITE
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:t_newtran: new_t
failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char []
in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_to: unexpected char []
in status 5: .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]:
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]:
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]:
ERROR:b2b_entities:b2b_tm_cback: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE 8 ENDING
INVITEnull sip:sa...@10.20.1.225:5062
Oct 12 19:34:17 sip01 /usr/local/sbin/opensips[5168
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Anca, I set debug=6 but it does not appear to print any more detailed information to my log (/var/log/messages). I reviewed the sip trace I posted at http://www.woollum.com/temp/opensips_trace.html and I still cannot find any packets that are missing the header. The error log I posted at http://www.woollum.com/temp/opensips.txt says that the To field, From field, and RR field could not be parsed. It seems as though the B2BUA module tried to open a new leg but didn't send the information along? Does that make sense? From the log earlier: Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:b2b_entities:b2b_prescript_f: cannot parse From header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE STARTING INVITE null sip:sa...@1.2.3.4 Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:rr:record_route: From parsing failed Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:new_t: no valid From in INVITE Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:t_newtran: new_t failed Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_to: unexpected char [] in status 5: . Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_from_header: bad from header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:b2b_entities:b2b_tm_cback: cannot parse From header Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE 8 ENDING INVITE null sip:sa...@10.20.1.225:5062 Oct 12 19:34:17 sip01 /usr/local/sbin/opensips[5168]: ERROR:b2b_entities:b2b_prescript_f: No dialog found, callid= [B2B.50.3250981], method=REFER Brett Woollum br...@woollum.com - Original Message - From: Anca Vamanu a...@opensips.org To: users@lists.opensips.org Sent: Thursday, October 14, 2010 12:45:19 AM GMT -08:00 US/Canada Pacific Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?) Hi Brett, You need to run a network trace and catch the message for which you get this error: ERROR:core:parse_to: unexpected char [] in status 5: You can run opensips in debug mode ( set 'debug=6' ) to see info from the message and be able to find it in the network trace. From the logs it seems that a message ( possibly REFER ) has a bad From header and OpenSIPS is not able to process right. Regards, -- Anca Vamanu www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Brett, Can you please get a full debugging log? Please post the section where the REFER message is handled. Regards, -- Anca Vamanu www.voice-system.ro On 10/14/2010 11:57 PM, Brett Woollum wrote: Hi Anca, I enabled the sip_trace module in OpenSIPS and dumped everything to my database. I put together a script to print everything to an HTML page and parse out the From: headers on each packet so it would be easy to check them all. They all appear correct to me. I've posted the output of the sip_trace here: http://woollum.com/temp/opensips_trace.html Brett Woollum br...@woollum.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Brett, You need to run a network trace and catch the message for which you get this error: ERROR:core:parse_to: unexpected char [] in status 5: You can run opensips in debug mode ( set 'debug=6' ) to see info from the message and be able to find it in the network trace. From the logs it seems that a message ( possibly REFER ) has a bad From header and OpenSIPS is not able to process right. Regards, -- Anca Vamanu www.voice-system.ro On 10/13/2010 11:54 PM, Brett Woollum wrote: Unfortunately the mailing list won't let me send replies with my logs or config file since they're too big. You can find them on this page: http://www.woollum.com/temp/opensips.txt Thanks! Brett Woollum br...@woollum.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hi Anca, I enabled the sip_trace module in OpenSIPS and dumped everything to my database. I put together a script to print everything to an HTML page and parse out the From: headers on each packet so it would be easy to check them all. They all appear correct to me. I've posted the output of the sip_trace here: http://woollum.com/temp/opensips_trace.html Brett Woollum br...@woollum.com - Original Message - From: Anca Vamanu a...@opensips.org To: users@lists.opensips.org Sent: Thursday, October 14, 2010 12:45:19 AM GMT -08:00 US/Canada Pacific Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?) Hi Brett, You need to run a network trace and catch the message for which you get this error: ERROR:core:parse_to: unexpected char [] in status 5: You can run opensips in debug mode ( set 'debug=6' ) to see info from the message and be able to find it in the network trace. From the logs it seems that a message ( possibly REFER ) has a bad From header and OpenSIPS is not able to process right. Regards, -- Anca Vamanu www.voice-system.ro On 10/13/2010 11:54 PM, Brett Woollum wrote: Unfortunately the mailing list won't let me send replies with my logs or config file since they're too big. You can find them on this page: http://www.woollum.com/temp/opensips.txt Thanks! Brett Woollum br...@woollum.com ___ 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] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Hello Everyone, In an attempt to figure out the best way to build my OpenSIPS config with the B2BUA module included, I've started over with a very simple script implementing nothing but the B2BUA module (and usrloc). My goal is to allow the phones to place calls between them and transfer the calls to other local phones (similar to a PBX). I have the B2BUA module configured to allow the call to be transferred (REFER) up to 4 times. This scenario script and OpenSIPS config file work well depending on which leg of the call is being transferred. It appears that the originator of the call cannot be put back on the opposite leg of the call, as shown in the second example above. Another way to think of the problem is that the remote side cannot be transferred. For both of the scenarios below, I have 3 phones. One is for the Sales department, one is for Tech Support, and the third represents the Boss. Here is a scenario where I can transfer the call four times successfully: 1. Sales places a call to Tech Support. (Sales has the local side of the call, and Tech Support has the remote side of the call.) 2. Sales transfers his leg of the call to the Boss. (The Boss has the local side of the call, and Tech Support has the remote side of the call.) 3. The Boss transfers his leg of the call back to Sales. (Sales has the local side of the call, and Tech Support has the remote side of the call.) 4. Sales transfers his leg of the call back to the Boss. (The Boss has the local side of the call, and Tech Support has the remote side of the call.) Here is a scenario where the process is interrupted: 1. Sales places a call to Tech Support. (Sales has the local side of the call, and Tech Support has the remote side of the call.) 2. Sales transfers his leg of the call to the Boss. (The Boss has the local side of the call, and Tech Support has the remote side of the call.) 3. Tech Support transfers his leg of the call back to Sales. (The Boss has the local side of the call, and Sales has the remote side of the call.) **THE CALL FAILS AT THIS POINT** - The Boss's phone is left on the call with nobody on the other end. Tech Support's phone appears to transfer successfully. Nothing happens with the Sales phone. My OpenSIPS Server is at 1.2.3.4 in this example, and the phones are on the 10.20.1.x subnet. There is no NAT between the devices. This appears to be no correlation between which devices are doing the transferring (meaning the Boss and Tech Support could switch roles and it still fails). I am running OpenSIPS 1.6.3 on CentOS 5.5 x64. I'll send my log file, config file, and scenario file in a moment (they were too big to fit in one email). Brett Woollum br...@woollum.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)
Unfortunately the mailing list won't let me send replies with my logs or config file since they're too big. You can find them on this page: http://www.woollum.com/temp/opensips.txt Thanks! Brett Woollum br...@woollum.com - Original Message - From: Brett Woollum br...@woollum.com To: users-request users@lists.opensips.org Sent: Wednesday, October 13, 2010 1:50:06 PM GMT -08:00 US/Canada Pacific Subject: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?) Hello Everyone, In an attempt to figure out the best way to build my OpenSIPS config with the B2BUA module included, I've started over with a very simple script implementing nothing but the B2BUA module (and usrloc). My goal is to allow the phones to place calls between them and transfer the calls to other local phones (similar to a PBX). I have the B2BUA module configured to allow the call to be transferred (REFER) up to 4 times. This scenario script and OpenSIPS config file work well depending on which leg of the call is being transferred. It appears that the originator of the call cannot be put back on the opposite leg of the call, as shown in the second example above. Another way to think of the problem is that the remote side cannot be transferred. For both of the scenarios below, I have 3 phones. One is for the Sales department, one is for Tech Support, and the third represents the Boss. Here is a scenario where I can transfer the call four times successfully: 1. Sales places a call to Tech Support. (Sales has the local side of the call, and Tech Support has the remote side of the call.) 2. Sales transfers his leg of the call to the Boss. (The Boss has the local side of the call, and Tech Support has the remote side of the call.) 3. The Boss transfers his leg of the call back to Sales. (Sales has the local side of the call, and Tech Support has the remote side of the call.) 4. Sales transfers his leg of the call back to the Boss. (The Boss has the local side of the call, and Tech Support has the remote side of the call.) Here is a scenario where the process is interrupted: 1. Sales places a call to Tech Support. (Sales has the local side of the call, and Tech Support has the remote side of the call.) 2. Sales transfers his leg of the call to the Boss. (The Boss has the local side of the call, and Tech Support has the remote side of the call.) 3. Tech Support transfers his leg of the call back to Sales. (The Boss has the local side of the call, and Sales has the remote side of the call.) **THE CALL FAILS AT THIS POINT** - The Boss's phone is left on the call with nobody on the other end. Tech Support's phone appears to transfer successfully. Nothing happens with the Sales phone. My OpenSIPS Server is at 1.2.3.4 in this example, and the phones are on the 10.20.1.x subnet. There is no NAT between the devices. This appears to be no correlation between which devices are doing the transferring (meaning the Boss and Tech Support could switch roles and it still fails). I am running OpenSIPS 1.6.3 on CentOS 5.5 x64. I'll send my log file, config file, and scenario file in a moment (they were too big to fit in one email). Brett Woollum br...@woollum.com ___ 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
