Sure sounds like a veiled threat to me. Post something they don't like and find your support ticket ignored or possibly your account closed? Oh well guess I won't be getting any support from livevoip anytime soon:) Straight from the network status page on their website... "If you are working a trouble ticket with LiveVoip support and start posting to mailing lists or newsgroups you are just wasting your time. LiveVoip LLC will not respond to such postings which in many cases are done to push support teams. If anything it will slow your ticket or cause the case to be closed. Our techs work hard for you! They are not going to take abuse in any form. Posting to these lists is done by some as a way of trying to obtain faster support or vent frustrations. LiveVoip has a Zero interest in these actions and will respond per our Terms & Conditions if required. Let our people help you. That is what they get paid for. Are they busy? Of course. Do they work long hours? Duh. Treat them nice and Say Thanks. You will get further by being part of solutions, not part of the problems. "
snacktime wrote:> Sure sounds like a veiled threat to me.Veiled? Looks pretty overt to me. Why do these folks always think they can treat their customers like XXXX, when this is a market that really does have competition? They're not the incumbents, for God's sake, who get to do whatever they want. Thanks for the useful warning. . . B.> Post something they don't > like and find your support ticket ignored or possibly your account > closed? Oh well guess I won't be getting any support from livevoip > anytime soon:) > > > Straight from the network status page on their website... > > "If you are working a trouble ticket with LiveVoip support and start > posting to mailing lists or newsgroups you are just wasting your time. > LiveVoip LLC will not respond to such postings which in many cases are > done to push support teams. If anything it will slow your ticket or > cause the case to be closed. Our techs work hard for you! They are not > going to take abuse in any form. Posting to these lists is done by > some as a way of trying to obtain faster support or vent frustrations. > LiveVoip has a Zero interest in these actions and will respond per our > Terms & Conditions if required. Let our people help you. That is what > they get paid for. Are they busy? Of course. Do they work long hours? > Duh. Treat them nice and Say Thanks. You will get further by being > part of solutions, not part of the problems. "
Unbelieavable, and utterly disgraceful. Anyone found responsible for establishing such a policy would quickly find their ass on the street in any organization that understands the first thing about customer service. One doesn't build or "protect" a business by threatening and bullying one's customers. If one is worried about the "bad impression" that complainers are giving about the operation, figure out WHY they are driven to such extremes and DO SOMETHING ABOUT IT. It isn't rocket surgery. The principles of running an effective customer service organization are well known and readily available to anyone. The mind boggles...> -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > snacktime > Sent: Sunday, April 17, 2005 2:38 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: [Asterisk-Users] Unbelievable... > > > Sure sounds like a veiled threat to me. Post something they > don't like and find your support ticket ignored or possibly > your account > closed? Oh well guess I won't be getting any support from livevoip > anytime soon:) > > > Straight from the network status page on their website... > > "If you are working a trouble ticket with LiveVoip support > and start posting to mailing lists or newsgroups you are just > wasting your time. LiveVoip LLC will not respond to such > postings which in many cases are done to push support teams. > If anything it will slow your ticket or cause the case to be > closed. Our techs work hard for you! They are not going to > take abuse in any form. Posting to these lists is done by > some as a way of trying to obtain faster support or vent > frustrations. LiveVoip has a Zero interest in these actions > and will respond per our Terms & Conditions if required. Let > our people help you. That is what they get paid for. Are they > busy? Of course. Do they work long hours? Duh. Treat them > nice and Say Thanks. You will get further by being part of > solutions, not part of the problems. "-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.15 - Release Date: 04/16/2005
Gregorio Toscano
2005-Apr-18 09:37 UTC
[Asterisk-Users] Unable to specify channel 1: No such device
Hi, I did not find any useful information to configure a Wildcard
TDM400P with a FXO card. I've tried everithing, I tried configure it
using the cvs and the information from digium page, I tried to
configure it using
debian packages, I tried to configure with kernels 2.4.30 and 2.6.11, I even
switched the mother board (I tried 3 motherboards).
I tanks in advace any help you could give me.
Best Regards,
Gregorio Toscano
gtoscano@gmail.com
The erros are:
Apr 15 16:08:37 WARNING[1468]: chan_zap.c:850 zt_open: Unable to
specify channel 1: No such device
Apr 15 16:08:37 ERROR[1468]: chan_zap.c:6458 mkintf: Unable to open
channel 1: No such device
here = 0, tmp->channel = 1, channel = 1
Apr 15 16:08:37 ERROR[1468]: chan_zap.c:9558 setup_zap: Unable to
register channel '1'
My configuration files are:
lsmod
Module Size Used by Not tainted
wctdm 97248 0 (unused)
zaptel 214784 0 [wctdm]
dmesg (final):
Module 0: Not installed
Module 1: Not installed
Module 2: Not installed
Module 3: Installed -- AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)
najay:/etc# cat zaptel.conf
loadzone = us
defaultzone = us
fxs_ks=1
najay:/etc/asterisk# cat zapata.conf
[channels]
signalling=fxo_ks
echocancel=yes ; You can set this to 32, 64, or 128, tweak to your needs.
echocancelwhenbridged=yes
echotraining=400 ; Asterisk trains to the beginning of the call,
number is in milliseconds
callerid=asreceived
group=1
context=default ; Points to the default context of your extensions.conf
channel = 1 ; Again X is the number of FXO modules you have
najay:/etc/asterisk# cat voicemail.conf
[general]
format=wav
[default]
8500 => 1234,Gummer,gtoscano@gmail.com
[root at fred asterisk]#cat extensions.conf
[default]
exten => 2999,1,VoicemailMain(${CALLERIDNUM})
exten => 0.,1,Dial(Zap/g1/${EXTEN}/20,t)
exten => s,1,Wait(1)
exten => s,2,Dial,Zap/g1 ; Dials the first available channel in group 1
exten => s,3,Voicemail,u9000
exten => s,4,Hangup
najay:/proc# cat interrupts
CPU0
0: 362024 XT-PIC timer
1: 6987 XT-PIC keyboard
2: 0 XT-PIC cascade
10: 2792513 XT-PIC wctdm
11: 10280 XT-PIC via82cxxx, eth0
12: 3653 XT-PIC PS/2 Mouse
14: 16860 XT-PIC ide0
NMI: 0
ERR: 0