| Summary: | ASTERISK-09099: ExtensionState action reports wrong extension state in 1.4.2 | ||
| Reporter: | Andre Courchesne (acourchesne) | Labels: | |
| Date Opened: | 2007-03-25 16:21:18 | Date Closed: | 2007-03-26 09:58:39 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) Manager_ExtensionState_Bug.pdf | |
| Description: | When using the ExtensionState action of the manager API, it will report a status of 0 if the queried extension is in fact busy. Same test ran with Asterisk 1.2.9 and 1.2.17 reports the extension as busy. See attachment Manager_ExtensionState_Bug.pdf for the exact information on tests conducted and results. | ||
| Comments: | By: Andre Courchesne (acourchesne) 2007-03-25 20:38:05 Just stumbled on bug id 8800 which looks related. By: Andre Courchesne (acourchesne) 2007-03-25 22:08:27 Ok, just tried 1.4.0 and 1.4.1 with the exact same method and they do the same as 1.4.2 By: Andre Courchesne (acourchesne) 2007-03-25 22:13:36 Ok, on 1.4.1, just tried a proposed "patch" in bug 8800 which involved adding limitonpeers=yes in the [general] section of sip.conf and call-limit=4 in the sip extension configuration. Well, it worked for me, but the question are, 1. Is this by design? If so why? 2. Why was this working in 1.2 without those 2 parameters? By: Serge Vecher (serge-v) 2007-03-26 09:58:38 this was indeed by design and related to devicestate changes that occured in chan_sip between 1.2 and 1.4. I'll add a request to 8800 that this is documented a bit clearer in UPGRADE.txt. | ||