| Summary: | ASTERISK-22504: [patch] chan_iax2: wrong expiry time in astdb | ||
| Reporter: | Stefan Wächtler (brietz) | Labels: | |
| Date Opened: | 2013-09-11 05:03:13 | Date Closed: | 2013-09-16 11:38:01 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_iax2 |
| Versions: | 11.5.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) chan_iax2.c.patch | |
| Description: | When a new IAX2 client registers, the astdb database is updated with the value of _minregexpire_ defined in iax.conf instead of using the expiry time that is provided by the client. (The provided expiry time of the client is updated after inserting the astdb entry.)
As a consequence, restarting or reloading asterisk creates clients whose registration may expire before they reregister. The clients are therefore unavailable after _minregexpire_ seconds until they reregister. The correct reregistration time in astdb is only set up, when asterisk detects a change of ip:port of an already registered client that does reregister (astdb is updated in this case). Bugfix: Use the expiry time provided by the client to update astdb. | ||
| Comments: | By: Stefan Wächtler (brietz) 2013-09-11 10:37:02.669-0500 Set expire time that is provided by client before updating astdb entry. By: Matt Jordan (mjordan) 2013-09-12 18:49:02.813-0500 Thanks for providing a patch Stefan! By: Stefan Wächtler (brietz) 2013-09-16 12:19:15.930-0500 Thanks for applying the patch! ;) | ||