| Summary: | ASTERISK-15896: (Regression) Pickup from Grandstream BLF button ignores the context specified in Pickup command | ||
| Reporter: | airman (airman) | Labels: | |
| Date Opened: | 2010-03-30 13:58:01 | Date Closed: | 2011-06-07 14:05:12 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_directed_pickup |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | We have Grandstream GXP2000 phones with buttons programmed as BLFs. In sip.conf, we specify: context=default subscribecontext=blf In the default context, we have: exten => _**5XX,1,Pickup(${EXTEN:2}@extensions) When you press the BLF button and the extension is busy, the phone dials **5XX instead of 5XX. Starting with Asterisk 1.6.2, this stopped working. Instead of picking up 5XX@extensions (as specified by the Pickup command), it tries picking up 5XX@blf. Dialing **5XX by hand still works correctly. Everything worked fine in Asterisk 1.6.1.x. Here is the output from asterisk -r -v... when we try pressing the BLF button: [Mar 30 09:48:26] NOTICE[30223]: chan_sip.c:19860 handle_request_invite: Trying to pick up 520@blf [Mar 30 09:48:27] NOTICE[30223]: chan_sip.c:19860 handle_request_invite: Trying to pick up 520@blf [Mar 30 09:48:27] NOTICE[30223]: app_directed_pickup.c:257 pickup_exec: No target channel found for 520. Let me know if you need any more information. Thanks. | ||
| Comments: | By: Leif Madsen (lmadsen) 2010-03-31 10:07:18 Required: * complete console output from start to finish of call * SIP trace from the console * related configuration of dialplan and sip.conf in order to reproduce this issue The information from both 1.6.1 and 1.6.2 would be ideal so we can determine what is different between the versions. By: Paul Belanger (pabelanger) 2010-04-28 16:14:22 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||