Bug 4811 - Problem to Login with Live365 VIP account
: Problem to Login with Live365 VIP account
Status: RESOLVED WORKSFORME
Product: MySqueezebox.com
Classification: Unclassified
Component: Internet Radio
: unspecified
: Macintosh MacOS X 10.4
: P2 normal (vote)
: Future
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-07 12:09 UTC by tomer maoz
Modified: 2009-01-15 10:28 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
Reply from LIve365 support (4.67 KB, text/plain)
2007-03-07 12:12 UTC, tomer maoz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tomer maoz 2007-03-07 12:09:27 UTC
The customer enters his Live365 VIP account info in to the SqueezeNetwork account and save the changes.
When he tries to listen to music via the Squeezebox he will get the music with the commercials (like the free account).

When he enter the same VIP account in slimserver and then try to play music from the squeezebox the music will play without commercials.

The customer contact Live365 support for help and they reply with the massage that they are not sure what causing that and that his account look fine. (I attach the reply the customer got from Live365 support)

OS: MAC 10.4
Slimserver version 6.5.1   
Firmware version: 72
Ticket #:070206-002188

I reset the customer squeezenetwork account, no change
Comment 1 tomer maoz 2007-03-07 12:12:15 UTC
Created attachment 1831 [details]
Reply from LIve365 support
Comment 2 tomer maoz 2007-03-16 13:27:35 UTC
I got another customer with similar issue.
The customer can login with his VIP account to live365 and then listen without commercials from the Slimserver or the SqueezeNetwork but when he try to add a new favorite to is list the account will reset itself to the basic account and he will get the commercial again.

Comment 3 Blackketter Dean 2008-02-06 09:38:31 UTC
Will review the outstanding SN bugs after 7.0 ships.
Comment 4 James Richardson 2008-09-11 11:01:14 UTC
Andy: is this issue still valid? Should we close or re-target the bug
Comment 5 Andy Grundman 2008-09-11 11:04:56 UTC
Yeah let's close it.