[OpenSIPS-Users] YNT: Re: YNT: Re: YNT: Re: RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE
Kaan Dandin
kaandandin at yahoo.com
Mon Oct 13 18:45:26 CEST 2014
Hi Bogdan,
I am using following lines (just sharing related part of the script) to check first if the method is REGISTER and sending to .3 (open ims node 1) and .5(open ims node 2) if it is coming from .11(ims bench traffic generator).
Otherwise I am sending directly to the set destination.
else if (is_method("REGISTER")) {
xlog("xlog_initialregister");
if($si=="192.168.2.11") {
t_relay("udp:192.168.2.3:4060");
t_relay("udp:192.168.2.5:4060");
exit;
}
if (!t_relay()) {
xlog("xlog_route1error");
sl_reply_error();
};
exit;
}
Kind regards,
Kaan
________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org>
To: Kaan Dandin <kaandandin at yahoo.com>; OpenSIPS users mailling list <users at lists.opensips.org>
Cc: Gunes Kurt <gkurt at itu.edu.tr>; "Ibrahim Hokelek, (BİLGEM-UEKAE)" <ibrahim.hokelek at tubitak.gov.tr>
Sent: Monday, October 13, 2014 5:26 PM
Subject: Re: YNT: Re: YNT: Re: YNT: Re: [OpenSIPS-Users] RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE
Hi Kaan,
In OpenSIPS, how do you script to have the REGISTER sent to both
.3 and .5 ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 13.10.2014 13:11, Kaan Dandin wrote:
Hi Bogdan,
Following 401 messages are coming from .3 , but not passed to .11
by opensips (.141)
Kind regards,
Kaan
63 1.233561 192.168.2.3 192.168.2.141 SIP Status: 401 Unauthorized - Challenging the UE (0 bindings)
>>> 64 1.241624 192.168.2.3 192.168.2.141 SIP Status: 401 Unauthorized - Challenging the UE (0 bindings)
Samsung Mobile tarafından gönderildi
-------- Orjinal mesaj --------
Kimden: Bogdan-Andrei Iancu <bogdan at opensips.org>
Tarih:13 10 2014 10:09 (GMT+02:00)
Alıcı: Kaan Dandin <kaandandin at yahoo.com>,OpenSIPS users mailling list <users at lists.opensips.org>
Cc: Gunes Kurt <gkurt at itu.edu.tr>,"Ibrahim Hokelek, (BİLGEM-UEKAE)" <ibrahim.hokelek at tubitak.gov.tr>
Konu: Re: YNT: Re: YNT: Re: [OpenSIPS-Users] RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE
Hi Kaan,
OK, you fork to .3 and .5 and I see only .5 answering -
nothing back from .3 . So OpenSIPS sends back to IMS .11 the
reply from .5, the 401.
Where is the problem?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 10.10.2014 23:48, Kaan Dandin wrote:
Yes 141 is opensips I am sending both 3 and 5 register messages when I get from 11 which is ims bench
Samsung Mobile tarafından gönderildi
-------- Orjinal mesaj --------
Kimden: Bogdan-Andrei Iancu <bogdan at opensips.org>
Tarih:09 10 2014 13:45 (GMT+02:00)
Alıcı: Kaan Dandin <kaandandin at yahoo.com>,OpenSIPS users mailling list <users at lists.opensips.org>
Cc:
Konu: Re: YNT: Re: [OpenSIPS-Users] RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE
Hi,
Is .141 your OpenSIPS ? I see .141 is sending the REGISTRAR to
both nodes ( .3 and .5) .
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 09.10.2014 10:00, Kaan Dandin wrote:
Hi Bogdan,
Thanks for your response.
In this situation how can I configure opensips to pass this message to the destination. Is it a configuration change or should I use another function instead of t_relay ?
Kind regards
Samsung Mobile tarafından gönderildi
-------- Orjinal mesaj --------
Kimden: Bogdan-Andrei Iancu <bogdan at opensips.org>
Tarih:07 10 2014 16:29 (GMT+02:00)
Alıcı: Kaan Dandin <kaandandin at yahoo.com>,OpenSIPS users mailling list <users at lists.opensips.org>
Cc:
Konu: Re: [OpenSIPS-Users] RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE
Hi Kaan,
The log you refer to is a DBG and not an ERR (error) -
when a new request is received, opensips (inside the
t_relay) tries to match it against existing transactions
to see if it a retransmission on not. The fact your
request does not match means it is not a retransmission,
but rather a new request.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 04.10.2014 11:18, Kaan Dandin wrote:
Hi all,
>
>I am making registration to the Open IMS nodes(192.168.2.3 and 192.168.2.5) simultaneously from IMS bench(192.168.2.11). Registration messages are going through OpenSIPS load balancer(192.168.2.141).
>
>Registration messages which are going to first Open IMS node(192.168.2.5) completed succesfully.
>
>
>But registration to second IMS node(192.168.2.3) is not completed successfully since t_relay() function in OpenSIPS load balancer is giving "DBG:tm:matching_3261: RFC3261 transaction matching failed" error and not passing the "Status: 401 Unauthorized - Challenging the UE (0 bindings)" messages to IMS bench.
>
>Below please find wireshark log and opensips logs in debug level=6.
>
>Do you have any idea for this problem.
>
>BR,
>Kaan
>
>
>o. Time Source Destination Protocol Info
> 55 1.186495 192.168.2.11
192.168.2.141 SIP Request: REGISTER
sip:open-ims.test
> 56 1.188443 192.168.2.141
192.168.2.3 SIP Request: REGISTER
sip:open-ims.test
> 57 1.189001 192.168.2.141
192.168.2.5 SIP Request: REGISTER
sip:open-ims.test
> 58 1.215792 192.168.2.5
192.168.2.141 SIP Status: 401 Unauthorized
- Challenging the UE (0 bindings)
> 59 1.216974 192.168.2.141
192.168.2.11 SIP Status: 401 Unauthorized
- Challenging the UE (0 bindings)
> 60 1.217486 192.168.2.11
192.168.2.141 SIP Request: REGISTER
sip:open-ims.test
> 61 1.218516 192.168.2.141
192.168.2.3 SIP Request: REGISTER
sip:open-ims.test
> 62 1.218804 192.168.2.141
192.168.2.5 SIP Request: REGISTER
sip:open-ims.test
> 63 1.233561 192.168.2.3
192.168.2.141 SIP Status: 401 Unauthorized
- Challenging the UE (0 bindings)
> 64 1.241624 192.168.2.3
192.168.2.141 SIP Status: 401 Unauthorized
- Challenging the UE (0 bindings)
> 65 1.246112 192.168.2.5
192.168.2.141 SIP Status: 200 OK - SAR
succesful and registrar saved (1 bindings)
> 66 1.246919 192.168.2.141
192.168.2.11 SIP Status: 200 OK - SAR
succesful and registrar saved (1 bindings)
>
>
>
>Oct 3 10:01:35 ubuntu /usr/local/opensips/sbin/opensips[8938]: xlog method: [REGISTER] totag: [<null>] sipid: [192.168.2.11] messageid: [68] callid: [56-6888 at 192.168.2.11] callsequence: [2]
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:uri:has_totag: no totag
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
xlog_initialregister
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:core:comp_scriptvar: str 20 : 192.168.2.11
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:tm:t_newtran: transaction on
entrance=0xffffffffffffffff
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:core:parse_headers: flags=ffffffffffffffff
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:core:get_hdr_field: content_length=0
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:core:get_hdr_field: found end of header
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:core:parse_headers: flags=78
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:tm:t_lookup_request: start searching: hash=35746,
isACK=0
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:tm:matching_3261: RFC3261 transaction matching
failed
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:tm:t_lookup_request: no transaction found
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:tm:run_reqin_callbacks: trans=0x7fcda4739918,
callback type 1, id 1 entered
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:tm:run_reqin_callbacks: trans=0x7fcda4739918,
callback type 1, id 0 entered
>Oct 3 10:01:35 ubuntu
/usr/local/opensips/sbin/opensips[8938]:
DBG:core:check_ip_address: params 192.168.2.11,
192.168.2.11, 0
>
>
>
>
>_______________________________________________
Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20141013/684aafa3/attachment-0001.htm>
More information about the Users
mailing list