similar to: Cannot do international dial with E1 in Spain

Displaying 20 results from an estimated 4000 matches similar to: "Cannot do international dial with E1 in Spain"

2010 Apr 10
2
PRI - Native ZAP bridge fails - Is this my patch?
Hi Guys, I am calling out 416-999-1111 on Channel 1 of PRI and then calling 416-999-2222 on Channel 2 of PRI. When the two channels are going to be ZAP native bridged, both channels hangup and CLI show PRI cause (16). Asterisk Verbose *(Channel 1 already connected to party)*: -- Requested transfer capability: 0x00 - SPEECH -- Called g0/4169992222 -- Zap/2-1 is proceeding passing it
2010 Apr 12
2
PRI Gurus ONLY - Too complex of an issue
Hi Guys, Full PRI installed in Canada with Sangoma A101DE and Asterisk 1.4.21.2, LibPRI 1.4.10. Placing a call into PRI and then transfering that call out to another number. Problem is that the call rings out but the moment the other party pickups both legs of the call are disconnected give Cause code 16.
2006 Feb 10
1
QSIG error -- can somebody explain?
Hi all, I tried to connect the bristuffed(0.3.0-PRE-1i) * to an Alcatel PBX via BRI (zaphfc) and Q.SIG. The Alcatel PBX is connected to the outside world and should forward our calls to the telco. This setup works correctly as far as I use euroisdn as the switchtype. The first problem was that it is only possible to run the * side in CPE-mode -- I wanted NET. Anyway, I configured * this way:
2004 May 09
1
No outbound calls at a PRI possible
Hello all, the scenario: Carrier ----S2M------ * -----S2M------Siemens | | SIP Clients and many other features With much help from the list, the PRI links are without alarms and inbound calls are working fine (from both: Carrier and Siemens). But I am not able to dial wether outbound nor to the Siemens PBX. I allways get the message: == Everyone is busy
2006 Jun 15
2
Bearer capabilities on PRI
Hey all, I am running a Asterisk 1.2.9.1 with Sangoma A101 card, newest firmware, configured with a help from Sangoma Tech Support, running fine. It is connected to a PRI circuit split from Cisco MC 3810, which in turn is connected to a Converged T from CTC Communications. While Asterisk works fine and I can call in/out on my BV account, I am only able to dial in through CTC. I have spent
2006 Oct 31
2
Bridging Video Calls using Zap
Hi! For demonstration purposes I try to bridge an incoming video call from a 3G mobile handset to another 3G mobile handset using asterisk as "switch". On the incoming call leg I see all expected bearer capabilities (Digital, 64k Transparent, G.7xx 384k video) but on the outgoing call leg the bearer capability G.7xx 384k video get lost and therefore the call is dropped from the mobile
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
2004 Jun 28
1
Protocol Error (6) using Zaphfc
Hi! Has anybody seen anything like this using zaphfc? On outgoing calls (via isdn) , the line gets hung-up as soon as the called party answers. As seen below i get some protocol error (6) - but i'm not sure if this is related to the "hang-up" which apparently comes a little earlier?! Incomming calls on the isdn (zaphfc) interface is working just fine (P.S. what about the
2006 Mar 22
3
PRI DMS100 -> Nortel Meridian Option 81
Hello all, I have Asterisk 1.2.1 and a TE110P connected to a Nortel Meridian Option 81C system. The PRI line is currently setup as DMS100. Here are the relevant lines from zaptel.conf and zapata.conf: zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone = us zapata.conf: [channels] language=en context=from-internal musiconhold=default switchtype=dms100
2006 Apr 08
1
ANI on a PRI
Is there a setting somewhere in * to define whether I am receiving callerID or true ANI? Global Crossing claims they are sending ANI but I dont think so. My understanding of ANI is that it is always sent, regardless if callerID is blocked. If I dial *67 and my DID, I get "Presentation: Presentation prohibited of network provided number" and no number. Before I call GC on Monday
2006 Dec 02
3
Problem in Poland
Hello All, I'm having problems connecting Asterisk to Telco in Poland (using E1). The telco guys are saying that the RING message is missing. How can I make Asterisk to send the RING message? Does anyone have any samples of zaptel and zapata for Poland? Best Regards, Alex ____________________________________________________________________________________ Do you Yahoo!? Everyone is
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: >> >>
2006 Apr 29
2
problame with outbound calls on pri
Hi. recently I have been trying to setup a PRI on asterisk. Inbound calls are working just fine but I am not able to make outbound calls. Does anyone know what I need to change to make outbound calls work? Right now the PRI is instantly hanging up on the outbound calls. I have included full debug info as well as config files. /etc/zaptel.conf span=1,1,1,esf,b8zs bchan=1-23 dchan=24
2006 Jan 16
2
Problem with calls starting from a legacy PBX
Hi, I have this setup: E1 PRI PSTN -- Asterisk -- Alcatel PBX - analog phones Can someone tell me what's wrong with this call initiating from an analog phone connected to Alcatel PBX? It dies with NOANSWER but all works if I call other destination numbers. Dialplan is a simple Dial(zap/g1/0984465691) statement. At the end you'll find also zapata.conf.
2004 Apr 23
1
Busy error
Hi, When have a incoming call from E1 to a extension FXS, and this extension is busy, the incoming call recive ring tone, and it is wrong. What can I do? Thanks in advance Pedro Here is the trace: asterisk-1*CLI> < Protocol Discriminator: Q.931 (8) len=41 < Call Ref: len= 2 (reference 66/0x42) (Originator) < Message type: SETUP (5) < Sending Complete (len= 4) < Bearer
2005 Jun 25
1
isdn channels busy
We've got a EuroISDN (32 channels) with a TE405p, running cvs head as of 5 days ago. In the past couple of days, we've hit a scenario where incoming calls to the * pbx from the PSTN are being marked as busy, but outgoing calls work just fine. When we reboot *, the problem goes away. Has anyone else had this ? I've attached a PRI debug below. I've changed the phone numbers (x
2006 Apr 10
1
ANI and DNIS Seperation on a PRI (Telephony Numbering Plan (E.164/E.163) (1) '*4105556654*8005550215*' ])
OK I am going to do it again. Global Crossing is now sending ANI but it is not in the format I expected. Any one know of a way to get this data into two seperate variables? The first number is ANI and the second is DNIS so it is "*tendigits*tendigits* on one line like below. < Called Number (len=26) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan
2008 Feb 19
1
A problem about digium TE220B
hello everyone, I have a trixbox server with an E1 card(not digium).It connects to an AVAYA pbx use E1. It works fine.But when i change the E1 card to digium TE220B,there is a problem. When sip extension A(on trixbox) call PSTN extension B(on avaya),A must wait longtime before B start to ring.From the log I find there are two times call. I don't know why the first request be rejected
2005 Oct 08
1
Outgoing call: hangup after answer
Hi, When we make an outgoing call on ISDN (zaphfc) with overlap dialing we get immidiate hangup after answer. But when we place a full number before dialing everything is ok. Any help appriciated!! Thanks here is info with debug: == Primary D-Channel on span 1 up -- Executing Dial("SIP/200-164c", "zap/g1/|100|tc") in new stack -- Making new call for cr 192 --
2006 Jun 22
2
PRI Issue - Calls being rejected with unacceptable channel
Hey all. We have a DS3 circuit with GBLX split off into 7 systems with a 4 port sangoma card (A104D) in the first 2 systems, and digium T410P cards in the other 5. GBLX numbers their spans from 0 to 3 instead of 1-4 and we have a NFAS configuration with the d-channel on chan 96. All of our systems are running 1.0.7 for stability reasons (and no good time for maintaince, the entire platform