search for: to_meetme

Hi all, I'm having an odd problem with my polycom 301. I am initiating a call to it with AMI Originate() function: Action: Originate Channel: local/112 at Management Context: to_meetme Exten: s Priority: 1 Variable: dropped_conf=111 The "to_meetme" context is very simple: [to_meetme] exten=>s,1,MeetMe(${dropped_conf},id) If I specify every other device I have to test: * Grandstream 101 * XLite Client * My Cell Phone It works as expected. But with the Polycom, t...

...ecause of it. I can easily reproduce the problem with Polycom phones (but not the actual error). Just issue a .call file using the local channel calling one number and having the call bridged to a polycom phone (at least 301's here): Action: Originate Channel: local/111 at Management Context: to_meetme Exten: s Priority: 1 Async: true The above will cause the polycom to exhibit the behavior mentioned above. However, sending a .call file like the following causes the phone to work as it should: Action: Originate Channel: local/111 at Management Context: to_meetme Exten: s Priority: 1 Variable...

Working with asterisk 1.4; using the AMI Originate command, it is possible to do something like: Variable: CDR(accountcode)123456 Or must the variable names be "var[n]" where n is a number? I'd like to set the accountcode for a Local channel that originates a call. Thanks. -A -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE

Has anyone tried to used VB6 to communicate with the Asterisk Manager? If so, would you be willing to share some basic code showing your approach to getting connected and parsing results? I've got a Telnet control that is allowing me to connect, authenticate and see the "flow" of status, etc., but I'm sure there is a better way to do this without using Telnet (maybe not?). Any