[Blink] Gray Account Names
ag at ag-projects.com
Fri Jan 4 15:58:47 CET 2013
The reason can be found only in the SIP trace, in the response (or lack thereof) from the SIP server for the REGISTER message sent by Blink.
On Jan 4, 2013, at 3:38 PM, Olav Seyfarth wrote:
> I have a similar problem: last year Blink was working fine but after the holiday
> (the laptop was roaming to other networks during that time) id doesn't anymore
> (accounts gray). I have 1 online account (across SOHO router) and 2 local
> accounts (against that SOHO router). All three worked no longer.
> The Router is a AVM Fritz!Box 7390 which also functions as local DNS proxy. It
> advertises itself as "fritz.box" so I used <sipuser>@fritz.box for the creation
> of the account. This did work in December. Not so today.
> After the holiday, when I was investigating the non-functioning of Blink, I did
> a "ipconfig -flushdns". No luck. I tried to change different settings, no luck.
> Picking up the hint to not just try to change an existing Blink account
> deleting but recreating it, the account creation wizard no longer accepted
> <sipuser>@fritz.box (just did not react on hitting the "Add" button) but only
> <sipuser>@<local_ip_of_that_box> (didn't need any additional settings): works,
> and does reenable my remote account(!) but not my other "@fritz.box" account.
> Maybe it's a IPv4/IPv6 issue? nslookup on the command line resolves "fritz.box"
> but gives IPv6 first. Does Blink cache any DNS entries itself? I'm asking
> because during holidays I used a network that also has a local "fritz.box" but
> different IPs.
> Blink mailing list
> Blink at lists.ag-projects.com
More information about the Blink