Yealink Forums

Full Version: T23G Send incoming number to URL
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,
I need to send the incoming number to an URL, How can I configure action URL?
regards.
Dear´╝î

Good day!

You can configure the action URL the IP phone sends when receiving an incoming call, as below line:
http://192.168.0.20/help.xml?IP=$ip

For more detailed information, please refer to Action URL feature that the section of the Guide (on the page 709), download it via below link:
http://download.support.yealink.com/down...V81_90.pdf

Any question, freely to let me know.

BR,
Evan
Hello,

thank you for your reply.
But that I want to send is the incoming number, not the ip phone.
Thank you and regards.
Dear,

So sorry for late reply.

This line just for example, you can customize configuration according to you needed, and then please refer to the guide I sent to you before.

Any question, freely to let me know.

Best Regards,
Evan
(09-11-2017 10:03 AM)Evan_Yealink Wrote: [ -> ]Dear,

So sorry for late reply.

This line just for example, you can customize configuration according to you needed, and then please refer to the guide I sent to you before.

Any question, freely to let me know.

Best Regards,
Evan

Hi i just found the post, and the creator of the post is my coleague, he was unable to do it because a big amount of work and i just took the task at the same point.

What we need is to send by the Action Url on the event INCOMING CALL the number of the number calling.
I reffer to the administrator guide you post, not the same because is not available anymore but from the yealink website aswell.

The structure of an Action Url always seems to be the same

http://192.168.0.20/help.xml?IP=$ip

and following the manual...

action_url.incoming_call (page 318 from my manual)

http://192.168.0.20/help.xml?IP=$ip

So.. using the variable that i need.

$call_id ---- The call_id of the active call
or $calledNumber ---- not sure wich one but tried both

http://192.168.0.20/help.xml?PHONE=$call_id
http://192.168.0.20/help.xml?PHONE=$calledNumber

Where 192.168.0.20 is the IP from the machine that im making the GET request,.
It doesn't work.

Where working on a Yealink T23G

A help will be apreciated!!!

Thanks!!!
Dear,

Good day!

For your question, please refer below parameter:
http://10.2.2.31/help.xml?IP=$callerID

Where 10.2.2.31 is the IP from the machine that im making the GET request, isn't the IP phone's IP.

$callerID:The display name of the caller when the IP phone receives an incoming call.

$calledNumber:The phone number of the callee when the IP phone places a call.

For example:
Input this parameter into the field of the Incoming call, as shown below:
[attachment=4663]

Where 10.2.10.34 is the IP from IP phone, 10.2.2.31 is the IP from machine that im making the GET request. As we can see from the PACP trace packet, the IP phone send an HTTP GET request to server with the number of the caller when the IP phone receive an incoming call.
[attachment=4664]

Any question, freely to let me know.

Regards,
Evan
Thanks for the help!!!but still , i was unable to do it!!

I used:

http://192.168.2.56/help.xml?PHONE=$callerID
http://192.168.2.56/help.xml?PHONE=$call_id
http://192.168.2.56/help.xml?PHONE=$calledNumber



http://192.168.2.56/help.xml?IP=$callerID
http://192.168.2.56/help.xml?IP=$call_id
http://192.168.2.56/help.xml?IP=$calledNumber

where 192.168.2.56 is the IP from the machine that i make the request, NEVER THE PHONE IP. I also tried to the ip from our server being 192.168.2.10 and still not working.I got the trace and i only see protocol TCP, not a HTTP!!!


[Image: Action_URLcalled_ID.png]

[Image: PACP_TRACE.png]

[Image: trace2.png]

What am i doing wrong???

Thanks!!
All solved!!!! Thanks to all you guys, great forum and great help.
Here was the mistake, or better said, the solution.

http://192.168.1.212:8060/help.xml?PHONE=$callerID

Where the IP is from the machine making the GET request and the 8060 the listening port!Yeaahhhhhhhh-Link!

It was the freaking port of the listening server,obviously until it pop up in my mindBig GrinBig GrinBig Grin

Thanks eitherway for all the support.
Reference URL's