Yealink Forums

Full Version: Visual Alert for BLF Pickup - brings up "unkown"
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hey there,

We're using several T4x Series phones on an FreePBX (Asterisk) System. (T41P, T46G and T48G)

Now, because there obviously is no other way, we want to enable the "Visual Alert for BLF Pickup" Option.

The thing is, it partially works. But the CID of the calling one (no matter if external, or internal caller) is always shown as "unknown"

we really are standing in front of a wall, and don't know what to do further to correct this behaviour.

We hope, one of you can help us out.

cheers!
Is it possible that this is a result of using PJSIP instead of SIP Protocol?

[EDIT]
We added

notifycid=yes
sendrpid=pai
trustrpid=pai
notifyringing=yes

into pjsip_custom.conf (FreePBX/Asterisk), but no positiv result so far.
We found this in another forum but from 2013...

What else can we do? I can't find any other option inside the phone setup. We obviously do oversee something in the asterisk settings, but what?
any ideas?
(10-12-2016 02:33 PM)P_Hackert Wrote: [ -> ]Is it possible that this is a result of using PJSIP instead of SIP Protocol?

[EDIT]
We added

notifycid=yes
sendrpid=pai
trustrpid=pai
notifyringing=yes

into pjsip_custom.conf (FreePBX/Asterisk), but no positiv result so far.
We found this in another forum but from 2013...

What else can we do? I can't find any other option inside the phone setup. We obviously do oversee something in the asterisk settings, but what?
any ideas?

Hi Sir,

Please provide the level 6 syslog, config.bin and pace trace to the Lucia@yealink.com when you reproduce the issue to do more trouble shooting. About how to get the three files, please refer to the link below:
http://support.yealink.com/faq/faqInfo?id=313
I've started the log recording. See file attatched.

I'm quite sure that there's an issue with the PJSIP Protocoll we're actually using. It seems that not all information will find its way through this protocol. CHAN_SIP might work better. We'll give it a try soon and report here afterwards.

If you can find something in this logfiles and you may know a way to fix it, please let us know Smile
Hi, have you fixed?
I have exactly the same problem and Chan_Sip.
No idea how to solve it.
Reference URL's