1899VoIP this morning

Can't log in to 1899VoIP this morning using ATA-486.

Tried sip.1899.com and iax.1899.com which both worked yesterday.

Does this confirm that they have pulled the plug on us non softphone
users.

I presume that their softphone must send some other information so that
they know when it's being used.

DF

David Floyd

Thus spaketh David Floyd:
> Can't log in to 1899VoIP this morning using ATA-486.
>
> Tried sip.1899.com and iax.1899.com which both worked yesterday.
>
> Does this confirm that they have pulled the plug on us non softphone
> users.
>
> I presume that their softphone must send some other information so
> that they know when it's being used.
>
> DF

Working here with Firefly and x-lite. Not have hardware so can't comment
there.

David Floyd <> wrote:
> Can't log in to 1899VoIP this morning using ATA-486.

It's logged in:

madras*CLI> iax2 show registry
Host Username Perceived Refresh State
213.61.187.156:4569 1899015278 217.169.21.20:4569 60 Registered

> Tried sip.1899.com and iax.1899.com which both worked yesterday.

I made a call over it yesterday evening, and it did work, although the
call quality was appalling and I eventually had to give up and use the
landline instead.

I've just tried another call now, and it still worked, even though it
gave a 1p/min charge indication for an 0800 call...

--
When in doubt, make a fool of yourself. There is a microscopically thin line
between being brilliantly creative and acting like the most gigantic idiot on
earth. So what the hell, leap.
- Cynthia Heimel

In message of Fri, 20 May 2005, Peter Corlett writes
>David Floyd <> wrote:
>> Can't log in to 1899VoIP this morning using ATA-486.
>
>It's logged in:
>
>madras*CLI> iax2 show registry
>Host Username Perceived Refresh State
>213.61.187.156:4569 1899015278 217.169.21.20:4569 60 Registered
>

No idea what your talking about here. Nothing like what's in my ATA-486

DF
>

In message of Fri, 20 May 2005, David Floyd writes
>In message of Fri, 20 May 2005, Peter Corlett writes
>>David Floyd <> wrote:
>>> Can't log in to 1899VoIP this morning using ATA-486.
>>
>>It's logged in:
>>
>>madras*CLI> iax2 show registry
>>Host Username Perceived Refresh State
>>213.61.187.156:4569 1899015278 217.169.21.20:4569 60 Registered
>>
>
>No idea what your talking about here. Nothing like what's in my ATA-486
>
>DF
>>
>

It's dawned on me that you might be talking about the 1899 softphone, if
so what does madras*CLI mean

DF

David Floyd <> wrote:
[...]
>>> madras*CLI> iax2 show registry
>>> Host Username Perceived Refresh State
>>> 213.61.187.156:4569 1899015278 217.169.21.20:4569 60 Registered

> It's dawned on me that you might be talking about the 1899
> softphone,

Nope, it's actually Asterisk. "iax2 show registry" shows all my
(attempted) IAX registrations, 213.61.187.156 is iax.1899.com, and
"Registered" means the registration was successful.

I can't run the 1899 softphone on my SPA-2000

> if so what does madras*CLI mean

It's the Asterisk prompt and the server's hostname is madras.

--
PGP key ID E85DC776 - finger for full key

Please contribute to the beer fund and a tidier house:
http://search.ebay.co.uk/_W0QQfgtpZ1...Z25QQsassZpndc

On Fri, 20 May 2005 10:20:59 +0100, David Floyd <>
wrote:

>Can't log in to 1899VoIP this morning using ATA-486.
>
>Tried sip.1899.com and iax.1899.com which both worked yesterday.
>
>Does this confirm that they have pulled the plug on us non softphone
>users.
>
>I presume that their softphone must send some other information so that
>they know when it's being used.
>
>DF

My Sipura is incapable of accessing 1899 VOIP. Until a couple of days
ago it worked fine, and I haven't changed the settings.

Is it just me or are others in the same boat? It says it's registered,
but when u try to call PSTN it just goes beep, beep, beep.

Thus spaketh :
> On Fri, 20 May 2005 10:20:59 +0100, David Floyd <>
> wrote:
>
>> Can't log in to 1899VoIP this morning using ATA-486.
>>
>> Tried sip.1899.com and iax.1899.com which both worked yesterday.
>>
>> Does this confirm that they have pulled the plug on us non softphone
>> users.
>>
>> I presume that their softphone must send some other information so
>> that they know when it's being used.
>>
>> DF
>
> My Sipura is incapable of accessing 1899 VOIP. Until a couple of days
> ago it worked fine, and I haven't changed the settings.
>
> Is it just me or are others in the same boat? It says it's registered,
> but when u try to call PSTN it just goes beep, beep, beep.


Sounds like the classic blocked number that has been plaguing many.

Register another number with 1899 and then program that new number into the
Sipura.

On Sun, 22 May 2005 21:08:09 +0100, "{{{{{Welcome}}}}}"
<> wrote:

>Thus spaketh :
>> On Fri, 20 May 2005 10:20:59 +0100, David Floyd <>
>> wrote:
>>
>>> Can't log in to 1899VoIP this morning using ATA-486.
>>>
>>> Tried sip.1899.com and iax.1899.com which both worked yesterday.
>>>
>>> Does this confirm that they have pulled the plug on us non softphone
>>> users.
>>>
>>> I presume that their softphone must send some other information so
>>> that they know when it's being used.
>>>
>>> DF
>>
>> My Sipura is incapable of accessing 1899 VOIP. Until a couple of days
>> ago it worked fine, and I haven't changed the settings.
>>
>> Is it just me or are others in the same boat? It says it's registered,
>> but when u try to call PSTN it just goes beep, beep, beep.
>
>
>Sounds like the classic blocked number that has been plaguing many.
>
>Register another number with 1899 and then program that new number into the
>Sipura.
>

Why would they block that number?

Thus spaketh :
> On Sun, 22 May 2005 21:08:09 +0100, "{{{{{Welcome}}}}}"
> <> wrote:
>
>> Thus spaketh :
>>> On Fri, 20 May 2005 10:20:59 +0100, David Floyd <>
>>> wrote:
>>>
>>>> Can't log in to 1899VoIP this morning using ATA-486.
>>>>
>>>> Tried sip.1899.com and iax.1899.com which both worked yesterday.
>>>>
>>>> Does this confirm that they have pulled the plug on us non
>>>> softphone users.
>>>>
>>>> I presume that their softphone must send some other information so
>>>> that they know when it's being used.
>>>>
>>>> DF
>>>
>>> My Sipura is incapable of accessing 1899 VOIP. Until a couple of
>>> days ago it worked fine, and I haven't changed the settings.
>>>
>>> Is it just me or are others in the same boat? It says it's
>>> registered, but when u try to call PSTN it just goes beep, beep,
>>> beep.
>>
>>
>> Sounds like the classic blocked number that has been plaguing many.
>>
>> Register another number with 1899 and then program that new number
>> into the Sipura.
>>
>
> Why would they block that number?

Have no idea, for some reason numbers have been blocked, my landline number
has been blocked on their VoIP service, but 1899 still works from the
landline, other numbers have got blocked also, but numbers I have added since
they had blocked many numbers a week or two back are still working fine.