Displaying 20 results from an estimated 6000 matches similar to: "Looking for input on which way to go with smallbusiness setup"
2006 Apr 27
1
Looking for input on which way to go with small business setup
Hey guys!
I'm the past week and a half, I have really learned a lot from the mailing
list and the wiki's posted online.
Now I have a question regarding different ways I can setup my asterisk
server for a small business with 12 extensions in the office. Cost is a
great concern, so I know cheap analog phones at the desks is what we are
looking at. My question is, should I go do a fractional
2005 May 09
0
SV: Re: Sangoma A102 cards testing FIXED
Hi again,
Well - I didn't see beta8a-2.3.3 in custom dir. Will try.
Also I tried to contact Sangoma - they are very fast to answer but main problem is time difference - it's 6 hours between Canada and Europe.
Br,
dmitry
Dmitry Zhukovski
System developer
ComX Networks A/S
Naverland 31, 2
DK-2600 Glostrup
Denmark
Phone: +45 70 25 74 74
Fax:???? +45 70 25 73 74
Web: www.comx.dk
2005 May 09
0
Re: Sangoma A102 cards testing FIXED
Hello,
Have you tried the wanpipe-beta8c-2.3.3.tgz release in the custom/2.3.3 dir
on their FTP site? Also, have you contacted Sangoma for support? They are
very responsive.
I am using wanpipe-beta8a-2.3.3.tgz and it's been working great on my A104
for a week now.
MATT---
-----Original Message-----
From: Dmitry Zhukovski [mailto:DZH@comx.dk]
Sent: Monday, May 09, 2005 5:20 AM
To: Asterisk
2010 Oct 01
2
No translator path exists for channel type DAHDI (native 76) to 256
Hello,
We are having issues with a NEW Sangoma A108D:
-- Executing [691918892 at pbx1:1] Dial("SIP/xtravoip200-009d24b0",
"DAHDI/g0/691918892|30|m") in new stack
[Oct 1 10:04:43] WARNING[14171]: channel.c:3170 ast_request: No translator
path exists for channel type DAHDI (native 76) to 256
[Oct 1 10:04:43] WARNING[14171]: app_dial.c:1237 dial_exec_full: Unable to
create
2007 Jul 26
1
Asterisk 1.2.23 and Sangoma a102 no incoming call detected
Hi,
after many issues we finally managed to make our system do outgoing
calls with perfect quality.
However I cannot detect *any* form of incoming call. when I use an
outside phone to call the E1 connected to the sangoma a102, I
instantly get a fast busy tone.
My /etc/zaptel.conf is:
loadzone=us
defaultzone=us
#Sangoma A102 port 1 [slot:1 bus:4 span: 1]
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
2007 Jul 26
1
Asterisk 1.2.23 and Sangoma a102 no incoming calldetected
Do you have any extension in default context of your extensions.conf
file to accept incoming calls ?
It must be something like;
exten => 12345678,1,Answer()
exten => 12345678,2,Playback(Welcome)
...
12345678 = The DID number you are calling to reach E1
Idris
-----Original Message-----
From: Erick Perez [mailto:eaperezh at gmail.com]
Sent: Thursday, July 26, 2007 7:03 AM
To:
2005 May 09
0
SV: Re: Sangoma A102 cards testing FIXED
Ok, I have tested with almost all versions both in 2.3.2--*-stable and 2.3.3-*-beta - I am getting same messages:
May 9 10:55:26 WARNING[3961]: chan_zap.c:1925 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16!
and same Down state
pb01*CLI> pri show span 1
Primary D-channel: 16
Status: Provisioned, Down, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
2007 Oct 26
1
Can't get sangoma A102D setup on asterisk
I have a new Sangoma A102 and I'm trying to get it running in asterisk. A
look through the dmesg log shows the card is detected and the various
channels created. However, when I start asterisk I get the error below.
Any ideas?
My zapata.conf is below.
Thanks,
MD
== Registered custom function SIPCHANINFO
== Registered custom function CHECKSIPDOMAIN
== Manager registered action
2007 Mar 20
1
modem passthru
Our setup is:
9.6k Modem <-analog-> Mitel SX-200 <-(pri)-> Asterisk <-(pri) -> Telco
The modem works fine with the Mitel directly connected to the Telco, but
once we add Asterisk in between connections start failing.
I suspect the issue is caused by the echo canceller, since I believe the
issue appear about the time we turned echo cancellation on (for the IAX
users). We
2007 Jan 03
2
Sangoma A102 w/ EC module gets intermittent echo /audio artifacts
I've replaced 2XTE110 with an A102 with echo cancellation specifically to
deal with echo problems. However, user feedback has indicated to me that on
some calls (not a lot, but some) the call is unusable, with audio
artifiacts, described by one user, as: "very bad phasing reverb & feedback
(from my rock & roll days)". This is quite intermittent, as in most cases,
the user
2007 Apr 23
1
Purchasing a Sangoma A102 - should I get the hw echo cancellation or not?
Shortly, I'll be purchasing a Sangoma A102. I'm wondering if I should
spring for the hardware echo cancellation circuit or not. Upon
initial implementation, the 2 T1 Ports will be used as a passthrough
as we slowly transition off of a legacy PBX. Eventually, we'll only
be using one of the ports, and will be providing VoIP service to a
bunch of SIP deskphones.
So - with that usage
2007 Jan 03
0
Sangoma A102 w/ EC module gets intermittent echo/audio artifacts
I think you are absolutely right. The audio I heard earlier sounds exactly
like a timing issue. So:
wanpipe1.conf:
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
wanpipe2.conf:
TE_CLOCK = MASTER
TE_REF_CLOCK = 1
zaptel.conf:
span=1,1,0,esf,b8zs
span=2,0,0,esf,b8zs
I'm going to make this change and reload at lunchtime, I'll document it and
post it to the list if it works.
2007 Jan 04
0
Sangoma A102 w/ EC module gets intermittent echo/audio artifacts <--followup and resolution
Followup on this issue, it appears that using a single PRI's clock as the
master clock avoids clock drift between the PRI's and we get no more
artifacts. So, :
wanpipe1.conf:
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
wanpipe2.conf:
TE_CLOCK = MASTER
TE_REF_CLOCK = 1
zaptel.conf:
span=1,1,0,esf,b8zs
span=2,0,0,esf,b8zs
-----Original Message-----
From: Michael L. Young
2007 Jan 09
2
Fax through Sangoma A102
Hello,
in our company we are trying to do this:
Fax <--> Traditional PBX <--> Asterisk <--> PSTN
In practice, we have put an Asterisk equipped with a Sangoma A102 (2 PRI
ports) between our PBX (Siemens HiCom) and the PSTN in order to have a VoIP
network along the traditional telephony network.
The problem is with the fax. We just want to send and receive faxes from/to
our fax
2006 Jan 25
1
Asterisk + Ericsson PBX
Hi all,
I've got an Asterisk box with 1 Sangoma A102 and 1 Ericsson PBX.
I need to use Asterisk as E1 line for the Ericsson PBX.
How do I have to connect them?
I'm trying to connect the Sangoma to the Ericsson, but RED alarms remain.
Any suggestions?
Thanks
--
.:FaberK:.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2006 Nov 27
1
Sangoma & Dell 750
Anyone using a Sangoma A102 with a Dell 750? We are looking at going this
route but needed some input. I really only need a Single T1 port, but this
server doesn't have a PCI-X port, which the A101 apparently requires?
Thoughts, Suggestions?
K
2006 Jun 16
1
sangoma card test
Is there any way of running a diagnostic on a Sangoma A102 card ? Our
lines have gone down and I want to avoid the usual BT "It must be your
equipment" line with technical proof.
At the moment I have a BLUE/RED alarm on zap show status
Julian.
2007 Aug 06
4
low-level dump for PRI dchan debugging
I've been going back and forth with my telco for several days, trying
different configurations to get a new PRI to come up. The bchannels
are all up and the T1 is not in alarm status. The dchannel refuses to
come up however. We've tried ni2, qsig, and now dms100 for the
switchtype. The telco tech I've been working with says that he's been
sending "reset all channels"
2005 Feb 13
3
Sangoma A102 cards testing
Does anyone have any experience ith configureing the sangoma A102 card for
testing using a e1 cross cable i've configured and installed the cards
properly even the lights on the card are green which proves that my cross
cable is properly built too. my problem is with asterisk which gives me these
errors
PRI got event: HDLC Abort (6)on Primary D-channel of span 1
PRI got event: HDLC Bad FCS
2007 Aug 01
5
pri "call by call" trunking?
I've been working with a telco for the past two days trying to get a
PRI span up and running. This is a small-ish telco and I get the
feeling they don't do this very often. Anyway, they specified a
pretty standard setup: ni2 switchtype, esf framing, b8zs coding, etc.
All of my b-channels are up, but we're having a heck of a time
getting the d-channel to come up. He finds out that