ATA issues on voipfone

Discussion in 'UK VOIP' started by Blu, May 12, 2011.

  1. Blu

    Blu Guest

    On 16/05/2011 22:14, Tmorley wrote:
    > On May 16, 11:36 am, Blu<> wrote:
    >> Does all this stuff make any sense to anyone here ?
    >>
    >> We send multiple INVITE requests to the device, asking it to accept the
    >> inbound call.
    >>
    >> We get nothing back at all, So give up and pass the call to voicemail.
    >>
    >> Trace of this below:
    >>
    >> >

    > FYI I spoke to one of the customer service girls at Voipfone today as
    > I was having some Nat and audio issues, and they informed me that the
    > sip.voipfone.co.uk is going to be retired in the near future, and that
    > I should register my phones to sip.voipfone.net I'm not quite sure
    > what the difference is between the new proxy and the old one is, but
    > it solved all my nat and audio issues, I also no longer needed to use
    > their nat proxy.
    >
    > May be this will help with your issues too worth a try, I guess
    >
    > T


    Thanks for your contribution. The only time the ATA actually worked was
    when it was set to sip.voipfone.co.uk but it used to change its status
    from 'Registered' to 'Error Forbidden' after about 3 days uptime.

    On Voipfone's advice I changed it to sip.voipfone.net and low and behold
    it stopped ringing at all and changing back to sip.voipfone.co.uk didn't
    help.

    I think its time to get a refund or replacement ATA, and for now its
    back to softphones and Skype !!

    Blu
    Blu, May 17, 2011
    #21
    1. Advertising

  2. Blu

    Roger Guest

    "Blu" wrote in message news:8VCAp.4405$2...

    On 17/05/2011 22:15, Blu wrote:
    > On 16/05/2011 20:33, Roger wrote:
    >> Blu
    >> firstly, always obscure or remove your ip address and account info from
    >> informatoin you post in messages.
    >>
    >> It looks like your router is blocking the requests from voipfone.
    >> Forward port 5060 as suggested and see if that resolves it (you'll also
    >> then need to set up a fixed range of RTP ports on the ATA and forward
    >> those as well).
    >>
    >> Roger.

    >
    > Roger,
    >
    > I normally would obscure personal details, but I really didn't
    > understand that much about what I was sending. Fortunately I don't have
    > a fixed ip address, so I can change that at least.
    >
    > Port Forwarding allows me to choose TCP, UDP or both. For now I'm
    > forwarding both, is this correct ?
    >
    > Under SIP Parameters there is a section called RTP Parameters, with a
    > setting for RTP Port Min and for RTP Port Max. Any suggestions for the
    > range to use. I don't want to clash with something else I use.
    >
    > Then I guess I set the same range in the router, again should this be
    > TCP, UDP or both.
    >
    > Thanks for your help sp far.
    >
    > Blu.
    >


    Well, its set to TCP and UDP and for the RTP packets I've forwarded the
    range from the TCP/UDP port table which is 16,000 or so to 34,000 or so.

    Turned off both the router and the ATA, turned the router back on 30
    mins later and then the ATA. Saved changes of course.

    Still does not work, calls go straight to voicemail. I think I'll try
    and get a refund off broadbandbuyer although they may insist on sending
    me a replacement ATA, I doubt you can actually repair these things.

    Seems to me VOIP and ATAs etc are only really for telephone engineering
    types, I see now wny people use Skype. Lets just hope M$ dont bugger
    that up for people.

    Thanks for all your help Roger and Graham.

    A very frustrated Blu.

    (time for a large brandy then bed !!)


    Just before you send it back - why not set up a free sipgate account and see
    if that works - then you'll now if its the ATA or something to do with
    voipfone.
    Roger, May 18, 2011
    #22
    1. Advertising

  3. Blu

    Graham. Guest


    >>

    >
    > Well, its set to TCP and UDP and for the RTP packets I've forwarded the
    > range from the TCP/UDP port table which is 16,000 or so to 34,000 or so.
    >
    > Turned off both the router and the ATA, turned the router back on 30
    > mins later and then the ATA. Saved changes of course.
    >
    > Still does not work, calls go straight to voicemail. I think I'll try
    > and get a refund off broadbandbuyer although they may insist on sending
    > me a replacement ATA, I doubt you can actually repair these things.
    >
    > Seems to me VOIP and ATAs etc are only really for telephone engineering
    > types, I see now wny people use Skype. Lets just hope M$ dont bugger
    > that up for people.
    >
    > Thanks for all your help Roger and Graham.
    >
    > A very frustrated Blu.
    >
    > (time for a large brandy then bed !!)
    >
    >
    > Just before you send it back - why not set up a free sipgate account and see if that works - then you'll now if its the ATA or
    > something to do with voipfone.


    Yes, I was going to suggest that too. Also, you could download the x-lite softphone
    and see if that has the same issues as the hardware.

    --
    Graham.

    %Profound_observation%
    Graham., May 19, 2011
    #23
  4. Blu

    Blu Guest

    On 19/05/2011 23:31, Graham. wrote:
    >>>

    >>
    >> Well, its set to TCP and UDP and for the RTP packets I've forwarded the
    >> range from the TCP/UDP port table which is 16,000 or so to 34,000 or so.
    >>
    >> Turned off both the router and the ATA, turned the router back on 30
    >> mins later and then the ATA. Saved changes of course.
    >>
    >> Still does not work, calls go straight to voicemail. I think I'll try
    >> and get a refund off broadbandbuyer although they may insist on sending
    >> me a replacement ATA, I doubt you can actually repair these things.
    >>
    >> Seems to me VOIP and ATAs etc are only really for telephone engineering
    >> types, I see now wny people use Skype. Lets just hope M$ dont bugger
    >> that up for people.
    >>
    >> Thanks for all your help Roger and Graham.
    >>
    >> A very frustrated Blu.
    >>
    >> (time for a large brandy then bed !!)
    >>
    >>
    >> Just before you send it back - why not set up a free sipgate account and see if that works - then you'll now if its the ATA or
    >> something to do with voipfone.

    >
    > Yes, I was going to suggest that too. Also, you could download the x-lite softphone
    > and see if that has the same issues as the hardware.
    >


    I have XLite on the Mac and Zoiper on the Windows 7 PC. Both work
    perfectly apart from the issue that the computer has to be on !!

    Haven't used either since making the changes to the router settings to
    forward port 5060 and the rtp packets though, guess I'd have to disable
    those changes.

    Does this suggest that the problem is with the ATA ?

    Trying Sipgate is a job for the weekend most likely.

    Thanks.
    Blu, May 20, 2011
    #24
  5. Blu

    News Reader Guest

    "Blu" <> wrote in message news:R6Wyp.56$2...
    >
    > I have a Patton micro ATA.
    >
    > The configuration looks correct to the untrained eye, it says it is up and
    > running, shows my correct a/c number as the user name, its set to
    > sip.voipfone.net as suggested by their support with the right port number,
    > and it correctly tells me the number of messages waiting.
    >
    > It makes outgoing calls fine.
    >
    > However the phone connected to it doesn't ring when a call comes in, I've
    > tried a number of different phones, both cordless and corded but it makes
    > no difference.
    >
    > Any suggestions of things to try please
    >
    > Blu.
    >
    > Router is Linksys WRT54G



    Hi,


    A few thoughts. Some commonalities which may be useful too.

    1) Factory Reset - A complete factory reset (should be a button on the
    device) would be recommended or at least a good idea. The device may have
    conflicting settings or acquired a hangover cross-setting or corruption.

    2) Router / SIP Systemics - Their are commonalities across
    implementations (or some might [perhaps] [overly] generously say
    mis-implementations) in or of routers and SIP devices / software (and as
    well, say more sensibly, "alternate" or "simple" products / services
    [devices, software, etc.]). Typically these manifest very loosely,
    briefly and total novice (style) as:

    - Routers: hang-ups or ("loose"[!]) implementations - impacting or
    affecting, port forwarding, SIP assistance / handling protocols or packages
    (e.g. ALGs - Application Layer Gateways), DMZ functionality, trigger -
    detect - latch - release on or with NAT (as an example), etc.

    - SIP devices / software: partial or varying interpretation
    implementations (and as / similar to router entries [above]) - impacting or
    affecting, configuration (differing terms or use of terms or missing terms,
    lack of options [or an option], etc.), one way audio / no incoming call
    detect (firewall handling / traversal issues, NAT / router, etc.),
    flexibility (much as or resultant to previous - e.g. some functions or
    features not working / partly implemented or unavailable or only available
    to specific configurations, devices [or much more infrequently and usually
    only special case scenarios - only {available} to devices or configurations
    with special or specific "additional" equipment, options, etc. {e.g. " super
    call waiting PLUS " by " XYZ Manufacturing " and only available on their
    devices, systems and configurations, etc., etc.]).

    - Generic - Much as the previous (ones) - corruption / data [/]
    stack issues, config issues or limitations (or exceptionally additions /
    extras), implementation issues or limitations, fade (losing config or
    environment / parameter variables over the medium term) ([can be]
    independent of the device or its function / role / duty, etc.).

    3) Service Provider(s) - Your ISP (internet service provider), your VSP
    (voice service provider ? ), etc. One or more of these may have issues,
    configuration problems or limitations (additions), etc., service
    restrictions / incompatibilites, etc., etc.


    Hence:

    - consider a factory reset of your device(s), and a careful slow
    ("manual" - if you are up to it) configuration ("re-configuration") (perhaps
    write down any settings you need before commencing - as long as you are sure
    they are not corruption / cross- settings, etc. - e.g. "known corrects" such
    as perhaps your ISP username, etc. [ - again, if you need it, and bearing in
    mind that you should have the originals or the originals for these
    somewhere, and should be known or know them to cross-reference against to be
    sure what you are storing is the original or correct version and not corrupt
    or other, etc.])

    - evaluate your service provider(s) - I would particularly focus on your
    ISP here (potentially) - e.g. some block VoIP or other ports, some implement
    ("multi-layer") NAT(s) (which can render a network partially or totally
    unnavigable).

    - SIP devices / software - some of these have varying configuration
    approaches and complexity. Hence, approaching the task from a perhaps
    "easier" direction, a proportion will assume certain settings where others
    will either not permit them or not have / work at all where yet others will
    require a very complete or full technical (or complex) configuration.

    - router ( / "perhaps as distinct from routing") - common approaches
    for users facing issues, include, DMZ (try this - temporarily / testing only
    [with appropriate, matching, destinations / equipment - i.e. a device or
    computer that can face, cope with or is configured for "direct" internet
    access - i.e. one ready for a testing or full access challenging
    environment]), port forwarding (often not too many ports or ranges or - ...
    gulp, router, strange / mis-behaviour), (SIP) ALGs (or equivalent) try on
    and off, enhanced or extra features off (UPnP, etc.) (or on?), always good /
    standard advice, or good idea or sensible to use wired connections for
    development or testing (new equipment, new gear, etc.), ("forced") (basic)
    configuration for WAN side (xDSL settings, etc. - but that is getting a bit
    carried away / advanced). (lol - ... [advanced / joke ?] don't forget
    matching settings in your SIP client).

    (Don't forget, the foregoing may require trying / "switching" independently,
    sometimes including or requiring a factory reset between [but that is
    getting a bit keen / carried away - sorry, "detailed pages" "here", e.g.
    sometimes you can second guess combinations that are likely to require such
    drasticness]), or to be used in combination).

    So, to avoid getting carried away, perhaps for yourself or your own
    situation / environment, try: factory reset, (basic) check of your service
    provider(s) ( ~ ISP) (mobile broadband environments are particularly prone
    to not pass [some or all] VoIP traffic, ULTRA bargain or special ISP
    packages / services, etc.) and simple check of your ATA (VoIP configuration)
    (key aspects, again perhaps if you are keen [enough], try combinations /
    variations - SIP port ranges, SIP server / hostnames, network / firewall -
    traversal or identification, configuration features or tools), simple check
    of your (home) router (key aspects, again consider combos / variations, DMZ,
    SIP help / special settings [if any], special or compatibility settings,
    port forwarding, etc.).

    If that doesn't work (sorry for skipping specifics / [ultra] details on some
    of the foregoing), most probable, equipment incompatibility ( / too or few
    configurability).... Some vendors hardware, set-ups / configurations, work
    poorly or not at all together, where some other (combinations) work
    immediately and / or excellently straight out of the box.

    Don't forget line impedance (as for or if available with your ATA) (i.e.
    match your telephone - UK setting?).

    Hope that helps. One simpler potential tip for you is, request people to
    advise examples of known simple or good hardware (and / or combinations), or
    look at (the same /) guidance on subject related user communications (feeds)
    (usergroups, etc.).


    Best wishes,




    News Reader
    News Reader, May 23, 2011
    #25
  6. Blu

    News Reader Guest

    "News Reader" <> wrote in message
    news:irec9g$edj$...
    >
    > "Blu" <> wrote in message
    > news:R6Wyp.56$2...
    >>
    >> I have a Patton micro ATA.
    >>
    >> The configuration looks correct to the untrained eye, it says it is up
    >> and running, shows my correct a/c number as the user name, its set to
    >> sip.voipfone.net as suggested by their support with the right port
    >> number, and it correctly tells me the number of messages waiting.
    >>
    >> It makes outgoing calls fine.
    >>
    >> However the phone connected to it doesn't ring when a call comes in, I've
    >> tried a number of different phones, both cordless and corded but it makes
    >> no difference.
    >>
    >> Any suggestions of things to try please
    >>
    >> Blu.
    >>
    >> Router is Linksys WRT54G

    >
    >
    > Hi,
    >
    >
    > A few thoughts. Some





    < SNIP >




    > communications (feeds) (usergroups, etc.).
    >
    >
    > Best wishes,
    >
    >
    >
    >
    > News Reader
    >
    >
    >



    Hi,


    If you might want some more particular help on the port forwarding (router
    type) issues. You could try the link (or the post itself [ - lol - keenness
    : - ) ]) in my previous post (below - start half way down the page - where
    the indentation marks end [ the " > " marks / indicators]):

    http://groups.google.com/group/uk.telecom.voip/msg/e63abab66a95eaa4?hl=en

    or

    news:i1gdu1$12oo$


    Best wishes,




    News Reader
    News Reader, May 23, 2011
    #26
  7. Blu

    Blu Guest

    On 23/05/2011 20:24, News Reader wrote:
    > "Blu"<> wrote in message news:R6Wyp.56$2...
    >>
    >> I have a Patton micro ATA.
    >>
    >> The configuration looks correct to the untrained eye, it says it is up and
    >> running, shows my correct a/c number as the user name, its set to
    >> sip.voipfone.net as suggested by their support with the right port number,
    >> and it correctly tells me the number of messages waiting.
    >>
    >> It makes outgoing calls fine.
    >>
    >> However the phone connected to it doesn't ring when a call comes in, I've
    >> tried a number of different phones, both cordless and corded but it makes
    >> no difference.
    >>
    >> Any suggestions of things to try please
    >>
    >> Blu.
    >>
    >> Router is Linksys WRT54G

    >
    >
    > Hi,
    >
    >
    > A few thoughts. Some commonalities which may be useful too.
    >
    > 1) Factory Reset - A complete factory reset (should be a button on the
    > device) would be recommended or at least a good idea. The device may have
    > conflicting settings or acquired a hangover cross-setting or corruption.
    >
    > 2) Router / SIP Systemics - Their are commonalities across
    > implementations (or some might [perhaps] [overly] generously say
    > mis-implementations) in or of routers and SIP devices / software (and as
    > well, say more sensibly, "alternate" or "simple" products / services
    > [devices, software, etc.]). Typically these manifest very loosely,
    > briefly and total novice (style) as:
    >
    > - Routers: hang-ups or ("loose"[!]) implementations - impacting or
    > affecting, port forwarding, SIP assistance / handling protocols or packages
    > (e.g. ALGs - Application Layer Gateways), DMZ functionality, trigger -
    > detect - latch - release on or with NAT (as an example), etc.
    >
    > - SIP devices / software: partial or varying interpretation
    > implementations (and as / similar to router entries [above]) - impacting or
    > affecting, configuration (differing terms or use of terms or missing terms,
    > lack of options [or an option], etc.), one way audio / no incoming call
    > detect (firewall handling / traversal issues, NAT / router, etc.),
    > flexibility (much as or resultant to previous - e.g. some functions or
    > features not working / partly implemented or unavailable or only available
    > to specific configurations, devices [or much more infrequently and usually
    > only special case scenarios - only {available} to devices or configurations
    > with special or specific "additional" equipment, options, etc. {e.g. " super
    > call waiting PLUS " by " XYZ Manufacturing " and only available on their
    > devices, systems and configurations, etc., etc.]).
    >
    > - Generic - Much as the previous (ones) - corruption / data [/]
    > stack issues, config issues or limitations (or exceptionally additions /
    > extras), implementation issues or limitations, fade (losing config or
    > environment / parameter variables over the medium term) ([can be]
    > independent of the device or its function / role / duty, etc.).
    >
    > 3) Service Provider(s) - Your ISP (internet service provider), your VSP
    > (voice service provider ? ), etc. One or more of these may have issues,
    > configuration problems or limitations (additions), etc., service
    > restrictions / incompatibilites, etc., etc.
    >
    >
    > Hence:
    >
    > - consider a factory reset of your device(s), and a careful slow
    > ("manual" - if you are up to it) configuration ("re-configuration") (perhaps
    > write down any settings you need before commencing - as long as you are sure
    > they are not corruption / cross- settings, etc. - e.g. "known corrects" such
    > as perhaps your ISP username, etc. [ - again, if you need it, and bearing in
    > mind that you should have the originals or the originals for these
    > somewhere, and should be known or know them to cross-reference against to be
    > sure what you are storing is the original or correct version and not corrupt
    > or other, etc.])
    >
    > - evaluate your service provider(s) - I would particularly focus on your
    > ISP here (potentially) - e.g. some block VoIP or other ports, some implement
    > ("multi-layer") NAT(s) (which can render a network partially or totally
    > unnavigable).
    >
    > - SIP devices / software - some of these have varying configuration
    > approaches and complexity. Hence, approaching the task from a perhaps
    > "easier" direction, a proportion will assume certain settings where others
    > will either not permit them or not have / work at all where yet others will
    > require a very complete or full technical (or complex) configuration.
    >
    > - router ( / "perhaps as distinct from routing") - common approaches
    > for users facing issues, include, DMZ (try this - temporarily / testing only
    > [with appropriate, matching, destinations / equipment - i.e. a device or
    > computer that can face, cope with or is configured for "direct" internet
    > access - i.e. one ready for a testing or full access challenging
    > environment]), port forwarding (often not too many ports or ranges or - ...
    > gulp, router, strange / mis-behaviour), (SIP) ALGs (or equivalent) try on
    > and off, enhanced or extra features off (UPnP, etc.) (or on?), always good /
    > standard advice, or good idea or sensible to use wired connections for
    > development or testing (new equipment, new gear, etc.), ("forced") (basic)
    > configuration for WAN side (xDSL settings, etc. - but that is getting a bit
    > carried away / advanced). (lol - ... [advanced / joke ?] don't forget
    > matching settings in your SIP client).
    >
    > (Don't forget, the foregoing may require trying / "switching" independently,
    > sometimes including or requiring a factory reset between [but that is
    > getting a bit keen / carried away - sorry, "detailed pages" "here", e.g.
    > sometimes you can second guess combinations that are likely to require such
    > drasticness]), or to be used in combination).
    >
    > So, to avoid getting carried away, perhaps for yourself or your own
    > situation / environment, try: factory reset, (basic) check of your service
    > provider(s) ( ~ ISP) (mobile broadband environments are particularly prone
    > to not pass [some or all] VoIP traffic, ULTRA bargain or special ISP
    > packages / services, etc.) and simple check of your ATA (VoIP configuration)
    > (key aspects, again perhaps if you are keen [enough], try combinations /
    > variations - SIP port ranges, SIP server / hostnames, network / firewall -
    > traversal or identification, configuration features or tools), simple check
    > of your (home) router (key aspects, again consider combos / variations, DMZ,
    > SIP help / special settings [if any], special or compatibility settings,
    > port forwarding, etc.).
    >
    > If that doesn't work (sorry for skipping specifics / [ultra] details on some
    > of the foregoing), most probable, equipment incompatibility ( / too or few
    > configurability).... Some vendors hardware, set-ups / configurations, work
    > poorly or not at all together, where some other (combinations) work
    > immediately and / or excellently straight out of the box.
    >
    > Don't forget line impedance (as for or if available with your ATA) (i.e.
    > match your telephone - UK setting?).
    >
    > Hope that helps. One simpler potential tip for you is, request people to
    > advise examples of known simple or good hardware (and / or combinations), or
    > look at (the same /) guidance on subject related user communications (feeds)
    > (usergroups, etc.).
    >
    >
    > Best wishes,
    >
    >
    >
    >
    > News Reader
    >
    >
    >

    Thanks for this. I'm no stranger to doing factory default resets and I
    know the information required for both Voipfone and Sipgate now.

    I got a new Windows 7 Sony Vaio which decided it would connect to all my
    neighbours wireless networks but didn't want to play with mine. A
    default factory reset of my router was one of the things that solved
    that problem.

    I'll do a reset and manual reconfigure tomorrow if I have the time.

    Blu
    Blu, May 23, 2011
    #27
    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. buffy

    ATA 133 HD on a ATA 100 Board

    buffy, Dec 23, 2003, in forum: Computer Support
    Replies:
    2
    Views:
    587
    mhicaoidh
    Dec 23, 2003
  2. Prinxce of Darkxness

    Ultra ATA/100 HDD on a Ultra ATA/33 motherboard

    Prinxce of Darkxness, Jan 6, 2004, in forum: Computer Support
    Replies:
    3
    Views:
    2,106
  3. Robert11
    Replies:
    1
    Views:
    581
  4. Andy Lord

    Voipfone on Cisco ATA 186

    Andy Lord, Jun 12, 2005, in forum: UK VOIP
    Replies:
    0
    Views:
    1,021
    Andy Lord
    Jun 12, 2005
  5. Blu
    Replies:
    8
    Views:
    1,230
    News Reader
    Jun 20, 2011
Loading...

Share This Page