similar to: ISDN PRI Caller ID problem

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

I there, I have some trouble to do working caller id name for outgoing calls on the PRI we just installed. Caller id name work on incoming calls only. Caller id number work on incoming and outgoing calls. The provider, Goup Telecom, said that's in what i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces

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

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

I have a user who's system crashes on pri hangup request. Tried 1.4.19.1 and 1.4.20 as well as the latest libpri no change Progress is as follows...... < Supervisory frame: < SAPI: 00 C/R: 0 EA: 0 < TEI: 000 EA: 1 < Zero: 0 S: 0 01: 1 [ RR (receive ready) ] < N(R): 025 P/F: 1 < 0 bytes of data -- ACKing all packets from 24 to (but not including) 25 -- Since

Hello, I am trying to diagnose an intermittent error when a call comes in over our PRI lines. The problem appears random, however I have feeling it has something to do with the call volume, as the frequency increases with more calls on the system. I am not an expert when it comes to reading the PRI Span Debug statements but here is a call that had a problem and I bolded, italicized, and

Hi All, In my dialplan and standard asterisk CLI logging i see that i am able to restrict the callerid when dialing out with asterisk. however, on the receiving phone, the callerid is still displayed. When i increment the logging of the pri with "pri set debug on span 1" on the CLI i also get the lower level debugging info from the pri.

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

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

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:

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

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

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

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 :

Hi I have recently upgraded my Asterisk system (from 1.2 to 1.4) and I have started to notice the following messages when I recieve a call on my Zap channel :- [Mar 11 09:20:17] WARNING[4294]: chan_zap.c:8851 zt_pri_error: 1 copying 5 bytes LLC I have a single PRI ISDN 30 link to a Siemens Realitis DX. Here is my zapata.conf :- [channels] echocancel=no echocancelwhenbridged=no rxgain=-5.0

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Hi,<br> <br> have any one sucessfully connected E100P to Cisco? I am

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

We fairly recently switched service providers for our 4 PRI circuits. Since that time, we started to notice some failed inbound calls. These calls terminate with an ISDN cause code 47 'resource unavailble'. Most of the time I see this error on the first or second channel on the second span in a trunk group (This is the providers trunk group for hunting, not an Asterisk trunk group). All

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: >> >>