| Summary: | ASTERISK-17537: Wrong Column Value When Using res_config_pgsql | ||
| Reporter: | dread (dread) | Labels: | |
| Date Opened: | 2011-03-10 04:50:05.000-0600 | Date Closed: | 2017-03-27 14:35:11 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_config_pgsql |
| Versions: | 1.8.3 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When realtime peer unregistred, asterisk update sip_user table with wrong value UPDATE asterisk_sip_users_tbl SET ipaddr = '(null)', port = '(null)', regseconds = '1299753779', defaultuser = '3001', useragent = '', lastms = '0', fullcontact = '' WHERE name = '3001' '(null)' is not NULL. after peer unregistred sip show peers show: Name/username Host Dyn Forcerport ACL Port Status Realtime 3001/3001 (Unspecified) D A 0 UNKNOWN Cached RT | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-03-31 12:22:29 res_config_odbc is more widely supported and tested. I would suggest you use that instead of res_config_pgsql directly if you're having any issues. By: Sean Bright (seanbright) 2017-02-28 12:30:02.876-0600 Are you able to reproduce this on Asterisk 13+? By: Sean Bright (seanbright) 2017-03-27 14:35:11.720-0500 I am not able to reproduce with Asterisk 13 from Git. Please re-open if you are able to reproduce. | ||