26 May
2003
26 May
'03
2:53 a.m.
At 11:57 PM 5/25/2003, Nils Ohlmeier wrote:
Ok i first overlooked a problem in the messages.
I think the ATA is guilty because the request URI of the ACK is not the same
as the URI from the INVITE. And if i'm not wrong the URIs has to be the same
because the ACK for a negative reply belongs to the transaction.
Thanks Nils -- indeed, that's an ATA bug -- the URIs must be the same.
To fix the problem, I urge ATA users to urge Cisco. You can use some workarounds
(like disabling tm "ruri_matching" tm parameter in the about to be released
ser 0.8.11 version) but ATA is the primary place to fix. Actually, the best
thing to do with ATA is to use RFC-3261 transaction matching -- 2541 matching
has been obsoleted quite a while ago.
-jiri
26 May
26 May
4:49 p.m.
New subject: [Serusers] SER is not matching ACK Messages
Hi Jiri,
Could you explain how to "use RFC-3261 transaction matching". Is this
something I can switch on in the ser.cfg?
Thanks,
Ricardo
----- Original Message -----
From: "Jiri Kuthan" <jiri(a)iptel.org>
To: <serusers(a)lists.iptel.org>rg>; "Ricardo Villa"
<ricvil(a)epm.net.co>co>;
<aolchik(a)telenova.net>
Cc: "List serusers" <serusers(a)lists.iptel.org>
Sent: Sunday, May 25, 2003 7:53 PM
Subject: Re: [Serusers] SER is not matching ACK Messages
workarounds
At 11:57 PM 5/25/2003, Nils Ohlmeier wrote:
>Ok i first overlooked a problem in the messages.
>I think the ATA is guilty because the request URI of the ACK is not the
same
>as the URI from the INVITE. And if i'm not
wrong the URIs has to be the
same
because the ACK
for a negative reply belongs to the transaction.
Thanks Nils -- indeed, that's an ATA bug -- the URIs must be the same.
To fix the problem, I urge ATA users to urge Cisco. You can use some (like disabling tm "ruri_matching" tm
parameter in the about to be
released
ser 0.8.11 version) but ATA is the primary place to
fix. Actually, the
best
thing to do with ATA is to use RFC-3261 transaction
matching -- 2541
matching
has been obsoleted quite a while ago.
-jiri
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
5:39 p.m.
New subject: [Serusers] SER is not matching ACK Messages
At 04:49 PM 5/26/2003, Ricardo Villa wrote:
Hi Jiri,
Could you explain how to "use RFC-3261 transaction matching". Is this
something I can switch on in the ser.cfg?
SER supports both -- it is about ATAs doing it correctly. The RFC3261
transaction matching is simple and good -- it uses explicit transaction
identifier (Via/branch parameter). Previously, transaction identifier
was calculated from a bunch of message elements, which was simply broken.
-Jiri
Thanks,
Ricardo
----- Original Message -----
From: "Jiri Kuthan" <jiri(a)iptel.org>
To: <serusers(a)lists.iptel.org>rg>; "Ricardo Villa"
<ricvil(a)epm.net.co>co>;
<aolchik(a)telenova.net>
Cc: "List serusers" <serusers(a)lists.iptel.org>
Sent: Sunday, May 25, 2003 7:53 PM
Subject: Re: [Serusers] SER is not matching ACK Messages
workarounds
--
Jiri Kuthan http://iptel.org/~jiri/
At 11:57 PM 5/25/2003, Nils Ohlmeier wrote:
>Ok i first overlooked a problem in the messages.
>I think the ATA is guilty because the request URI of the ACK is not the
same
>as the URI from the INVITE. And if i'm
not wrong the URIs has to be the
same
because
the ACK for a negative reply belongs to the transaction.
Thanks Nils -- indeed, that's an ATA bug -- the URIs must be the same.
To fix the problem, I urge ATA users to urge Cisco. You can use some (like disabling tm "ruri_matching" tm
parameter in the about to be
released
ser 0.8.11 version) but ATA is the primary place
to fix. Actually, the
best
thing to do with ATA is to use RFC-3261
transaction matching -- 2541
matching
> has been obsoleted quite a while ago.
>
> -jiri
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
27 May
27 May
7:19 p.m.
New subject: [Serusers] SER is not matching ACK Messages
Jiri Kuthan writes:
To fix the problem, I urge ATA users to urge Cisco.
You can use some
workarounds (like disabling tm "ruri_matching" tm parameter in the
about to be released ser 0.8.11 version) but ATA is the primary place
to fix. Actually, the best thing to do with ATA is to use RFC-3261
transaction matching -- 2541 matching has been obsoleted quite a
while ago.
wasn't this the same bug that i found and cisco actually fixed a couple
of months ago?
-- juha
8:03 p.m.
New subject: [Serusers] SER is not matching ACK Messages
At 07:19 PM 5/27/2003, Juha Heinanen wrote:
Jiri Kuthan writes:
it was.
-ijri
To fix the problem, I urge ATA users to urge
Cisco. You can use some
workarounds (like disabling tm "ruri_matching" tm parameter in the
about to be released ser 0.8.11 version) but ATA is the primary place
to fix. Actually, the best thing to do with ATA is to use RFC-3261
transaction matching -- 2541 matching has been obsoleted quite a
while ago.
wasn't this the same bug that i found and cisco actually fixed a couple
of months ago?
28 May
28 May
12:40 a.m.
New subject: [Serusers] SER is not matching ACK Messages
Could be. The ATA 2.16 Release Notes say the the following problem was
fixed:
a.. CSCdz87773
If the Cisco ATA sends an INVITE message that includes the user=phone
parameter, the corresponding ACK message does not always contain the
user=phone parameter.
----- Original Message -----
From: "Juha Heinanen" <jh(a)lohi.eng.song.fi>
To: "Jiri Kuthan" <jiri(a)iptel.org>
Cc: <serusers(a)lists.iptel.org>rg>; "Ricardo Villa"
<ricvil(a)epm.net.co>co>;
<aolchik(a)telenova.net>
Sent: Tuesday, May 27, 2003 12:19 PM
Subject: Re: [Serusers] SER is not matching ACK Messages
Jiri Kuthan writes:
To fix the problem, I urge ATA users to urge
Cisco. You can use some
workarounds (like disabling tm "ruri_matching" tm parameter in the
about to be released ser 0.8.11 version) but ATA is the primary place
to fix. Actually, the best thing to do with ATA is to use RFC-3261
transaction matching -- 2541 matching has been obsoleted quite a
while ago.
wasn't this the same bug that i found and cisco actually fixed a couple
of months ago?
-- juha
5:01 p.m.
New subject: [Serusers] SER is not matching ACK Messages
The problem is that ATA 2.16 brings other bugs,
probably worst than this.
After sometime the ATA start to send registration
messages with an invalid host in the From or To
field (don't remember which one), and registration
is lost. I had to move back to 2.15.
Alejandro
Ricardo Villa said:
Could be. The ATA 2.16 Release Notes say the the
following problem was
fixed:
a.. CSCdz87773
If the Cisco ATA sends an INVITE message that includes the user=phone
parameter, the corresponding ACK message does not always contain the
user=phone parameter.
----- Original Message -----
From: "Juha Heinanen" <jh(a)lohi.eng.song.fi>
To: "Jiri Kuthan" <jiri(a)iptel.org>
Cc: <serusers(a)lists.iptel.org>rg>; "Ricardo Villa"
<ricvil(a)epm.net.co>co>;
<aolchik(a)telenova.net>
Sent: Tuesday, May 27, 2003 12:19 PM
Subject: Re: [Serusers] SER is not matching ACK Messages
Jiri Kuthan writes:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers To fix the problem, I urge ATA users to urge
Cisco. You can use
some workarounds (like disabling tm "ruri_matching" tm
parameter in
the about to be released ser 0.8.11 version) but ATA is the primary
place to fix. Actually, the best thing to do with ATA is to use
RFC-3261 transaction matching -- 2541 matching has been obsoleted
quite a while ago.
wasn't this the same bug that i found and cisco actually fixed a
couple of months ago?
-- juha
7649
days inactive
7651
days old
6 comments
4 participants
participants (4)
-
Alejandro Olchik -
Jiri Kuthan -
Juha Heinanen -
Ricardo Villa