similar to: QSIG-SIP overlap dialing and Asterisk (RFC4497)

Displaying 20 results from an estimated 5000 matches similar to: "QSIG-SIP overlap dialing and Asterisk (RFC4497)"

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|
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
2009 Jul 20
0
No subject
We use asterisk 1.6 with DAHDI and a PRI ISDN 30 line in the Netherlands. Can anyone help me sorting out this issue?? Thanks in advance! -- Executing [s at macro-transfer:25] NoOp("SIP/joostkuif-00000003", "gehe= im") in new stack -- Executing [s at macro-transfer:26] NoOp("SIP/joostkuif-00000003", "voor= de SET CALLERPRES() =3D
2018 Apr 05
2
Asterisk / PRI and Outbound Overlap Dialing
I am trying to setup Asterisk to act like a PBX connected via a PRI gateway to a voice netowrk where Asterisk is doing outbound overlap dialing for calls that terminate via that PRI. AFter researching through the archives and online dcocs, I thought I had everyting setup right, dialplan configured for '_X!' and the 'overlapdial=yes' in the chan_dahdi.conf file, but when I try and
2009 Oct 25
1
some issue with libpri cant go past 1.4.1
I have a working system with asterisk 1.4.26.2 libpri 1.4.1 and zaptel 1.4.12.1 With a digium TE205p. I am trying to update to libpri 1.4.10.2. When I do, incoming calls work but outgoing does not. When I do this I "rm /usr/lib/libpri*" then just install libpri-1.4.10.2 as normal. I then do a make clean in asterisk and make distclean ,then configure, make and make install. I do
2009 Jul 20
0
No subject
We use asterisk 1.6 with DAHDI and a PRI ISDN 30 line in the Netherlands. Can anyone help me sorting out this issue?? Thanks in advance! -- Executing [s at macro-transfer:25] NoOp("SIP/joostkuif-00000003", "gehe= im") in new stack -- Executing [s at macro-transfer:26] NoOp("SIP/joostkuif-00000003", "voor= de SET CALLERPRES() =3D
2011 Apr 21
0
Nationalprefix chan_dahdi option
Asterisk 1.8.4-rc2 (and 1.8.3) DAHDI Version: 2.4.1.2 libpri version: 1.4.12-beta3 We are having a problem with getting the nationalprefix option of chan_dahdi.conf to work. National calls do not have a "1" added to them when nationalprefix=1. The PRI debug shows the call coming in as a National Call, but the dialplan sees the call without a 1. chan_dahdi.conf: <snip>
2013 May 24
0
Pri-Debug-Log / Is Early Media supported by provider?
Hi, I tried to use Early Media: exten => 1,1,Playback(demo-thanks,noanswer) same => n,Hangup() But when calling my extension I do not hear the voicefile - I only hear the ring tone. In the Asterisk-Log I can see, that the voicefile is played. I got the same result when using "Progress()" in the first priority. I tried "pri set debug on span 1" and got the
2005 Sep 09
0
BRI debug, national ISDN speech call problem
hello, I have a Junghanns QuadBRI card in my asterisk server. I'm able to dial & connect to local numbers through the ZAP interfaces however when I try to dial national numbers with the according area code the connection fails, an intense BRI debug is shown below. The error being Ext: 1 Cause: Unallocated (unassigned) number (1), class = Normal Event (0) about half way through the
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.
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
2007 Nov 06
1
Telus (Alberta) PRI Caller ID NAME, Display IE, Facility ID
We are trying to send caller ID NAME information over a Telus PRI in Alberta. The PRI tech says that he sees the NAME information, and for calls over the same network, that NAME info should be reaching the receiving station, but it is not. The technician was stumped. I suspect there's something specific that I need to do to make it work, since many PBXs can do this. The switch is a
2005 Mar 18
0
ISDN phone Hold-Problem connected to QuadBRI/Zap
Folks, (sorry for overlong lines) I have recently configured one port on my QuadBRI card to work in NT mode with NET signalling configured so that I can use an ISDN telephone on it. I have set up a separate group in zapata.conf and can call the phone and place calls from it like a charm. No problems at all. Problems came up when trying to hold a call and get it back. I turned on "pri debug
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:
2009 Mar 19
1
PRI QSIG Asterisk - Legacy PBX
I have a PRI E1 link between Asterisk 1.4.24 and Alcatel-Lucent OmniPCX Enterprise R9.0. As EuroISDN it works fine. However, I need to move to QSIG because of a firmware upgrade on the Alcatel PBX which doesn't support EuroISDN (please don't ask why). Besides, I've read somewhere that 2 B Channel Transfers "should" work with * 1.4, the latest 1.4 libpri and QSIG. So this
2003 Jul 17
0
error "WARNING[28697]: File app_dial.c, Line 304 (wait_for_answer): Unable to forward voice"
I am trying to put a call on a E1 ISDN : The configuration are simple: zapata.conf : [channels] context=inbound switchtype=euroisdn signalling=pri_cpe usecallerid=yes hidecallerid=no callwaiting=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes ;echocancel=no echocancelwhenbridged=yes rxgain=0.0 txgain=0.0 ;immediate=yes immediate=no callerid => asreceived amaflags
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
2011 May 01
4
Odd error in libpri
I just updated libpri 1.4 on my system to the latest from that branch and my QSIG connection to an NEC SV8300 stopped working. The trace showing the problem is below: q931.c:5640 q931_connect: Call 7168 enters state 10 (Active). Hold state: Idle > DL-DATA request > Protocol Discriminator: Q.931 (8) len=21 > TEI=0 Call Ref: len= 2 (reference 7168/0x1C00) (Sent to originator) >
2004 Sep 06
0
Wildcard TE410P still making trouble
We are still having problems getting a Wildcard to work with a German E1 (PMX) interface. When starting asterisk it shows all B-channels starting up successfully (although our carrier told us only the first B-channel starts, if any at all). Incoming calls are not being signaled at all. (They seem to be intercepted by the carrier's switch, as no B-channel is up) Outgoing calls sometimes work,
2010 Jun 09
0
CID name in Facility message for Q.SIG
The latest libpri is supposed to handle this properly, but doesn't seem to. Here's the debug info. CALLERID(name) is set to empty. < Protocol Discriminator: Q.931 (8) len=66 < TEI=0 Call Ref: len= 2 (reference 256/0x100) (Sent from originator) < Message Type: SETUP (5) < [04 03 80 90 a2] < Bearer Capability (len= 5) [ Ext: 1 Coding-Std: 0 Info transfer capability: