[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Application for obtaining caller ID from hacked box...?
Hi Andy,
Send me (offlist) a few complete example packets of the CID data -
including the lead in characters (which can be random as the modem
synchs to the data stream) and I'll see about adding some support in
xAPTel for these 'raw' devices. This won't happen quickly but I do need
to revisit general modem support in xAPTel and I'll look at adding it
then.
I did my own CD50 hack a while back but since moving I haven't yet
re-discovered that unit, I have another one here (and some similar to
the unit you used) which I could hack which would allow some testing
but in practice I expect I'm just not going to get around to it . As
xAPTel uses the Active CTI OCX for the Meteor I'm guessing that you see
nothing when using xAPTel with your device ?
I'll refresh myself on the appropriate SIN document from BT too. I
am very keen to see if the raw incoming data actually sets the 'messages
waiting' parameter as that would be most useful to me. Do you use 1571
? If so an example packet when there is a new message waiting would be
most appreciated.
Kevin
Andrew Kilgore wrote:
> Hi Patrick,
>
> Thanks for the reply.
>
> I'll dig out a Win2K box tonight and retest - if that doesn't work
> then I think your suggestion of a recompile is the next logical step.
>
> Also, I've just retested on my work machine (another XP Pro box) and
> it has xap-meteor consuming 50% CPU which is what you'd expect on a
> Hyperthreaded machine. Out of interest, how much CPU utilisation does
> xap-meteor use on your Win2K machine...?
>
> I've just had a look at your source and at the cygwin documentation
> which states:
>
>
> Select
>
> The UNIX select function is another call that does not map cleanly
> on top of the Win32 API. Much to our dismay, we discovered that
> the Win32 select in Winsock only worked on socket handles. Our
> implementation allows select to function normally when given
> different types of file descriptors (sockets, pipes, handles, and
> a custom /dev/windows Windows messages pseudo-device).
>
> Upon entry into the select function, the first operation is to
> sort the file descriptors into the different types. There are then
> two cases to consider. The simple case is when at least one file
> descriptor is a type that is always known to be ready (such as a
> disk file). In that case, select returns immediately as soon as it
> has polled each of the other types to see if they are ready. The
> more complex case involves waiting for socket or pipe file
> descriptors to be ready. This is accomplished by the main thread
> suspending itself, after starting one thread for each type of file
> descriptor present. Each thread polls the file descriptors of its
> respective type with the appropriate Win32 API call. As soon as a
> thread identifies a ready descriptor, that thread signals the main
> thread to wake up. This case is now the same as the first one
> since we know at least one descriptor is ready. So select returns,
> after polling all of the file descriptors one last time.
>
> Not sure if this explains anything or not.
>
> Many thanks,
> Andy.
>
> On 12/8/05, *Patrick Lidstone (Personal E-mail)* <patrick@xxxxxxx
> <mailto:patrick@xxxxxxx>> wrote:
>
> I checked it out here, and it works fine under Win2k. I don't have
> an XP box to hand, I will see if I can lay my hands on one. In the
> meantime I'd suggest a recompile of the source against the current
> version of cygwin as a starting point?
>
> Patrick
>
>
------------------------------------------------------------------------
> *From:* Andrew Kilgore [mailto:andrew.kilgore@xxxxxxx
> <mailto:andrew.kilgore@xxxxxxx>]
> *Sent:* 08 December 2005 00:38
> *To:* xap_automation@xxxxxxx
> <mailto:xap_automation@xxxxxxx>
> *Subject:* Re: [xap_automation] Application for obtaining
> caller ID from hacked box...?
>
> Hi Patrick,
>
> I've just retested xap-meteor on XP Pro (SP2) with the same
> results :o(
> Any light you can shed on this would be greatly appreciated.
> Just let me know if you require any more details.
>
> Many thanks,
> Andy.
>
> On 12/7/05, *Andrew Kilgore* <andrew.kilgore@xxxxxxx
> <mailto:andrew.kilgore@xxxxxxx>>
wrote:
>
> Hi Patrick,
>
> I was testing on XP (Home) SP2 - I can probably try XP Pro
> or Win2K tonight.
> I agree that this is odd behaviour especially as no one
> else seems to have reported it.
> Possibly another one of those "Just me" things
;o)
>
> Many thanks,
> Andy.
>
>
> On 12/7/05, *Patrick Lidstone (Personal E-mail)* <
> patrick@xxxxxxx <mailto:patrick@xxxxxxx>> wrote:
>
>
> > However, this presented another problem.
> > As the Meteor connector is cross platform I doubt
> whether it makes use of any of the Windows specific
> COM functions (i.e. WaitForCommMask()). This
> > means that it polls the COM port and results in
the
> CPU maxing out :o(
>
> If you are seeing it consuming max-cpu, then it's
> likely that the meteor code is missing a select on the
> poll - I will take a look. I've used the Cygwin
> com-port support under windows extensively in general,
> and it works just fine. It certainly shouldn't max out
> the cpu. Out of interest, which version of windows are
> you using?
>
> Patrick
>
>
------------------------------------------------------------------------
> 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/>.
>
>
>
------------------------------------------------------------------------
>
>
>
>
>
> SPONSORED LINKS
> Workflow automation
> <http://groups.yahoo.com/gads?t=ms&k=Workflow+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=F4tRNBO_G_ZzajQmbmwe7Q>
> Automation equipment
> <http://groups.yahoo.com/gads?t=ms&k=Automation+equipment&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=9-eliEiH2rHCvwCe6xpvLw>
> Industrial automation
> <http://groups.yahoo.com/gads?t=ms&k=Industrial+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=xI5A0mNmlPHiPI__bxZwUQ>
>
> Test automation
> <http://groups.yahoo.com/gads?t=ms&k=Test+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=babdTZ-cZ8AbgxQRUJqztw>
> Sales automation
> <http://groups.yahoo.com/gads?t=ms&k=Sales+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=-x7c78RB2nUpuPBRifr1YA>
> Factory automation
> <http://groups.yahoo.com/gads?t=ms&k=Factory+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=zQtSND_pDmyn0UaMn4LPgQ>
>
>
>
>
------------------------------------------------------------------------
> 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/>.
>
>
>
------------------------------------------------------------------------
>
>
>
>
> SPONSORED LINKS
> Workflow automation
> <http://groups.yahoo.com/gads?t=ms&k=Workflow+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=F4tRNBO_G_ZzajQmbmwe7Q>
> Automation equipment
> <http://groups.yahoo.com/gads?t=ms&k=Automation+equipment&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=9-eliEiH2rHCvwCe6xpvLw>
> Industrial automation
> <http://groups.yahoo.com/gads?t=ms&k=Industrial+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=xI5A0mNmlPHiPI__bxZwUQ>
>
> Test automation
> <http://groups.yahoo.com/gads?t=ms&k=Test+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=babdTZ-cZ8AbgxQRUJqztw>
> Sales automation
> <http://groups.yahoo.com/gads?t=ms&k=Sales+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=-x7c78RB2nUpuPBRifr1YA>
> Factory automation
> <http://groups.yahoo.com/gads?t=ms&k=Factory+automation&w1=Workflow+automation&w2=Automation+equipment&w3=Industrial+automation&w4=Test+automation&w5=Sales+automation&w6=Factory+automation&c=6&s=145&.sig=zQtSND_pDmyn0UaMn4LPgQ>
>
>
>
>
------------------------------------------------------------------------
> 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/>.
>
>
>
------------------------------------------------------------------------
>
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|