[Sipp-users] Re: recv request="INVITE" is discarded

[Olivier J. <oja...@gm...>]

On 6/28/05, Emanuel Eick <spa...@gm...> wrote:
> From the Posting from Peter Higginson I didn't understand the problem com=
pletly.
> At first I have the registration process with its own callid. Then the fi=
rst
> Invite attemp is started and comes back with an unauthorized. This is als=
o
> correct. The next try follows with the same callid, therefore sipp should=
n't
> think that it is a new session, even when the sequencenumber is itterated=
.
> Please correct me if I am wrong.

You are right. As long as SIPp receives a SIP message with the same
Call-Id as the one it generated (through [call-id]), then the SIP
message will be seen as part of this call.

> This is the sequence for sceneario, showing the callid symbolized at the =
end of
> the arrows.
>=20
>  SERVER               SER               Server
>    |=3DRegister=3DID 123=3D>|                   |
>    |<=3D 401 Unauth 123=3D|                   |
>    |=3DRegister=3DID 123=3D>|                   |
>    |<=3D OK =3D ID 123=3D=3D=3D=3D|                   |
>    |                  |<=3DInvite =3D ID XYZ =3D| CSEQ 1
>    |                  |=3D=3D 401 Unauth XYZ=3D>| CSEQ 1
>    |                  |<=3D 200 ACK ID XYZ =3D| CSEQ 1
>    |                  |<=3DInvite =3D ID XYZ =3D| CSEQ 2
>    |                  |=3D=3D100 try=3D ID XYZ =3D| CSEQ 2
>    |<=3DInvite  ID XYZ =3D|                   | CSEQ 2
>    |<=3DInvite  ID XYZ =3D|                   | CSEQ 2
>            ...


But here, the Invite is using another ID (not 123), right? Then SIPp
can't recognize it as one of its call.

Can you send the output of -trace_msg or an Ethereal capture?

Olivier.
--=20
http://www.hp.com/go/opencall/