Summary: | ASTERISK-07921: Pickup feature not usable... | ||
Reporter: | generalfiretech (generalfiretech) | Labels: | |
Date Opened: | 2006-10-12 09:12:51 | Date Closed: | 2006-11-14 10:24:22.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | we are using 2 hfc cards through bristuff-0.3.0-PRE-1s with zaptel and zaphfc. DTMF detection works and so it is perfectly possible, to use builtin asterisk feature extensions, for example atxfer or blindxfer. BUT if we want to use pickup feature in order to catch a call on another phone, the "feature extension" is not properly recognized. Log tells me: Extension '*8' in context 'from-internal' from '10' does not exist. Rejecting call on channel 0/2, span 1 This sucks! Using misdn brought us many problems, but this one worked... Did i do something wrong in configuration? THX in advance, R. Oldenburg - GFT ****** ADDITIONAL INFORMATION ****** zaptel.conf: loadzone=de defaultzone=de # 1. Karte span=1,1,3,ccs,ami bchan=1-2 dchan=3 # 2. Karte span=2,1,3,ccs,ami bchan=4-5 dchan=6 zapata.conf: [channels] ; 1. Karte im NT-Modus musiconhold=default useincomingcalleridonzaptransfer=yes switchtype=euroisdn priindication=outofband ;inband signalling=featd usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=no callreturn=yes echocancel=yes echocancelwhenbridged=yes echotraining=yes echotraining=800 relaxdtmf=yes cidsignalling=DTMF cidstart=polarity rxgain=7% txgain=8% callgroup=1 pickupgroup=1 signalling=bri_net_ptmp pridialplan=unknown prilocaldialplan=unknown echocancel=yes immediate=no usecallingpres=yes overlapdial=yes group=1,3 context=from-internal channel=>1-2 ; 2. Karte im NT-Modus musiconhold=default useincomingcalleridonzaptransfer=yes switchtype=euroisdn usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=no callreturn=yes echocancel=yes echocancelwhenbridged=yes echotraining=yes echotraining=800 relaxdtmf=yes cidsignalling=DTMF cidstart=polarity rxgain=7% txgain=8% callgroup=1 pickupgroup=1 signalling=bri_net_ptmp pridialplan=unknown prilocaldialplan=unknown echocancel=yes immediate=no usecallingpres=yes overlapdial=yes group=2,3 context=from-internal channel=>4-5 features.conf: ; ; Sample Parking configuration ; [general] ; do not manually enter parkinglot config information, use the parkinglot module ; ; the parking_additional.inc file is auto-generated by the Parkinglot Module, do ; not hand edit that file #include parking_additional.inc #include features_general_custom.conf [featuremap] blindxfer => *# ; Blind Transfer disconnect => *0 ; Disconnect Call ;automon => *1 ; One Touch Record atxfer => ** ; Attended Xfer pickupexten = *8 | ||
Comments: | By: Serge Vecher (serge-v) 2006-11-07 14:36:56.000-0600 briStuff is not officially supported by the Asterisk project. You have to reproduce the problem with a clean Asterisk tarball installation in order for us to help you. By: Matthew Fredrickson (mattf) 2006-11-07 16:11:03.000-0600 Yes, if there is a problem with chan_zap using bristuff, then we can't really do anything about it. bristuff patches up chan_zap quite a bit, and very likely this is a bug in bristuff. By: Serge Vecher (serge-v) 2006-11-14 10:24:22.000-0600 feel free to reopen if reproducable as per note ASTERISK-5262083 |