From: sip-implementors-boun...@lists.cs.columbia.edu
[sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Mia Cizmic
[mia.ciz...@ericsson.com]
Namely, we have sent a Re-Invite on an existing session and received 100
Trying reply.
100 Trying reply
Hi Mia
you can go through thread with title "How long can a Dialog be in
Early state". dated 10th July 2010.
Even though it's for initial request but help you understand timer in
a better way.
also read below bug and RFC 5057 (how final responses to transaction
affect dialog).
http://bugs.sipit.n
Hi,
This problem occurs not only in ReInvite but in INVITE transactions also.
Its a bug in SIP and has been reported as well. In our implementation, we
didnt hamper the existing timers but created a new one whose value we set >
timerB.
For sure the dialog needs to be terminated.
cheers!!
sarvpriy
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Mia Cizmic
Sent: Tuesday, July 27, 2010 11:59 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] RFC 3261, 100 Trying on Re-Invite
Hi
Hi,
in our SIP implementation, we have encountered a problem for which we
don't find a clear statement in RFC 3261.
We would like to hear your opinion about this issue, if possible.
Namely, we have sent a Re-Invite on an existing session and received 100
Trying reply.
100 Trying reply turned of
