[asterisk-bugs] [Asterisk 0018596]: [patch] Realtime Peers Cannot Register

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18596 
====================================================================== 
Reported By:                jcovert
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18596
Category:                   Channels/chan_sip/DatabaseSupport
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for review
Asterisk Version:           1.8.1.1 
JIRA:                       SWP-2894 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-01-11 00:15 CST
Last Modified:              2011-04-06 17:31 CDT
====================================================================== 
Summary:                    [patch] Realtime Peers Cannot Register
Description: 
Prior to 1.8, it was not necessary for an explicit "type" to be set for an
asterisk LDAP realtime peer.  Now the routine find_peer actually checks the
type field during registration and fails to find the peer if it is not set.

The attached patch makes a realtime peer be "type=peer" if it is still
type 0 upon return from routine build_peer.

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

---------------------------------------------------------------------- 
 (0133478) jcovert (reporter) - 2011-04-06 17:31
 https://issues.asterisk.org/view.php?id=18596#c133478 
---------------------------------------------------------------------- 
Ping...  This is critical to one of my clients.  It is a regression. 
Simple fix to restore previous behaviour. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-06 17:31 jcovert        Note Added: 0133478                          
======================================================================