> Thanks Shon,
>
> Should we remove
> www.audiorealm.com
> 69.59.147.44
> 208.96.32.84
>
> Jim
>
>
> Shon Elliott wrote:
>> Just A followup to my own message for you guys,
>>
>> If Anyone on this list uses the AudioRealm Request Feature, please make sure 
>> you
>> have these IP addresses in your allowed list in SAM Broadcaster:
>>
>> 66.207.166.135
>> 66.207.166.140
>> 66.207.166.141
>> 66.207.166.142
>> 66.207.166.143
>> 66.207.166.144
>> 66.207.166.145
>>
>>
>>   
From [email protected]  Sat Dec 29 23:33:19 2007
From: [email protected] (James Henline)
Date: Sun Dec 30 00:10:15 2007
Subject: [General-discussion] requests error 703 
In-Reply-To: <[email protected]>
References: 
<[email protected]><003c01c84a4c$e855b4c0$6401a...@radioman>
      <bdaeecd3eba341a586575e3e6804c...@spacialceo>
        <[email protected]>
Message-ID: <01d001c84a9d$1baa5dd0$52ff19...@com>

Bill,
I am sure Bryan will respond in due time, but I wanted to let you know there
is already a users helping users forums available.
Http://spacialaudio.com/forums has been around for a very long time; it is
extremely active and is used on a daily basis.
All of us in support are required to participate in the forums so you can be
sure that any questions asked will be answered.

This discussion list is for discussions, it is not designed for support,
though sometimes we do help when there is a problem asked.

However if you have a problem and you are not receiving a quick enough
answer in here, please make sure to use the HelpDesk.

James Henline.
Help Desk Manager
Development Manager
Spacial Audio Solutions LLC.
972-739-6420 ext: 110
www.audiorealm.com
www.spacialnet.com
www.spacialaudio.com 

CONFIDENTIALITY NOTICE:  This email, including any attachments, contains
information from SpacialAudio Solutions LLC., which may be confidential or
privileged. The information is intended to be for the use of the individual
or entity named above. If you are not the intended recipient, be aware that
any disclosure, copying, distribution or use of the contents of this
information is prohibited. If you have received this email in error, please
notify the sender immediately by "reply to sender only" message and destroy
all electronic and hard copies of the communication, including attachments.






-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Bill Curd
Sent: Saturday, December 29, 2007 9:30 PM
To: 'Bryan Payne'; [email protected]
Subject: RE: [General-discussion] requests error 703 

Bryan;

Then why last Sunday were we not told about the outages either?
We stream a live church service and no one told us audio realm would be
down. On a Sunday that would most likely be hosting thousands of Christmas
messages. 

Also Bryan you emailed me personally about some stuff but once again I never
got a response. I love SAMB with no doubt but as I have said, seems the move
from Denver to Texas has created a shortage of activity on the list and
other areas. 

Wiki this is the 1st time I have ever heard about the Wiki. 
I'll speak for myself and not the others but If I am having troubles I don't
want to have to spend 15 or 30 mins. reading to find the answer. I mean,
when I need an answer I want someone to be on the list to answer it. I
believe that email lists are the most effective way to keep a customer base
informed about what is truly happening. 

I think I will start a "peers helping peers" list for internet radio after
the 1st of the year, I am about to install a Dual Quad core AMD system that
I plan to use for some side services, it will work great for a list also. 

BTW: there is a list of "Request Error Codes" in the help files of SAMB I
did want to give credit for the great help files you software has. 

Just my 2? 

Bill Curd
Hope Radio Online
www.hoperadio.us
270-589-1737


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Bryan Payne
Sent: Saturday, December 29, 2007 1:45 PM
To: [email protected]
Subject: Re: [General-discussion] requests error 703 

Now come on guys? This is getting totally unfair!

1st - Currently it's the holidays. Most all our team is away on vacation, 
etc.

2nd - Need I remind you all this is not a "Support" list. It's a Discussion 
list right?

Besides I know for a fact that we (including myself) always monitor and when

relevant generally reply to this discussion list, maybe not as timely as 
some of you might personally desire, but we do inevitably reply none the 
less.

I will admit the Ball was dropped recently regarding the IP change. We 
recently opened a new colo facility in Dallas and our Network admin found a 
window of opportunity to move the main Audiorealm web services to this new 
facility. However there was a failure to alert everyone of the move and the 
IP change that is associated with it. I promise that won't happen again!!

Finally, when there are support issues folks? The best recourse has and 
always will be to check the Help docs first and then if all fails, to open a

Trouble Ticket, or even take the time to try checking the very extensive and

vast Knowledge base as well as our online forums and now you can even use 
our new Wiki - www.spacialaudio.com/wiki

I will say that from now on and continuing through 2008, all the Spacial 
team including management will be much more vocal and will participate much 
more widely in all venues we host including this "Discussion" list. We have 
not forgotten nor forsaken you all and this Discussion list is an important 
avenue for specifically discussing trends, business and legal issues 
relevant to our industry and what the upcoming plans and or products 
releases from Spacial are, etc. You can also try checking our new blog - 
http://spacialaudio.blogspot.com

We will certainly try to address small tech issues and some configuration 
issues on this list but again , this is NOT a support list. So if your 
question is support related this would be one of the last venues we would 
monitor for that. Although most times one of you or another fellow Spacial 
client/software user will assist here, our support channels from Spacial's 
perspective are very to the point and clear!

Bryan Payne, CEO
Spacial Audio Solutions, LLC

[email protected]
www.spacialaudio.com
www.spacialnet.com
www.audiorealm.com


----- Original Message ----- 
From: "Michael Hughes" <[email protected]>
To: <[email protected]>; <[email protected]>
Sent: Saturday, December 29, 2007 12:59 PM
Subject: Re: [General-discussion] requests error 703


> It means that you need to add more IP addresses to your accepted request 
> list. I mentioned it earlier, but no one from Spacial responded 
> (surprising).
>
>
> ----- Original Message ----- 
> From: "Bill Curd" <[email protected]>
> To: <[email protected]>
> Sent: Saturday, December 29, 2007 9:40 AM
> Subject: [General-discussion] requests error 703
>
>
>> Can anybody tell me what a error 703 on the requests means?
>>
>>
>>
>> Bill Curd
>>
>> Hope Radio Online
>>
>>
>>
>> _______________________________________________
>> General-discussion mailing list
>> [email protected]
>> http://mailman.spacialaudio.com/mailman/listinfo/general-discussion
>>
>> TO unsubscribe to this list, simply send a blank email to
>> [email protected]
>>
>> with the subject
>> 'unsubscribe'
>
> _______________________________________________
> General-discussion mailing list
> [email protected]
> http://mailman.spacialaudio.com/mailman/listinfo/general-discussion
>
> TO unsubscribe to this list, simply send a blank email to
> [email protected]
>
> with the subject 'unsubscribe'
>
> 

_______________________________________________
General-discussion mailing list
[email protected]
http://mailman.spacialaudio.com/mailman/listinfo/general-discussion

TO unsubscribe to this list, simply send a blank email to
[email protected]

with the subject 
'unsubscribe'

_______________________________________________
General-discussion mailing list
[email protected]
http://mailman.spacialaudio.com/mailman/listinfo/general-discussion

TO unsubscribe to this list, simply send a blank email to
[email protected]

with the subject 
'unsubscribe'

Reply via email to