[Asterisk-Users] Re: queue issue

2006-04-10 Thread Tomislav Parčina
In article [EMAIL PROTECTED], [EMAIL PROTECTED] says...
 On Thu, 06 Apr 2006 13:17:29 +0200, Tomislav ParÄŤina [EMAIL PROTECTED]  
 wrote:
 How did you modify it? and will the ATXFR be perceived as a discharge from  
 the queue system as a blind transfer using #?

features.conf

blindxfer = #1 ; Blind transfer
atxfer = #2; Attended transfer
automon = #9   ; One Touch Record
disconnect = #0; Disconnect


--
Tomislav Parcina
tparcina#lama.hr
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] Re: queue issue

2006-04-06 Thread Tomislav Parčina
In article [EMAIL PROTECTED], [EMAIL PROTECTED] says...
 on a related note, we notice that if we've set atxfer = *1 in features.conf 
 and blindxfer=#1, then attended transfers dont work. somehow, the Queue app 
 captures the '*' and hangs up the call. is this the behaviour others have 
 observed ? obviously, since we've used *2 for auto monitor, that doesnt 
 work as well.

Yes, this is well known (problem?). I have solved it by editing features.conf 
file.


--
Tomislav Parcina
tparcina#lama.hr
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Re: queue issue

2006-04-06 Thread Lenz
On Thu, 06 Apr 2006 13:17:29 +0200, Tomislav Parčina [EMAIL PROTECTED]  
wrote:



In article [EMAIL PROTECTED], [EMAIL PROTECTED] says...
on a related note, we notice that if we've set atxfer = *1 in  
features.conf
and blindxfer=#1, then attended transfers dont work. somehow, the Queue  
app
captures the '*' and hangs up the call. is this the behaviour others  
have

observed ? obviously, since we've used *2 for auto monitor, that doesnt
work as well.


Yes, this is well known (problem?). I have solved it by editing  
features.conf file.




How did you modify it? and will the ATXFR be perceived as a discharge from  
the queue system as a blind transfer using #?

Yours
l.




--
Loway Research - Home of QueueMetrics
http://queuemetrics.loway.it

___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Re: queue issue

2006-04-06 Thread Dinesh Nair



On 04/06/06 19:17 Tomislav Parèina said the following:

In article [EMAIL PROTECTED], [EMAIL PROTECTED] says...

on a related note, we notice that if we've set atxfer = *1 in features.conf 
and blindxfer=#1, then attended transfers dont work. somehow, the Queue app 
captures the '*' and hangs up the call. is this the behaviour others have 
observed ? obviously, since we've used *2 for auto monitor, that doesnt 
work as well.



Yes, this is well known (problem?). I have solved it by editing features.conf 
file.


i've opened a bug and provided a fix for this at 
http://bugs.digium.com/view.php?id=6897


on investigation into the source, it wasnt the queue app but rather 
chan_agent which was doing this.


--
Regards,   /\_/\   All dogs go to heaven.
[EMAIL PROTECTED](0 0)http://www.alphaque.com/
+==oOO--(_)--OOo==+
| for a in past present future; do|
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo The opinions here in no way reflect the opinions of my $a $b.  |
| done; done  |
+=+
___
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users