search for: blem

Hmm i found the problem... I?m using a Grandstream BT100. The transfer just works in a queue if I first acknowledged the call using the # key, and then press the TRANSFER key in the Grandstream. In the asterisk console I receive a: -- SIP/4002-4563 acknowledged Then I can transfer the call... Weird because i?m using...

...use? Try using the # transfer. Hope that helps.. Guido Hecken -----Urspr?ngliche Nachricht----- Von: Diego Magalh?es [mailto:diego@redetaho.com.br] Gesendet: Mittwoch, 2. Februar 2005 17:21 An: asterisk-users@lists.digium.com Betreff: [Asterisk-Users] AgentLogin / AgentCallbackLogin transfer problem Hello guys, I?m running Asterisk CVS-HEAD-02/01/05-12:22:46 and having a problem with call transfers using the cmds AgentCallBackLogin and AgentLogin... First Case (using cmd AgentCallbacklogin): When the incoming call comes and enters the queue, the agent logged in answer the call. But when I...

faced this exact same problem a few times on more than one servers and it was 1) dialplan issue which was not hanging up the zap channels correctly 2) using more than 8 spans on a server. Asterisk can't handle more than 96 zap channels on T1s. FXO/FXS combinations can vary the number of spans but if you know what I mean by...