Summary:ASTERISK-05129: Can't fetch sip registration binding
Reporter:mikma (mikma)Labels:
Date Opened:2005-09-22 15:38:55Date Closed:2008-01-15 15:49:10.000-0600
Versions:Frequency of
Description:Asterisk doesn't send final responses for REGISTER requests without Contact headers. According to RFC 3061 section 10.2.3 a REGISTER request with no Contact header can be used to fetch the existing bindings.

Asterisk responds with 100 Trying and logs the following warnings, but doesn't send any final response.

Sep 22 22:18:27 NOTICE[12969]: chan_sip.c:5576 parse_contact: '' is not a valid SIP contact (missing sip:) trying to use anyway

Sep 22 22:18:27 WARNING[12969]: chan_sip.c:5605 parse_contact: Invalid host ''

Sep 22 22:18:27 WARNING[12969]: chan_sip.c:6104 register_verify: Failed to parse contact info

  10.2.3 Fetching Bindings

  A success response to any REGISTER request contains the complete list

  of existing bindings, regardless of whether the request contained a

  Contact header field.  If no Contact header field is present in a

  REGISTER request, the list of bindings is left unchanged.
Comments:By: mikma (mikma) 2005-09-22 15:44:58

The category should have been "Interoperability problems", but it got changed when  I hade to go back in the browser since I had forgotten to fill in one field.

By: Kevin P. Fleming (kpfleming) 2005-09-25 21:25:46

Fixed in CVS HEAD, although I don't have any devices to test this with easily, so please test and re-open if there is still a problem.

By: Digium Subversion (svnbot) 2008-01-15 15:49:10.000-0600

Repository: asterisk
Revision: 6656

U   trunk/channels/chan_sip.c

r6656 | kpfleming | 2008-01-15 15:49:10 -0600 (Tue, 15 Jan 2008) | 3 lines

properly respond to REGISTER queries (issue ASTERISK-5129)
remove unused sip_peer expiry field