similar to: Numbering Plan and Siemens EWSD

Displaying 20 results from an estimated 900 matches similar to: "Numbering Plan and Siemens EWSD"

2007 Mar 20
2
Problem with "AT&T Maintenance" protocol in PRI connection, no B+D channels available
Hi guys, We are experiencing a problem with a T1 PRI connection. After trying a number of variations in the configuration files, the behavior is always the same: no B channels come up and the D channel doesn't appear to be working well. We can see there are AT&T Maintenance messages being exchanged by asterisk and the provider, CONNECT and CONNECT ACKNOWLEDGE, but that doesn't
2011 Jun 07
2
PRI issue its BUSY
Hi all, I just configures my PRI and incoming calls are working fine but outside calling giving error PRI is BUSY :( any idea ? I have same setup on other box and that boxes works perfect. -- DAHDI/i1/6463279153-2 is proceeding passing it to SIP/7328-00000002 -- DAHDI/i1/6463279153-2 is making progress passing it to SIP/7328-00000002 -- DAHDI/i1/6463279153-2 is busy -- Hungup
2004 Dec 19
1
BRI Error with zaphfc
Hi I have a small ISDN PABX , (BRI) at home - Siemens Gigaset 4175 which has cordless DECT extensions. I have set up asterisk on FC3 with two HFC cards and I am using the latest bristuff. I am trying to use * between my ISDN line and my PABX. One card is in TE mode and can receive and make calls OK. I can make and receive external calls to a SIP phone. I cannot get the other card to talk to my
2005 Jan 09
5
Help in E1-T1 encoding
I have an asterisk with a TE110P configured as T1 which is behind a PSTN gateway. This gateway has an E1 to PSTN and a T1 to asterisk. This T1 is configured as Network and * as CPE. Every call I receive in E1 gateway is directly switched to asterisk using T1. Remember E1 is alaw. Both E1 and T1 have Natural Microsystems boards with a very simple software. When I call to E1 asterisk signalling
2014 Aug 01
1
Connecting Asterisk and BT Versatility PBX via NT BRI port
Hi All, I've a BT Versatility PBX that I want to connect to my asterisk 11.9.0 box via BRI port in NT mode but actually I wasn't able to get it working. I've another standalone PBX, it's a Panasonic model, which works fine connected to the same port. The BT connected to a UK BT BRI line works quite fine after roughly a minute once connected. The PBX can be seen at
2003 Aug 18
8
PRI Question
I managed to get Asterisk working with my PBX using T1, now I am moving on to trying to make PRI work. I have my zaptel.conf and zapata.conf configured as follows: Zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us Zapata.conf: [channels] transfer=yes immediate=yes callprogress=yes language=en context=default switchtype=national signalling=pri_net group=1
2004 Oct 07
1
T100P Pri Audio
I've been working on an asterisk box at work for a few weeks now, things were finally starting to sail smoothly until I hit this head scratcher this morning. It's a rather intricate problem, so bear with me. Heres the scenario. What works: If I call from my sip phone -> sip phone everythings ok If I call from sip phone -> external pots number ok as well If I map one of our
2007 Jun 06
3
1.4 Zaptel/Sangoma Issues on CentOS
Any ideas? Sangoma support is closed for the evening. I have the latest Sangoma drivers and Asterisk 1.4 everything installed. When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" repeated over and over. The B channels never come up. There are no errors in any of the logs, zttool, or the wanpipe tools. Intense pri debug output: < Unnumbered frame: < SAPI:
2010 Jun 21
1
DAHDI: Inbound BRI call, DDI not presented
Hello- I have a system with one D410P and one B200P (both OpenVox). All is well with the D410P, inbound and outbound, and I can initiate calls on the B200P BRI span, but there may be something wrong with my inbound BRI setup: there is no indication of an inbound call when I dial in to it from the PSTN. When I run "pri intense debug" and make a call to the BRI span, I can see a
2005 Mar 10
7
Panasonic TDA200 E1 -> E100P negotiation issues
Hi, I hope someone can help me with this.... Asterisk 1.0.6 Zaptel 1.0.6 Libpri 1.0.6, 1 Digium E100P card installed Panasonic TDA200 firmware v2.0.6 E1 Card Firmware 1.0.2 System is located in Australia, so as technologies go, I believe it is twist on the euro standard for the E1 signalling. Here is the situation. The TDA E1 card is set in cross over mode and I am using a functional
2003 Nov 21
3
PRI problems
I've got a couple of PRIs coming in from a SUMA 4 switch with some 800 numbers routed through it. When the calls come in, I get the following message on the console and the call never makes it through: (800 number is fake) Extension '8005551212' in context 'nonauthenticated' from '232102749585' does not exist. Rejecting the call on span 4, channel 1. I do have the
2016 Mar 25
2
PRI error "ROSE REJECT"
PRI debug of the entire call would be great, also, switchtype would be awesome as well. Thanks! Matthew Fredrickson On Thu, Mar 24, 2016 at 4:07 PM, Carlos Rojas <crt.rojas at gmail.com> wrote: > Hi > > Did you activate the pri debug on the cli asterisk? > > On Thu, Mar 24, 2016 at 12:59 PM, Carlos Chavez <cursor at telecomabmex.com> > wrote: >> >>
2003 Aug 25
1
I4L CallerID not working
Can anyone work out why my callerid doesn't work on my isdn4Linux with asterisk (or without asterisk for that matter)... This used to work fine, and I am quite confident that the telco is sending callerid information (because they always do on all ISDN lines standard, only extra cost on POTS lines). This is the information from dmesg, whether asterisk is running or not: isdn_net: Incoming
2005 Jun 08
1
EuroISDN Italy - quadbri - zaptel.conf - what settings work ?
Hi, I'm pulling my hair out, cause cannot connect to EuroISDN BRI in Italy with octobri card from Beronet. I use bristuff and have following zaptel.conf... # # This file is parsed by the Zaptel Configurator, ztcfg # # # First come the span definitions, in the format # span=<span num>,<timing>,<line build out (LBO)>,<framing>,<coding>[,yellow] # # The timing
2009 May 22
2
BT ISDN-30 Pri getting 'stuck' on outgoing calls.
I've having problems with a BT 2 span ISDN-30/Digium TE205P asterisk setup with outgoing calls not completing and requiring an Asterisk reset to 'unstick' span 1. Sorry this is a bit long but I'm completely out of my depth :-( This system has been in use for some while and I recently upgraded it to asterisk 1.4.24, zaptel 1.4.11 and libpri 1.4.9. I didn't change
2010 Sep 29
1
Weird Behavior with DAHDI
Hello, I'm experiencing some weird problems on my server: - 1) The following messages are filling up my logs: [Sep 29 08:24:59] WARNING[7077]: chan_dahdi.c:2789 pri_find_dchan: No D-channels available! Using Primary channel 140 as D-channel anyway! [Sep 29 08:24:59] WARNING[7078]: chan_dahdi.c:2789 pri_find_dchan: No D-channels available! Using Primary channel 171 as D-channel anyway!
2010 Dec 16
1
PTMP BRI Unable to receive TEI from network in state 2(Assign awaiting TEI) - Asterisk 1.6.2, Latest DAHDI, LibPRI
Hi all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16
2004 Mar 18
4
zaphfc problem
Hi, I have a partial working installation with zaphfc. Incoming call : For incoming call, seems work fine. But the sound is very bad with bounce short crashing sound. Same sound with echo cancel off or on. SDA work fine. Another problem, it's seems that's zaphfc don't reset correctly the line. I have one of my D channel how was busy even after stop communication. Outgoing call :
2007 Oct 31
4
PRI over T1 calls dropping, cause 100
I have a T1 link from asterisk 1.2.23 (also tried with 1.4.13) to a Meridian Option 61C. Calls either way drop with error "Channel 0/23, span 1 got hangup, cause 100". Can anyone offer insight into the cause and solution/workaround? (I tried upgrading to Ast 1.4.13, and upgrading matching zaptel & libpri, put the problem is identical). For testing, I tried a call from the
2006 Mar 11
1
FW: I need to set NO CRC4 on zaptel.conf?
Hi all, Can somebody help me out, to get the call going through to my provider? I connected my A104D Sangoma card to E1/isdn and each I tried to make call I get the errors below. My protocol analyzer can see only setup info and release complete. WIRELESS2*CLI> set debug 9 Core debug was 0 and is now 9 WIRELESS2*CLI> pri intense debug span 1 Enabled EXTENSIVE debugging on span 1 T203