Re: Meteor caller id help

[James <james@xxxxxxx>]

--------------060209080202060602010501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I think a few things are going on here that's complicating things.
Firstly to answer the why is it talking question. The plugin, through
the wizard, is able to access any xAP device but there are some schemas
that the plugin supports beyond the wizard. It supports the X10 schema
to allow xAP devices to send X10 messsaes through HomeSeer.
HomeSeer.Command to control HomeSeer. Email sending using the standard
email schema to allow xAP devices to send email through the builtin
HomeSeer. Text to speech using the HomeSeer voice engine.  This will
explain why HomeSeer is talking the Switchboard messages. Now to why
changing the source make it stop.  Every xAP message received by the
plugin is matched against a list of known devices. If the source address
is matched then the xAP message is process, if however the source
address isn't known then the message is diverted into the new hardware
wizard. What  I'm guessing is that one of your source addresses is know
by the plugin and so the message is spoken and the other one isn't.
Now i'm not sure why the speech is repeating by homeseer this is either
the plugin or homeseer itself doing this. i'll look into it.
What you really what to do is add some targets to these xAP messages.
Targets allow a xAP message to be delivered only a specific device.

xap-header
{
v=12
hop=1
uid=FF812800
class=tts.speak
source=KCSoft.Send.Anya
target=mi4.speech.anya
}
tts.speak
{
Say=this is a zap speech test.
Volume=100
}

for example would only cause mi4.speech.anya to speak  or in the case of
the tosend file in switchboard:
<start>
Type=tts
Target=mi4.speech.anya
L1=*Direction**LineDescription* Call from *NameCompanyNumberSpace*
<end>

Hope this all makes sense

James

Ian Davidson wrote:

>Hello
>
>I have tried to find out why I have the TTS error. I downloaded the
>xapsend app and the xap speech app and installed onto my main pc.
>
>I tried sending other xap tts messages, they worked fine and were only
>spoken by the xap tts app and not homeseer. I then started changing the
>xap message to see what caused homeseer to speak it. Below are two
>messages the first one works normally and the second gets spoken by
>homeseer continuously until it is terminated.
>
>1st message
>xap-header
>{
>    v=12
>    hop=1
>    uid=FF812800
>    class=tts.speak
>    source=KCSoft.Send.Anya
>}
>tts.speak
>{
>Say=this is a zap speech test.
>Volume=100
>}
>
>2nd message
>xap-header
>{
>    v=12
>    hop=1
>    uid=FF812800
>    class=tts.speak
>    source=mi4.switchboard.GALEFORCE9-MAIN
>}
>tts.speak
>{
>Say=this is a zap speech test.
>Volume=100
>}
>
>The only thing that has changed is the source but I don't understand
how
>this could be causing the fault. Can anyone tell me what's happening or
>suggest any other tests to try to eliminate this.
>
>Thank you
>
>Ian D
>
>
>-----Original Message-----
>From: xap_automation@xxxxxxx
>[mailto:xap_automation@xxxxxxx] On
Behalf Of Ian Davidson
>Sent: 27 August 2005 20:01
>To: Ian
>Subject: RE: [xap_automation] Meteor caller id help
>
>Hello Kevin
>
>Ok I managed to grab 1/2 hour to see if I could see what was happening.
>I installed the viewer onto the server and everything was correct.
>However I did find the exact text which was being spoken and logged.
Xap
>switchboard was sending out a tts message. I did not realise the
>homeseer plugin would automatically speak a Xap tts message, and I do
>not know why it is repeated until homeseer is destroyed.
>
>Anyway I looked at the Xap switchboard confg but could not see how to
>disable the sending of tts messages. After looking in the install
>directory I found
>
>Tosend.txt
>
>And removed the following lines
>
>'<start>
>'Type=tts
>'Target=>
>'L1=*Direction**LineDescription* Call from *NameCompanyNumberSpace*
>'<end>
>
>Problem is now cured although I think I would sooner get to the bottom
>of this, it is likely to come back and attack again!
>
>Ian D
>
>
>-----Original Message-----
>From: xap_automation@xxxxxxx
>[mailto:xap_automation@xxxxxxx] On
Behalf Of Kevin Hawkins
>Sent: 27 August 2005 13:31
>To: Ian
>Subject: Re: [xap_automation] Meteor caller id help
>
>Hmm curious - I must admit I use xAP TSS for my incoming call
>announcements and not HomeSeer , and that works fine. What would be
>useful is to look at the xAP messages in xAP Viewer and see if you are
>getting a flood of those, if so which ones and which specific one
>triggers the situation. I will also try this myself and see if I can
>reproduce it, although I am currently running HS v2 . The interaction
>with xAP Switchboard is quite 'stateful' as the call progress messages
>go through a sequence and this might make it awkward to identify the
>issue, it may also confuse xAP SB if the messages arrive out of order.
>
>The install version of xAPTel is slightly out of date - I will send you
>the latest offlist , although the changes are minor and I don't think
>will have any bearing on this. I would also recommend disabling
"Basic
>CID Schema" in the configuration box (save and restart xAPTel).
This
>occasionally causes duplicated announcement messages as xAPTel is
>sending two callerID schemas if this is enabled. However you would have
>only got 2 and not continually repeating announcemnets. Which version
of
>
>the xAP HS plugin are you running BTW ? I need to also work out just
how
>
>that announcement happens - the ' incoming call from ....' bit - is
that
>
>generated in a script or is it an inbuilt aspect of HS. xAP SB can
>generate very similar TTS messages but as the speech is hapening from
>the HS server machine and you dont have xAP TTS it is curious .
>
>Kevin
>
>Ian Davidson wrote:
>
>
>
>>Hi All,
>>
>>I have Homeseer 1.7 installed on my main server which up until now
>>used a pace modem for caller id. I installed XAP plugin a while
back
>>to allow me to interface to a netiom I had purchased and all is
fine.
>>
>>Yesterday I received my Meteor to replace the Pace as it only
worked
>>once in a blue moon. Rather than upset the server install I decided
to
>>
>>
>
>
>
>>try it on my main pc. I have a XAP hub running, XAPtel to talk to
the
>>Meteor and XAP switchboard to log calls. All setup in minutes and
>>working 100%. However when I receive an incoming call my homeseer
>>install on the server announces the call constantly with the voice
>>saying "incoming call from xxxxxxxx". The log also fills
up with the
>>message and homeseer becomes unresponsive and has to be killed. I
do
>>not have any scripts that contain "incoming call", if I
disconnect the
>>
>>
>
>
>
>>server from the network it no longer sees the CID info so it has to
be
>>
>>
>
>
>
>>coming from the XAP message. I have not set CID up in homeseer, I
>>haven't even set up the CID devices within the plugin yet! Can
anyone
>>shed any light on this so I can stop it happening?
>>
>>Thanks
>>
>>Ian D
>>
>>
>>
>>
>>
>------------------------------------------------------------------------
>
>
>>YAHOO! GROUPS LINKS
>>
>>    * Visit your group "xap_automation
>>      <http://groups.yahoo.com/group/xap_automation>"
on the web.
>>    * To unsubscribe from this group, send an email to:
>>      xap_automation-unsubscribe@xxxxxxx
>>
>>
>>
><mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe>
>
>
>>    * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>>      Service <http://docs.yahoo.com/info/terms/>.
>>
>>
>>
>>
>>
>------------------------------------------------------------------------
>
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>


--------------060209080202060602010501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">


Hi,<br>
<br>
I think a few things are going on here that's complicating things.
Firstly to answer the why is it talking question. The plugin, through
the wizard, is able to access any xAP device but there are some schemas
that the plugin supports beyond the wizard. It supports the X10 schema
to allow xAP devices to send X10 messsaes through HomeSeer.
HomeSeer.Command to control HomeSeer. Email sending using the standard
email schema to allow xAP devices to send email through the builtin
HomeSeer. Text to speech using the HomeSeer voice engine.&nbsp; This
will
explain why HomeSeer is talking the Switchboard messages. Now to why
changing the source make it stop.&nbsp; Every xAP message received by
the
plugin is matched against a list of known devices. If the source
address is matched then the xAP message is process, if however the
source address isn't known then the message is diverted into the new
hardware wizard. What&nbsp; I'm guessing is that one of your source
addresses is know by the plugin and so the message is spoken and the
other one isn't.<br>
Now i'm not sure why the speech is repeating by homeseer this is either
the plugin or homeseer itself doing this. i'll look into it.<br>
What you really what to do is add some targets to these xAP messages.
Targets allow a xAP message to be delivered only a specific
device.<br>
<pre wrap="">xap-header
{
v=12
hop=1
uid=FF812800
class=tts.speak
source=KCSoft.Send.Anya
target=mi4.speech.anya
}
tts.speak
{
Say=this is a zap speech test.
Volume=100
}</pre>
for example would only cause mi4.speech.anya to speak&nbsp; or in the
case
of the tosend file in switchboard:<br>
&lt;start&gt;<br>
Type=tts<br>
Target=mi4.speech.anya<br>
L1=*Direction**LineDescription* Call from
*NameCompanyNumberSpace*<br>
&lt;end&gt;<br>
<br>
Hope this all makes sense<br>
<br>
James<br>
<br>
Ian Davidson wrote:
<blockquote
cite="mid1964797EF65B7C42877FDA720CA68CDB5BF2@xxxxxxx"
type="cite">
<pre wrap="">Hello

I have tried to find out why I have the TTS error. I downloaded the
xapsend app and the xap speech app and installed onto my main pc.

I tried sending other xap tts messages, they worked fine and were only
spoken by the xap tts app and not homeseer. I then started changing the
xap message to see what caused homeseer to speak it. Below are two
messages the first one works normally and the second gets spoken by
homeseer continuously until it is terminated.

1st message
xap-header
{
v=12
hop=1
uid=FF812800
class=tts.speak
source=KCSoft.Send.Anya
}
tts.speak
{
Say=this is a zap speech test.
Volume=100
}

2nd message
xap-header
{
v=12
hop=1
uid=FF812800
class=tts.speak
source=mi4.switchboard.GALEFORCE9-MAIN
}
tts.speak
{
Say=this is a zap speech test.
Volume=100
}

The only thing that has changed is the source but I don't understand how
this could be causing the fault. Can anyone tell me what's happening or
suggest any other tests to try to eliminate this.

Thank you

Ian D


-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:xap_automation@xxxxxxx";>xap_automation@xxxxxxx</a>
[<a class="moz-txt-link-freetext" href="mailto:xap_automation@xxxxxxx";>mailto:xap_automation@xxxxxxx</a>]
On Behalf Of Ian Davidson
Sent: 27 August 2005 20:01
To: Ian
Subject: RE: [xap_automation] Meteor caller id help

Hello Kevin

Ok I managed to grab 1/2 hour to see if I could see what was happening.
I installed the viewer onto the server and everything was correct.
However I did find the exact text which was being spoken and logged. Xap
switchboard was sending out a tts message. I did not realise the
homeseer plugin would automatically speak a Xap tts message, and I do
not know why it is repeated until homeseer is destroyed.

Anyway I looked at the Xap switchboard confg but could not see how to
disable the sending of tts messages. After looking in the install
directory I found

Tosend.txt

And removed the following lines

'&lt;start&gt;
'Type=tts
'Target=&gt;
'L1=*Direction**LineDescription* Call from *NameCompanyNumberSpace*
'&lt;end&gt;

Problem is now cured although I think I would sooner get to the bottom
of this, it is likely to come back and attack again!

Ian D


-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:xap_automation@xxxxxxx";>xap_automation@xxxxxxx</a>
[<a class="moz-txt-link-freetext" href="mailto:xap_automation@xxxxxxx";>mailto:xap_automation@xxxxxxx</a>]
On Behalf Of Kevin Hawkins
Sent: 27 August 2005 13:31
To: Ian
Subject: Re: [xap_automation] Meteor caller id help

Hmm curious - I must admit I use xAP TSS for my incoming call
announcements and not HomeSeer , and that works fine. What would be
useful is to look at the xAP messages in xAP Viewer and see if you are
getting a flood of those, if so which ones and which specific one
triggers the situation. I will also try this myself and see if I can
reproduce it, although I am currently running HS v2 . The interaction
with xAP Switchboard is quite 'stateful' as the call progress messages
go through a sequence and this might make it awkward to identify the
issue, it may also confuse xAP SB if the messages arrive out of order.

The install version of xAPTel is slightly out of date - I will send you
the latest offlist , although the changes are minor and I don't think
will have any bearing on this. I would also recommend disabling "Basic
CID Schema" in the configuration box (save and restart xAPTel). This
occasionally causes duplicated announcement messages as xAPTel is
sending two callerID schemas if this is enabled. However you would have
only got 2 and not continually repeating announcemnets. Which version of

the xAP HS plugin are you running BTW ? I need to also work out just how

that announcement happens - the ' incoming call from ....' bit - is that

generated in a script or is it an inbuilt aspect of HS. xAP SB can
generate very similar TTS messages but as the speech is hapening from
the HS server machine and you dont have xAP TTS it is curious .

Kevin

Ian Davidson wrote:

</pre>
<blockquote type="cite">
<pre wrap="">Hi All,

I have Homeseer 1.7 installed on my main server which up until now
used a pace modem for caller id. I installed XAP plugin a while back
to allow me to interface to a netiom I had purchased and all is fine.

Yesterday I received my Meteor to replace the Pace as it only worked
once in a blue moon. Rather than upset the server install I decided to
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">try it on my main pc. I have a XAP hub
running, XAPtel to talk to the
Meteor and XAP switchboard to log calls. All setup in minutes and
working 100%. However when I receive an incoming call my homeseer
install on the server announces the call constantly with the voice
saying "incoming call from xxxxxxxx". The log also fills up with
the
message and homeseer becomes unresponsive and has to be killed. I do
not have any scripts that contain "incoming call", if I
disconnect the
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">server from the network it no longer sees the
CID info so it has to be
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">coming from the XAP message. I have not set
CID up in homeseer, I
haven't even set up the CID devices within the plugin yet! Can anyone
shed any light on this so I can stop it happening?

Thanks

Ian D



</pre>
</blockquote>
<pre
wrap=""><!---->------------------------------------------------------------------------
</pre>
<blockquote type="cite">
<pre wrap="">YAHOO! GROUPS LINKS

* Visit your group "xap_automation
<a class="moz-txt-link-rfc2396E" href="http://groups.yahoo.com/group/xap_automation";>&lt;http://groups.yahoo.com/group/xap_automation&gt;</a>"
on the web.
* To unsubscribe from this group, send an email to:
<a class="moz-txt-link-abbreviated" href="mailto:xap_automation-unsubscribe@xxxxxxx";>xap_automation-unsubscribe@xxxxxxx</a>

</pre>
</blockquote>
<pre wrap=""><!----><a
class="moz-txt-link-rfc2396E" href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>&lt;mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe&gt;</a>
</pre>
<blockquote type="cite">
<pre wrap="">    * Your use of Yahoo! Groups is subject to
the Yahoo! Terms of
Service <a class="moz-txt-link-rfc2396E" href="http://docs.yahoo.com/info/terms/";>&lt;http://docs.yahoo.com/info/terms/&gt;</a>.



</pre>
</blockquote>
<pre
wrap=""><!---->------------------------------------------------------------------------
</pre>
<pre wrap=""><!---->