"Mark Adamson" wrote in message
...


Maybe they do their backups every day at 6.30AM and don't realise how much
system resources it uses up or something. Just an idea.

Its got to be something that should be possible to trace as it happens
without fail every morning.
Its strange no one else has reported anything, Ian is using NTL and I am
using Virgin so my other thoughts are that it is something to do with NTL.
Maybe network congestion. At first I thought it was a DNS problem, I do get
occasional DNS failure shown in the logs, however in December I just used
the IP of voipfone and it made no difference to the problem.
In all its a very reliable service apart from this time in the morning.

John

Please folks forgive my previous posts being badly formatted, I was trying
to use Google groups!!
I now have uk.telecom.voip set up on my main computer.

John

"John golf1jod" wrote in message
...

"Mark Adamson" wrote in message
...


Maybe they do their backups every day at 6.30AM and don't realise how
much system resources it uses up or something. Just an idea.



Its got to be something that should be possible to trace as it happens
without fail every morning.


Further to my earlier post, I have been comparing all the logs.
The phone sends registration requests to voipfone 10 times, the router then
sends timeout to the phone.
It then sends 3 registration requests to voipfone and receives sip 200 Ok.
It then sends 7 registration requests before receiving response back from
voipfone.
That is just a small sample from the log between 7.35.22 AM and 7.36.00, it
seems the connection is very flaky somewhere.
This morning everything was fine again at 7.38.
I guess it could be the packets getting lost or out of sync (if that makes
sense) I am more at home with RF (analogue) than networking!! possibly due
to congestion somewhere in the internet chain around this time, the
turnaround response to the voipfone server being to slow and the packets
getting rejected by the phone, router or voipfone server. The router does
seem to reject *many* incoming packets from voipfone between these times (
100,200,401 responses all rejected by the router received from the voipfone
server)
All other applications email checking, ntp, as is sipgate working fine
between these times.

I just cant think of any other reason at the moment.

I will try and catch the problem in the morning and try pinging voipfone
between these times.

The other thing (if I remember correctly) the time period has gradually
shifted later by about 10 mins over the past six or so weeks, maybe as Mark
suggests it could be an automated back up somewhere.

Could the network, server be under attack from somewhere at this time? its a
real mystery to me!.


John

"John golf1jod" wrote in message
...


The router does seem to reject *many* incoming packets from voipfone
between these times

100,200,401 responses all rejected by the router received from the
voipfone server)

Sorry just checked and its the other way round!

Just checked the routers "basic" log from the 15th it is voipfone that is
rejecting the packets as no state, see extract from last part of log below.
No further forward I am afraid!

John

JAN 15 07:33:31:tSip:notice:SIP 200 response from 212.187.162.178 rejected,
no state
JAN 15 07:33:33:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 07:33:33:tSip:notice:SIP 200 response from 212.187.162.178 rejected,
no state
JAN 15 07:34:22:tSip:error:No answer from destination 212.187.162.178:5060
JAN 15 07:34:35:tSip:error:No answer from destination 212.187.162.178:5060
JAN 15 07:34:43:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 07:34:43:tSip:notice:SIP 401 response from 212.187.162.178 rejected,
no state
JAN 15 07:35:15:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 07:35:15:tSip:notice:SIP 200 response from 212.187.162.178 rejected,
no state
JAN 15 07:35:36:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 07:35:36:tSip:notice:SIP 200 response from 212.187.162.178 rejected,
no state
JAN 15 07:36:12:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 07:36:12:tSip:notice:SIP 200 response from 212.187.162.178 rejected,
no state
JAN 15 07:36:12:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 07:36:12:tSip:notice:SIP 200 response from 212.187.162.178 rejected,
no state
JAN 15 08:44:04:tDhcpsTask:infoHCP server bound address 192.168.0.41 to
0x000413210501 via interface mac1
JAN 15 08:46:35:tDhcpsTask:infoHCP server bound address 192.168.0.42 to
0x00041321064b via interface mac1
JAN 15 08:58:28:tDhcpsTask:infoHCP server bound address 192.168.0.35 to
0x000413230dd3 via interface mac1
JAN 15 08:59:43:tDhcpsTask:infoHCP server bound address 192.168.0.33 to
0x0001e300a348 via interface mac1
JAN 15 10:44:02:tDhcpsTask:infoHCP server bound address 192.168.0.41 to
0x000413210501 via interface mac1
JAN 15 10:46:33:tDhcpsTask:infoHCP server bound address 192.168.0.42 to
0x00041321064b via interface mac1
JAN 15 10:50:30:tSip:notice:SIP 100 response from 212.187.162.178 rejected,
no state
JAN 15 10:58:32:tDhcpsTask:infoHCP server bound address 192.168.0.35 to
0x000413230dd3 via interface mac1
JAN 15 10:59:37:tDhcpsTask:infoHCP server bound address 192.168.0.34 to
0x001109c3d174 via interface mac1
JAN 15 10:59:46:tDhcpsTask:infoHCP server bound address 192.168.0.33 to
0x0001e300a348 via interface mac1
JAN 15 11:01:17:tDhcpsTask:infoHCP server bound address 192.168.0.40 to

In message , John golf1jod
writes

"John golf1jod" wrote in message
...


The router does seem to reject *many* incoming packets from voipfone
between these times

100,200,401 responses all rejected by the router received from the
voipfone server)

Sorry just checked and its the other way round!

Just checked the routers "basic" log from the 15th it is voipfone that is
rejecting the packets as no state, see extract from last part of log below.
No further forward I am afraid!

[Snip]

John, your experiences are essentially the same as mine. I have been in
regular contact with Voipfone over the last few weeks about this.

I have run regular tcpdump traces of ATA registration traffic and seen
the dropouts you mention -- registration begins to falter sometime after
06:30, and fails completely sometime after 07:20 or so. The ATA then
goes to sleep for 20 minutes, and when it wakes up, registration works
properly again. There are no other dropouts at any other time of day.

The traces included one-minute pings of the Voipfone registration host
and an NTP server -- the pings responded normally, without any breaks or
unusual delays, so I am convinced this is not a network problem.

Just a few minutes ago I received an email from Voipfone, saying they
think they have finally identified the cause of the problem. Let's see
tomorrow morning if they are right!

--
Ian

"news" wrote in message
...

Just a few minutes ago I received an email from Voipfone, saying they
think they have finally identified the cause of the problem. Let's see
tomorrow morning if they are right!

--
Ian

Hi Ian,

It would be most interesting to see if the problem is sorted soon, and what
the problem was. I have a feeling it was since they made alterations to the
equipment last year that I noticed the problem ( I cant be absolutely sure
though) Its just that the router I am now using reports any SIP errors and
logs them, I have been getting the log filled every morning!!
Looking forward to tomorrow, Wont be able to check until later in the day.

John

Looks promising,

Just a few errors now, would be interesting to know what caused the problem.

I would also like to say to the group, that I have always been very pleased
with Voipfone's service and have found it very reliable, and can highly
recomend them, keep up the good work.
I never use BT anymore,actually since having broadband fitted the BT line is
very faint in both directions!! I put this down to being 5 KM from the
exchange!

John

Latest log below,
JAN 19 02:00:43:tSip:error:No answer from destination 212.187.162.1*8:5060
JAN 19 02:00:44:tSip:error:No answer from destination 212.187.162.1*8:5060
JAN 19 02:00:58:tSip:error:No answer from destination 212.187.162.1*8:5060
JAN 19 03:27:10:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:27:10:tSip:notice:SIP 200 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:27:35:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:27:35:tSip:notice:SIP 401 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:28:01:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:28:01:tSip:notice:SIP 401 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:28:02:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 03:28:02:tSip:notice:SIP 200 response from 212.187.162.1*8 rejected,
no state

JAN 19 06:34:08:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 06:34:08:tSip:notice:SIP 401 response from 212.187.162.1*8 rejected,
no state
JAN 19 06:34:09:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 06:34:09:tSip:notice:SIP 401 response from 212.187.162.1*8 rejected,
no state
JAN 19 12:10:23:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state
JAN 19 14:58:35:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state

JAN 19 17:36:13:tSip:notice:SIP 100 response from 212.187.162.1*8 rejected,
no state

It looks like Voipfone has cracked it. There was no break in service
this morning.

~~~~~~~~~~~~~~~~~~~~~
In message , John golf1jod
writes

I would also like to say to the group, that I have always been very pleased
with Voipfone's service and have found it very reliable, and can highly
recomend them, keep up the good work.

Agreed entirely! Their service is very good, and in particular their
help desk is extremely responsive and helpful. During the recent
difficulty with short breaks in service, they were in regular contact
with me by email and phone (calling me several times to explain in
detail what they were doing -- not many help desks do that), and it
turns out the problem was outside their direct control.

Other companies could learn a lot from them. Definitely recommended.

--
Ian

"news" wrote in message
...
It looks like Voipfone has cracked it. There was no break in service this
morning.

Other companies could learn a lot from them. Definitely recommended.

--
Ian

No problems at all here now , all working perfectly.
Excellent service from Voipfone.

John