-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Paul,
Le 20/11/2013 09:04, Paul Belanger a écrit : > Well, it is a way lot harder to figure out because you used > features.conf. Because of this, local channels are involved. Right, but this is sometimes necessary, and it's an asterisk feature. > Specifically, you are going to have to track the channel IDs and look at > the sequence of events. Then make an educated guess about what is > happening. ok, but it could be so much easier (and reliable) if we had a CEL (or AMI event) that tracks the requested atxfer, like the CLI debug message: [Nov 20 13:09:28] DEBUG[12002][C-00000174]: features.c:2701 builtin_atxfer: Executing Attended Transfer SIP/CROcqu0s-000002b5, SIP/ngqckJos-000002b6 (sense=2) Or adding the physical channel in the extra field of the CEL when CHAN_START event is fired for Local channels. Thanks, - -- Jean-Denis Girard SysNux Systèmes Linux en Polynésie française http://www.sysnux.pf/ Tél: +689 50 10 40 / GSM: +689 79 75 27 -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlKNeQoACgkQuu7Rv+oOo/isFQCeMTifSJNZ4IKS469dQFIkb+ti FNEAnR2pRTbNcCAIbOp5FS83/gGq1Fk9 =O7tw -----END PGP SIGNATURE----- -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
