I repeat “as is” the title of a post someone did a few months ago,
since I am facing the same problem and did not see one single answer
to his post. Maybe I’ll be a little bit more lucky.
When I’m trying to issue an Atxfer AMI command, in the asterisk 1.8
branch, what happens is that some DTMF’s are sent, like this :
[Mar 22 15:46:27] DTMF: channel.c:3900 __ast_read: DTMF end ‘1’ received on SIP/bmwgsjrponciuj-0000009f, duration 0 ms
[Mar 22 15:46:27] DTMF: channel.c:3926 __ast_read: DTMF begin emulation of ‘1’ with duration 100 queued on SIP/bmwgsjrponciuj-0000009f
[Mar 22 15:46:27] DTMF: channel.c:4018 __ast_read: DTMF end emulation of ‘1’ queued on SIP/bmwgsjrponciuj-0000009f
[Mar 22 15:46:27] DTMF: channel.c:3900 __ast_read: DTMF end ‘4’ received on SIP/bmwgsjrponciuj-0000009f, duration 0 ms
[Mar 22 15:46:27] DTMF: channel.c:3926 __ast_read: DTMF begin emulation of ‘4’ with duration 100 queued on SIP/bmwgsjrponciuj-0000009f
It is compliant with what is written into the main/manager.c code,
but I am unable to find the reason why and/or under which conditions
my phone should handle these values like a request for attended transfer.
For the record, I have seen that a patch had been submitted a while ago :
http://bugs.digium.com/view.php?id=10585, with some files kined, like
this one :
we can find under “atxfer-trunk-r90428.diff”
Besides, it appears :
that the difference has nothing to do with the original patch,
despite the comment
Adding the Atxfer manager command. With this, you may initiate
an attended transfer over AMI
(closes issue #10585)
Reported by: ornati
atxfer-trunk-r90428.diff uploaded by ornati (license 210)
(with modifications from me)
Tested by: putnopvut
(Modified Wed Mar 5 22:33:05 2008 UTC (3 years ago) by mmichelson)
Of course it is written “with modifications from me”, but my main point
is : what’s the reason behind this way of handling the atxfer ?
What would be the configuration tweaks in order to achieve this to work ?
On asterisk ? On my phone(s) ?