Yealink Forums

Full Version: Call-Info sip header for T46G
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

the user manual says that the sip header "Call-Info" is supported for the T46G model. Which purposes are supported?

I tried the icon purpose, but this didn't work for basic picture formats. I used the format (Asterisk):
SIPAddHeader(Call-Info: <http://<ip>/callinfo/test.bmp>\;purpose=icon)

I have SIP phones from a different vendor where things work as expected. Therefore the Asterisk configuration is unlikely the problem.
Please test with below syntax.
Call-Info: <http://ip/callinfo/test.bmp>;purpose=icon
This does not work. The ";" needs to get escaped because it is the line comment character in Asterisk. Asterisk will just stop to process the line when it sees the ";".

Some phones support the alternate syntax Call-Info: icon=http://<ip>/callinfo/test.bmp, but this doesn't work either.

I just checked that the SIP header is send correctly when Call-Info: <http://<ip>/callinfo/test.bmp>\;purpose=icon. The "\" is removed by the dialplan interpreter and the header is as intended.
Do you use the latest version of T46G which can support call-info and alert-info message?
Copied from the Status page:
Version

Firmware Version 28.72.0.1
Hardware Version 28.1.0.128.0.0.0

This should be the latest firmware.
@Yealink Support: Can you confirm that Call-Info is not working with the recent firmware, or is it supposed to work?
Hi sidjf3zhdu,

It seems that this format can't take effect and i am consulting our engineer the exact format.
Thank you.
Hi sidjf3zhdu,

Yealink phones do support "Call-Info: <http://<ip>/callinfo/test.bmp>\;purpose=icon" .
If your phone still can't work with this call-info, please supply me syslog level 6, config.bin and pcap.
How to Get the Correct Syslog, Config.bin and Trace
Hello,

I just encountered exactly the same issue in firmware v28.83.19.2 and hardware v28.2.0.128.0.0.0, where a T46G is getting called without handling the picture specified in call-info header. Any updated information about this?

Attached is what I have seen in the syslog.

Thank you in advance.

Jiansong
Reference URL's