(06-05-2017 12:15 PM)joao.schlemm Wrote: Hello Kevin,
You are right, everything works very well, despite the call forwarding and also the Music on Hold (but we can survive without the last for a while!) 
By the way, Cisco Call Manager can handle Third party phones as well with their own phones. Features like Transfer, Hold, Conference, Auto Redial, LDAP works like a charm!
Recently we approve Yealink T19 E2 Phones as the alternative to the Cisco basic Phones. In our environment we have something like 3.000 IP phones and other 4.000 conventional TDM, that we are planing to migrate in the next years with the new projects.
Attached are the two cenarios, the first with a normal call (Ext. 7235 call to Ext. 5065) and the other with the Call Forward feature activated (Ext. 6321 call to Ext. 7235 forwarded to Ext. 5065). As we can see, the Yealink handle well with the transfer, but when activate the Call Forward, the Cisco Call Manager answer is "Call cannot be completed as dialed", like the number does not exist (we tried with all possible combination, but with no sucess!). About the Cisco syslog, pacp we can provide as soon as we build the lab.
Thanks in advance,
Hello friend
Thanks for those files with information. From the files, i can see that:
6321 call 7235, 7235 reply 302 with 5065 number.
Now we can't see wht 6321 don't invite 5065 after 302. So please help test again and export pacp,syslog,config.bin from 6321/7235/5065 and cisco server side.
I need all files from the all party, then i can know which part have this issue.
For the new projects, can you share me about it? May i know do you ever contact with yealink sales? Can you tell me your plan?
Maybe we can contact via personal email kevin@yealink.com if you don't share private information on forums.
BR
Kevin
