Re: [asterisk-users] AMI interface problem

2009-01-09 Thread Barry L. Kline
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Mark Michelson wrote:

 
 Thanks for pointing this out. I have located the erroneous code and have 
 fixed 
 it in subversion, revision 161490. The next rc of 1.6.0 will not have this 
 bug.

Mark --

This bug still exists in the recently-released 1.6.0.3.  I just went
from 1.6.0.3-rc1 (which had the bug) to 1.6.0.3 with the same problem.
Reverting back to 1.6.0.1 makes the problem disappear.

Barry

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFJZ7nxCFu3bIiwtTARAtK8AKClSd5lEd0V1jxz7nsqwYEr1LUwmwCfbVRQ
+keIC2kqp4sZ1jFwy2jQq6E=
=PqM1
-END PGP SIGNATURE-

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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


Re: [asterisk-users] AMI interface problem

2009-01-09 Thread Tilghman Lesher
On Friday 09 January 2009 14:56:17 Barry L. Kline wrote:
 Mark Michelson wrote:
  Thanks for pointing this out. I have located the erroneous code and have
  fixed it in subversion, revision 161490. The next rc of 1.6.0 will not
  have this bug.

 This bug still exists in the recently-released 1.6.0.3.  I just went
 from 1.6.0.3-rc1 (which had the bug) to 1.6.0.3 with the same problem.
 Reverting back to 1.6.0.1 makes the problem disappear.

Mark erroneously assumed there would be another release candidate, which
there was not.  So while it's not in 1.6.0.3, it will be in the 1.6.0.4
release, when that occurs.

-- 
Tilghman

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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


Re: [asterisk-users] AMI interface problem

2009-01-09 Thread Barry L. Kline
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tilghman Lesher wrote:

 Mark erroneously assumed there would be another release candidate, which
 there was not.  So while it's not in 1.6.0.3, it will be in the 1.6.0.4
 release, when that occurs.

Thanks Tilghman.  I wait with bated breath.

Best regards,

Barry



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFJZ+rlCFu3bIiwtTARAoHRAJ9gjZl8D2QuNOfrBprnPbohaCj5qgCgotCY
tL6Cq+q+skp28mLAhbfZXlE=
=3xZD
-END PGP SIGNATURE-

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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


[asterisk-users] AMI interface problem

2008-12-05 Thread Jim Dickenson
I installed version 1.6.0.3-rc1 and my AMI application stopped working. I
reinstalled 1.6.0.1 and it worked again. I reinstalled 1.6.0.3-rc1 and it
stopped. Looks like a problem in the software to me.

Following the same steps using the same code for the AMI and conf files for
* I get bad behavior in 1.6.0.3-rc1 and good behavior in 1.6.0.1.

I have this action:

Action: Originate
Channel: SIP/GXP280-18
Application: queue
data: tqe
ActionID: callandqueue
Callerid: 12
Async: true


And I get this response:

Response: Error
ActionID: callandqueue
Message: Channel not specified

Is anyone else seeing anything like this?


-- 
Jim Dickenson
mailto:[EMAIL PROTECTED]

CfMC
http://www.cfmc.com/




___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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


Re: [asterisk-users] AMI interface problem

2008-12-05 Thread Mark Michelson
Jim Dickenson wrote:
 I installed version 1.6.0.3-rc1 and my AMI application stopped working. I
 reinstalled 1.6.0.1 and it worked again. I reinstalled 1.6.0.3-rc1 and it
 stopped. Looks like a problem in the software to me.
 
 Following the same steps using the same code for the AMI and conf files for
 * I get bad behavior in 1.6.0.3-rc1 and good behavior in 1.6.0.1.
 
 I have this action:
 
 Action: Originate
 Channel: SIP/GXP280-18
 Application: queue
 data: tqe
 ActionID: callandqueue
 Callerid: 12
 Async: true
 
 
 And I get this response:
 
 Response: Error
 ActionID: callandqueue
 Message: Channel not specified
 
 Is anyone else seeing anything like this?
 
 

Thanks for pointing this out. I have located the erroneous code and have fixed 
it in subversion, revision 161490. The next rc of 1.6.0 will not have this bug.

Mark Michelson

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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