It should have the name popup in MP if it is in the name subtitutions list of YAC. Does your little YAC window show the name for the caller correctly?
Hi I have been using the external YAC plug-in since starting with MP as it paused media when a call comes in. Here is the updated version that I compiled if anyone wants it. It needs to go into the process directory e.g. on XP "C:\Program Files\Team MediaPortal\MediaPortal\plugins\process" or where ever it sits in your system. (If you have what was the old core caller id plug-in they will need to be disabled, configure plug-in from your plugins section of MediaPortal-Configuration). Hope this is useful for those who say they can't get it to work in 1.2.1Final and want to pause media on incoming call.
Hi RoChess
This doesn't happen on my system and I presume not on others so a few questions:
1./ Is your YAC host service running on your MP system?
2./ Do you have the YAC client running on your MP system?
3./ What is your modem type and model number?
4./ Can you check your YAC caller log file and see how many entries are there for each call e.g. 1 or more?
5./ There should be some more entries in the MP logfile (info)ones above the debug you provided. These show the calling information as per below, need to know if it's receiving multiple call information for a single call! Close your mediaportal client, open it again then make a test call, clear the popup(s) and post the whole MediaPortal.log file thanks (I want to also check what other plugins are load and that sequence will tell me).
1./ RoChess can I ask for your MP.log (one more time) file as before, but 1st open up MP configuration go to the general tab and set Verbosity to 'debug' please.
2./ Can you also do a test listeners from the YAC listeners screen and see if it gives the same problem.
I see you are running vista
I personally have the YAC host on an XP machine (with external USB modem) with a MP client running, plus a win7 machine with the MP server and MP client none of these exhibit or issue you experience.
Hoping the full debug log gives me some clues!
I have moved some code around in the external plugin so you could try that first v1.1.2