| Summary: | ASTERISK-08043: BLF not working when call-limit is enabled | ||
| Reporter: | Manuel Merelles (manuel) | Labels: | |
| Date Opened: | 2006-11-01 19:28:07.000-0600 | Date Closed: | 2006-12-01 04:01:28.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Subscriptions |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) sipdebug-CL-disabled.txt ( 1) sipdebug-CL-enabled.txt | |
| Description: | I require to activate BLF for the GPX2000 assistant phones, while limiting the maximum simultaneous calls to 2 for each user (250 extensions aprox.) I'm still unable to use BLF because it seems there's a bug when call-limit is present at sip.conf After several hours of testing in a laboratory environment, as well as performing some testings at our production asterisk, I realized the following: 1. BLF works well when call-limit=X is not present at sip.conf for the extensions you want to hint to. It properly shows IDLE / RINGING / BUSY when you run SHOW HINTS at CLI as well as lighting the phone leds. 2. As soon as I configure call-limit=2 for the sip devices and perform a sip reload, BLF stops working, it always reports IDLE no matter if the device is ringing, or on a call (BUSY). I tried call-limit 1, 2, 3 and there's no difference. It doesn't work. 3. I also realized, that removing call-limit and RELOADING asterisk to get BLF back to work doesn't solve the problem, you need to remove call-limit and RESTART asterisk to get it back to operation. We have tested several asterisk versions having the same behavior, it is always reproducible. asterisk 1.2.6 asterisk 1.2.12.1 asterisk 1.2.13 | ||
| Comments: | By: Olle Johansson (oej) 2006-11-04 12:49:46.000-0600 If this is the case, something must have been broken, because setting a call-limit will enhance the reporting, not disable it. Or should. I will have to look into this. By: Manuel Merelles (manuel) 2006-11-05 11:47:00.000-0600 Thanks for getting involved, I really need this to work. So, I'll be pleased to assist you to solve this. By: Serge Vecher (serge-v) 2006-11-09 11:02:13.000-0600 As per bug guidelines, you need to attach a SIP debug trace illustrating the problem. Please do the following for both call-limit enabled and disabled so we can see the difference. Thanks: 1) Prepare test environment (reduce the amount of unrelated traffic on the server); 2) Make sure your logger.conf has the following line: console => notice,warning,error,debug 3) restart Asterik. 4) Enable SIP transaction logging with the following CLI commands: set debug 4 set verbose 4 sip debug 5) Save complete console log to file and _attach_ said file to the bug. i.e. asterisk -Tvvvvvdddddgc | tee /tmp/sipdebug.txt By: Manuel Merelles (manuel) 2006-11-09 16:12:02.000-0600 I have uploaded the outputs. One file contains the outputs having call-limit configured, while the other debug file was performed without call-limit. We did the testings having NO traffic at asterisk as per your seggestion. By: Olle Johansson (oej) 2006-11-10 13:08:15.000-0600 Ok, Murf - check this too while you're into the device states! By: Olle Johansson (oej) 2006-11-30 01:55:21.000-0600 I can't confirm this, anyone else? By: Olle Johansson (oej) 2006-12-01 04:01:17.000-0600 Moving all of these discussions about subscriptions and call limits to bug ASTERISK-7238. Thanks. | ||