similar to: Pri-Debug-Log / Is Early Media supported by provider?

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

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|

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

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>

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

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

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

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

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

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:

Hello, I seem to be having an issue with the configuration of my PRI on a new asterisk server I've created to replace an old install that I have. The card is Digium Wildcard TE133. I continually get messages like "Primary D-Channel on span 1 down", rather irregularly: [2013-07-29 17:31:39] VERBOSE[3621] sig_pri.c: == Primary D-Channel on span 1 up [2013-07-29 17:31:39]

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

Dear All, I am trying to setup an ISDN line from local telco on a digium card. The problem I am facing is that I am not getting any caller id from the telco. They say that they have enabled caller id. Please help me out. My zapata.conf -------------------------------------------------------------------------------------------------------------------- [trunkgroups] [channels]

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

Hello everyone, I am facing a strange problem on my asterisk box (using isdn lines with pri card installed on it). Normal incoming/outgoing calls are working perfectly fine. When a user dial a wrong/out-of-service number they don't hear back any such message like "The number is wrong or user is switched off" in some cases, and it's just a silence for the user. Now while

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

I have a problem calling a certain number from our PRI line. Calling the number from a separate PSTN phone works fine. The remote number seems to have some funny call redivert setup, when you call it, it answers immediately, makes some kind of beep and then starts to ring. Our PRI is in the UK from Telewest/NTL/Virgin Media and most outgoing calls work without a problem. The server is

Hello, I have a problem, and I'm looking for you help. When I dial certain number my calls are getting dropped. I initiate the call, I hear IVR, then I am being transfered to operator, and then suddenly I get ISDN DISCONNECT message. I had this type of problem some time ago, and I thought it was a problem on the other end. But now this is a second time it occurred and I want an expert to

Hi all, I am running to the following problem, when using the below dialplan to receive fax, everything works perfect till this line exten => receive,n,ReceiveFAX(${FAXFILE}): and then the following line cannot be executed, it's like asterisk can't go back to dialplan and continue, the good news is when i check what is received in my fax folder i find that the file is a valid one (not

Hi, Starting in Asterisk 1.8.0, Asterisk supports connected line updates. This is fantastic for SIP. How can I prevent them from being sent to a PRI channel? I'm having problems when a call is answered by an internal SIP extension, then transferred (blind or attended) to another internal SIP extension. One of my PRI providers can't handle the ROSE_ETSI_EctInform APDU and drops the