[asterisk-bugs] [Asterisk 0014205]: Cisco 7940 Fails to Register in 1.6.x after upgrade

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14205 
====================================================================== 
Reported By:                maxgo
Assigned To:                blitzrage
====================================================================== 
Project:                    Asterisk
Issue ID:                   14205
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1-beta4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-09 15:58 CST
Last Modified:              2009-01-12 11:27 CST
====================================================================== 
Summary:                    Cisco 7940 Fails to Register in 1.6.x after upgrade
Description: 
Having the same network config, 7940, NAT, Asterisk v1.4, the phone
registers OK.

After upgrading to 1.6.0.3 or 1.6.1-beta4, Asterisk doesn't reply to the
REGISTER messages, although the received messages from the phone are
displayed on the console, no replies are seen to be sent - not even replies
denying the registration.

====================================================================== 

---------------------------------------------------------------------- 
 (0097505) blitzrage (administrator) - 2009-01-12 11:27
 http://bugs.digium.com/view.php?id=14205#c97505 
---------------------------------------------------------------------- 
Here is what my MySQL is seeing upon registration and such. I think this is
what is causing the negative impacts on the realtime engine. It seems like
something is wrong in causing the fullcontact to be filled with the
'username', and the 'name' field to attempt to be matched on the
'fullcontact'.

In 1.4 it looks to be OK, and calls work. In trunk, calls due not work for
me.


Asterisk trunk:

REGISTER
--------

UPDATE sipfriends SET ipaddr='192.168.128.129', port='11912',
regseconds='1231765983', username='X-Lite release 1014k stamp 47051',
fullcontact='X-Lite release 1014k stamp 47051' WHERE
name='sip:105 at 192.168.128.129:11912;rinstance=581a52fa91ce3e64'

UN-REGISTER
----------

UPDATE sipfriends SET fullcontact='', ipaddr='', port='', regseconds='0',
username='', regserver='' WHERE name=''

UPDATE sipfriends SET ipaddr='0.0.0.0', port='0', regseconds='1231765914',
username='X-Lite release 1014k stamp 47051', fullcontact='' WHERE name=''


Asterisk 1.4:

REGISTER
--------

UPDATE sipfriends SET fullcontact='', ipaddr='', port='', regseconds='0',
username='', regserver='' WHERE name='105'

UPDATE sipfriends SET ipaddr='192.168.128.129', port='65484',
regseconds='1231766289', username='X-Lite release 1014k stamp 47051',
fullcontact='sip:105 at 192.168.128.129:65484;rinstance=44b8b2727d4ff361'
WHERE name='105'


UN-REGISTER
-----------

UPDATE sipfriends SET fullcontact='', ipaddr='', port='', regseconds='0',
username='', regserver='' WHERE name='105'

UPDATE sipfriends SET ipaddr='0.0.0.0', port='0', regseconds='1231766197',
username='X-Lite release 1014k stamp 47051', fullcontact='' WHERE
name='105' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-12 11:27 blitzrage      Note Added: 0097505                          
======================================================================