From admin@sip-router.org Fri Mar 26 17:54:48 2010
From: sip-router <admin@sip-router.org>
To: sr-dev@lists.kamailio.org
Subject: [sr-dev] [tracker] Comment added: wrong TM response code
Date: Fri, 26 Mar 2010 17:54:46 +0100
Message-ID: <20100326165446.3438.1416763311.swift@sip-router.org>
In-Reply-To: <FS53@sip-router.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1388506157=="

--===============1388506157==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#53 - wrong TM response code
User who did this - Andrei Pelinescu-Onciul (andrei)

----------
Yes, it did, but on the lo interface (that's why it's not in the ngrep dump).
First of all you can see that the INVITE forwarded back to  83.136.33.3:5200 =
it's on the second branch (branch number 1 and not 0):
Via: SIP/2.0/UDP 83.136.32.159;branch=3Dz9hG4bK404.f2951c02.1  (note the .1 a=
t the end)

Then looking at syslog.txt:
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: 3df9=
71d27197-l2satt3hm9s8(a)83-136-33-3 appending branch to gateway ...=20
.....
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>:   ma=
in branch:
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>:     =
$ru=3Dsip:00123456(a)labs.nic.at
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>:     =
$du=3D<null>
....
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>:   ad=
ditional branch 0:
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>:     =
RURI=3Dsip:klaus.darilion(a)83.136.33.3:5200;line=3Dm3yhutkd
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>:     =
DURI=3Dsip:83.136.33.3:5200

Basically there are 2 branches and the main/first branch tries to send the in=
vite to sip:00123456(a)labs.nic.at which will cause it to loop it back to the=
 proxy (that's not probably what you want, either the uri is wrong, the dst u=
ri is not set or you miss a forward gateway rule).
The proxy receives the INVTIE for sip:00123456(a)labs.nic.at, and the auth. f=
ails (the credentials are probably removed in the script before forwarding, b=
ut even if they would not be removed they would be for klaus.darilion and not=
 for 00123456):

Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30990]: INFO: <script>: 3df9=
71d27197-l2satt3hm9s8(a)83-136-33-3 authentication failed, wrong or missing c=
redentials, challenging...
....
Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30990]: DEBUG: sl [sl.c:318]=
: reply in stateless mode (sl)

Then the proxy will reply with 407 for the INV to sip:00123456(a)labs.nic.at,=
 on the lo interface (that's why it's not in the ngrep dump).
In the end there are 2 responses for the INV transaction: the 407 and the 482=
 and the proxy chooses the 407.
----------

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=3Ddetails&task_id=3D53#comment54

You are receiving this message because you have requested it from the Flyspra=
y bugtracking system.  If you did not expect this message or don't want to re=
ceive mails in future, you can change your notification settings at the URL s=
hown above.


--===============1388506157==--