12 Dec
2006
12 Dec
'06
10:58 a.m.
yes you are right:)
but the stange situation is the following
(version from svn):
UA1 SIPProxy
| |
|INVITE 3 |
|------------->|
| |
|407 3 |
|<-------------|
| |
|ACK 3 |
|------------->|
| |
|INVITE 4 |
|------------->|
| |
|TRYING 4 |
|<-------------|
| |
|INVITE 4 |
|<-------------|
| |
|ACK 3 |
|------------->|
| |
|INVITE 4 |
|<-------------|
| |
after the end of dialog related to cseq 3
ua (sipsak) sends an invite (with cseq 4) to sipproxy
then there is the provisional response trying and sipproxy sends invite
further (actually the same ua) to sipsak
and the reaction of sipsak is: ACK with with cseq 3 instead of OK or 4xx,
this scenarion is repeated until sipproxy sends the 408 timeout with cseq 4
after wich ua (sipsak) resposes with ACK with cseq 4
what do you think about this?:)
bests tomek
---- Wiadomość Oryginalna ----
Od: Michal Matyska <michal(a)iptel.org>
Do: serusers(a)lists.iptel.org
Data: 11 grudnia 2006 20:59
Temat: Re: [Serusers] SIPSAK - wrong behaviour??
I was just curious, so I took look on the ngrep....
there is short jump in the description between points 2 and 3....
2a. sipsak sends ACK upon 407 reply, which is 100% correct
2b. sipsak resends INVITE with correct credentials
2c. ser forwards the INVITE to the sipsak @ port 5060
3. sipsak sends ACK (with the CSeq: 3, Via: headers look like
combination of original ACK and passed INVITE Vias), which you've found
inappropriate, right? Just to make sure we talk about the same ACK :-D
Michal
On Mon, 2006-12-11 at 19:12 +0100, Nils Ohlmeier wrote:
Hi Tomasz,
On Monday 11 December 2006 17:21, tzieleniewski wrote:
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hi ALL!
I am trying to run some tests under sipsak but I obtain strange result
I invoke sip stack with the following command:
sipsak -IU -vv -s sip:sipsak@scscf.ims.touk.pl -a sipsak -l 5061 -H
192.168.0.129 The registration proces runs without any problem, user
registers and then sipsak sends invite to ser. And here comes the strange
thing
1. sipsak sends invite to ser:
2. Ser sends the proxy authentication required response 407 (from ngrep)
3. sipsak receives the message andresponses with the ACK????
Ive placed the ngrep from the sipsak socket in the attached file.
that looks like a bug. I'll try to look into that later.
It would be great if you could try if the same behavior is still present in
the latest version from subversion (let me know if I should send you a
tarball of that). And the output from sipsak with -vvv would be a great help.
Just send that directly to me.
Thanks
Nils
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers