| Summary: | ASTERISK-20356: JABBER_RECEIVE timeout in milliseconds, documentation says seconds | ||
| Reporter: | Noah Engelberth (mlnoah) | Labels: | |
| Date Opened: | 2012-09-04 08:21:38 | Date Closed: | 2012-09-27 16:05:47 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_jabber Resources/res_xmpp |
| Versions: | SVN | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS 6.3 | Attachments: | |
| Description: | When passing a timeout to JABBER_RECEIVE, the function is expecting time in milliseconds, but the "core show function" documentation from within the console says the timeout needs to be in seconds. | ||
| Comments: | By: Noah Engelberth (mlnoah) 2012-09-11 15:32:02.989-0500 It appears I reported this in error. Asterisk is honoring the timeout in seconds -- the "premature timeout" i was seeing was due to Asterisk receiving a bodyless message (typing notification) from the XMPP client, not a timeout problem. By: Mark Michelson (mmichelson) 2012-09-25 18:13:31.471-0500 So should this issue just be closed with no further action needing to be taken? By: Noah Engelberth (mlnoah) 2012-09-27 11:59:28.519-0500 I can no longer reproduce it reliably (or even that infrequently). | ||