Hello.
I've experience a rather surprising behaviour of the AMI 1.1
> Event: Newstate^M
> Privilege: call,all^M
> Channel: SIP/XXXXXX-089c63b8^M
> ChannelState: 4^M
> ChannelStateDesc: Ring^M
> CallerIDNum: XXXXXXXX^M
> CallerIDName: YYYYYYYYY^M
> Uniqueid: 1256089773.59^M
Usually ChannelStateDesc gives me 'Ringing' but sometimes it only gives
me 'Ring', which drives my application to 100% CPU (OK, not a very
resilient app for now...)
My question is: is 'Ring' a specific state for a channel, or is it a
known bug in the AMI?
All the best,
--
Guillaume Yziquel
http://yziquel.homelinux.org/
_______________________________________________
-- 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
