On Wed, 15 Oct 2008, Sebastian wrote:
> Rick Green wrote:
>> I defined one of my extensions, using the same extension #
>> and secret as
>> before. Then I went into the sipura ATA config, and changed
>> only the IP
>> address of the line1 'proxy' config, but it failed to register.
>> I don't see any message on the alt-f9 console telling me
>> it even saw a
>> registration attempt, much less a reject reason. Where should I look?
>
> This may be stating the obvious but did you reboot the ATA? I presume it
> registered with the old asterisk server OK? When you say 'it failed to
> register', I presume you mean that it remains unregistered, rather than
> receiving an error in ATA telling you that registration failed?
>
I didn't power cycle the ATA afterupdating the line1 config. The web gui
told me it was restarting the ATA.
The info page on the ATA (Sipura SPA-2002) told me 'not registered'
immediately after the config change, but when I refresh the page a minute
later, it says 'failed', and next attempt in 13s.
I've tried deleting the extension definition and re-creating it several
times. I'm sure I haven't fat-fingered the secret, or left the caps-lock
on.
Now I'm encountering an even more serious problem. I can't contact the
*NOW box at all. From the console, `ifconfig` returns nothing! Executing
`/etc/init.d/network start` brings it back online, but WTF! Looking back
at /var/log/messages, I see a few at 10:24 this morning from avahi-daemon,
beginning with one that says 'Withdrawing address record 192.168.156.101
from eth0'. A googling I will go....
--
Rick Green
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisknow mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisknow
