No subject

implementation in Asterisk is broken enough so that most people are
going to have difficulties with it. If that is the case shouldn't it
be moved out to a branch and fixed before releasing it?

It seems a bit like "experimental feature" here is "half done new
feature". Asterisk has always changed at a rate of knots and us users
are used to treating new releases and features as "experimental".
Knowing that a new feature is broken at best will be fine for those of
us that keep an eye on things and know to avoid it but will be really
painful for new users trying to get up and running with broken
implementations. Those users that do want to "experiment" can checkout
the branch.

As to the fact that having a broken SIP TCP channel is ok becuase the
UDP one is alright it is worth considering that some user agents, such
as the xten softphones, will use TCP as first preference over UDP. So
if an Asteirsk 1.6 user who is only just learning SIP activates the
TCP channel they'll have problems which is not good for the community.

The other underlying issue here is that adding TCP to the Asterisk SIP
channel should not have been this big a deal in the first place. The
fact that is is stems from the way the SIP channel has been
implemented and that the whole 20,000+ (last time I checked) lines of
code have to be gone through to see where modifications are required.
I have seen a SIP stack implementation where going from UDP to TCP
meant adding a transport class of 400 lines and a small number of
adjustments in the Via headers and URI handling, all up probably a
couple of days work.

Regards,

Greyman.