similar to: chan_agent MOH was (Re: CVS Error 2003-06-19)

chan_agent.c: In function `login_exec': chan_agent.c:595: parse error before '<<' token chan_agent.c:602: parse error before '>>' token make[1]: *** [chan_agent.o] Error 1 make[1]: Leaving directory `/usr/src/asterisk/channels' make: *** [subdirs] Error 1

Hi I am trying Manager interface for originate a call. This is what I get --------------- Action: Originate Exten: 555 CallerID: test <6656> Context: local Timeout: 600 Channel: SIP/8782 Priority: 1 Response: Error Message: Originate failed ---------------- What do I do wrong? Thank you Serge _________________________________________________________________ MSN Premium with Virus Guard

Hello, I am trying to run festival, it is running but I am getting this when I run tts_ping.agi WARNING[278546]: File app_festival.c, Line 304 (festival_exec): Text passed to festival server : Enter the eye-p address you wish to ping. WARNING[278546]: File app_festival.c, Line 381 (festival_exec): Passing text to festival... WARNING[278546]: File app_festival.c, Line 400 (festival_exec):

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge kernel module. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge kernel module. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge kernel module. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

AGI's are resulting in unusual behaviors. Can someone please tell me if this is my inappropriate use of AGI's, inappropriate use of Time::HiRes, or a bug with *: I call this script twice: #!/usr/bin/perl use Time::HiRes qw( gettimeofday ); ($seconds, $microseconds) = gettimeofday; $hirestime = sprintf("%s","$seconds$microseconds"); print "SET VARIABLE

Hi, I have more or less decided to do with the SNOM phones for the next stage of testing with Asterisk becasue they seem to be the best value for money and have support for the GSM codec and easy upgrades.. But now I have to decied wheather to get the 100 or 200 and if its the 200 then I need to have some justification for the extra cost.. Can someone who knows these 2 phones tell me what the

O -fPIC -c -o chan_agent.o chan_agent.c chan_agent.c: In function `login_exec': chan_agent.c:595: parse error before '<<' token chan_agent.c:602: parse error before '>>' token make[1]: *** [chan_agent.o] Error 1 make[1]: Leaving directory `/usr/src/asterisk/channels'

Hey, We've been working on tracking all inbound calls to certain call-centre members and have hit a snag, it seems when a queue delivers a call to an Agent, chan_agent will call Local/whatever but provide no means of associating the call in the queue with the local call. To that end i added in an event called AgentAssociate which looks like this: 'DestChan' =>

AgentCallBackLogin is going to be deprecated, so I've decided to emulate chan agent using AQM and RQM funcions and Local channel. I use asterisk 1.2.13 and latest 1.2.x. zapata. I used example 2 from http://www.voip-info.org/wiki/view/Agents+without+agent+channel and example from queues-with-callback-members.txt from asterisk 1.4 doc directory. My dialplan is very similar to Digium's

I am beating my head against a problem where queue calls offered by Agent channel to a SIP UA cannot be REFER transferred if the target UA/extension hasn't accepted the call. If the members of the queue are SIP channels, this is not a problem. I suspect chan_agent isn't flagging the bridge from Zap/n -> SIP/n properly, or this is by design. The following line is what is spoken before

First, many thanks to Greg Boehnlein for his patch to chan_agent.c for adding a "preackannounce" option. I am running CVS HEAD from 2005/07/31, and the patch failed in a few hunks, since the code was refactored to add in some CASE statements where there were compound if statements before. Anyway, I have successfully updated the patch to work against head as of 3 weeks ago, and would

Does anyone know what this means? It is in DMESG, and we have people complaining about echo. Disabled echo canceller because of tone (rx) John

Has anyone solved the problem on the ADSI phones that when you hit one of the soft keys, the Number Pad stops working?

I'm trying to fix a problem with the GrandStream Budgetone 102. I've been reading the source code, mailing lists and other resources. Here's the scenario and the approach I have been pursuing. I'm having some problems with the AGI calls and I hope someone can give me some clarification. PSTN <---> T1,PRI * <---> Grandstream BT 102 (12)

2008-01-18 22:04 +0000 [r99080-99085] Russell Bryant <russell at digium.com> * CREDITS, include/asterisk/http.h, main/tcptls.c (added), main/manager.c, channels/chan_sip.c, doc/siptls.txt (added), main/Makefile, main/http.c, include/asterisk/tcptls.h (added), configs/sip.conf.sample, CHANGES: Merge changes from team/group/sip-tcptls This set of changes

Hey all, Did I see something on here about using an AGI script to do reverse lookups via anywho.com? I have a PRI that only gets caller-id number and no Alpha. TIA, -- Daniel Jimenez <djimenez[at]pobox[dot]com>

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA