Displaying 20 results from an estimated 1000 matches similar to: "Problem with Operator Unallocated number message"
2007 Jan 25
1
IAX softphone fails through PRI trunks with Hangup
I've a call center using IAX softphones provided by a third party.
We've observed problems where the IAX phones seem unable to use our PRI
trunks. A sample anonymized call is provided below with the PRI debug
calls embedded. Any thoughts,
comments or suggestions would be welcome. In anonymizing it, I preseved
the format
and number of digits sent.
-- Accepting AUTHENTICATED
2005 Sep 22
0
priindication passthru TE410P EuroISDN?
Hi all,
I have to asterisk-1.0.9BRIstuffed-0.2.0n boxes each equipped with a TE410P.
Box A is connected with pri1 to the PSTN.
Box B is connected with pri1 (cpe) to the Box A at pri2 (net).
Now I want Box B to dial out to the PSTN tunneled thru Box A
and have it get all ISDN indications in case of call failure, eg.
unallocated destination number etc.
But currently Box B always gets only
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.
2010 Apr 13
0
PRI Gurus ONLY - Too complex of an issue - SOLVED
Told you it was too complex of an issue :-) I figured to do this in
zapata.conf and all is fine now:
transfer=no
That was the magic two letter which was sending a request for RLT feature on
the line. Set transfer to "no" and all worries gone.
Thanks for the input everyone.
-Bruce
On Mon, Apr 12, 2010 at 10:10 PM, bruce bruce <bruceb444 at gmail.com> wrote:
> Futher check
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
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:
2005 Jul 11
0
zaphfc / incoming call - error 6
Hi Folks,
I've Asterisk Bristuffed up and running behind an Auerswald Commander
Basic ISDN PBX on the internal ISDN Bus (BRI/PTMP). The HFC Card works
marvelleous for outgoing calls (as the parallely installed avm fritzcard
with chan_capi does), but when I'm trying to call in, I get a short ring
signal and then the connection is terminated. This does not happen with
chan_capi and
2006 Nov 21
1
Call to disconnected number on PRI just rings
Hi,
Running Asterisk 1.2.12.1 when dialing a known disconnected number the calls
just rings and rings. We never get the "The number you are trying to reach...".
If we dial the same number from an Asterisk 1.0.11 server again over PRI, we get
the message on the 1st ring.
Here is the PRI debug of such a call that just rings and rings. Any ideas?
PRI debug sur CPL:
-- Executing
2004 Dec 04
0
PRI debug output - still not working :(
Hi all,
I'm debugging a PRI problem, i can see the calling
number but i get a busy all the time. From the output
below, I guess asterisk hangs up immediately. Can
anyone point out what the problem is?
Thanks in advance.
*CLI> < Protocol Discriminator: Q.931 (8) len=32
< Call Ref: len= 2 (reference 4865/0x1301)
(Originator)
< Message type: SETUP (5)
< [04 03 80 90 a3]
<
2006 Feb 06
0
Called party number
I have trouble getting ${EXTEN} or ${DID} when receiving incoming call from
TE110P in Japan.
Does anyone have idea how to fix this?
Is this because TE110P does not support INS1500 as switchtype?
pri debug does not show "Called Number".
< Protocol Discriminator: Q.931 (8) len=32
< Call Ref: len= 2 (reference 68/0x44) (Originator)
< Message type: SETUP (5)
< [04 03 80 90 a2]
2007 Jul 12
0
No subject
handled.
So....what do I do?
Thanks,
MD
=1===================================================
!! Invalid Protocol Profile field 0x11
-- Accepting call from '2004000' to '111' on channel 0/23, span 1
-- Executing NoOp("Zap/23-1", "Incoming call from Meridian1") in new
stack
-- Executing NoOp("Zap/23-1", " From number: 2004000|
2006 Jan 14
1
Problem with just one number!
I have this setup:
(PSTN E1 PRI) -- Asterisk -- (crosscable) -- Alcatel PBX --- analog phones
and a few of VoIP phones directly connected to Asterisk.
Calling a number (just one!) - an automatic responder (IVR) -
from VoIP phones works, from analog phones doesn't work:
NOANSWER after a few seconds.
I'm using no 'r' in dial options (this caused a problem with an IVR some
time
2007 Jul 12
0
No subject
picture. I know the firmware on the Nortel is old, so I'm guessing that
libpri is sending something that the Nortel does not know how to handle.
Is there a way to dumb down what libpri sends? From everything I've read
PRI is an evolving standard - and older devices may struggle with newer
extensions/developments. (This might be very handy for users trying to talk
to old pbx's.)
Is
2008 Jun 25
0
unable to send a fax to a given FAX number
Hi all,
I have some problem to send a FAX to a given number. I use asterisk 1.2.18, on
a openSUSE 10.2, i586 host.
The FAX is sent out via an ISDN PRI interface, I'm in Germany, and the
destination FAX devices are in Germany too, but in different areas, so I have
to use a city prefix.
I did set the pri device in debug mode, below are two calls, to two different
FAX numbers, the first is
2004 Sep 03
0
busy signalling on PRI doesn't work...
hi all
Attachd is a PRI DEBUG dumped while dialling out to a busy number among
with zap(ata|tel).conf. asterisk did not flag busy, and I got a busy
indicator going meeeeep-meep-meeeeep-meep-meeeeep-meep (never heard
this before)
Can someone help me out here?
thanks
roy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zapata.conf
Type:
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 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
2005 May 21
0
PRI doesn't call cellphones
Hi all,
I am using a Sangoma with two PRI's. As far as land phones, the calls are
fine but it refuses all cellphone calls:
My configuration in Zaptel is
span=1,0,0,ccs,hdb3,crc4
bchan=1-15
dchan=16
bchan=17-31
span=2,0,0,ccs,hdb3,crc4
bchan=32-46
dchan=47
bchan=48-61
and on Zapata.conf:
[channels]
language=it
context=default
switchtype=national
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
2004 Sep 05
0
DTMF with HFC-S, not supported yet?
Salve,
I'm somewhat stuck on how to get DTMF working with my setup
and googling didn't yield anything similar.
My setup consists of one CAPI-capable board (AVM Fritz!DSL)
connected to a BRI (T-ISDN), one HFC-S board running in NT-mode
connected to an internal S0 bus with some ISDN devices (DECT
stations, TA) and, of course, some ethernet interfaces. ISDN
standard used is Euro-ISDN.