|
Home > Archive > Voice Over IP in UK > January 2006 > Voipfone dies every morning
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Voipfone dies every morning
|
|
|
| Every morning, between about 07:15 and 07:40, Voipfone stops responding
to registration requests from my Sipura 2100 ATA. I have conducted
continuous traces of registration and network activity, and the failure
is consistently repeating at around these times every day. There is no
problem at any other time.
I know that at least one other person is experiencing the same problem,
but Voipfone insists it is not on their end.
Is anyone else here experiencing the same problem? If you use Voipfone,
try picking up the phone from time to time between about 07:15 and
07:40. Is the line dead?
--
Ian
| |
|
| On Fri, 13 Jan 2006 08:25:36 GMT, news <news@care4free.net> wrote:
>Every morning, between about 07:15 and 07:40, Voipfone stops responding
>to registration requests from my Sipura 2100 ATA. I have conducted
>continuous traces of registration and network activity, and the failure
>is consistently repeating at around these times every day. There is no
>problem at any other time.
>
>I know that at least one other person is experiencing the same problem,
>but Voipfone insists it is not on their end.
>
>Is anyone else here experiencing the same problem? If you use Voipfone,
>try picking up the phone from time to time between about 07:15 and
>07:40. Is the line dead?
I will check it out and report back.
Meanwhile there is new 2100 firmware on the Sipura web site - but
you'll need a TFTP server as they put the wrong loader program in the
upgrade package.
| |
| Tim Bray 2006-01-16, 7:45 am |
| Mark wrote:
> Meanwhile there is new 2100 firmware on the Sipura web site - but
> you'll need a TFTP server as they put the wrong loader program in the
> upgrade package.
Another way is just to put the firmware image file on a webserver. Then
paste the URL into the upgrade_rule box on the provisioning tab.
Tim
| |
|
| In message <3ophs1pm2qm8fm2tephdp6pk6hsbesm1iq@4ax.com>, Mark
<markincambs@yahoo.co.uk> writes
>
>Meanwhile there is new 2100 firmware on the Sipura web site - but
>you'll need a TFTP server as they put the wrong loader program in the
>upgrade package.
Mark, I'm not sure I understand that. (I do understand what TFTP is).
Are you saying that the TFTP client in the ATA cannot talk to the TFTP
server at Sipura for some reason? What exactly is broken? Can you please
explain.
--
Ian
| |
| Paul Hayes 2006-01-16, 5:45 pm |
| news wrote:
> In message <3ophs1pm2qm8fm2tephdp6pk6hsbesm1iq@4ax.com>, Mark
> <markincambs@yahoo.co.uk> writes
>
>
>
> Mark, I'm not sure I understand that. (I do understand what TFTP is).
>
> Are you saying that the TFTP client in the ATA cannot talk to the TFTP
> server at Sipura for some reason? What exactly is broken? Can you please
> explain.
>
The Sipura firmware you download from the site comes with a small app to
load the firmware to the adaptor/phone. I guess he's saying the app
supplied with the current 2100 firmware is broken, which it might be
I've not tried it. You can use a TFTP or a HTTP server to upload the
file too, put the link to the file in the upgrade rule in the
provisioning tab of the Sipura.
Paul.
| |
|
| On Mon, 16 Jan 2006 15:14:36 +0000, Paul Hayes <paul@nomail.org>
wrote:
>news wrote:
>
>The Sipura firmware you download from the site comes with a small app to
>load the firmware to the adaptor/phone. I guess he's saying the app
>supplied with the current 2100 firmware is broken, which it might be
>I've not tried it. You can use a TFTP or a HTTP server to upload the
>file too, put the link to the file in the upgrade rule in the
>provisioning tab of the Sipura.
Correct. It's completely the wrong app in the zipfile.
To their credit, Sipura's online support was absolutely excellent and
responded really quickly to my query. They pointed me to a suitable
free TFTP server (from solarwinds.net) and the .bin file flashed with
no problem.
One aspect of the new firmware is that the unit is now branded Linksys
on its admin web page....
--
Mark
| |
|
| On Fri, 13 Jan 2006 08:25:36 GMT, news <news@care4free.net> wrote:
>Every morning, between about 07:15 and 07:40, Voipfone stops responding
>to registration requests from my Sipura 2100 ATA. I have conducted
>continuous traces of registration and network activity, and the failure
>is consistently repeating at around these times every day. There is no
>problem at any other time.
>
>I know that at least one other person is experiencing the same problem,
>but Voipfone insists it is not on their end.
>
>Is anyone else here experiencing the same problem? If you use Voipfone,
>try picking up the phone from time to time between about 07:15 and
>07:40. Is the line dead?
Monday: No, line not dead, dialtone available and ATA working fine.
Today (Tuesday): Yes, no dialtone. I then enabled full logging to a
syslog server and that kicked the ATA into life once more.
Hmmm.
| |
|
| In message <itcps19p4ck7ld4sv77u8b261jl7ov7luf@4ax.com>, Mark
<markincambs@yahoo.co.uk> writes
>
>Monday: No, line not dead, dialtone available and ATA working fine.
>
>Today (Tuesday): Yes, no dialtone.
I was not around at 0700 onwards yesterday or today to check.
> I then enabled full logging to a
>syslog server and that kicked the ATA into life once more.
I have found that after the ATA has tried unsuccessfully to register for
about 15 minutes, it then goes to sleep for 20 minutes before attempting
to register again (usually successfully). If you had left your ATA alone
for about 20 minutes I suspect it would then have sprung back into life
of its own accord.
>
>Hmmm.
Indeed!
--
Ian
| |
|
| In message <rlcps1dm4ososrjcs2vorpkl3effcan576@4ax.com>, Mark
<markincambs@yahoo.co.uk> writes
>On Mon, 16 Jan 2006 15:14:36 +0000, Paul Hayes <paul@nomail.org>
>wrote:
>
>Correct. It's completely the wrong app in the zipfile.
Now I am really confused. I looked at the Sipura site yesterday for the
latest 2100 firmware zip (spa2100-3.2.5d), and saw that it only
contained a .bin file. No sign of any loader program.
Also, why do they bother to zip the file? The zipped file is only a few
bytes shorter than the unzipped version. Instead, they could just post
the .bin file, which would then be directly downloadable to the ATA. Or
have I missed the point?
>
>To their credit, Sipura's online support was absolutely excellent and
>responded really quickly to my query. They pointed me to a suitable
>free TFTP server (from solarwinds.net) and the .bin file flashed with
>no problem.
So I guess I have to install the TFTP server on my WinXP PC, then tell
the ATA to talk to the server, giving the location on my PC of the
Sipura .bin file which I have already downloaded?
--
Ian
| |
| Paul Hayes 2006-01-17, 7:45 am |
| news wrote:
> In message <rlcps1dm4ososrjcs2vorpkl3effcan576@4ax.com>, Mark
> <markincambs@yahoo.co.uk> writes
>
>
>
> Now I am really confused. I looked at the Sipura site yesterday for the
> latest 2100 firmware zip (spa2100-3.2.5d), and saw that it only
> contained a .bin file. No sign of any loader program.
>
> Also, why do they bother to zip the file? The zipped file is only a few
> bytes shorter than the unzipped version. Instead, they could just post
> the .bin file, which would then be directly downloadable to the ATA. Or
> have I missed the point?
>
>
>
> So I guess I have to install the TFTP server on my WinXP PC, then tell
> the ATA to talk to the server, giving the location on my PC of the
> Sipura .bin file which I have already downloaded?
>
Perhaps they've just completely removed the broken loader program from
the 2100 firmware download then? Normally you'll find a few files in
that zip file. Yes you can install a TFTP server, any should do I seem
to remember you have to fill in a load of forms to download the
Solarwinds one but I could be getting it mixed up with something else.
You can also use a webserver in the same way if that's easier or you
already have one.
| |
|
| On Tue, 17 Jan 2006 10:48:29 GMT, news <news@care4free.net> wrote:
>In message <rlcps1dm4ososrjcs2vorpkl3effcan576@4ax.com>, Mark
><markincambs@yahoo.co.uk> writes
>
>Now I am really confused. I looked at the Sipura site yesterday for the
>latest 2100 firmware zip (spa2100-3.2.5d), and saw that it only
>contained a .bin file. No sign of any loader program.
It *used* to have two files, one was called spc2100-03-02-05-d.exe
but it wasn't the correct Windows app. I guess they have removed the
offending .exe file after I told them of the problem :-)
>Also, why do they bother to zip the file? The zipped file is only a few
>bytes shorter than the unzipped version. Instead, they could just post
>the .bin file, which would then be directly downloadable to the ATA. Or
>have I missed the point?
Safer to obfuscate the file and ensure you do the right thing.
(Would you be happy flashing your ATA with an image file hosted on the
other side of the world? I wouldn't.) TFTP is not routable so only
works on the same subnet, AFAICR.
>
>
>So I guess I have to install the TFTP server on my WinXP PC, then tell
>the ATA to talk to the server, giving the location on my PC of the
>Sipura .bin file which I have already downloaded?
Yup.
1. Disconnect the WAN-side RJ45 cable and any phone leads.
2. Install TFTP server on a PC on the same local subnet as the SPA.
Make sure you give the TFTP server the right permissions, or the file
transfer process will fail.
3. Put the firmware upgrade "spa.bin" file in the tftp root directory
of the active TFTP server. I renamed the long file from the ZIP file
to avoid typing errors.
4. Find the IP address of the powered-up SPA
5. Request the upgrade via a web browser. If the TFTP server is
running on the same computer: assuming a.b.c.d is the SPA IP address,
http://a.b.c.d/upgrade?/spa.bin
If the tftp server is on a different computer (a.b.c.d is the SPA
address, a.b.c.z is the tftp server address), use the following URL:
http://a.b.c.d/upgrade?tftp://a.b.c.z/spa.bin
6. SPA will get the firmware from the TFTP server and reboot.
HTH
Mark
| |
|
| In message <d3jps15bj7rh3424d6uvrjkf7rqk58tq40@4ax.com>, Mark
<markincambs@yahoo.co.uk> writes
>1. Disconnect the WAN-side RJ45 cable and any phone leads.
>2. Install TFTP server on a PC on the same local subnet as the SPA.
>Make sure you give the TFTP server the right permissions, or the file
>transfer process will fail.
> 3. Put the firmware upgrade "spa.bin" file in the tftp root directory
>of the active TFTP server. I renamed the long file from the ZIP file
>to avoid typing errors.
>4. Find the IP address of the powered-up SPA
>5. Request the upgrade via a web browser. If the TFTP server is
>running on the same computer: assuming a.b.c.d is the SPA IP address,
>http://a.b.c.d/upgrade?/spa.bin
>If the tftp server is on a different computer (a.b.c.d is the SPA
>address, a.b.c.z is the tftp server address), use the following URL:
>http://a.b.c.d/upgrade?tftp://a.b.c.z/spa.bin
>6. SPA will get the firmware from the TFTP server and reboot.
>
>HTH
>
It does indeed help. Thanks Mark.
--
Ian
| |
| RJHN *1JOD 2006-01-17, 7:45 am |
| Hi,
Managed to wake up in time to catch things misbehaving!
Please forgive me for thinking out loud at the moment, wanted to report
my findings ASAP.
It looks like the phone is trying to register between 4 and 7 times
with the voipfone server, before getting a reply back, sometimes it
gets a reply back that is reported as no state.
Sometimes the phone manages to stay registered other times things
break completely and the phone becomes unregistered.
This seems to start about 6.30 AM through to 7.30 AM every morning.
Below, later half of log from router when the phone lost registration
this morning.
All started working OK at 7.38 and has been fine since.
1, Snom 360 connected to Intertex IX66 router using Virgin broadband.
I will give it more time later in the day hopefully!! And compare the
phone log also.
Hopefully these notes are of help in trying to resolve this strange
problem.
Regards
John
JAN 17 07:35:39:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:39:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:43:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:47:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:51:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:53:tSip:info:SIP registration expired
(300948**@voipfone.co.uk, 3009****).
JAN 17 07:35:55:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:55:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:55:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:56:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:57:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:35:59:tSip:error:No answer from destination
212.187.162.178:5060
JAN 17 07:35:59:tSip:info:No destination SIP server(s) left to fall
back to.
JAN 17 07:35:59:t1:info:send sf 192.168.0.35: SIP/2.0 408 Request
Timeout
JAN 17 07:36:59:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:36:59:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:36:59:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:00:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:00:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:00:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:37:00:tSip:info:recv 212.187.162.178: SIP/2.0 401
Unauthorized
JAN 17 07:37:00:t1:info:send sf 192.168.0.35: SIP/2.0 401 Unauthorized
JAN 17 07:37:01:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:01:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:01:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:01:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:37:01:tSip:info:recv 212.187.162.178: SIP/2.0 200 OK
JAN 17 07:37:01:t1:info:send sf 192.168.0.35: SIP/2.0 200 OK
JAN 17 07:37:31:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:31:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:32:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:32:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:33:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:34:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:35:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:38:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:39:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:42:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:46:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:47:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:50:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:54:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:57:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:37:57:tSip:info:recv 212.187.162.178: SIP/2.0 401
Unauthorized
JAN 17 07:37:57:t1:info:send sf 192.168.0.35: SIP/2.0 401 Unauthorized
JAN 17 07:37:57:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:57:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:57:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:58:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:58:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:37:58:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:37:58:tSip:info:recv 212.187.162.178: SIP/2.0 200 OK
JAN 17 07:37:58:t1:info:send sf 192.168.0.35: SIP/2.0 200 OK
JAN 17 07:37:59:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:37:59:tSip:notice:SIP 100 response from 212.187.162.178
rejected, no state
JAN 17 07:37:59:tSip:info:recv 212.187.162.178: SIP/2.0 200 OK
JAN 17 07:37:59:tSip:notice:SIP 200 response from 212.187.162.178
rejected, no state
JAN 17 07:38:28:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:28:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:29:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:38:29:tSip:info:recv 212.187.162.178: SIP/2.0 401
Unauthorized
JAN 17 07:38:29:t1:info:send sf 192.168.0.35: SIP/2.0 401 Unauthorized
JAN 17 07:38:29:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:29:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:29:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:38:29:tSip:info:recv 212.187.162.178: SIP/2.0 200 OK
JAN 17 07:38:29:t1:info:send sf 192.168.0.35: SIP/2.0 200 OK
JAN 17 07:38:59:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:59:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:59:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:38:59:tSip:info:recv 212.187.162.178: SIP/2.0 401
Unauthorized
JAN 17 07:38:59:t1:info:send sf 192.168.0.35: SIP/2.0 401 Unauthorized
JAN 17 07:38:59:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:59:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:38:59:tSip:info:recv 212.187.162.178: SIP/2.0 100 Trying
JAN 17 07:38:59:tSip:info:recv 212.187.162.178: SIP/2.0 200 OK
JAN 17 07:38:59:t1:info:send sf 192.168.0.35: SIP/2.0 200 OK
JAN 17 07:39:29:tSip:info:recv 192.168.0.35: REGISTER
sip:voipfone.co.uk SIP/2.0
JAN 17 07:39:29:t5:info:send sf 212.187.162.178: REGISTER
sip:voipfone.co.uk SIP/2.0
| |
| Mark Adamson 2006-01-17, 7:45 am |
|
"RJHN *1JOD" <john_norton@talk21.com> wrote in message
news:1137500063.682824.167840@g14g2000cwa.googlegroups.com...
> Hi,
> Managed to wake up in time to catch things misbehaving!
> Please forgive me for thinking out loud at the moment, wanted to report
> my findings ASAP.
> It looks like the phone is trying to register between 4 and 7 times
> with the voipfone server, before getting a reply back, sometimes it
> gets a reply back that is reported as no state.
> Sometimes the phone manages to stay registered other times things
> break completely and the phone becomes unregistered.
> This seems to start about 6.30 AM through to 7.30 AM every morning.
> Below, later half of log from router when the phone lost registration
> this morning.
>
> All started working OK at 7.38 and has been fine since.
>
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.
| |
| John golf1jod 2006-01-17, 7:45 am |
|
"Mark Adamson" <fliblebibble@adamsonfdfgdf.com> wrote in message
news:dqiofe$nil$1@wisteria.csv.warwick.ac.uk...
>
> 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 2006-01-17, 5:45 pm |
|
"John golf1jod" <john_norton@talk21.com> wrote in message
news:MP5zf.385$_C5.166@newsfe1-win.ntli.net...
>
> "Mark Adamson" <fliblebibble@adamsonfdfgdf.com> wrote in message
> news:dqiofe$nil$1@wisteria.csv.warwick.ac.uk...
[vbcol=seagreen]
> 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
| |
|
| On Tue, 17 Jan 2006 14:48:24 GMT, "John golf1jod"
<john_norton@talk21.com> wrote:
>Could the network, server be under attack from somewhere at this time? its a
>real mystery to me!.
Maybe VoIPfone's CEO (cjd?) who sometimes lurks in this NG can advise.
Or at least get it fixed, as it does look like a non user-specific
problem.
| |
| John golf1jod 2006-01-17, 5:45 pm |
|
"John golf1jod" <john_norton@talk21.com> wrote in message
news:Ys7zf.76507$uR.21453@newsfe7-gui.ntli.net...
> 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:info:DHCP server bound address 192.168.0.41 to
0x000413210501 via interface mac1
JAN 15 08:46:35:tDhcpsTask:info:DHCP server bound address 192.168.0.42 to
0x00041321064b via interface mac1
JAN 15 08:58:28:tDhcpsTask:info:DHCP server bound address 192.168.0.35 to
0x000413230dd3 via interface mac1
JAN 15 08:59:43:tDhcpsTask:info:DHCP server bound address 192.168.0.33 to
0x0001e300a348 via interface mac1
JAN 15 10:44:02:tDhcpsTask:info:DHCP server bound address 192.168.0.41 to
0x000413210501 via interface mac1
JAN 15 10:46:33:tDhcpsTask:info:DHCP 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:info:DHCP server bound address 192.168.0.35 to
0x000413230dd3 via interface mac1
JAN 15 10:59:37:tDhcpsTask:info:DHCP server bound address 192.168.0.34 to
0x001109c3d174 via interface mac1
JAN 15 10:59:46:tDhcpsTask:info:DHCP server bound address 192.168.0.33 to
0x0001e300a348 via interface mac1
JAN 15 11:01:17:tDhcpsTask:info:DHCP server bound address 192.168.0.40 to
| |
|
| In message <Mc8zf.40742$yu.9479@newsfe6-gui.ntli.net>, John golf1jod
<john_norton@talk21.com> writes
>
>"John golf1jod" <john_norton@talk21.com> wrote in message
>news:Ys7zf.76507$uR.21453@newsfe7-gui.ntli.net...
>
>
>
>
>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
| |
| John golf1jod 2006-01-19, 5:46 pm |
| 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 <_5Rzf.1046$Y6.290@newsfe3-win.ntli.net>, John golf1jod
<john_norton@talk21.com> 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
| |
| John golf1jod 2006-01-20, 5:45 pm |
|
"news" <news@care4free.net> wrote in message
news:bX9p3vBqkJ0DFwFK@care4free.net...
> 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
| |
|
| On Fri, 20 Jan 2006 16:15:12 GMT, "John golf1jod"
<john_norton@talk21.com> wrote:
>
>"news" <news@care4free.net> wrote in message
>news:bX9p3vBqkJ0DFwFK@care4free.net...
>
>No problems at all here now , all working perfectly.
>Excellent service from Voipfone.
Yes indeed. Long may it be so.
|
|
|
|
|