[sip-comm-dev] Different Call-ID in keep-alive REGISTER messages


#1

Hi,
I have a question about SIP Communicator's SIP standard implementation. The SIP RFC 3261 states in "10.2 Constructing the REGISTER Request" that the Call-ID header field value SHOULD be the same in registrations from a UAC, but I noticed that SIP Communicator uses different Call-IDs when sending REGISTER as a keep-alive message. Why is that? Is there some reason not to send subsequent REGISTER messages with the same Call-ID?

···

--
regards,
Filip Koczorowski

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hey Filip, all

Filip and I had a quick chat on IRC about this, so for the record:

This sounds like a problem indeed. Filip has submitted the following issue:

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=674

He has also attached a wireshark dump. If this confirms, it is clearly a
bug so we'll handle it in 1.0

Cheers
Emil

Filip Koczorowski wrote:

···

Hi,
I have a question about SIP Communicator's SIP standard implementation.
The SIP RFC 3261 states in "10.2 Constructing the REGISTER Request" that
the Call-ID header field value SHOULD be the same in registrations from
a UAC, but I noticed that SIP Communicator uses different Call-IDs when
sending REGISTER as a keep-alive message. Why is that? Is there some
reason not to send subsequent REGISTER messages with the same Call-ID?

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net