Voipfone dies every morning

Discussion in 'UK VOIP' started by news, Jan 13, 2006.

  1. news

    news Guest

    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
    news, Jan 13, 2006
    #1
    1. Advertising

  2. news

    Mark Guest

    On Fri, 13 Jan 2006 08:25:36 GMT, news <> 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.
    Mark, Jan 14, 2006
    #2
    1. Advertising

  3. news

    Tim Bray Guest

    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
    Tim Bray, Jan 16, 2006
    #3
  4. news

    news Guest

    In message <>, Mark
    <> 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
    news, Jan 16, 2006
    #4
  5. news

    Paul Hayes Guest

    news wrote:
    > In message <>, Mark
    > <> 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.
    >


    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.
    Paul Hayes, Jan 16, 2006
    #5
  6. news

    Mark Guest

    On Mon, 16 Jan 2006 15:14:36 +0000, Paul Hayes <>
    wrote:

    >news wrote:
    >> In message <>, Mark
    >> <> 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.
    >>

    >
    >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
    Mark, Jan 17, 2006
    #6
  7. news

    Mark Guest

    On Fri, 13 Jan 2006 08:25:36 GMT, news <> 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.
    Mark, Jan 17, 2006
    #7
  8. news

    news Guest

    In message <>, Mark
    <> 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
    news, Jan 17, 2006
    #8
  9. news

    news Guest

    In message <>, Mark
    <> writes
    >On Mon, 16 Jan 2006 15:14:36 +0000, Paul Hayes <>
    >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.


    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
    news, Jan 17, 2006
    #9
  10. news

    Paul Hayes Guest

    news wrote:
    > In message <>, Mark
    > <> writes
    >
    >> On Mon, 16 Jan 2006 15:14:36 +0000, Paul Hayes <>
    >> 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.

    >
    >
    > 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?
    >


    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.
    Paul Hayes, Jan 17, 2006
    #10
  11. news

    Mark Guest

    On Tue, 17 Jan 2006 10:48:29 GMT, news <> wrote:

    >In message <>, Mark
    ><> writes
    >>On Mon, 16 Jan 2006 15:14:36 +0000, Paul Hayes <>
    >>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.

    >
    >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.

    >
    >>
    >>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?


    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
    Mark, Jan 17, 2006
    #11
  12. news

    news Guest

    In message <>, Mark
    <> 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
    news, Jan 17, 2006
    #12
  13. news

    RJHN *1JOD Guest

    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
    RJHN *1JOD, Jan 17, 2006
    #13
  14. news

    Mark Adamson Guest

    "RJHN *1JOD" <> wrote in message
    news:...
    > 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.
    Mark Adamson, Jan 17, 2006
    #14
  15. "Mark Adamson" <> wrote in message
    news:dqiofe$nil$...
    >>

    >
    > 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, Jan 17, 2006
    #15
  16. "John golf1jod" <> wrote in message
    news:MP5zf.385$...
    >
    > "Mark Adamson" <> wrote in message
    > news:dqiofe$nil$...
    >>>

    >>
    >> 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, Jan 17, 2006
    #16
  17. news

    Mark Guest

    On Tue, 17 Jan 2006 14:48:24 GMT, "John golf1jod"
    <> 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.
    Mark, Jan 17, 2006
    #17
  18. "John golf1jod" <> wrote in message
    news:Ys7zf.76507$...


    > 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
    John golf1jod, Jan 17, 2006
    #18
  19. news

    news Guest

    In message <Mc8zf.40742$>, John golf1jod
    <> writes
    >
    >"John golf1jod" <> wrote in message
    >news:Ys7zf.76507$...
    >
    >
    >> 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, Jan 17, 2006
    #19
  20. "news" <> wrote in message
    news:...
    >
    > 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
    John golf1jod, Jan 17, 2006
    #20
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. alex

    Echo Reply dies at pix

    alex, Jul 28, 2004, in forum: Cisco
    Replies:
    3
    Views:
    2,354
  2. Jim

    Quickcam just dies???

    Jim, Oct 4, 2003, in forum: Computer Support
    Replies:
    4
    Views:
    400
  3. Sano

    W98 dies this week, tips <chuckle>

    Sano, Jan 12, 2004, in forum: Computer Support
    Replies:
    6
    Views:
    452
  4. Neil Greenough

    Start up dies

    Neil Greenough, Oct 11, 2004, in forum: Computer Support
    Replies:
    1
    Views:
    460
    STANLEY ERVIN
    Oct 13, 2004
  5. Paul McGuinness

    Voipfone registers every 60 secs?

    Paul McGuinness, Jan 7, 2009, in forum: UK VOIP
    Replies:
    10
    Views:
    1,094
    Harry Broomhall
    Jan 9, 2009
Loading...

Share This Page