Summary: | ASTERISK-17222: [patch] Realtime Peers Cannot Register | ||
Reporter: | John Covert (jcovert) | Labels: | |
Date Opened: | 2011-01-11 00:15:21.000-0600 | Date Closed: | 2012-09-05 09:14:07 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/DatabaseSupport |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) chan_sip.c.306619.patch ( 1) chan_sip.c.312889.patch ( 2) chan_sip.c.patch ( 3) issue_18596.diff ( 4) issue_18596.diff | |
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. | ||
Comments: | By: John Covert (jcovert) 2011-02-08 07:05:47.000-0600 Patch as needed for current trunk head uploaded. By: John Covert (jcovert) 2011-04-06 17:31:17 Ping... This is critical to one of my clients. It is a regression. Simple fix to restore previous behaviour. By: David Vossel (dvossel) 2011-05-03 14:25:58 Please test the patch I uploaded. Your patch works, but is not a complete fix. |