Ideas, please

JW

Jono wrote:
> "JW" <jw@privacy.net> wrote in message
> news:12tsesb7hgdisc9@corp.supernews.com...
>
>
>>You should check that the Avaya doesn't have some odd short-code set-up
>>dialling this number. The SMDR application can log calls to help you
>>trace the source. It's possible someone has forwarded their extension to
>>this mobile and incoming calls are going straight out again.
>
>
> SMDR?
>
>
Call logging. There's an application on one of the Avaya
discs (assuming this is IP Office) that installs on a
network PC and connects to the PABX to receive call records,
stored as a CSV file for each day.

JW

Jono wrote:
> "Harry Broomhall" <haeb@pc60.easynet.co.uk> wrote in message
> news:uuast21qf2jq0e26f01fbtcjlmemrqggmi@4ax.com...
>
>> The '8 hour' thing is a SystemX oddity. It so happens that BT
>>reduce all their call records to SystemX style for
>>historical/hyterical reasons. In addition, the 8 hour points are
>>exactly where you state.
>>
>> This means that this is indeed one call. I have seen this
>>frequently on BT bills submited to us (another telco) for checking.
>>
>> Whether this is *correct* is completely another bag of ferrets.
>>However, I have to say that out of about 20 BT bills submitted to us
>>over a number of years, only one was 'wrong' (didn't agree with our
>>own records).
>
>
> I still can't fathom why the call wasn't dropped before the 7 days were up
>
> This is one call, isn't it?
>
> CLI StartTime Duration Destination
> 01204XXXXXX 24/01/2007 11:27:18 35261 07929XXXXXX
> 01204XXXXXX 24/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 25/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 25/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 25/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 26/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 26/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 26/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 27/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 27/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 27/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 28/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 28/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 28/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 29/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 29/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 29/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 30/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 30/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 30/01/2007 21:15:00 28800 07929XXXXXX
> 01204XXXXXX 31/01/2007 05:15:00 28800 07929XXXXXX
> 01204XXXXXX 31/01/2007 13:15:00 28800 07929XXXXXX
> 01204XXXXXX 31/01/2007 21:15:00 9981 07929XXXXXX
> Total Duration 650042 Seconds
> Total Duration 180.5672 Hours
>
>

The BT exchange (for 01204xxxxxx) hasn't received a call
clear message from either party. It could be an issue with
the mobile-to-BT interface. 07929 is an Orange code. That
would cost around £800, by my reckoning.

If you can get the Orange itemised bill for that number, you
can probably prove that made other calls in that period, so
the call must have terminated early.

Jono

JW wrote on 23/02/2007 :
> Jono wrote:
>> "JW" <jw@privacy.net> wrote in message
>> news:12tsesb7hgdisc9@corp.supernews.com...
>>
>>
>>>You should check that the Avaya doesn't have some odd short-code set-up
>>> dialling this number. The SMDR application can log calls to help you
>>> trace the source. It's possible someone has forwarded their extension to
>>> this mobile and incoming calls are going straight out again.
>>
>>
>> SMDR?
>>
>>
> Call logging. There's an application on one of the Avaya discs (assuming
> this is IP Office) that installs on a network PC and connects to the PABX to
> receive call records, stored as a CSV file for each day.

Cheers. I take it their installer would have had to enable call logging
first? Unfortunately, he didn't....

Denis McMahon

Jono wrote:

> So you think it *is* likely that it is a single call spanning 9 days or so?

Almost definately.

Mobile handset batteries don't usually last this long, but the call
might have gone to a voicemail platform or otherwise been diverted by
the mobile number. Voicemail systems usually time out unless the caller
interacts with them, but the call could have gone to someone's home
phone etc.

Normally I'd expect such a long duration call to flag an alarm in one or
more of the exchanges ot was passing through that would trigger operator
intervention to (a) check that the circuit was genuinely in use, and (b)
manually disrupt the call if it appeared to be silent (no data tones,
isdn data activity or speech) on the basis that a device involved in the
call may have locked up.

Denis McMahon

Capt Jack Sparrow

"Denis McMahon" <denis.mcmahon@ntlworld.com> wrote in message
news:cNHDh.36275$Fm2.35538@newsfe1-gui.ntli.net...

>
> Mobile handset batteries don't usually last this long,

Unless the mobile was on a charging station - like mine spends a lot of time
when I'm at home.

JJ

Jono

JW submitted this idea :

>>
>> I still can't fathom why the call wasn't dropped before the 7 days were up
>>
>>
>> CLI StartTime Duration Destination
>> 01204XXXXXX 24/01/2007 11:27:18 650042 07929XXXXXX

>> Total Duration 180.5672 Hours
>>
>>
>
> The BT exchange (for 01204xxxxxx) hasn't received a call clear message from
> either party. It could be an issue with the mobile-to-BT interface. 07929
> is an Orange code. That would cost around £800, by my reckoning.

It is an Orange code & it is still an Orange number.

> If you can get the Orange itemised bill for that number, you can probably
> prove that made other calls in that period, so the call must have terminated
> early.

Oh dear.....can't show the mobile bill. Well, could show the bill,
however, there were NO outbound calls during that period, so no help.

Jono

After serious thinking Capt Jack Sparrow wrote :
> "Denis McMahon" <denis.mcmahon@ntlworld.com> wrote in message
> news:cNHDh.36275$Fm2.35538@newsfe1-gui.ntli.net...
>
>>
>> Mobile handset batteries don't usually last this long,
>
> Unless the mobile was on a charging station - like mine spends a lot of time
> when I'm at home.
>

Yes, I'd considered that - with auto answer turned on.

IPGURU

Jono wrote:
> Hello,
>
> I have a client whose recent phone bill has a number of very long calls
> to a single mobile number.
>
> The first call to this mobile number was on 24th January at 11 am (ish)
> with a duration of over 9 hours. Adding the duration to the start time
> yields a finish time of 21:15:00
>
> Now then, the next call starts at 21:15:00 for exactly 8 hours, followed
> by another at 05:15:00 for another 8 hours, followed by another at
> 13:15:00 for another 8 hours exactly.......
>
> This cycle is repeated 21:15=>05:15=>13:15=>21:15 every day until 31st
> January.
>
> Phone system is an Avaya (sp?) ISDN 2e lines - phone system installed
> the week before the problems started.
>
> Questions - I assume Orange has a timeout on voicemail...? Should it
> disconnect the call assuming a user has accidentally placed the call on
> hold? Does it seem likely that this is a single call that, for some
> reason BT have chopped up into 8 hour blocks?
>
>
If this is an IP Office it is also possible that the installer has added
an internet service that is constantly trying to connect.
I would check the configuration of the system & make sure that you have
no entries in services.

Otherwise follow the suggestion of starting some call logging software.
there is nothing needed to be set in the IP Office system itself but you
will need toinstall DeltaServer onto a pc & configure it to output SMDR
(Station Message Detail Reporting)data to a CSV file to try & identify
whre the callis comming from.

My gut feeling is that this IPO has been poorly installed (I offten find
examples of poor instalation when I take on maintanence of a system that
has been installed by smaller installers).

Jono

IPGURU wrote :
> Jono wrote:
>> Hello,
>>
>> I have a client whose recent phone bill has a number of very long calls to
>> a single mobile number.
>>
>> The first call to this mobile number was on 24th January at 11 am (ish)
>> with a duration of over 9 hours. Adding the duration to the start time
>> yields a finish time of 21:15:00
>>
>> Now then, the next call starts at 21:15:00 for exactly 8 hours, followed by
>> another at 05:15:00 for another 8 hours, followed by another at 13:15:00
>> for another 8 hours exactly.......
>>
>> This cycle is repeated 21:15=>05:15=>13:15=>21:15 every day until 31st
>> January.
>>
>> Phone system is an Avaya (sp?) ISDN 2e lines - phone system installed the
>> week before the problems started.
>>
>> Questions - I assume Orange has a timeout on voicemail...? Should it
>> disconnect the call assuming a user has accidentally placed the call on
>> hold? Does it seem likely that this is a single call that, for some reason
>> BT have chopped up into 8 hour blocks?
>>
>>
> If this is an IP Office it is also possible that the installer has added an
> internet service that is constantly trying to connect.
> I would check the configuration of the system & make sure that you have no
> entries in services.

They have had their installer back in to check their IP Office - the
dial-up internet service was the first thing I thought of, when I
presumed there were several calls.

Still baffled why it didn't time out - it is one call, not several.

> Otherwise follow the suggestion of starting some call logging software.
> there is nothing needed to be set in the IP Office system itself but you will
> need toinstall DeltaServer onto a pc & configure it to output SMDR (Station
> Message Detail Reporting)data to a CSV file to try & identify whre the callis
> comming from.
>
> My gut feeling is that this IPO has been poorly installed (I offten find
> examples of poor instalation when I take on maintanence of a system that has
> been installed by smaller installers).

Thanks for your reply.

The call is no longer on the go. As it was one call (that lasted 7
days) installing the SMDR (which I WILL suggest to them) will only
highlight future occurrences, not explain what happened at the end of
January, unfortunately.