RE: Problem with xAP Switchboard reporting OG Call length

["Nigel Giddings" <nigel@xxxxxxxxxxxxxx>]

Kevin,

Thanks for the help...

I have just made another test call and have copied the messages out of
the Hub below. It would seem that xAP TEL does provide the duration
information.

My concern relating to multiple messages stemmed from the idea that
Homeseer may repeat out variables that it had received from xAP TEL, I
understand what you mean by the source information being different for
each device though.

I believe xAP TEL is Version 0.92.xx (Beta) 28th February 2005, there is
no option for version info from the GUI that I can see.

I don't know how to check for revision number on xAP Switchboard.
Looking at the exe it is dated 11/12/2005

The xAP messages below do not show a random I/C call during the process
so this earlier comment might have been a red herring?

xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.CallInitiated
{
datetime=20080621110258
}


xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.DigitPressed
{
dialled=019595
digit=5
}

xap-header
{
v=12
hop=1
uid=FF111300
class=CID.Lookup
source=mi4.switchboard.MERLIN
}
CID.Info
{
type=
lookup=NotFound
number=01959 5
datetime=20080621110258
company=
name=
line=ukusa.tel.522555
std=Knockholt, Kent [Sevenoaks]
rnnumber=
location=
}

xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.DigitPressed
{
dialled=0195952
digit=2
}

xap-header
{
v=12
hop=1
uid=FF111300
class=CID.Lookup
source=mi4.switchboard.MERLIN
}
CID.Info
{
type=
lookup=NotFound
number=0195952
datetime=20080621110258
company=
name=
line=ukusa.tel.522555
std=Knockholt, Kent [Sevenoaks]
rnnumber=
location=
}

xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.DigitPressed
{
dialled=01959522
digit=2
}


xap-header
{
v=12
hop=1
uid=FF111300
class=CID.Lookup
source=mi4.switchboard.MERLIN
}
CID.Info
{
type=
lookup=NotFound
number=01959522
datetime=20080621110258
company=
name=
line=ukusa.tel.522555
std=Knockholt, Kent [Sevenoaks]
rnnumber=
location=
}

xap-header
{
v=12
hop=1
uid=FF40841E
class=xAPBSC.info
source=mi4.homeseer.merlin.37:xAP.Lookuptype
}
output.state
{
state=ON
location=xAP
name=Lookup type
text=NotFound
}

xap-header
{
v=12
hop=1
uid=FF40841E
class=xAPBSC.info
source=mi4.homeseer.merlin.37:xAP.Lookuptype
}
output.state
{
state=ON
location=xAP
name=Lookup type
text=NotFound
}

xap-header
{
v=12
hop=1
uid=FF40841E
class=xAPBSC.info
source=mi4.homeseer.merlin.37:xAP.Lookuptype
}
output.state
{
state=ON
location=xAP
name=Lookup type
text=NotFound
}

xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.DigitPressed
{
dialled=019595225
digit=5
}

xap-header
{
v=12
hop=1
uid=FF111300
class=CID.Lookup
source=mi4.switchboard.MERLIN
}
CID.Info
{
type=
lookup=NotFound
number=019595225
datetime=20080621110258
company=
name=
line=ukusa.tel.522555
std=Knockholt, Kent [Sevenoaks]
rnnumber=
location=
}

xap-header
{
v=12
hop=1
uid=FF40841E
class=xAPBSC.info
source=mi4.homeseer.merlin.37:xAP.Lookuptype
}
output.state
{
state=ON
location=xAP
name=Lookup type
text=NotFound
}


xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.DigitPressed
{
dialled=0195952255
digit=5
}

xap-header
{
v=12
hop=1
uid=FF111300
class=CID.Lookup
source=mi4.switchboard.MERLIN
}
CID.Info
{
type=
lookup=NotFound
number=0195952255
datetime=20080621110258
company=
name=
line=ukusa.tel.522555
std=Knockholt, Kent [Sevenoaks]
rnnumber=
location=
}


xap-header
{
v=12
hop=1
uid=FF40841E
class=xAPBSC.info
source=mi4.homeseer.merlin.37:xAP.Lookuptype
}
output.state
{
state=ON
location=xAP
name=Lookup type
text=NotFound
}

xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.DigitPressed
{
dialled=01959522555
digit=5
}

xap-header
{
v=12
hop=1
uid=FF111300
class=CID.Lookup
source=mi4.switchboard.MERLIN
}
CID.Info
{
type=
lookup=NotFound
number=01959522555
datetime=20080621110258
company=
name=
line=ukusa.tel.522555
std=Knockholt, Kent [Sevenoaks]
rnnumber=
location=
}

xap-header
{
v=12
hop=1
uid=FF233200
class=CID.Meteor
source=UKUSA.Tel.522555
}
Outgoing.CallComplete
{
duration=00:00:30
phone=01959522555
datetime=20080621110329
}






























-----Original Message-----
From: xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx] On
Behalf Of Kevin Hawkins
Sent: 21 June 2008 10:50
To: xap_automation@xxxxxxx
Subject: Re: [xap_automation] Problem with xAP Switchboard reporting OG
Call length

Hi Nigel,

I don't expect your issue is due to multiple applicatons - although I'm
not quite sure what you mean by 'pushing the same xAP info around' --
every xAP message has a unique source= line that identifies which device

sent it and there should be no duplicated messages. Multiple xAPTel
instances can run (as long as the xAP source/linename is different and
xAP Switchboard can handle bucketloads of different lines with no
issues. How many lines do you have - is it just the one ?

IIRC the way Switcboard displays outgoing call duration changed in a
recent version and I'm not sure currently whether it bases this on the
values presented by xAPTel or performs its own calculations. If, as I
suspect, it just displays the info from xAPTEL then it's possible I'm
sending an incorrect value or omitting the duration= in the schema. I'll

wait for James to respond on the mechanism but it's likely we will need
you to capture a 'session' of messages that originate from xAPTel from
the outgoing call initiated to the outgoing callcomplete message. You
can capture these very easily in xAP Viewer.

If you can send me these for a call that exhibits the issue I'll take a
look - inparticular the outgoing.callcomplete one........

Outgoing.CallComplete
{
DateTime=YYYYMMDDHHMMSS
--- Mandatory
*Duration=HH:MM:SS
--- Mandatory (duration of event eg total call time*)
Phone=01234567890
--- Mandatory (may be blank if no number was dialled)
Formatted_Time=11:36:00
--- Optional
Formatted_Date=30 December 2002
--- Optional
}



Can you let us know which version of xAPTel and Switchboard you are
running ? IIRC for xAPTel there was the installer and then a .exe update

- it's many years ago I last visited that app and I'm using the xAP
embedded CallerID device now rather than xAPTEL so I can't easily check.


cheers Kevin





Nigel Giddings wrote:
>
> Hi,
>
> I am running a number of xAP applications on a number of machines
> however I still something of a novice and haven't quite got to the
> bottom of how all this black magic works...
>
> I think one of my issues is that I am pushing the same xAP info round
> the network from different sources...
>
> I am currently running
>
> xAP Hub (ver 1.2.9.12)
>
> xAP Conduit (ver 2.0.0.313) Homeseer Plug-in?
>
> xAP Switchboard
>
> xAP Floorplan
>
> xAP Tel (with a Meteor CID unit)
>
> The issue I see at the moment is that xAP Switchboard works great
> apart from O/G call duration. It appears that it reports an O/G Call
> of 3 seconds (showing partial number) followed by a second entry with
> the correct number and no duration once the call completes.
>
> During an O/G call the current status is correctly displayed at the
> top of the xAP Switchboard 'home page' but without duration (I/C calls

> update duration while a call is in progress).
>
> I am guessing that xAP Switchboard is receiving a message from
> somewhere suggesting the call is complete and so stops timing? It then

> receives another complete call message which results in an entry with
> no duration information...
>
> Thanks for any help in advance
>
> Nigel
>
>


------------------------------------