martin f krafft
2009-Jun-16 07:29 UTC
[asterisk-users] Unable to use # as feature key prefix
Hi folks, I was using the following featuremap: blindxfer => *1 disconnect => *9 atxfer => *2 parkcall => *7 automixmon => *0 and everything worked. Then the need arouse to use some features like automixmon during a conference, but MeetMet has the * key bound to the (admin) menu. Thus, in order to enable features like automon and transfers even during a conference, I tried to swap * fro # in the featuremap: blindxfer => #1 disconnect => #9 atxfer => #2 parkcall => #7 automixmon => #0 Unforunately, I cannot seem to make any of the features happen, neither during a normal call, nor during a conference. I've tried with multiple phones. What could be the problem? -- martin | http://madduck.net/ | http://two.sentenc.es/ "and if the cloud bursts, thunder in your ear you shout and no one seems to hear and if the band you're in starts playing different tunes i'll see you on the dark side of the moon." -- pink floyd, 1972 spamtraps: madduck.bogus at madduck.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090616/45de9618/attachment.pgp
Danny Nicholas
2009-Jun-16 14:56 UTC
[asterisk-users] Unable to use # as feature key prefix
The problem is the Asterisk Read function. It is set to accept as many 0-9 and * as you want to throw at it, then stop on # or timeout. Unless you disable the # stops, you can't use # in features. I would strongly caution against that because you would almost certainly break something else. -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of martin f krafft Sent: Tuesday, June 16, 2009 2:29 AM To: asterisk users mailing list Subject: [asterisk-users] Unable to use # as feature key prefix Hi folks, I was using the following featuremap: blindxfer => *1 disconnect => *9 atxfer => *2 parkcall => *7 automixmon => *0 and everything worked. Then the need arouse to use some features like automixmon during a conference, but MeetMet has the * key bound to the (admin) menu. Thus, in order to enable features like automon and transfers even during a conference, I tried to swap * fro # in the featuremap: blindxfer => #1 disconnect => #9 atxfer => #2 parkcall => #7 automixmon => #0 Unforunately, I cannot seem to make any of the features happen, neither during a normal call, nor during a conference. I've tried with multiple phones. What could be the problem? -- martin | http://madduck.net/ | http://two.sentenc.es/ "and if the cloud bursts, thunder in your ear you shout and no one seems to hear and if the band you're in starts playing different tunes i'll see you on the dark side of the moon." -- pink floyd, 1972 spamtraps: madduck.bogus at madduck.net
Seemingly Similar Threads
- feature keys no longer work after a call has been parked
- Problem: features (from features.conf) not available if call was originated by manager API or call file
- features.conf and mixmonitor stop and start
- Zap connection problem
- virt-manager slow to connect, hangs on new host dialog