[mythtv-users] mythmessage - what I learned

[Scott & Nicole Harris]

>Nb
>On Jun 24, 2012 11:19 PM, "Michelle Dupuis" <mdupuis at ocg.ca> wrote:
>>
>> based on reading lots of posts, I thought I would summarize for any 
>> others interested:
>> 1. The wiki is wrong - the default port in use my mythmessage is 6948 
>> (not 6549)
>> 2. The wiki is wrong - mythmessage won't listen to broadcasts, only 
>> packets directed just to that IP
>> 3. The wiki is incomplete - the timeout for messages ONLY applies while 
>> playback is in progress.  Otherwise, timeout is ignored and an OK button 
>> appears and the message stays on screen, and queue >>up.
>>
>> And of interest...messages queue up on screen!  So if you plan to use 
>> mythmessage interface to show CID info, you may find 100 dialog boxes 
>> queued up all waiting for an OK click...when you return to >the frontend
>>
>> yuk....

>I just went through this myself.  I tweaked my cid script to query each fe 
>and only send the message if playback was in progress to avoid messages 
>piling up on the other fes.

Could you share that script?  I have held off on integrating CID info with 
my FreePBX / MythTV setup because of the timeout issue.  Then I'll just have 
to figure out how to have FreePBX execute a script when a call comes in.