Callid broken in version 1.8

We recently upgraded from Asterisk 1.4 to 1.8. We have Polycom 8002 phones which were working but now they will not register with Asterisk. The log shows the following:

[2011-10-12 17:45:11] VERBOSE[2625] chan_sip.c: — (11 headers 0 lines) —
[2011-10-12 17:45:11] DEBUG[2625] chan_sip.c: Invalid SIP message - rejected , no callid, len 331
[2011-10-12 17:45:12] VERBOSE[2625] chan_sip.c:
<— SIP read from UDP: —>

Nothing has changed on the phones but the registration process in Asterisk appears to have changed. I’ve found some other references in the forum to similar problems, but not a solution.

Any ideas on how to get this working again would be appreciated.

Is there any news on this. We also have Polycom 8002 phones that were working fine on our 1.4 asterisk install. That server crashed and I upgraded to 1.8, now our Polycom 8002 do not register correctly. Googling has given many suggestions but nothing seemed to work. Calls can be placed on the 8002’s to other working system phones/SIP trunks but the 8002s cannot receive calls. The caller hears a fast busy. The SIP peers for these units show a host of (Unspecified) a port of 0 and Status of Unmonitored.

There is not enough information in the thread to work out why it is going wrong. However, I think it is safe to say that it is either fixed or affects very few people. I am sure any problem that affected all Polycom users would have been fixed very quickly.

You need to provide the same level of information as would be needed for an official bug report, i.e. verbose >= 5, debug >= 5, sip set debug on, and a log covering the complete register exchange.