Paul,
I found several things in RFC3261 that made me wonder as well:
- INVITE server transaction (Figure 7): responses 101-199 from TU are to be
sent, what happens to 100?
- What happens if a retransmitted INVITE arrives within 200ms and the
application has not yet sent a 100?
I think an application (TU) should not send a 100 trying twice. What could
happen, is that 100 is the last response sent, so when a retransmitted
INVITE arrives the 100 is repeated.
A reason for sending multiple 100 trying could be to account for packet loss
on an unreliable transport. However, it's probably better to rely on the
sender to retransmit its INVITE for this purpose. So IMO an application
SHOULD NOT send more than one 100 trying
Regards,
Jeroen
----- Original Message -----
From: "Paul Kyzivat" <[EMAIL PROTECTED]>
To: "Martin Koenig" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Friday, October 14, 2005 12:30 AM
Subject: Re: [Sip-implementors] 100 trying
Why would you think it is *not* ok?
Paul
Martin Koenig wrote:
Hello all,
is it legal per RFC3261 to send two separate "100 trying" provisional
responses for a SIP Request?
A B
INVITE ------>
<----- 100 trying
<----- 100 trying
<----- (180 ringing)
<----- 200 ok
etc.
A B
REGISTER ------>
<------ 100 trying
<------ 100 trying
<------ 200 ok
etc.
With best regards,
Martin
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
