[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Viewer port validation with ephemeral range
- Subject: RE: Viewer port validation with ephemeral range
- From: "Kevin Hawkins" <lists@xxxxxxxxxxxxxxxxx>
- Date: Thu, 3 Jun 2004 16:48:59 +0100
Ooops my bad.. was runnng on another machine with older OCX - copied the
new OCX over but got
"Failed to load control 'Xapax' from xapax.ocx. Your version of
xapax.ocx
may be outdated. Make sure you use the version of the control that was
provided with your application."
Recompiled it and it launches just dandy now . Hadnt realised I needed to
do that too.
xap-hbeat
{
v=12
hop=1
uid=FF232300
class=xap-hbeat.alive
source=UKUSA.Tel.LineOne
interval=60
port=32768 :-)
}
Mark - did you get the the caller ID application running OK - you had a
siimilar issue with the Active CTI OCX although Stuart, Steve and Mike all
have it running OK (with a Meteor). Could you have ever had a prev ActivCTI
ocx perhaps ?? (or Active CID perhaps).
Kevin
> -----Original Message-----
> From: Patrick Lidstone (Personal e-mail)
> [mailto:patrick@xxxxxxx]
> Sent: 03 June 2004 16:25
> To: xAP_developer@xxxxxxx
> Subject: RE: [xAP_developer] Viewer port validation with
> ephemeral range
>
> There was an intermediate release of the OCX which got the
> ephemeral ports wrong - but only Kevin had a copy of this,
> perhaps he has picked the wrong version up by mistake
> here? The current version (1.7) works OK. (If you actually
> do string->number conversion in xFx then it could be that
> you are assuming a short int?)
>
> P.
>
> > -----Original Message-----
> > From: Stuart Booth [mailto:lists@xxxxxxx]
> > Sent: 03 June 2004 16:20
> > To: xAP_developer@xxxxxxx
> > Subject: Re: [xAP_developer] Viewer port validation with
> ephemeral
> > range
> >
> >
> > On Thu, 3 Jun 2004 16:12:56 +0100, "Kevin Hawkins"
> > <lists@xxxxxxx> wrote:
> >
> > >xap-hbeat
> > >{
> > :
> > >port=-32768
> > >}
> > >
> > >The error that was generated is as follows:
> > >Specified argument was out of the range of valid
> values. Parameter
> > >name: port
> >
> > xFx doesn't like a port number of "-32768" in the xAP
> message. I think
> > that's more your end?? I could convert it to an unsigned number
> > internally though, but I think the app should send out
> well-formed
> > numbers. What do you think?
> >
> > S
> > --
> > Stuart Booth <stuart@xxxxxxx> xAPFramework.net - a xAP
> > software development framework for .net
> >
> http://www.xapautomation.org/
http://www.xapframework.net/
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> --------------------~--> Yahoo! Domains - Claim yours for
> only $14.70
> http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/dpFolB/TM
> -----------------------------------------------------------
> ---------~->
>
>
> Yahoo! Groups Links
>
>
>
>
>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|