Yealink Forums
T22P Action URI ATrans and BTrans not working? - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Phone specific topic (/forumdisplay.php?fid=12)
+---- Forum: T2xP Series (/forumdisplay.php?fid=21)
+---- Thread: T22P Action URI ATrans and BTrans not working? (/showthread.php?tid=16634)



T22P Action URI ATrans and BTrans not working? - DaveThompson - 06-17-2016 10:20 PM

Hi,

I have been trying to get the remote calls for Transfers and Conference working with the T22P.

I am receiving http 404 responses when calling through to the ATrans and BTrans Action URI's, full form of these urls:
http://192.168.20.236/cgi-bin/ConfigManApp.com?ATrans=01628564670
http://192.168.20.236/cgi-bin/ConfigManApp.com?BTrans=01628564670

I have also tried:
http://192.168.20.236/servlet?ATrans=01628564670
http://192.168.20.236/servlet?BTrans=01628564670

All of which return a 404.

from the documentation I believe that this is the correct format, as I can get the CALLEND, and number=xxx&outgoing_uri=y forms working. I have tried this while both on and off calls, though I would expect it not to work while off a call.

I am able to successfully call through and do remote key presses, so I don't believe it's a security setting.

Does anyone know if this functionality works in this model of phone?

As an side, it appears the softkeys work, though it's not an ideal solution as getting the correct events to accept the transfer doesn't work:
http://192.168.20.236/cgi-bin/ConfigManApp.com?key=F_TRANSFER
http://192.168.20.236/cgi-bin/ConfigManApp.com?key=01628564670OK
-- warm transfer at this point
(gives an established event)
http://192.168.20.236/cgi-bin/ConfigManApp.com?key=F_TRANSFER
-- fully complete transfer (needs to be after answer)
(gives events in order: Transfer, Terminated, Attended Transfer)


Thanks in advance,
Dave


RE: T22P Action URI ATrans and BTrans not working? - Ec2 Solutions - 09-09-2019 02:54 PM

(06-17-2016 10:20 PM)DaveThompson Wrote:  Hi,

I have been trying to get the remote calls for Transfers and Conference working with the T22P.

I am receiving http 404 responses when calling through to the ATrans and BTrans Action URI's, full form of these urls:
http://192.168.20.236/cgi-bin/ConfigManApp.com?ATrans=01628564670
http://192.168.20.236/cgi-bin/ConfigManApp.com?BTrans=01628564670

I have also tried:
http://192.168.20.236/servlet?ATrans=01628564670
http://192.168.20.236/servlet?BTrans=01628564670

All of which return a 404.

from the documentation I believe that this is the correct format, as I can get the CALLEND, and number=xxx&outgoing_uri=y forms working. I have tried this while both on and off calls, though I would expect it not to work while off a call.

I am able to successfully call through and do remote key presses, so I don't believe it's a security setting.

Does anyone know if this functionality works in this model of phone?

As an side, it appears the softkeys work, though it's not an ideal solution as getting the correct events to accept the transfer doesn't work:
http://192.168.20.236/cgi-bin/ConfigManApp.com?key=F_TRANSFER
http://192.168.20.236/cgi-bin/ConfigManApp.com?key=01628564670OK
-- warm transfer at this point
(gives an established event)
http://192.168.20.236/cgi-bin/ConfigManApp.com?key=F_TRANSFER
-- fully complete transfer (needs to be after answer)
(gives events in order: Transfer, Terminated, Attended Transfer)


Thanks in advance,
Dave

Just in case anybody ever runs across this again in the future, this is the correct/complete URL to get it working:

http(s)://phone IP address/servlet?key=BTrans=xxx

e.g.
http://192.168.1.111/servlet?key=BTrans=1234


RE: T22P Action URI ATrans and BTrans not working? - DaveThompson - 09-10-2019 10:47 AM

(09-09-2019 02:54 PM)Ec2 Solutions Wrote:  Just in case anybody ever runs across this again in the future, this is the correct/complete URL to get it working:

http(s)://phone IP address/servlet?key=BTrans=xxx

e.g.
http://192.168.1.111/servlet?key=BTrans=1234

Thanks for the reply, I can't confirm whether this works or not any more, but hopefully it helps out someone in the future.